---
name: slack-zapier-integration
description: Connect Slack and Zapier: what syncs, which editions carry it, the setup order, and the failures to expect. Covers messages. Use when the user wants to set up, audit or troubleshoot Slack and Zapier together, or asks why data is not moving between them.
---

# Slack and Zapier

> Generated from https://www.reversecontact.com/integrations-hub/slack-integrations/slack-zapier-integration
> Every tier requirement, sync direction and limit below was read from the vendors' own documentation on 2026-10-11.
> Vendors change these without notice. Re-check anything load-bearing before you rely on it.

**What you have to buy first:** A Zapier plan sized to your task volume, and a free app slot on a free Slack plan

**What moves:** messages, events only.
**How it is built:** zapier, make or n8n, marketplace app. **Effort:** minutes.

## The short version

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.

## Which plans carry what

Rows: Zapier plan. Columns: Slack plan. 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.

| 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 |

- **No slot to install it.** A free Slack workspace holds ten apps in total. At the limit, installing Zapier means uninstalling something else, and no Zapier plan changes that.
- **Triggers and actions, default polling.** Every trigger and action, including the instant ones, on whatever polling interval a free Zapier account gets for the polling trigger.
- **Plus polling control.** Adds control of the polling interval, which only matters for New Message From Query, because the rest are instant.

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.

## What actually syncs

Direction is written from Slack's point of view: out means out of Slack, in means into it.

| 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 | Events 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. |

## Which field lands where

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. |

**What does not cross:**

- A message from a bot, a slash command or another integration. Those arrive as attachments and cannot trigger a workflow, though an attachment can be extracted for use inside one.
- A slash command, as an action. It posts as text.
- An eleventh app on a free Slack workspace. The slot limit is ten in total.

## Connect it, in this order

**Who has to do it:** Anybody with a Slack account, unless the workspace restricts apps, in which case a workspace owner or admin.
**How long:** Three minutes, and then a decision about which trigger to use.

### 1. Count your app slots if you are on free Slack

*Where:* 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.

### 2. Add the connection from Zapier

*Where:* 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.

### 3. Choose an instant trigger where one exists

*Where:* 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.

### 4. Filter out thread replies deliberately

*Where:* 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.

### 5. Write mentions with the special formatting

*Where:* 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.

### 6. Keep posting under one message per second per channel

*Where:* 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.

## How to check it worked

- Post in a thread and confirm the Zap does not fire, assuming you added the filter.
- Have a bot or another integration post a message and confirm the Zap ignores it, which it will.
- Send a test message containing a mention and check somebody actually got a notification rather than seeing plain text.
- Put a slash command in an action and watch it post as text. Knowing that now is cheaper than designing a workflow around it.

## When it goes wrong

Each row is a symptom somebody reports, the documented reason, and the fix. Work down it before escalating to either vendor, because most of these are configuration.

| Symptom | Why it happens | What to do |
|---|---|---|
| A Zap never fires on messages posted by another tool | Messages 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. |
| The Zap fires constantly during a busy conversation | Thread 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. |
| The message posted but nobody was notified | A 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. |
| A slash command in an action did nothing | It posts as text rather than running. | Call the underlying thing directly from the Zap instead, or trigger the automation another way. |
| Messages are dropping during a burst | Slack 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. |
| Zapier cannot be installed at all | A 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. |

## What breaks, from the vendors' own docs

- **A bot message cannot start a Zap.** Messages with indented attachments, the normal shape of a post from a bot, a slash command or another integration, cannot trigger Zaps. So the obvious design of letting one tool post to Slack and having Zapier react to it does not work. Extract the attachment if you must, but the sound answer is to trigger from the system that generated the event rather than from its announcement.
- **One message a second, then no guarantees.** Slack permits about one message per second per channel including incoming webhooks, maintains a workspace-wide ceiling of several hundred a minute, and states that beyond a burst there is no guarantee that messages will be stored or displayed to users. Readers get a notice that some of the app's messages are not being shown, which means a noisy automation does not fail loudly, it fails selectively.
- **Slash commands post as text.** A slash command typed into a Zapier action is sent as plain text and does not execute, and mentions need specific formatting before they notify anyone. Both produce a Zap that runs successfully and achieves nothing, which is the hardest class of bug to notice because every dashboard is green.
- **Reading history is tiered against you.** Slack rate limits per method, per workspace, per app. Marketplace-approved and internal customer-built apps get Tier 3 on conversations.history, which is 50 or more requests a minute with a limit parameter up to 999. A commercially distributed app that is not Marketplace approved gets Tier 1, one request a minute, with the limit parameter capped at 15 objects. That matters the moment you consider building your own connector instead of renting one.

## The APIs, if you are building around it instead

### Slack

- **Base:** `https://slack.com/api`
- **Auth:** `Authorization: Bearer xoxb-...` (bot token). Scope `chat:write`, plus `chat:write.public` to post to a channel the bot has not joined.

| Call | Request | What it does |
|---|---|---|
| `POST /api/chat.postMessage` | `{ "channel": "C0123", "text": "...", "blocks": [...] }` | The only call most of these workflows need. Use this when you need to choose the channel at runtime. |

**Rules that will cost you time if you skip them:**

- **HubSpot's Slack workflow action cannot route to the channel associated with the record.** It sends to a channel chosen at design time. If you need per-record routing, look the association up yourself and call `chat.postMessage` directly.
- Creating a Slack channel from a HubSpot workflow requires HubSpot Professional or Enterprise.
- Route only events a named human must act on within minutes. A channel that fires forty times a day gets muted, and a muted channel is indistinguishable from a working one in the admin screen.

Docs: https://api.slack.com/methods/chat.postMessage

## Filling the record this integration moves

The integration above moves a record between two systems. Neither of them creates what is in it, so a sync that works perfectly still carries whatever gaps the record arrived with. Reverse Contact resolves an email, a domain or a profile URL into a verified people and company record through one API, and returns null with a confidence score rather than a guess.

### Reverse Contact

- **Base:** `https://api.reversecontact.com/v2`
- **Auth:** `Authorization: Bearer rc_your_api_key`. Keys are created in Workspace > API Keys.

| Call | Request | What it does |
|---|---|---|
| `POST /v2/enrich/persons` | `{ "email": "j.okafor@northwind.io" }` | Resolve a person from an email, a name plus company, or a profile URL. Cached resolution, returns in the response. |
| `POST /v2/enrich/companies` | `{ "domain": "northwind.io" }` | Resolve a company from a domain or a name. |
| `POST /v2/fetch/persons` | `{ "linkedInUrl": "..." }` | Standard profile lookup from the database. |
| `POST /v2/fetch/persons/live` | `{ "linkedInUrl": "..." }` | Live on-demand resolution. ASYNCHRONOUS: returns a webhookId to poll, not a record. |
| `POST /v2/search/people` | `{ "filters": { "currentCompanyDomain": "northwind.io" } }` | Filtered people search. 1 credit a profile delivered, and /v2/search/people/count is free. It replaced /v2/search/persons, which returns 410 Gone since 13 October 2026. |
| `POST /v2/search/organizations` | `{ "filters": { "companyDomain": "northwind.io" } }` | Filtered company search. A domain can also go straight to a company through POST /v2/enrich/companies, or through the enrich_company MCP tool since November 2026. |
| `POST /v2/contact/email` | `{ "linkedInUrl": "..." }` | Find an email. ASYNCHRONOUS: returns a taskId to poll. 3 credits for a professional address, 5 for a personal one, 8 for both, refunded when neither is found. |
| `GET /v2/webhooks/:webhookId` | - | Poll an async job until status is "succeeded". Polling is free and does not count against the rate limit. |

Response shape:

```json
{
  "success": true,
  "data": {
    "person": {
      "fullName": "Jane Okafor",
      "headline": "VP Sales at Northwind",
      "location": "London, United Kingdom",
      "linkedInUrl": "https://linkedin.com/in/...",
      "currentPosition": { "title": "VP Sales", "companyName": "Northwind", "startDate": "2023-04" },
      "emails": [], "experience": [], "education": [], "skills": []
    },
    "company": { "name": "Northwind", "domain": "northwind.io",
                 "industry": "Software Development", "employeeCount": 220 }
  },
  "error": null,
  "metadata": { "requestId": "req_...", "executionTimeMs": 480, "updatedAt": "2026-09-01T..." },
  "quotas": { "creditsConsumed": 1, "workspace": { "credits": { "total": 10000, "used": 4521, "left": 5479 } } }
}
```

**Rules that will cost you time if you skip them:**

- A miss returns **null**, not a best guess. Every response carries a confidence score, and you can raise the precision threshold on the request. Branch on it: do not treat a low-confidence answer as a match.
- Use the cached endpoints anywhere that must answer inside one HTTP request. The `/live` endpoints return a task and need polling.
- `quotas.workspace.credits.left` is on every response. Log it, or you will find out about the balance from a 402.
- Credit costs per call are published and a dollar rate per lookup is not: 2 credits for a reverse lookup from an email, 1 for a cached profile lookup, 2 for a live refresh, 3 for a business email and 20 for a direct phone number, with the last two charged only when one is found. Checks and the search count endpoint are free. Credit packs expire after 3 months. Do not hard-code a dollar cost assumption.

**MCP server:** `https://api.reversecontact.com/mcp`

- Auth: OAuth 2.1 where the client supports it, otherwise `Authorization: Bearer rc_your_api_key`.
- Tools: `enrich_person`, `enrich_person_live`, `enrich_company`, `enrich_company_live`, `search_persons`, `search_companies`, `check_usage`, `check_task`
- Streamable HTTP, JSON-RPC 2.0. The `_live` tools return a task id that `check_task` polls.

Docs: https://docs.reversecontact.com/getting-started

## Sources

- Zapier: how to get started with Slack on Zapier: https://help.zapier.com/hc/en-us/articles/8495993391629-How-to-get-started-with-Slack-on-Zapier
- Slack developer docs: Web API rate limits: https://docs.slack.dev/apis/web-api/rate-limits/
- Slack developer docs: rate limit changes for non-Marketplace apps: https://docs.slack.dev/changelog/2025/05/29/rate-limit-changes-for-non-marketplace-apps/
- 14 practitioner threads read on 2026-10-11, summarised on the page: https://www.reversecontact.com/integrations-hub/slack-integrations/slack-zapier-integration#reddit
- This pair, with the reasoning behind each step: https://www.reversecontact.com/integrations-hub/slack-integrations/slack-zapier-integration

---

*Published by Reverse Contact, which appears in this directory as a data provider.
No other vendor pays for placement. Where a vendor publishes no public figure, this file says so
rather than estimating. Reverse Contact costs are stated in credits, which it publishes; no dollar
rate per lookup appears here, because none is published and dividing a pack price is not their number.*
