Slack Workflow Builder or an AI agent: which recurring job goes where

Sort a recurring Slack job by where its data lives, not by how complex it sounds. A weekly list of unpaid invoices is a simple job, and Workflow Builder still cannot do it if your books are in QuickBooks or Xero, because Slack's connector list includes neither. A form with an approval and a few branches is a more complicated job, and it stays in Workflow Builder because the work happens inside Slack. Anything that needs the books or the CRM goes to an agent, and decisions about money, client wording and exceptions stay with a person.
- Workflow Builder takes jobs with a fixed shape: a form, a message, a choice between a few paths, or a post that starts on a schedule without anyone triggering it. You can build one from a template.
- An agent takes jobs that need to read data from a tool Workflow Builder cannot reach, or to put several records together before anyone looks.
- A person keeps decisions about money, wording to a client, and exceptions.
Why "simple versus hard" sorts the wrong way
The usual advice is Workflow Builder for simple tasks and an agent for hard ones. It does not tell a ten-person firm which of its own jobs is which, and it hides two facts that change the answer: what your Slack plan allows and which tools hold your data. The usual next moves are to stack separate workflows to fake branching, or to hire a coordinator to do the lookups by hand.
A guide from a vendor that sells AI agents says Workflow Builder does not branch and cannot pull data in from outside systems. The second claim holds for the tools named above. The first depends on your plan, as the next section shows.
What Workflow Builder can reach, plan by plan
Four facts from Slack's help center set the boundary. Check them against your own plan before you build anything.
- Plan. Workflow Builder is available on paid plans. By default, all Full Members can create workflows, and members and guests can use them.
- Branches. Branches need the new version of Business+, per Slack's page on adding a branch to a workflow. You can add up to 15 branches and nest up to 5 additional branches beneath a primary branch. Nesting branches below nested branches is not supported.
- Connectors. A connector step carries out an action in a third-party service. You authenticate your account with that service first, and some connectors need additional approval or configuration. The connector list includes Salesforce, Google Sheets, Google Mail, Zendesk, Intercom, Jira Cloud, Linear, Notion, Airtable and Box. It does not include HubSpot, Pipedrive, QuickBooks, Xero or Stripe.
- AI steps. Per Slack's page on using AI in workflows, AI steps are available on the new version of Business+ and Enterprise+, or on Pro, Business+ and Enterprise Grid for customers who still have the legacy Slack AI add-on. An AI answer step cannot be added to workflows in Salesforce channels or channels with external people, and an AI agent conversation step must be the last step in a workflow.
Two of these change the answer for most small firms. Branching is a plan question. If you are on Pro, the claim that Workflow Builder cannot branch is true for you, and your choice is to upgrade the Slack plan, stack workflows, or move the job. If you are on Business+, a flow that routes a request by the severity someone picks on a form is a Workflow Builder job, and it should stay there.
The connector gap is the usual reason a small firm outgrows the tool. If the numbers you need live in QuickBooks, Xero, HubSpot, Pipedrive or Stripe, no connector step on Slack's list reads them.
Price the branching question before you build a third workflow. At Slack's US list prices, Business+ costs $15 per user per month on annual billing against $7.25 for Pro, and $18 against $8.75 on monthly billing, so moving ten people up costs $77.50 or $92.50 more a month. That can be cheaper than maintaining a pile of stacked flows. It buys branches and AI steps, not connectors: QuickBooks, Xero, HubSpot and Pipedrive stay off the list, so the upgrade does not turn the invoice list into a Workflow Builder job.
The decision table
These are examples of the jobs a founder or operations generalist at a small Slack-first firm typically owns, not survey data. The "where" column assumes a paid Slack plan, QuickBooks or Xero for the books and HubSpot or Pipedrive for deals.
| Recurring job | Where it goes | Reason from the sources |
|---|---|---|
| Time-off or equipment request form that posts to one channel | Workflow Builder | Fixed shape, all inside Slack |
| Welcome message when someone joins a channel | Workflow Builder | A built-in trigger; no outside data |
| Monday scheduled post with fixed text | Workflow Builder | Scheduled workflows start automatically |
| Route a request by the severity picked on a form | Workflow Builder with a branch | Branches take form answers; needs the new Business+ |
| Weekly list of unpaid invoices from QuickBooks or Xero | Agent | Neither is on the connector list |
| Weekly list of deals with no activity this week from HubSpot or Pipedrive | Agent | Neither is on the connector list |
| Weekly row summary from a Google Sheet, Notion database or Airtable base | Either | All three are on the connector list; the agent also reads them with the asking person's own access |
| Payment reminder email to a late client | Agent drafts, person approves | A write to an outside party needs a human click |
| Approve a spend, grant an exception, decide what to tell a disputing client | Person | Judgment and accountability |
The "Either" row shows the tie-breaker. When your data is on both sides, keep the job in Workflow Builder, because a fixed job does not need a model and a scheduled post is easier to read in a workflow list than in an agent job.
What an agent adds, and how it behaves
The Kipwise agent works in a Slack thread. You mention it once, and plain replies in the thread continue the conversation. It uses your own access to the tools you connect, and its connection list includes QuickBooks, Xero, HubSpot, Pipedrive, Stripe, Gmail and Google Drive. It says which organisation or company it acted in. That covers the jobs missing from the connector list.
The recurring version works the same way, in plain language. You ask for a weekly Monday check once, approve it once, and it posts the result in the channel using your Slack timezone. A realistic made-up example for a twelve-person services firm:
In the thread, the owner writes: "Every Monday at 8, list unpaid invoices from QuickBooks with the aged receivables report, list HubSpot deals with no activity this week, and post one list here."
The agent shows an Approve card for the schedule. The owner presses it. On Monday the list appears in the channel. A later reply in the same thread says "only invoices over $2,000", and the next run follows it.
Aged receivables is one of the reports the agent can run in QuickBooks or Xero. For what to do with the late invoices it lists, see chasing overdue invoices from Slack.
Keep scheduled jobs read-only
Approve a scheduled agent job as a read-only report, so every write it later proposes arrives as a fresh Approve or Deny card instead of running on its own. This is a recommendation, built on how the product works: a scheduled task needs approval once, together with the list of changes it may make on its own, and any other change shows a fresh approval card. Only the person who asked can press the card, and it expires after 30 minutes. A list that posts every Monday is a report. A payment reminder email is a write. Keep them in different jobs, and nobody has to wonder what the report might send.
What can still go wrong after the sort
The data is missing or stale. An agent reads what the connected tool holds. If the books were not updated last week, the list is short, and the agent cannot know. Put the date of the last bank reconciliation in the thread, or have a person confirm the books before the Monday list is trusted. The guide to scheduling recurring agent jobs without silent failures goes deeper and separates a job that ran from a result someone received.
The access belongs to a person. The agent uses the asking person's own connections and permissions, the same as a live request from them. Decide who asks for a scheduled job, and write that name in the thread. If that person leaves or loses access to the books, the job stops reading them.
The Workflow Builder side has limits too. A flow that has to do something after an AI agent step cannot be built, because that step has to come last. Slack's own AI features are a third option for text-shaped jobs inside Slack, such as a summary of a channel, but they do not add the tools listed above.
A person still decides. Approving a bill, agreeing a payment plan or choosing what to say to an unhappy client stays with someone who can answer for it. If the approval is the hard part of a job, the human approval guide shows how to put it on a card without handing it away.
When a job should move
Use one rule per job, and write the decision where the team can see it, for example in the channel topic.
- Start every recurring job in Workflow Builder if the data it needs is inside Slack or on the connector list.
- Move it to an agent when it needs a tool that is not on the connector list, or when it has to combine records before anyone looks at them. Do not move it just because it feels important.
- Move it to a person when the result is a decision about money, an outside party or an exception. An agent can prepare the page. Someone presses the button.
- Move it back to Workflow Builder when, after a month, the agent job reads the same fixed thing every week and nobody changes the wording. A fixed job should have the simplest tool.
- Count your stacked workflows. If more than two differ only by one answer, check the plan before building a third.
This also answers the hiring question. A coordinator whose week is mostly lookups across QuickBooks and the CRM is doing agent work by hand. The judgment and the client relationship are the part worth paying for. The overdue invoice guide linked above walks through that split for one job.
Start with the job that costs the most Monday time
Open your Workflow Builder list today and write each recurring job next to the tool it needs. Mark every job whose tool is not on Slack's connector list. Pick the one that currently costs someone the most Monday time, and run it as a two-week pilot.
For the first two Mondays, open the aged receivables report in QuickBooks or Xero, and the deals view in HubSpot or Pipedrive, and check the agent's list against it line by line. You can ask the agent to list your jobs and what happened on previous runs, including failures, so check that every Monday has a run and a post. Ask for one write on purpose, such as a draft reminder, and confirm it waits for the Approve card instead of going out. If the owner corrects the same thing twice in the thread, change the instruction once and re-approve. On the Workflow Builder side, the workflow activity view lists in-progress and completed runs and any errors.
If that job is the unpaid-invoice or no-activity-deal list, the Kipwise agent can run it from one thread once QuickBooks or HubSpot is connected. The Kipwise price is $10 per user per month, or $108 per user per year, with a minimum of 3 users and a trial; see Kipwise pricing for the current trial terms. The QuickBooks agent page and the HubSpot agent page describe those connections. For the "what is it" side of Workflow Builder, with eight example workflows, use the Kipwise help center tutorial.



