Loading tutorials…
Loading tutorials…
Slack Workflow Builder is the no-code automation tool that's been in Slack since 2019, and most marketing teams have never opened it. Done well, it replaces a quarter of your meetings and most of your DMs to recurring people.
Who this is forMarketing leads on teams of 5+ who are tired of being the DM-routed bottleneck for every brief, request, or status update. Also useful for ops leads building intake systems.
What you'll need
Step 1
Slack → workspace name dropdown → Tools & settings → Workflow Builder. Workflows are sequences of steps triggered by an event (form submit, emoji react, schedule, channel join).
Workflow Builder lives in: Slack → click your workspace name (top-left) → Tools & settings → Workflow Builder. It is a separate window from the main Slack app.
Workflows have a trigger (what starts it) and steps (what happens). Common triggers: link click, form submit, emoji reaction, scheduled time, new channel member.
Common steps: send a message, send a form, post to a channel, add to a Slack List, send an email, run a custom code step (paid plans).
What it can do well: intake forms, recurring posts, simple approval flows, onboarding sequences, status-update collection.
What it cannot do: complex branching logic, multi-system orchestration (use Zapier or Make for that), anything requiring database lookups (unless you bolt on Slack Lists or external API).
Step 2
A form that funnels all marketing requests through one channel, with structured fields and an owner assigned. Replaces the "got a sec?" DM flood.
In Workflow Builder, click "Create Workflow" → name it "Marketing request intake."
Trigger: "From a link in Slack" (this gives you a shareable URL to put in your team intake doc, sidebar, or signature).
Step 1: Open a form. Fields: Request type (dropdown — design asset, blog post, email campaign, paid ad creative, other), Requestor (auto-filled), Deadline (date picker), Description (long text), Urgency (dropdown — this week / this month / quarter).
Step 2: Post to channel #ops-marketing-requests. Format the message with the form data and tag the marketing lead.
Step 3: Send a confirmation DM to the requestor: "Your request is logged. Expected response: 24-48 hours."
Publish the workflow. Pin the trigger link in #general and in your team Canvas.
Step 3
Replace the 30-min Monday standup with a Workflow Builder form that prompts each team member at 9am Monday and posts a thread in #team-marketing.
Create Workflow → name it 'Weekly marketing standup.'
Trigger: 'Scheduled' → every Monday at 9am.
Step 1: For each member of #team-marketing, send a DM with a form. Fields: 'Wins from last week,' 'Focus this week,' 'Blockers / asks.'
Step 2: Post a 'Standup thread for [date]' message in #team-marketing.
Step 3: When a member submits the form, post their response as a reply to the standup thread.
Save 30 min/week per person. For a 5-person team, that's 2.5 hours of recovered time/week.
Step 4
Triggered by an emoji reaction on a content draft post. Routes the draft to the approver, captures their decision, posts the outcome back.
Create Workflow → name it 'Content approval.'
Trigger: 'Emoji reaction' → :eyes-needed: (create a custom emoji for this) on any message in #content-drafts.
Step 1: Send a DM to the content approver (e.g., marketing director) with a link to the draft message and a form: 'Approve / Request changes / Reject' + comment field.
Step 2: Post the decision back as a thread reply on the original draft message.
Step 3: If approved, add the message to a Slack List 'Approved content — Q2 2026' (more on Lists in tutorial 6).
Cuts approval cycle time from days (chasing the director in DMs) to hours (one click on the emoji).
Step 5
Triggered when someone joins a channel. Auto-posts the channel norms, pinned resources, and a welcome from the channel owner.
Create Workflow → name it 'New member welcome — [channel name].'
Trigger: 'New member joins channel' → select the channel.
Step 1: Send a DM to the new member with: (a) channel purpose, (b) link to pinned Canvas, (c) "ping @owner with questions."
Step 2: (Optional) Post a 'Welcome @newmember!' message in the channel. Helps with social warmth on async-heavy teams.
Build this for every project channel and team channel. Onboarding effort drops to near-zero.
Step 6
Decide who can build workflows in your workspace, who can publish to the workspace (vs. their own channels), and who owns each published workflow.
Slack → workspace name → Settings & administration → Workspace settings → Permissions → Workflow Builder.
Default: any member can build workflows for channels they are in. Restrict if you have a chaos problem.
'Publish workflows to workspace' is a separate permission — only admins should have this. Workspace-published workflows show up in everyone's Workflow Builder shortcuts.
For each published workflow, document the owner in the workflow description. Owner is responsible for maintenance when the workflow breaks (e.g., a referenced channel is archived).
Step 7
In Workflow Builder, each workflow has analytics. Look at "completion rate" and "drop-off step" to find friction.
In Workflow Builder, click any workflow → Analytics tab. You see: total runs, completion rate, average completion time, drop-off by step.
Low completion rate (under 70%) usually means the form has too many fields or one of the fields is confusing.
Drop-off at step 3 of a 5-step form means step 3 is the friction point. Shorten or split.
Review workflow analytics monthly. Kill workflows with under 50% completion — they're noise.
Common mistakes
Building workflows that nobody discovered
What goes wrong: You spend 2 hours building a slick intake form, nobody knows it exists, requests still come via DM. Time wasted, frustration persists. Average cost of a built-and-ignored workflow is ~3 hours of dev time + ongoing DM chaos.
How to avoid: Workflow launch checklist: pin the trigger link in #general, mention it in #announcements, add to the team Canvas, mention it in the next standup. Discovery is half the work.
Forms that ask too much
What goes wrong: A 12-field intake form gets a 30% completion rate. People give up halfway, default back to DMs, the workflow becomes dead code. ~$200/mo of lost productivity on a 10-person team from unbuilt requests sitting in DMs.
How to avoid: Maximum 5 fields per form. Required fields only. Everything optional gets removed. If you need more info, ask in the follow-up thread.
Workflows with no owner
What goes wrong: A workflow references #project-x. Six months later, #project-x is archived. The workflow breaks silently — submitters see a generic error and stop using it. Nobody fixes it because nobody owns it.
How to avoid: Every published workflow names an owner in the description. Owner reviews quarterly. When a workflow breaks, the owner gets the alert.
Automating things that should not be automated
What goes wrong: You build a workflow for kickoff meetings, replacing a 30-min human conversation with a 12-field form. The form gets done; the alignment that the meeting created does not happen. Project drifts.
How to avoid: Automate intake (structured data collection). Do not automate alignment (human conversation about ambiguous tradeoffs). Use Workflow Builder to feed meetings, not replace them.
Letting workflows accumulate without auditing
What goes wrong: After 12 months you have 40 workflows, half are broken, nobody knows what runs on the workspace anymore. New hires get random DMs from workflows whose owner left the company. Brand chaos.
How to avoid: Quarterly workflow audit: open Workflow Builder, sort by last-run-date, archive any workflow not run in 60 days. Re-validate active workflows against current channel/owner structure.
Not testing the workflow before publishing
What goes wrong: You publish a workflow. The trigger fires on real submissions. The third step references a deleted channel. The workflow throws an error. Submitters see a broken experience and stop trusting workflows in general.
How to avoid: Every new workflow gets a 3-submission test by you and one other admin before publishing. Use a test channel (#workflow-testing) so you can iterate without polluting real channels.
Recap
Done — what's next
How to set up Slack integrations for a marketing stack
Read the next tutorial
Hand it off
Building workflows is the easy part. Designing the *right* workflows for your team's actual processes is harder. A growth-ops specialist on EverestX will audit your team's recurring DMs and meetings, map the highest-leverage workflows, and build them. Typically a 10-15 hour project at $14-16/hr — pays back in saved meeting time within a month.
See specialist rates
Yes. Workflow Builder is unavailable on the Free plan. Pro ($8.75/user/mo) includes unlimited workflows. Business+ adds custom code steps (run JavaScript or call APIs inside a workflow), which most marketing teams do not need.
No — workflows are scoped to a single workspace. For cross-workspace automation, use Slack Connect channels (which can have shared workflows on Enterprise Grid) or use Zapier as the cross-workspace bridge.
Workflow Builder is for Slack-internal flows: trigger something inside Slack, do something inside Slack. Zapier and Make are for cross-system flows: Slack → HubSpot → Google Sheets → email. Use both — they complement each other.
Yes — by default, workflow forms capture the submitter's name and you can use that variable in any subsequent step. You can also make the submission anonymous if needed (Workflow Builder → form settings).
The workflow throws an error on the next run. Submitters see a generic 'Workflow failed' message. The owner gets an email alert (if you set one up). Always audit workflows when archiving channels — Workflow Builder shows you which workflows reference each channel.
Slack
Slack has 2,600+ integrations in the App Directory. Most teams install 30, get hammered with notifications, and turn most of them off. This is the structured way to pick, install, and govern integrations.
Slack
Connecting your CRM, project management, and marketing automation to Slack is a 30-minute task. Connecting them in a way that does not drown your team in notifications is the actual work. Here is the right pattern for each integration.
Slack
Slack Canvas (launched 2023) and Slack Lists (launched 2024) closed two gaps that used to push teams out of Slack: structured docs and project tracking. Used well, they cut your tool count by 1-2 and your context-switching by 30%.