The flow
Starts it 2Logic 5Service 5
The steps in the order they run, from what starts it.
- 1When SMS ReceivedRelayion triggerStarts it
- 2When Slack Message ReceivedSlack triggerStarts it
- 3Set Slack Channel IDSetLogic
- 4Check If Threaded ReplyIfLogic
- 5Prepare Slack Message TextSetLogic
- 6Fetch Slack Thread MessagesHttp RequestService
- 7Post Message to SlackSlackService
- 8Extract Phone and Reply DetailsCodeLogic
- 9Relay SMS ReplyRelayionService
- 10If SMS Sent SuccessfullyIfLogic
- 11Post Success ReactionSlackService
- 12Post Failure ReactionSlackService
How it's built
- Starts on
- An event in a connected app
- Steps
- 12, with 2 branches
- 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. 12 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 12 steps before you point it at anything that matters.