The flow
Starts it 1Logic 6Service 8
The steps in the order they run, from what starts it.
- 1Slack TriggerSlack triggerStarts it
- 2Get Thread Messages1SlackService
- 3Format Conversation TextCodeLogic
- 4Gemini 2.0 Flash SummarizeHttp RequestService
- 5Check Summary SuccessIfLogic
- 6Gemini Image generation API call1Http RequestService
- 7Slack Text ErrorSlackService
- 8JS code Conversion 1CodeLogic
- 9Set Variable SetLogic
- 10JS code Conversion 65CodeLogic
- 11Slack getUploadURLExternal API call1Http RequestService
- 12Set SetLogic
- 13Convert to File1Convert To FileService
- 14Slack File Upload Binary1Http RequestService
- 15Slack API call completeUpload1Http RequestService
How it's built
- Starts on
- An event in a connected app
- Steps
- 15, with 1 branch
- Size
- Medium: a working afternoon
- Connects to
- Slack
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n account, plus your own Slack account. You connect your own accounts after importing it; none are included.
What starts it?
It starts on an event in a connected app.
Does it use AI?
No. Every step is fixed logic or a call to a service, so it does the same thing every time.
How long does it take to set up?
Plan an afternoon. 15 steps is enough that you should read each one before running it.
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.
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 15 steps before you point it at anything that matters.