The flow
Starts it 1Logic 6Service 4
The steps in the order they run, from what starts it.
- 1New Message CatcherSlack triggerStarts it
- 2Set Extruct Table IDSetLogic
- 3Extract Company Name InputCodeLogic
- 4Company Name Exists?IfLogic
- 5Start Company EnrichmentHttp RequestService
- 6Hold for API ProcessingWaitLogic
- 7Check Enrichment StatusHttp RequestService
- 8Is Company Info Ready?IfLogic
- 9Get Company DataHttp RequestService
- 10Format Slack Company CardCodeLogic
- 11Send Company DetailsSlackService
How it's built
- Starts on
- An event in a connected app
- Steps
- 11, with 2 branches, 1 loop or waits
- 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. 11 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 11 steps before you point it at anything that matters.