Workflow webhook triggers are 10 a minute, which is the real ceiling on enrich on demand.
A Reverse Contact API key, somewhere to run the lookup, and a Slack app or an incoming webhook
Messages, Contacts, Companies, one way, in.
Slack is where the answer is delivered and never where the lookup happens. Nothing in Workflow Builder sends a request to an arbitrary URL, so the work runs in Clay, n8n, Zapier, Make or a custom step you host, and Slack receives a message. That is a smaller claim than most pages here make and it is the whole of this one: get the routing and the volume right, because the enrichment is somebody else's job.
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 |
|---|---|---|
| The ask | One way, out | A workflow link, a slash command or a webhook trigger carries an email or a domain out of Slack. |
| The lookup | One way, out | POST /v2/enrich/persons in the orchestrator or the custom step. 2 credits on a match, nothing on an error. |
| The answer | One way, in | chat.postMessage or an incoming webhook, one message per second per channel. |
| The routing | One way, in | Which channel it lands in, decided by what came back rather than by who asked. |
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 nothing to map, because Slack holds no record to map onto. What matters instead is which part of the response earns a line in a message somebody reads in two seconds, and which part belongs in the system that stores it.
| In Slack | In Reverse Contact | What to know about the match |
|---|---|---|
| An email typed into a workflow or slash command | POST /v2/enrich/persons, 2 credits | Identity, the current role and the company behind it on one schema. A miss returns null with a confidence score and costs nothing, because every 4xx and 5xx is free. |
| A domain from an inbound signup | POST /v2/enrich/companies, 2 credits | Firmographics from a domain. Run it once per account rather than once per person who signs up from it. |
| A profile URL somebody pasted in a channel | POST /v2/fetch/persons, 1 credit | Half the price of a reverse lookup, and unmetered from the $249 plan rather than the $699 one. Pasting a profile link into Slack is a common enough habit to build on. |
| currentPosition.title and companyName | The first line of the message | The two values that decide whether a person reads any further. Everything else is detail that belongs behind a link. |
| The confidence score | Whether to post at all | A thin match is a judgement, and the judgement is better made by your rule than by whoever happens to read the channel. |
| The whole record | The CRM, not the channel | Slack stores nothing you can query later. If the answer is worth keeping, it has to be written somewhere that is not a message. |
| The message itself | chat.postMessage, or an incoming webhook | One per second per channel either way. Bursts are tolerated and sustained excess shows the reader an error the sender never sees. |
| Anything outbound to Reverse Contact | Only the identifier you send | This is a read layer. No message, channel or member is sent anywhere, and there is nothing in the product to send it to. |
A Slack message is read in about two seconds and then scrolled past, so the schema is not the thing to print. Each row below is a field the response actually carries, judged only on whether it helps the person in the channel decide what to do next.
| In the response | Whether it earns a line |
|---|---|
| currentPosition.title and companyName | Yes, and they are the first line. These two decide whether this is worth anybody's attention, and burying them under a header defeats the message |
| data is null, with a confidence score | Yes. Say the lookup did not resolve rather than posting nothing, because a silent channel reads as a broken integration and nobody reports it |
| isInRemembrance | Yes, and it should stop whatever was going to happen next. This is the one field on the schema where a cheerful alert would be unforgivable |
| currentPosition.companyName against the account you hold | Yes, when they disagree. A job change is the most actionable thing this response carries and it is found by comparing two values rather than reading one |
| Education, skills and the full position history | No. All useful, none of it a reason to interrupt somebody, and all of it available on the record behind the link |
| hasVerificationBadge and followersCount | No. They read as seniority and they are not, which is worse in a channel than on a record because nobody will check |
A few 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: eight field mappings, six in the response rows and four documented exclusions, each one's note, and the thirteen 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 useful half of this table is the second one, and the pattern it describes is subtractive: the response carries far more than a message should. On every other page here the question is which field to write, and on this one it is which field to leave out, because the cost of a full record in a channel is that nobody reads the one line that mattered.
The reason this page sends the lookup somewhere else is not Slack being limited; it is that most of the tools people sit in all day cannot make an outbound request and read the answer. Every figure below is from the vendor's own documentation, and the column that matters is the second one, because sending a request without reading the reply is half an integration. Pick one on each side and the grid marks the answer.
Pick one on each side.
| The surface | Send an identifier out | Read the answer back in | Works without a plan upgrade | Can wait for an async job |
|---|---|---|---|---|
| Slack: built-in Workflow Builder steps | No | No | No | No |
| Slack: a custom step you build and host | Yes | Yes | No | Partly |
| ClickUp: the Call webhook automation | Yes | No | No | No |
| Google Sheets: Apps Script | Yes | Yes | Yes | Partly |
| Gong: nothing in product, the API only | No | No | No | No |
Counted off that grid, of twenty pairings: six give you yes, two give you partly, twelve give you no. The bottom row and the top row agree, which is the finding: the two tools in this directory that people spend the most time looking at are the two that cannot fetch anything. More uncomfortably, the only surface here that can send a request, read the reply and do it without an upgrade is a spreadsheet, which is a poor argument for building anything important in a spreadsheet and a very good explanation of why so many teams do.
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.
Your own process, not a settings screen
An alert that names no owner is a notification, and a channel that fires often enough gets muted by everybody in it. Pick the channel before the trigger, name the person who acts on it, and accept that this decision is worth more than every technical choice below it.
Your own architecture
Outside means an orchestrator calls Reverse Contact and posts the result, works on any Slack plan, and is an afternoon. Inside means a custom step built with the Deno Slack SDK or Bolt, needs a paid plan and an org-ready app, and is the only way the answer reaches the next workflow step instead of a human.
Reverse Contact: Workspace > API Keys
The trial takes no card and a new account starts with 500 credits, which is 250 reverse lookups and more than enough to find your own match rate. It runs until those credits are spent rather than for a number of days. GET /v2/usage keeps answering whatever the balance, which makes it the right thing for a bot to check on a schedule.
Slack: your app's configuration
An incoming webhook URL is itself a secret and belongs wherever your orchestrator keeps secrets. The Reverse Contact key travels in an Authorization header and never in a query string, because a URL is the thing that ends up in a log.
POST /v2/fetch/persons/check
The free check says whether a profile is cached and when it was last updated, so a sweep spends 2 credits only where the answer is actually missing. On a channel that posts every inbound signup this is the difference between a budget and a surprise.
Your orchestrator, or the custom step
A person reads a Slack message in about two seconds and the useful content is almost never the whole record. Lead with the one thing that decides what happens next, put the rest behind a link to the record, and resist the temptation to print the schema because it is available.
Your orchestrator
Reverse Contact returns null with a confidence score rather than a guess, so a miss is a branch rather than an error. Posting nothing is usually wrong, because silence reads as the integration being broken; posting the identifier and saying it did not resolve is honest and keeps the channel trustworthy.
The channel itself
The volume question is the one that kills these integrations and it is answerable by looking. If the channel is already firing more often than anybody reads it, a second trigger makes the first one worthless rather than making the channel more useful.
Only the first step cannot be undone cheaply, and it is the one with no screen attached: a channel that has been muted stays muted long after the routing is fixed. The rest is ordinary plumbing, and the choice in step two is the one that decides whether this is an afternoon or a project.
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-reverse-contact/SKILL.md https://www.reversecontact.com/integrations-hub/skills/slack-reverse-contact.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.
WhyA silent integration and a working integration look identical in Slack, because the absence of a message is not an event.
Post a heartbeat on a schedule, or have the orchestrator post its own failures to the same channel. A channel that has never told you it is broken has not proved it is working.
WhyThe trigger was too broad, so the channel fired more often than anyone could read, which is the failure mode of every integration on the Slack hub.
Narrow the trigger rather than the message. One event type, one channel, one named owner, and move everything else to a report nobody has to read in real time.
WhyWorkflow webhook triggers are limited to 10 per minute, and the eleventh is refused rather than queued.
Move the busy case to a scheduled sweep and keep the on-demand trigger for the occasional question. If people genuinely need to ask eleven times a minute, the answer belongs on the record rather than in a channel.
WhyPosting is limited to one message a second per channel, by chat.postMessage and incoming webhooks alike, and sustained excess is throttled.
Batch into one message rather than posting a line at a time, which is better for the reader as well. Slack shows the reader an error about undisplayed messages that the sending app never sees, so watch the channel rather than the logs.
Whyconversations.history and conversations.replies moved from Tier 3 to Tier 1 for commercially distributed apps that are not Marketplace approved, with a maximum of 15 objects and one request a minute.
If this is your own app for your own workspace it is an internal customer-built app and is explicitly unaffected, so check how it was registered before rewriting anything. If it is genuinely distributed, Marketplace approval is the documented route back.
WhyApps carrying workflow steps have to be org-ready, and custom steps cannot be developed on a Free plan.
Confirm the plan and the org-readiness before building, not after. Where neither is available, the orchestrator route reaches the same channel with none of these conditions.
WhyThe enrichment returned a current employer and nothing compared it with the account the alert was about.
Compare currentPosition.companyName against what you already hold and say so when they disagree. It is the highest-value check on the response and it is two values rather than a new field.
WhyBelow 2 Reverse Contact credits the free Check endpoints are paused as well and answer 402 NO_CREDITS, because the fetch a check precedes can itself cost 2.
Watch quotas.workspace.credits.left, which rides on every response, and check GET /v2/usage on a schedule because it keeps answering whatever the balance.
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 28 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.
At my company, we usually wait for the stakeholders to send us a Slack message saying that the data seems wrong. We then spend a few hours investigating. Sometimes the data is wrong, sometimes not. [...] That's not how you're supposed to do it ?
r/dataengineering·November 2023·212 points
The highest-scoring comment in the whole harvest, and it describes the status quo rather than a tool: Slack is the alerting layer already, and the sensor is a person noticing. That is the thing being replaced here, which is worth saying because it sets the bar low. Anything that posts a correct answer before somebody has to ask is an improvement on the arrangement most teams actually have.
We use slack for all alerts and have them broken out into different channels by area and severity. High fidelity alerts go to "prod" channel for the area of the business that had SMEs in the channel for that area. Then the low fidelity alerts go to separate channels and generally these arent reviewed but become context later [...] Alerts are auto-enriched in slack with user information, host information, virustotal, related alerts by user/host, and more.
r/SIEM·January 2023·2 points
A security team describing, three years early and in another discipline, exactly the design this page recommends. Two things are worth copying. The enrichment happens before the alert reaches Slack rather than being looked up afterwards, and the channel is chosen by the quality of the answer rather than by who asked, which is the routing row in the sync table above.
All alerts go to our SOAR platform (Tines) for formatting, enrichment, etc... before they head off to Slack. Our SOAR platform handles all the back and forth with the buttons in Slack and interactions that are available to an analyst.
r/SIEM·January 2023·1 points
This is the architecture on this page with the names changed, and the division of labour is the part to take: the orchestrator owns the enrichment and the state, Slack owns the conversation. Swap Tines for Clay, n8n, Zapier or Make and nothing else about it changes, which is a good sign that the shape is right rather than fashionable.
You can get pretty close by treating Slack as the "front door" and pushing the real CSP logic into your CRM / data layer, then surfacing 3 things: a single account object (from SF or similar) into a Slack canvas, a lightweight planning channel or canvas per account [...] and AI agents that listen to those channels and spit out next-best-actions based on playbooks and health signals.
r/CustomerSuccess·March 2026·2 points
Written about replacing a customer success platform and it states this page's thesis more briskly than the page does. Slack is the front door; the record and the logic live in the layer below. The reason it matters for an enrichment build is that it answers where to store the answer, which is the question the fields table exists to settle.
in my experience enrichment's also great for auto-prioritizing outreach based on intent signals and firmographic fit, detecting title changes to trigger win-back or offboarding flows, and feeding real-time fit scores into SDR queues so reps know who to call first
r/GrowthHacking·October 2025·1 points
A list of uses from somebody doing it, and the middle one is the one that suits a channel. A title change is an event with a date, which is exactly the shape a Slack message is good at, while a fit score is a number that belongs in a queue. It also corroborates the comparison in the table above: the valuable signal is found by noticing that two values disagree.
Nobody discusses this pair by name, so the search was for the job: getting an enriched answer in front of somebody in Slack. The most useful threads turned out to be from security and customer success rather than from sales, and they describe the same architecture this page argues for, in more detail and with more scars. The pattern they report independently is enrich first, post second, and route by severity to a channel with an owner.
Not one of the five is about this pair, and two of the best are from a security team rather than a sales one, which is the honest reading of a job that Slack has been doing for longer in other disciplines. The one to act on is the second, because it answers the question this page opens with: the enrichment happens before the message, and the channel is chosen by what came back.
Every other page in this directory is about filling a record. This one is about the two seconds in which somebody reads it, which is a different problem and has a different failure mode: not a wrong value but a message nobody opens. Slack holds no contact and no company, so there is nothing here to keep in sync and nothing to map, and the design question is which answers deserve to interrupt a person.
The route that works on any plan is the one that treats Slack as an output. The n8n pair is the same shape with a loop in the middle, which matters because n8n is the one orchestrator here that can poll an asynchronous job, and the live Reverse Contact endpoints are documented as possibly taking tens of minutes. Where the record belongs in a CRM anyway, enriching at the HubSpot end and letting its workflow post to Slack keeps one copy of the answer instead of two.
The in-Slack route is worth it for one reason, which is that a custom step returns its outputs into the workflow. A connector or a posted message gives a human the answer; a custom step gives the next step the answer, so a workflow can branch on a job title without a person reading anything. That is a real capability and it costs a Deno or Bolt app, an org-ready review and a paid plan, which is why it is the second route on this page rather than the first.
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, Reverse Contact 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. Reverse Contact maintains apps on Clay, Zapier and Make, and nothing inside Slack. What exists is two honest routes: an orchestrator does the lookup and posts the answer to a channel, or you build a custom step for Workflow Builder yourself with the Deno Slack SDK or Bolt. The first is an afternoon and the second is a project.
Slack documents no built-in Workflow Builder step that sends a request to an arbitrary URL. The documented way to add one is a custom step, which is a function you ship as an app and which finishes by calling functions.completeSuccess or functions.completeError with its outputs. That is also the only route that puts the answer back into the workflow rather than into a channel.
Workflow webhook triggers are capped at 10 per minute, which is the number that decides whether a team can type a lookup whenever they like. Posting is one message per second per channel, by chat.postMessage or an incoming webhook alike, and event triggers get 10,000 an hour. None of those figures moves with your Slack plan.
It changes where the lookup can run, not how fast. Workflow Builder is on paid plans and custom steps cannot be developed on a Free plan, so a Free workspace has to do the lookup outside Slack and post the result in through an incoming webhook. The rate limits are the same on every plan, which is unusual and worth knowing before anybody prices an upgrade.
Wherever the record lives, which is almost never Slack. Slack holds no contact and no company, so enriching for Slack alone writes the answer to a channel and then loses it. Enrich in the CRM or the orchestrator, store it there, and treat the Slack message as a view of a record rather than as the record.
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.