Automation library · Research and reporting

Summarize & reply to Slack channel messages with Claude

Started by another system calling it. It calls services over plain HTTP rather than through connectors. It hands the judgement calls to Claude. 8 steps: small enough to read in one sitting and change without fear.

SmallCalls a model: Claude

8 stepsSmall: readable in one sitting
0Branches: places the flow splits
0Loops or waits
0Services by connector: it calls them over plain HTTP

The flow

Starts it 1Model 2Logic 3Service 2

The steps in the order they run, from what starts it.

  1. 1Slash Command WebhookWebhookStarts it
  2. 2Anthropic Chat ModelLm Chat AnthropicModel
  3. 3Parse RequestCodeLogic
  4. 4Claude AI: SummarizeChain LlmModel
  5. 5Fetch Unread MessagesHttp RequestService
  6. 6Build Slack BlocksCodeLogic
  7. 7Prepare Prompt for ClaudeCodeLogic
  8. 8Post to Slack (Ephemeral)Http RequestService

How it's built

Starts on
Another system calling it
Steps
8
Size
Small: readable in one sitting
Connects to
Nothing by connector; it calls services over plain HTTP
Model
Claude

Questions

What does it need to run?

An n8n account, and a key for Claude. You connect your own accounts after importing it; none are included.

What starts it?

It starts on another system calling it.

Does it use AI?

Yes. It calls Claude. Model calls are billed by the provider, not by n8n.

How long does it take to set up?

Not long. At 8 steps it can be read in one sitting and changed without fear.

How do I import it?

Copy the workflow, open a new workflow in n8n and paste. The steps appear on the canvas, ready for your own accounts.

Before you run it

Nothing here has been tested by us. It is somebody's working automation, read and described from its own steps. Treat the connections it wants as a list of accounts it will touch, and read the 8 steps before you point it at anything that matters.