What it is.
You start from a template or from scratch, then add steps: collect information in a form, send a message, wait for someone, post to a channel. It runs inside Slack, so nobody has to learn a new tool.
For marketing teams the obvious use is intake. Design requests, content requests, and campaign briefs all arrive as unstructured DMs, and a workflow turns them into a form with required fields.
Workflows can be started from a link, a channel shortcut, or an event, so you can put the entry point where people already ask.
What you get.
- A no-code form that collects required fields before anything reaches your team.
- Steps that post to channels, message people, and route based on answers.
- Templates to start from, so a first workflow takes minutes.
- Multiple ways to start it, including links and channel shortcuts.
- Requests arriving in one place with the same structure every time.
How to set it up.
Write down what you need to know before you can start a request, since those become the required fields.
Open Workflow Builder and start from a template if one matches, because editing is faster than building.
Add a form step and mark the fields you cannot work without as required.
Add a step that posts the submission to the channel where the work gets picked up.
Give the workflow a link or channel shortcut and put it where people currently DM you.
Test it as a requester and not as the builder, since that is the experience deciding adoption.
Use cases
Kill the ad hoc request
Put a form in Slack that collects the fields before the work reaches you.
Post to the right channel
Route each submission where the team already looks.
No-code intake
Build it inside Slack instead of adding another tool.
Best for
Design and content request intake
Unstructured requests cost a round trip every time. A form removes it.
Teams that live in Slack
Adoption is the hard part of intake, and this needs nobody to open a new tool.
Small ops teams
No code, no license to buy, and it works the same day.