One message a second per channel, and a bot message cannot start a Zap.
A Zapier plan sized to your task volume, and a free app slot on a free Slack plan
Messages, events only.
The Zapier Slack integration is the cheapest way to make Slack the place a stack announces itself, and the limits are all about rate and shape rather than about tiers. Nothing needs upgrading on either side: a free Slack plan works provided you have one of its ten app slots free, and Zapier's free plan covers 100 tasks a month. What catches teams is narrower than pricing. A bot's message cannot start a Zap, a slash command in an action posts as text instead of running, and Slack allows about one message a second per channel before it stops guaranteeing that anything is displayed at all.
Object by object, with the direction each one moves in. This is the table to read before the feature list, because a capability that only moves one way is a different product from the one you think you are buying.
| What | Direction | What that means in practice |
|---|---|---|
| Messages into a channel | One way, out | Public, private and direct, with editing, deleting and scheduling. Roughly one message per second per channel. |
| New messages as triggers | One way, in | Anywhere public, in a named channel, in a private channel, or matching a saved query. Not from bots or other integrations. |
| Reactions and mentions | One way, in | A new reaction or a mention can start a Zap, which is the lightest way to let a human approve something. |
| Channel administration | One way, out | Create public and private channels, set a topic, invite and remove users. More than most teams realise is available. |
| Files and users | One way, in | New file and new user triggers, useful for onboarding automation rather than for sales alerting. |
| Message history in bulk | Event only | Not here. Reading history at volume is a Slack API tier question, and an app distributed outside the Slack Marketplace is capped at one request a minute. |
Nothing in that table moves in both directions. Whichever system you treat as the source of record, the other one is downstream of it, and a correction made in the wrong place does not travel.
There is no record to map here. What matters is which messages can start a Zap at all, because three common kinds cannot.
| In Slack | In Zapier | What to know about the match |
|---|---|---|
| A human message in a channel | An instant trigger | Public, private or saved, with separate triggers for each, plus new file and new channel. |
| A message matching a search | A polling trigger | New Message From Query is the one that polls, so it is the one with latency. |
| A thread reply | The same trigger as a top-level message | Zapier always returns a thread timestamp field, which is how you tell them apart and filter. |
| A Zapier action | A posted Slack message | Mentions need Zapier's special formatting to notify. A slash command typed into an action posts as literal text rather than running. |
Three things are worth knowing before you plan around this mapping, because each one is a decision somebody has to own rather than a setting to find.
Every row above travels as a file: four field mappings and three documented exclusions, each one's note, and the three vendor documents behind them. The CSV opens in a spreadsheet, the JSON is the shape an agent wants, and the Markdown is the table to paste into a ticket.
The bot-message exclusion is the one that catches teams building a chain: if a Zap posts to a channel and another Zap is supposed to react to it, the second one never fires.
Slack sets no feature gate on the Zapier app itself. What it does set is a ceiling on how many apps a free workspace may hold at all, and Zapier gates how fast a polling trigger may run. Pick one on each side and the grid marks the answer.
Pick one on each side.
| Zapier plan | Free, under 10 apps | Free, at 10 apps | Any paid plan |
|---|---|---|---|
| Free | Triggers and actions, default polling | No slot to install it | Triggers and actions, default polling |
| Professional | Plus polling control | No slot to install it | Plus polling control |
| Team or Enterprise | Plus polling control | No slot to install it | Plus polling control |
Counted off that grid, of nine pairings: three give you no slot to install it, two give you triggers and actions, default polling, four give you plus polling control. The middle column is the only hard stop on this pair, and it is a Slack housekeeping problem rather than a licensing one: somebody has to decide which of the ten apps matters least.
Every step below is from the two vendors' own setup documentation, in the order they document it. Two of them cost you an afternoon if taken late, so the order is the useful part rather than the clicks.
Slack: installed apps
A free Slack workspace is limited to ten apps in total. Zapier takes one of them, and on a workspace that has been collecting integrations for a year that is the thing that blocks this rather than anything about Zapier.
Zapier: Apps, Add connection
Search for Slack, authenticate in the tab that opens and grant access. If apps are managed in your workspace, an owner or admin has to approve the install.
The Zap editor
New message in a channel, new public message anywhere, new file and new saved message are all instant. New Message From Query polls. The instant ones mean the Zap fires when the thing happens rather than on a schedule.
A filter step after the trigger
Zapier documents that test data for a new Slack message always includes a thread timestamp field, even when the message is not in a thread. That field is how you filter a Zap down to top-level messages, and without the filter every reply in a busy thread fires your automation.
The action step
A plain @name in a Zapier action does not notify anybody. Zapier publishes the formatting that makes mentions and notifications work, and the failure mode is silent: the message posts and nobody is pinged.
Your Zap design
Slack allows roughly one message a second per channel with short bursts tolerated. A Zap that fans out over a list will exceed that, so batch the output into a single message rather than looping.
The two steps that save the most time later are the thread filter and the mention formatting, because both fail quietly: the Zap runs, the message posts, and the thing you wanted does not happen.
The same sequence, the sync table, the documented limits and the error list ship as one agent skill. Point Claude Code, Cursor or anything that reads a file at this pair as a skill and it has the whole pair without reading two sets of vendor docs first.
curl -o .claude/skills/slack-zapier/SKILL.md https://www.reversecontact.com/integrations-hub/skills/slack-zapier.md
Every limit below is documented by one of the two vendors. They are here because they change decisions, not because they are flaws.
Each of those is documented behaviour rather than a fault, so none of them is going to be fixed by a support ticket. The ones that produce a symptom you would misread are below.
Each one below is a symptom somebody reports, the documented reason behind it, and the fix. Most are configuration rather than faults, which is why they survive a support ticket.
WhyMessages preceded by indentation, which is how bots, slash commands and integrations post, cannot trigger a workflow.
Trigger on something else, or extract the attachment using Zapier's documented route. A chain of Zaps posting to each other will not work.
WhyThread replies trigger the same way top-level messages do.
Add a filter on the thread timestamp field, which Zapier always returns, including on messages that are not in a thread.
WhyA plain mention in an action is text. Slack needs Zapier's special formatting for mentions and notifications to work.
Use the documented formatting. There is no error to find, because the post succeeded.
WhyIt posts as text rather than running.
Call the underlying thing directly from the Zap instead, or trigger the automation another way.
WhySlack allows about one message per second per channel, tolerating short bursts and rate-limiting sustained ones.
Batch into a single message. A loop that posts per row will hit this on any list worth automating.
WhyA free Slack workspace at its ten-app limit, or a workspace that restricts app installs.
Free a slot, or get a workspace owner or admin to approve it. Neither is a Zapier setting.
If none of those is it, the next thing to check is the thing most pairs fail on: whether the plan you are on carries the feature at all, which the grid above answers. The same symptom on another pair is often the same cause, so the directory indexes all of them by the message rather than by the integration.
The right-hand column is the one worth being honest about, because every item in it is a reason to spend the budget somewhere else in the stack rather than a reason to configure harder.
Searched for the problem this pair solves rather than for the pair itself, because the pair by name returns almost nothing. 14 threads from 2023 to 2026 were read in full on 11 October 2026, and the 5 below are the ones that carry a point. Each is one person's experience rather than a measurement, and the vendors' own documentation is what the rest of this page rests on.
the question is not "How can we use Slack/Zapier/Hubspot", the question is more like: How can we improve our internal communications and sales processes?
r/productivity·November 2023·6 points
Transcribed with the contractions expanded. It is the right frame for this pair in particular, because Slack automation is cheap enough to build before anybody has decided what it is for, and that is how a channel ends up muted.
Even for people doing lots of integrations it is still very difficult. My suggestions. Really understand how api calls and web hooks work at a system level. Focus on one integration at a time.
r/productivity·November 2023·5 points
The specific thing worth understanding here is which triggers are instant and which poll, because that single choice decides whether a Zap feels immediate or arrives five minutes late, and it is invisible in the editor unless you look.
Slack Lists is one of the products we are exploring. I can see at the moment Slack Lists does not integrate with Zapier or similar automat
r/Slack·July 2025·3 points
Worth checking before you design around a newer Slack feature. The Zapier app covers messages, files, channels and users well, and a product Slack shipped recently is a separate question with its own answer.
Does anyone have any idea how to set up a personal AI assistant for a channel on slack using Zapier and OpenAI? ideally, anyone on that channel can use a prompt like /ai
r/zapier·January 2023·3 points
Note the two walls that design meets on this page: a slash command typed into a Zapier action posts as text rather than running, and a message posted by a bot cannot trigger another Zap. Both are documented, and both are discovered late.
As a consultant you are hired to assess and improve the business processes.
r/productivity·November 2023·3 points
Which is the honest answer to how much this pair is worth. The connector costs minutes; the value is entirely in whether the thing you automate was worth routing into a channel somebody reads.
Hardly anybody discusses this pair as a pair, so the search was for the job of automating around Slack. What comes back is mostly people at the beginning of it, and the advice they get is consistently to start from the process rather than the tool. The one specific technical complaint in the set is about a Slack surface the Zapier app does not reach.
Nothing in the threads argues against building this, and the useful constraint they imply is to build one Zap, watch who acts on it, and only then build the second.
Slack is the step that decides whether the rest of a stack gets used, and Zapier is the cheapest way to reach it from a tool that never built a Slack app. That makes this a useful pair and a frequently misdesigned one, because the natural architecture is wrong. Teams try to use Slack as the message bus: tool A posts to a channel, Zapier watches the channel, tool B gets updated. Zapier documents that this cannot work, since a message carrying indented attachments, which is how integrations post, will not trigger a Zap, so trigger from the source, post to Slack as the final step, and the whole class of problem disappears.
The rate limits are the other thing worth internalising, and they argue for a design rather than merely constraining one. One message a second per channel is generous for alerting and nowhere near enough for logging, and Slack is unusually honest that past a burst it simply may not display your messages. So the failure is partial and invisible: the Zap history shows success, the channel shows some of the events, and nobody can tell which ones are missing. Route the events a named human must act on within minutes and batch everything else, which is the same conclusion every pairing on the collaboration layer reaches by a different route.
If the requirement turns out to be reading Slack rather than writing to it, stop and price the route properly. Slack's 2025 change moved conversations.history and conversations.replies to one request a minute for commercially distributed apps that are not Marketplace approved, with the page size cut to 15 objects, while Marketplace apps and internal customer-built apps keep 50 or more a minute and a page size up to 999. Renting a Marketplace-approved connector and building your own are therefore not the same project with different effort, they are two different rate limits, and the gap is a factor of fifty.
Reverse Contact resolves an email, a domain or a profile URL into a verified people and company record, through one API with a consistent schema. It sits under Slack, Zapier and everything else in this directory, and it returns null with a confidence score rather than a guess.
Free trial, no card required, and 500 credits to start.
No, a free Slack plan works. The constraint is the app slot rather than the plan: Slack's free plan allows ten apps per workspace, so you need an open one. If your workspace restricts who may install apps, a workspace owner or admin has to install Zapier rather than the person building the Zap, which is a five minute favour that frequently takes a week to arrange.
Because Zapier documents that messages with indented attachments, which is how bots, slash commands and other integrations usually post, cannot trigger Zaps. This is the most common dead end on the pair and it bites exactly when you are trying to chain two tools together. The documented workaround is to extract the attachment and use that instead, and the more reliable answer is to trigger from the source system rather than from its Slack message.
Slack allows roughly one message per second per channel, with short bursts tolerated and a workspace-wide ceiling of several hundred messages a minute above that. Slack is explicit that when bursts go too far there is no guarantee that messages will be stored or displayed to users, and readers see a notice saying some of the app's messages are not being shown. A digest is therefore not just better manners than a message per event, it is more reliable.
No. Zapier documents that entering a slash command in an action sends it as plain text rather than running it, so the channel gets the literal text of the command. Mentions need particular formatting to notify anybody too. Both are documented behaviours rather than faults, and both account for a good share of the Zaps that look like they work and quietly do nothing.
Tier requirements, sync behaviour and limits read from each vendor's own documentation in September, October and November 2026. Vendors change these without notice.
Reverse Contact appears in this directory as a data provider and publishes it. Every other tool is here on merit and nobody pays for placement.