Slack Workflow Builder vs BotFerry: the return trip
Workflow Builder comes with your Slack plan and can post a request into any channel you name. It has no idea which operator thread belongs to which original thread, so the answer stays where the operator typed it. That return leg is what you would be paying 9€ a month for.
Prices checked 28 July 2026. Written by the BotFerry team, so read the Workflow Builder column as a competitor's account of a competitor and follow the source link before you decide.
The short version
Use Workflow Builder for anything that travels one way. Request intake, announcements, a form that drops into #ops, an approval button. It costs nothing beyond Slack and no third party sees the message.
Use BotFerry when the requester needs the answer in the thread they asked in, under your app's name, without joining the channel your team works in. Workflow Builder cannot pair those two threads; that pairing is the product.
BotFerry vs Workflow Builder, side by side
Swipe the table sideways for the other columns.
| BotFerry This is us | Workflow Builder | |
|---|---|---|
| Billing unit | Flat monthly, whole workspace | Included in paid Slack plans |
| Entry price | 9€ / mo Starter: 3 bots, unlimited operators | No extra charge Part of Slack, no third-party vendor |
| Five operators, one month | 9€ / mo | No extra charge |
| Volume on the entry plan | 5,000 messages | Slack workspace limits apply |
| Operator replies land back in the original thread | Yes | No |
| Flat price, operators not billed per seat | Yes | Yes |
| You create the Slack app and hold the token | Yes | No |
| Relay vendor keeps no message content | Yes | Yes |
| Several separate front doors on one plan | Yes | Yes |
| One private thread per request | Yes | No |
| Attachments relay both directions | Yes | No |
| Internal notes the requester never sees | Yes | No |
| Ticket statuses, assignment, queues | No | No |
| SLA timers and escalation | No | No |
| Reporting and analytics | Activity log only | No |
| AI drafting or AI agents | No | No |
| Email or web chat intake | No | No |
| One-click install, no app to build | No | Yes |
Prices read 28 July 2026 from each vendor's own pricing page, linked below. BotFerry bills in euro, the others list dollars, so treat the two currencies as separate numbers rather than a converted total.
The volume row does not compare like with like. One BotFerry message is a single hop across the ferry, either a mention carried into your ops channel or a reply carried back. A ticket, conversation, or credit elsewhere covers a whole exchange. Seat prices in the rows above are directly comparable.
Sources: Workflow Builder
What Workflow Builder does well
A link trigger or a form kicks off a workflow, collects fields, and posts a tidy message into whichever channel you choose. No code, no vendor, no extra invoice, and the data never leaves Slack. For request intake that ends in a channel, this is the correct answer and BotFerry is the wrong one.
It also runs unattended. Nobody has to remember a syntax, and admins can see every workflow in one list. Whatever you can express as a form and a destination, express it there and keep the 9€.
Where the trip breaks
Someone asks a question in #madrid-office. The workflow copies it into #it-desk. An admin answers in #it-desk. Now what? The person who asked is not in #it-desk and should not be. Workflow Builder holds no record connecting the message it posted to the message it came from, so there is no destination to send the answer to.
Closing that gap yourself means storing a pair of Slack timestamps somewhere, listening for replies in the ops thread, and posting them back into the source thread with the source channel's ID. That is a webhook, a database and somewhere to run both. Which is buildable, and is roughly the shape of what we run.
The other absences follow from the same missing state. Files do not cross. There is no way to mark a reply as internal, so an operator's aside to a colleague either gets forwarded or the forwarding never happens. Nobody can tell whether a given message reached the other side, because there is nothing keeping score.
What 9€ a month adds
A mention of your app opens a fresh thread in your private operator channel, carrying who asked and which channel they asked in. Your team answers in that thread. The reply posts into the requester's original thread as your app, so the requester sees @Support answering rather than a named colleague. Files cross both directions. A reply beginning with // stays in the ops channel as an internal note, never relayed.
Then the parts you find out you needed in week three. Loop prevention, so your bot does not relay its own messages back into the channel it posted them in. Retries when Slack rate-limits you. A per-bot activity log recording, for each event, whether it relayed and the reason it did not, which is the difference between debugging a complaint and shrugging at one. Attachment failures post a warning into the thread rather than vanishing.
Starter runs three separate bots on one plan with 5,000 relayed messages a month, and every operator you add is free. Workflow Builder charges nothing at all, so the comparison is 9€ against a weekend of your own time plus whatever you host it on.
The honest recommendation
Write the workflow first. It takes twenty minutes and settles the question, because you will see within a week whether people expect an answer in their own thread. Plenty of intake never needs one: bug reports, holiday requests, anything you triage in a channel and follow up over DM.
When the follow-up keeps happening over DM, that is the return leg asking to exist. Come back then, with a 14-day trial and no card, and keep the workflow for everything one-directional.