# Tool integrations directory: every record > The full dataset behind https://www.reversecontact.com/integrations-hub, inline. Verified against each vendor's own documentation between 2026-09-18 and 2026-10-28, every record carrying the date it was last read. Where a vendor publishes no public figure, this file says so rather than estimating. Published by Reverse Contact, which also appears in this dataset as a data provider. No other vendor pays for placement. ## How to read a record - **Built as** is how the connection is actually made: native, marketplace app, Zapier/Make/n8n, built on the API, or an MCP server. A pair listed as "built on the API" has no app to install in either direction. - **Syncs** is the direction records move: both ways, one way in, one way out, or events only. A capability that only moves one way is a different product from the one people assume they are buying. - **Costs to turn on** is the field that decides most evaluations. The integration is nearly always free; the plan that carries it is the bill. ## Taxonomy **Stack layer:** CRM (The system of record); Data (Enrichment and identity); Prospecting (Lists and buying signals); Engagement (Sequencing and sending); Orchestration (Workflow and glue); Collaboration (Where the team works); Revenue intelligence (Calls and forecasting). **How it is built:** Native (Built by one of the two vendors); Marketplace app (Listed, installed in a few clicks); Zapier, Make or n8n (Glue you rent); Built on the API (You own the code); MCP server (An agent drives it). **Which way it syncs:** Two-way sync (Both sides write); One way, in (Into the hub tool); One way, out (Out of the hub tool); Events only (Triggers, no record sync). **What moves:** Contacts; Companies; Deals; Activities; Lists; Tasks; Messages; Custom objects. **Setup effort:** Minutes (Connect and go); Hours (Mapping to think about); Days (A real project). **Cost to turn on:** Included on both sides (No upgrade, no metering); Needs a higher plan (A paywall on one side); Paid add-on or licence (A separate purchase); Metered by usage (Credits, tasks or rows). ## Stack layers - **CRM** (https://www.reversecontact.com/integrations-hub/stack/crm): Where every customer record finally lives. Tools: HubSpot, Salesforce, Attio, Pipedrive, Zoho CRM, monday CRM. 33 integrations touch it. - **Data** (https://www.reversecontact.com/integrations-hub/stack/data): Enrichment, identity and confidence scores. Tools: Reverse Contact, ZoomInfo, Apollo, Clay. 26 integrations touch it. - **Prospecting** (https://www.reversecontact.com/integrations-hub/stack/prospecting): Finding accounts and their buying signals. Tools: ZoomInfo, Apollo, LinkedIn Sales Navigator. 10 integrations touch it. - **Engagement** (https://www.reversecontact.com/integrations-hub/stack/engagement): Sequencing, sending and handling the replies. Tools: Apollo, Outreach, Smartlead, lemlist, Salesloft, Instantly. 20 integrations touch it. - **Orchestration** (https://www.reversecontact.com/integrations-hub/stack/orchestration): The glue between every other layer. Tools: Clay, n8n, Zapier, Make. 23 integrations touch it. - **Collaboration** (https://www.reversecontact.com/integrations-hub/stack/collaboration): Where the team sees it happen. Tools: Slack, ClickUp, Google Workspace. 15 integrations touch it. - **Revenue intelligence** (https://www.reversecontact.com/integrations-hub/stack/revenue-intelligence): Calls, recordings and the forecast. Tools: Gong. 4 integrations touch it. ## Tools ### HubSpot - Layer: CRM - Best for: The most connected CRM in B2B - Entry: $0/mo. Free tier: Free CRM for up to 2 users, with full CRM API access - Auth: Private app token, or OAuth for marketplace apps - Rate limits: 190 requests per 10 seconds per private app on Professional and Enterprise, 100 on Free and Starter. Daily caps are 250,000, 625,000 and 1,000,000 calls per account. - Automation: Up to 50 simple workflows on Starter, up to 300 fully customisable workflows on Professional - Integrations in this directory: 17 (hub: https://www.reversecontact.com/integrations-hub/hubspot-integrations) - Site: https://www.hubspot.com/ | Docs: https://developers.hubspot.com/docs/api/overview ### Salesforce - Layer: CRM - Best for: The CRM everything integrates with, eventually - Entry: Quote only. Free tier: No free tier. Developer Edition is for building, not for running a team. - Auth: OAuth 2.0, connected app - Rate limits: Daily API request allocation set by edition and licence count, published in Salesforce limits documentation - Automation: Flow, on every edition with API access - Integrations in this directory: 12 (hub: https://www.reversecontact.com/integrations-hub/salesforce-integrations) - Site: https://www.salesforce.com/ | Docs: https://developer.salesforce.com/docs/apis ### Attio - Layer: CRM - Best for: The CRM whose objects you define - Entry: $0/mo. Free tier: Free plan available - Auth: API key or OAuth - Rate limits: Published per endpoint in the Attio developer documentation - Automation: Automations on paid plans - Integrations in this directory: 3 (hub: https://www.reversecontact.com/integrations-hub/attio-integrations) - Site: https://attio.com/ | Docs: https://developers.attio.com/ ### Pipedrive - Layer: CRM - Best for: A pipeline a sales team will actually keep up to date - Entry: €14/seat/mo. Free tier: No free plan. A 14-day trial, no credit card required. - Auth: API token, or OAuth 2.0 for apps - Rate limits: A daily token budget of 30,000 base tokens times a plan multiplier times seats, the multiplier being 1 on Lite, 2 on Growth, 5 on Premium and 7 on Ultimate. Burst limits are per token on a rolling 2-second window: 20 requests on Lite up to 120 on Ultimate, and 80 up to 480 for OAuth apps. Search is 10 requests per 2 seconds on every plan. - Automation: Automations from Growth. The webhook action inside one is global admin only and needs a webhook pre-created as an Automation webhook. - Integrations in this directory: 1 - Site: https://www.pipedrive.com/ | Docs: https://pipedrive.readme.io/docs ### Zoho CRM - Layer: CRM - Best for: A CRM bought as part of a whole software estate - Entry: $0/mo. Free tier: A free edition for up to 3 users. A 15-day trial on the paid editions, no credit card. - Auth: OAuth 2.0 - Rate limits: API credits in a rolling 24-hour window: 5,000 on the free edition, and 50,000 plus 250 to 2,000 per user licence by edition above it, capped at 100,000 on Standard and 3,000,000 on Professional. Concurrency rather than a per-minute limit: 5 simultaneous calls per org per app on free, 10 on Standard, 15 on Professional and 20 on Enterprise. - Automation: Workflow rules on every paid edition. Functions in full on Enterprise and above, with a 30-second timeout inside automation and a 5,000,000 a day ceiling on invokeUrl across the org. - Integrations in this directory: 1 - Site: https://www.zoho.com/crm/ | Docs: https://www.zoho.com/crm/developer/docs/api/v8/ ### monday CRM - Layer: CRM - Best for: A sales team already living in the same boards as everyone else - Entry: €12/seat/mo. Free tier: No free CRM plan. A free trial, no credit card required. - Auth: Personal API token, app token, or OAuth - Rate limits: A daily call limit resetting at midnight UTC: 1,000 on Basic and Standard, 10,000 on Pro and 25,000 on Ultimate. Separately a complexity budget of 5,000,000 points a minute each for reads and writes on an app token, or 10,000,000 combined on a personal token and 1,000,000 on trial, NGO and free accounts. Queries a minute are 1,000, rising to 2,500 on Pro and 5,000 on Ultimate. - Automation: Custom automations from Standard at 250 a month, 25,000 on Pro. Webhooks fire on item creation and column changes, verify the endpoint with a challenge, and retry once a minute for 30 minutes. - Integrations in this directory: 1 - Site: https://monday.com/crm | Docs: https://developer.monday.com/api-reference/ ### Reverse Contact - Layer: Data - Best for: The data layer under the whole stack - Entry: $100 of credits. Free tier: 500 credits free to try, no card required, and the trial runs until they are spent. - Auth: Bearer token: Authorization: Bearer rc_your_api_key - Rate limits: A workspace minute limit across all keys: 50 on the free trial, 100 on pay as you go and on all three Unlimited plans, with a paid add-on of 200 or 500, and from 1,000 on Enterprise. Separately a daily cap of 100,000 profiles per workspace per UTC day on Go, Plus and Max, which only the calls a plan covers count against. Exceeding either returns 429, costs nothing, and names which one in the error code. - Automation: API, webhooks, CSV, MCP and a CLI. Native apps on Clay, Zapier and Make, and no app inside any CRM or sequencer. - Integrations in this directory: 22 (hub: https://www.reversecontact.com/integrations-hub/reverse-contact-integrations) - Site: https://www.reversecontact.com/ | Docs: https://docs.reversecontact.com/getting-started ### ZoomInfo - Layer: Data, Prospecting - Best for: Enrichment bought at the enterprise end - Entry: Quote only. Free tier: No free tier. Pricing is quoted per seat and per package. - Auth: API key or OAuth, depending on product - Rate limits: Published per contract - Automation: Inbound Enrich, scheduled bulk enrichment, Copilot signals - Integrations in this directory: 3 (hub: https://www.reversecontact.com/integrations-hub/zoominfo-integrations) - Site: https://www.zoominfo.com/ | Docs: https://api-docs.zoominfo.com/ ### Apollo - Layer: Data, Prospecting, Engagement - Best for: Data and sending behind one connector - Entry: $49/user/mo. Free tier: Free plan available, but it does not include CRM integrations - Auth: API key in the x-api-key header - Rate limits: Published per plan and per endpoint category in the Apollo documentation - Automation: Sync settings with field mapping, configurable per object - Integrations in this directory: 7 (hub: https://www.reversecontact.com/integrations-hub/apollo-integrations) - Site: https://www.apollo.io/ | Docs: https://docs.apollo.io/ ### Clay - Layer: Orchestration, Data - Best for: The join between your CRM and everyone else - Entry: $0/mo. Free tier: Free plan available - Auth: API key per workbook - Rate limits: Concurrency governed by plan rather than a published per-minute cap - Automation: Auto-update on a schedule, plus conditional runs per row - Integrations in this directory: 10 (hub: https://www.reversecontact.com/integrations-hub/clay-integrations) - Site: https://www.clay.com/ | Docs: https://university.clay.com/ ### n8n - Layer: Orchestration - Best for: Glue you can self-host - Entry: $0 self-hosted. Free tier: Community edition, self-hosted, free - Auth: Credentials stored per connection - Rate limits: Whatever your own host and the target API allow - Automation: Workflows on cron, webhook or queue - Integrations in this directory: 6 (hub: https://www.reversecontact.com/integrations-hub/n8n-integrations) - Site: https://n8n.io/ | Docs: https://docs.n8n.io/ ### Zapier - Layer: Orchestration - Best for: The widest app coverage, metered - Entry: $0/mo. Free tier: Free plan with a monthly task allowance - Auth: Per-app connections held by Zapier - Rate limits: Task throughput by plan - Automation: Zaps on trigger, schedule or webhook - Integrations in this directory: 6 (hub: https://www.reversecontact.com/integrations-hub/zapier-integrations) - Site: https://zapier.com/ | Docs: https://docs.zapier.com/ ### Make - Layer: Orchestration - Best for: Branching logic without code - Entry: $0/mo. Free tier: Free plan with a monthly operations allowance - Auth: Per-app connections held by Make - Rate limits: Operations per month by plan - Automation: Scenarios on trigger or schedule - Integrations in this directory: 2 - Site: https://www.make.com/ | Docs: https://www.make.com/en/help ### LinkedIn Sales Navigator - Layer: Prospecting - Best for: The prospecting surface reps refuse to leave - Entry: Quote only. Free tier: No free tier. Sales Navigator is sold per seat by edition. - Auth: OAuth 2.0. Sales permissions need SNAP partner approval, and LinkedIn is not accepting new partners. - Rate limits: Per endpoint, reset at midnight UTC. The standard limits are not published; yours are in the Developer Portal. - Automation: Auto-Save lists and activity writeback - Integrations in this directory: 8 (hub: https://www.reversecontact.com/integrations-hub/linkedin-integrations) - Site: https://business.linkedin.com/sales-solutions/sales-navigator | Docs: https://www.linkedin.com/help/sales-navigator ### Outreach - Layer: Engagement - Best for: Sequencing with a real CRM contract - Entry: Quote only. Free tier: No free tier - Auth: OAuth 2.0 - Rate limits: 10,000 requests an hour, metered per user rather than per org. Bulk endpoints and Kaia have their own rules, Kaia being 3 calls a second and 6,000 a day at org level. Outreach states it may change these at any time. - Automation: Sequences, triggers and plays - Integrations in this directory: 8 (hub: https://www.reversecontact.com/integrations-hub/outreach-integrations) - Site: https://www.outreach.io/ | Docs: https://developers.outreach.io/ ### Smartlead - Layer: Engagement - Best for: Sending volume without per-mailbox pricing - Entry: $39/mo. Free tier: No free tier. Entry pricing comes off a plan slider, so confirm your tier. - Auth: API key as a query parameter, api_key=YOUR_API_KEY, rather than a header - Rate limits: Per API key and plan-wide across all endpoints: 60 requests a minute and 1,000 an hour on Standard with a 10 a second burst, 120 and 3,000 on Pro with a 20 a second burst, custom on Enterprise. A few endpoints carry their own tighter limit. - Automation: Webhooks plus a full campaign API - Integrations in this directory: 3 - Site: https://www.smartlead.ai/ | Docs: https://api.smartlead.ai/reference ### lemlist - Layer: Engagement - Best for: Multichannel sequences with a CRM sync - Entry: $0/mo. Free tier: Free plan available - Auth: HTTP Basic, not Bearer. Empty username, the API key as the password, so the string to base64-encode is :YourApiKey with a leading colon. - Rate limits: 20 requests per 2 seconds, on all routes, metered per API key. X-RateLimit-Reset comes back as a human-readable date rather than a timestamp. - Automation: Sequences, conditions and webhooks, plus an MCP server and its own bulk enrichment endpoint - Integrations in this directory: 3 (hub: https://www.reversecontact.com/integrations-hub/lemlist-integrations) - Site: https://www.lemlist.com/ | Docs: https://developer.lemlist.com/ ### Salesloft - Layer: Engagement - Best for: Enterprise outbound with a rate limit the whole team shares - Entry: Quote only. Free tier: No free tier and no public pricing. The site routes to sales. - Auth: OAuth 2.0 authorization code for partners, client credentials for private apps, and API keys for customers only - Rate limits: 600 cost a minute, applied per team rather than per integration, so another integration on the same team spends your budget. Each endpoint costs 1 by default and Salesloft can change a cost at any time. Deep pagination costs more: 3 points past page 100, 8 past 150, 10 past 250 and 30 past 500. - Automation: Webhooks on 37 event types. A failing webhook is retried three more times, 15 seconds apart, then marked failed. - Integrations in this directory: 1 - Site: https://www.salesloft.com/ | Docs: https://developer.salesloft.com/ ### Instantly - Layer: Engagement - Best for: High-volume cold email with the API limits to match - Entry: $47/mo. Free tier: No free plan. Growth is the entry point. - Auth: Bearer token: Authorization: Bearer your_api_key - Rate limits: 100 requests a second and 6,000 a minute, shared between API v1 and v2 and across every key in the workspace. A few endpoints are tighter: listing emails is 20 a minute, a test send is 10 a minute. - Automation: Webhooks with typed events, an OAuth flow for connecting mailboxes, and a provider registry whose effectiveCostPerAction is 0 when the workspace holds its own key. - Integrations in this directory: 1 - Site: https://instantly.ai/ | Docs: https://developer.instantly.ai/ ### Slack - Layer: Collaboration - Best for: Where the stack tells a human - Entry: $0/mo. Free tier: Free plan available, with limits on history and apps - Auth: OAuth 2.0, app-level tokens for events - Rate limits: Published per method tier in the Slack API documentation - Automation: Workflow Builder, plus events and slash commands - Integrations in this directory: 10 (hub: https://www.reversecontact.com/integrations-hub/slack-integrations) - Site: https://slack.com/ | Docs: https://api.slack.com/ ### ClickUp - Layer: Collaboration - Best for: Turning a closed deal into delivery work - Entry: $0/mo. Free tier: Free Forever plan available - Auth: Personal API token or OAuth - Rate limits: Published per plan in the ClickUp API documentation - Automation: Automations with triggers, conditions and actions - Integrations in this directory: 4 (hub: https://www.reversecontact.com/integrations-hub/clickup-integrations) - Site: https://clickup.com/ | Docs: https://developer.clickup.com/ ### Gong - Layer: Revenue intelligence - Best for: Putting what was said onto the record - Entry: Quote only. Free tier: No free tier - Auth: OAuth 2.0 or API key - Rate limits: Published in the Gong API documentation - Automation: Rules and alerts on call content - Integrations in this directory: 4 (hub: https://www.reversecontact.com/integrations-hub/gong-integrations) - Site: https://www.gong.io/ | Docs: https://gong.app.gong.io/settings/api/documentation ### Google Workspace - Layer: Collaboration - Best for: The integration everybody installs first - Entry: $0/mo. Free tier: Personal Google accounts connect at no cost - Auth: OAuth 2.0 - Rate limits: Published per API in the Google Workspace documentation - Automation: Apps Script, plus native connectors on both CRMs - Integrations in this directory: 3 (hub: https://www.reversecontact.com/integrations-hub/google-integrations) - Site: https://workspace.google.com/ | Docs: https://developers.google.com/workspace ## Integrations ### HubSpot and LinkedIn Sales Navigator Two-way, genuinely useful, and only on the Sales Navigator edition nobody quotes you first. - Built as: Native, Marketplace app - Syncs: Two-way sync - Moves: Contacts, Companies, Deals, Activities - Costs to turn on: Paid add-on or licence. Setup: Hours - Requires: Sales Hub Professional or Enterprise, plus Sales Navigator Advanced Plus - Full guide: https://www.reversecontact.com/integrations-hub/hubspot-integrations/hubspot-linkedin-integration **Verdict.** The integration is good and the gate is expensive. CRM Sync writes Sales Navigator activity back to HubSpot, creates and updates contacts from Sales Navigator, and matches your records so reps can filter searches by what is already in the CRM. All of that needs Advanced Plus, which is the quoted edition rather than the one on the pricing page. If your reps are on Advanced, what you have is an embedded profile card, and the honest description of that is a convenience feature rather than a sync. **What syncs:** - Contacts and Leads (two-way): HubSpot contacts import into Sales Navigator lists; Sales Navigator can create and update HubSpot contacts. - Companies and Accounts (two-way): Matched so account pages show CRM context and searches can filter on it. - Deals and Opportunities (two-way): Open pipeline is visible inside Sales Navigator and feeds revenue attribution reporting. - Owners (in): HubSpot only. Owner data goes across so book ownership is respected; nothing comes back. - Sales Navigator activity (out): InMails, messages and notes log to HubSpot as activities. This is the half most teams are buying. **Which editions carry it** (rows HubSpot, columns LinkedIn Sales Navigator): - Free or Starter with Core: Nothing - Free or Starter with Advanced: Nothing - Free or Starter with Advanced Plus: Nothing - Sales Hub Professional with Core: Nothing - Sales Hub Professional with Advanced: Profile card only - Sales Hub Professional with Advanced Plus: Full CRM Sync - Sales Hub Enterprise with Core: Nothing - Sales Hub Enterprise with Advanced: Profile card only - Sales Hub Enterprise with Advanced Plus: Full CRM Sync **How to connect it** (A HubSpot Super Admin and a Sales Navigator contract admin, which in most companies is two people on two teams.. About half an hour for the admins, then one authentication per rep.): 1. Price both editions before you touch a settings page [Contracts]. LinkedIn documents two requirements for CRM Sync: Sales Navigator Advanced Plus, and a HubSpot Sales Hub Professional licence or higher. Advanced Plus is quoted rather than listed, so get the number across your whole seat count while this is still a decision. 2. Install the Sales Navigator app for every user first [HubSpot App Marketplace]. Embedded Profiles is a per-user install, and LinkedIn recommends doing it before CRM Sync so the embedded experiences arrive complete. This half runs on Advanced as well as Advanced Plus, which is why some teams already have it and think the sync is next. 3. Disconnect Business Manager if it is already paired [HubSpot: Settings, Integrations, Connected Apps]. An existing LinkedIn Business Manager connection blocks the Sales Navigator pairing. The documented order is disconnect, sync, then reconnect Business Manager afterwards. Skip it and the pairing simply will not complete. 4. Install LinkedIn CRM Sync and choose the environment [HubSpot App Marketplace]. Install the app, click Connect to LinkedIn CRM Sync, sign in, and pick the contract if you sit on more than one. Then choose Production or Sandbox: one HubSpot account pairs with one Sales Navigator environment at a time, so a sandbox trial holds the slot your production pairing needs. 5. Start all four syncs [HubSpot: Connected Apps, LinkedIn CRM Sync]. Start all syncs covers contacts, companies, deals and owners in one click. Each object has a Configure, Limit and Organize view that says which records qualify and whether associations and deletions travel, and those are worth reading before you walk away from it. 6. Make every rep authenticate individually [Sales Navigator: Settings, CRM Settings]. Admin authentication does not cover writeback. Contact creation and activity writeback need each user to click Connect to CRM themselves, and a rep who never does it logs nothing while appearing to be set up. 7. Select LinkedIn in the activity filter [HubSpot contact record]. Writeback reaches the record and stays invisible until LinkedIn is ticked under Filter activity. A team that misses this reads a working sync as a failed install on day one. **How to check it worked:** - Open a HubSpot contact a rep has messaged on LinkedIn since go-live, tick LinkedIn under Filter activity, and confirm the InMail or message appears in the timeline. - In Sales Navigator, search a company you know is in HubSpot and confirm the CRM badge marks the existing records. - Have one rep who is not an admin send an InMail and check it lands. That is the test of per-user authentication, and an admin-only test will pass while every rep logs nothing. - Create a contact from Sales Navigator for somebody who is already in HubSpot under a different email, then check whether you have one record or two. That tells you how much duplicate control you need before the reps start. Agent skill for this pair: https://www.reversecontact.com/integrations-hub/skills/hubspot-linkedin.md **Field mapping:** - Contacts maps to Leads. Matched automatically, and CRM Badges in Sales Navigator show whether a lead already exists in HubSpot. An unmatched profile can create a HubSpot contact, but only if you supply an email address. - Companies maps to Accounts. Badged the same way, and a wrong match can be corrected from the account page rather than in HubSpot. - Deals maps to Opportunities. Open pipeline becomes visible inside Sales Navigator, which is also what feeds the revenue attribution report. - Owners maps to No LinkedIn equivalent. Owner data crosses so Sales Navigator knows who holds a record, and it connects HubSpot users to LinkedIn users for verification. Nothing comes back. - Does not cross: Individual mappings. There is no per-field switch, so a HubSpot property you would rather keep in HubSpot cannot be held back. - Does not cross: Anything that happened before go-live. Only new and updated data syncs once the sync is on. - Does not cross: The ROI report. LinkedIn gates it behind your account representative rather than a settings page. **What breaks:** - **It will not backfill.** Only new and updated data syncs once the sync is turned on. Getting history across means uninstalling and reinstalling the app, which is a documented procedure rather than a support workaround. Plan the switch-on date, because everything before it stays where it is. - **Field mapping is all or nothing.** Individual field mappings cannot be customised. Every supported field syncs, or none of them do. If you hold a property in HubSpot that should not leave it, this integration is not the thing that keeps it in. - **Advanced is not Advanced Plus.** The embedded Sales Navigator card runs on Advanced. Activity writeback, contact creation and record matching do not. This is the single most common surprise on this pair, and it is a contract conversation rather than a settings one. - **Install needs two admins.** Super Admin or App Marketplace access permissions in HubSpot, plus admin rights on the Sales Navigator contract. In most companies those are two different people on two different teams. **Failures people hit:** - The Sales Navigator card does not appear on the contact record. Why: Either the seat is on Sales Navigator Core, or the per-user app install never happened. Embedded Profiles needs Advanced or Advanced Plus and an install by each user, not just by the admin. Fix: Check the edition on the seat, then have that user install the LinkedIn Sales Navigator app from the HubSpot App Marketplace themselves. - InMails and messages are not reaching the timeline. Why: LinkedIn is not selected in the activity filter. The writeback arrives on the record and the timeline hides it. Fix: On the contact record, open Filter activity and tick LinkedIn. Check one rep who has definitely sent an InMail since go-live. - Writeback works for some reps and not others. Why: Activity writeback and contact creation need each user to authenticate with the CRM individually. Admin authentication does not cover them. Fix: Send the reps who are missing to Sales Navigator, Settings, CRM Settings, Connect to CRM. Confirm the admin has enabled writeback for the contract, because user authentication only appears once that is on. - A rep cannot update a HubSpot contact from Sales Navigator. Why: Sales Navigator respects HubSpot permissions. Without read and write access to that record in the CRM, the update is refused on the LinkedIn side. Fix: Fix the permission in HubSpot rather than in Sales Navigator. This is also the first thing to check when a correctly licensed Advanced Plus install appears to do nothing. - The pairing will not complete. Why: A LinkedIn Business Manager connection is already in place, or the HubSpot account is paired to a different Sales Navigator environment. Only one pairing exists at a time. Fix: Disconnect Business Manager, complete the Sales Navigator sync, then reconnect it. If a sandbox was paired for testing, release it before pairing production. - The CRM filled up with duplicate contacts. Why: Contact creation from Sales Navigator writes a new record whenever no match is found, and a rep working a list will not stop to look for the match. Fix: Require an email address and an account association on creation, keep HubSpot duplicate management running, and train reps to use Find CRM record before Create new CRM record. This is the failure mode practitioners raise most often. - Two years of LinkedIn history is missing. Why: There is no backfill. Only new and updated data syncs after go-live. Fix: Uninstalling and reinstalling the app resets the sync and sends every record again, which is documented rather than a support trick. Decide this before the first report, not after. **What practitioners say** (14 threads from 2019 to 2026, read 2026-10-11): Across those threads the native integration is almost never the answer people land on. The complaints cluster in three places, and all three are documented behaviour rather than bugs: the edition gate catches people after they have already paid, contact creation fills the CRM with duplicates, and the activity nobody can see is the reason anyone wanted this in the first place. The recommendations that follow are consistently third-party browser extensions, which tells you what the gap is worth to the people paying for it. - People buy Sales Navigator, then find out the integration needs a different edition (r/hubspot, February 2026, 2 points): https://www.reddit.com/r/hubspot/comments/1r7aafq/linkedin_sales_navigator_premium_plus/ - Contact creation is where the data quality goes (r/hubspot, February 2026, 10 points): https://www.reddit.com/r/hubspot/comments/1qdrkh5/does_a_good_linkedin_hubspot_integration_exist/ - The thing being bought is visibility, not sync (r/CRM, February 2026, 11 points): https://www.reddit.com/r/CRM/comments/1ra21l0/how_do_you_log_linkedin_messages_in_hubspot/ - The cost of not logging it shows up when somebody leaves (r/CRM, February 2026, 5 points): https://www.reddit.com/r/CRM/comments/1ra21l0/how_do_you_log_linkedin_messages_in_hubspot/ - Threads answer with a browser extension, not the native app (r/hubspot, January 2026, 6 points): https://www.reddit.com/r/hubspot/comments/1qdrkh5/does_a_good_linkedin_hubspot_integration_exist/ Sources: https://knowledge.hubspot.com/integrations/connect-hubspot-and-linkedin-crm-sync | https://www.linkedin.com/help/sales-navigator/answer/a8037044 ### HubSpot and ZoomInfo Enrichment the moment a record is created, with the two-way half sold one edition up. - Built as: Native, Marketplace app - Syncs: One way, in - Moves: Contacts, Companies, Lists - Costs to turn on: Paid add-on or licence. Setup: Hours - Requires: ZoomInfo Advanced for the native sync, Elite for two-way sync and intent fields - Full guide: https://www.reversecontact.com/integrations-hub/hubspot-integrations/hubspot-zoominfo-integration **Verdict.** Inbound Enrich is the part worth buying. A record appears in HubSpot from a form, an import or a rep typing it, and it comes back filled in, with field mapping you control so it does not flatten what someone already entered. The parts teams assume are included, two-way sync and intent fields, sit on Elite. Price this on the edition rather than on the integration, because the integration costs nothing and the edition is most of your bill. **What syncs:** - New contacts (in): Enriched on creation with title, department, seniority and contact fields, subject to your mapping. - New companies (in): Firmographics written to company properties on creation. - Existing records (in): Scheduled bulk enrichment keeps the back catalogue current rather than only new rows. - Account lists (in): With Copilot and Account Fit Score, high-fit accounts can push into HubSpot lists on a daily schedule. - Everything back to ZoomInfo (two-way): Elite only. On Advanced this integration is a one-way enrichment pipe. **Which editions carry it** (rows ZoomInfo, columns HubSpot): - Below Advanced with Free or Starter: No native sync - Below Advanced with Professional: No native sync - Below Advanced with Enterprise: No native sync - Advanced with Free or Starter: One-way enrichment - Advanced with Professional: One-way enrichment - Advanced with Enterprise: One-way enrichment - Elite with Free or Starter: Plus two-way sync and intent - Elite with Professional: Plus two-way sync and intent - Elite with Enterprise: Plus two-way sync and intent **How to connect it** (A ZoomInfo admin with the Admin Portal, and a HubSpot Super Admin or an admin carrying the CRM object permissions below.. An afternoon, and one decision at the start that is awkward to change later.): 1. Choose the connection model before anything else [ZoomInfo Admin Portal]. ZoomInfo offers a service account connection, which is the default and its preferred option, or individual user account connections. With a service account every export and every HubSpot filtering job runs through one account, which is why ZoomInfo recommends it: nobody has to troubleshoot a departed rep's connection. 2. Set the HubSpot permissions on whichever account connects [HubSpot: Settings, Users and Teams, Edit permissions]. Under CRM objects, contacts need View, Edit and Delete. ZoomInfo gives a minimum of "contacts they own" and recommends "all contacts", and the same pattern applies to companies. A service account on the minimum will quietly export less than you asked for. 3. Make the admin connection [ZoomInfo Admin Portal: Integrations, HubSpot]. Connect as a HubSpot Super Admin, or as an admin user holding the permissions above. Everything after this inherits that account's reach. 4. Decide what HubSpot Import is allowed to do, because it is on by default [Integration settings: HubSpot Import]. ZoomInfo documents this as enabled by default, letting it import and analyse information about your team and your prospects and customers from HubSpot. Whether that is fine is a question for whoever owns your data agreements, and the default answers it for them unless somebody looks. 5. Configure export mapping field by field, with behaviour per field [Integration settings: Export Mapping]. Each ZoomInfo field is paired with a HubSpot field and given a behaviour for export. This is where enrichment either respects what a rep typed or flattens it, and it is the step people skim. 6. Set the duplicate policy as an admin rather than leaving it to reps [Admin Portal: duplication settings]. The admin sets the default behaviour when an export hits a duplicate. Reps are then shown the flag during export and can update the existing record, create a duplicate, or take whichever other options you left open. Leaving all of them open means the CRM's duplicate policy is decided one rep at a time. 7. Turn it on for users last [Admin Portal: user enablement]. Only after mapping and duplicate settings are agreed. Enabling export first and configuring afterwards means the first week of exports was the test run, in production. **How to check it worked:** - Export five contacts and five companies. Companies fail separately from contacts on this pair, and testing only contacts is how that gets missed. - Export somebody you know is already in HubSpot and watch the duplicate flag appear. If it does not, the policy is not doing what you think. - Check a field a rep owns after an export, to confirm the export behaviour on that mapping is not overwriting it. - Read the HubSpot Import setting and write down who decided it, because it is on unless somebody turned it off. Agent skill for this pair: https://www.reversecontact.com/integrations-hub/skills/hubspot-zoominfo.md **Field mapping:** - A ZoomInfo contact field maps to The HubSpot contact property you choose. With an export behaviour set per field, which is where overwrite is decided. - A ZoomInfo company field maps to The HubSpot company property you choose. Configured alongside contacts and reported in the wild as populating less reliably. Test companies separately. - A record ZoomInfo matches to an existing one maps to A duplicate flag at export time. The rep then chooses from whatever options the admin left available, including creating the duplicate anyway. - Your HubSpot data maps to ZoomInfo, for analysis. HubSpot Import is enabled by default and lets ZoomInfo import and analyse information about your team, prospects and customers. - Does not cross: Anything, if the connecting account cannot see it. Permissions on the service account cap the whole integration. - Does not cross: Intent and two-way sync, below the ZoomInfo edition that carries them. Those are a contract question rather than a configuration one. **What breaks:** - **The edition is the integration.** Native HubSpot sync starts at ZoomInfo Advanced. Two-way sync and intent fields are Elite. There is no configuration that moves a feature down a tier, so the evaluation question is which edition, not which integration. - **Enrichment is a write, and writes overwrite.** Field mapping is the whole configuration here. Point ZoomInfo at a property a rep maintains and it will win. Map to dedicated ZoomInfo properties and let your workflows decide what gets promoted to the fields people trust. - **Watch what it does to source reporting.** Anything that writes to a record on creation sits close to the properties original-source attribution depends on. Keep enrichment away from source fields unless you have decided, deliberately, that it should own them. - **It needs admin on both sides.** Setting up the native integration requires admin access in HubSpot and in ZoomInfo. On the ZoomInfo side that is usually the person who owns the contract, not the person who uses it. **Failures people hit:** - Contact fields populate and company fields do not. Why: Company mapping is configured in the same place and behaves independently, and practitioners report exactly this asymmetry with mappings that look correct in the Admin Portal. Fix: Check the connecting account's permissions on companies specifically, not just on contacts, then re-test with a single company export. - Exports reach fewer records than expected. Why: The connecting account is on the minimum permission of records they own rather than all records. Fix: Raise the permission to the recommended level on both contacts and companies. ZoomInfo documents both the minimum and the recommendation, and the gap between them is silent. - Duplicates are piling up after exports. Why: The admin left the create-a-duplicate option available, and reps in a hurry take it. Fix: Restrict the duplicate options in the Admin Portal so updating the existing record is the path of least resistance. - The integration broke when somebody left the company. Why: Individual user account connections tie the integration to people. Fix: Move to the service account connection, which ZoomInfo describes as the default and preferred option for exactly this reason. - Nobody authorised ZoomInfo to read the CRM. Why: HubSpot Import is enabled by default and allows ZoomInfo to import and analyse information from HubSpot about your team and your prospects and customers. Fix: Decide it deliberately and record who decided. This is a data-sharing setting rather than a performance one, so the person to ask is not the CRM admin. - Reps complain the data overwrote their notes. Why: Export behaviour on those field mappings. Fix: Change the behaviour per field. The mapping screen allows it and the default is not always what a rep would choose. **What practitioners say** (14 threads from 2024 to 2026, read 2026-10-11): Thin and specific. There is no great debate about this pair, which fits a package that mostly works; what surfaces instead is one recurring configuration failure and a general wariness about how many third-party connectors a CRM ends up carrying. The most useful thread in the set is a single unanswered question about company fields. - Company fields are the ones that quietly do not arrive (r/hubspot, April 2025, 3 points): https://www.reddit.com/r/hubspot/comments/1jzw8gx/zoominfo_company_fields_not_mapping_to_hubspot/ - The workaround people reach for is a custom property (r/hubspot, November 2025, 3 points): https://www.reddit.com/r/hubspot/comments/1ow12ri/ughh_zoom_info_to_hubspot/ - Every connector is configuration that does not travel (r/salesforce, March 2024, 7 points): https://www.reddit.com/r/salesforce/comments/1b8bcwg/tech_stack_migration_from_hubspot_to_sfdc/ - The stack this sits in is the familiar one (r/salesforce, March 2024, 4 points): https://www.reddit.com/r/salesforce/comments/1b811h8/salesforce_hubspot_zoominfo/ - People are still asking which integration to struggle with (r/hubspot, August 2026, 3 points): https://www.reddit.com/r/hubspot/comments/1w0vt79/what_one_hubspot_integration_youre_currently/ Sources: https://university.zoominfo.com/page/integrations-implementations | https://tech-docs-library.zoominfo.com/hubspot-integration-guide.pdf ### HubSpot and Reverse Contact A whole record from an email or a domain, by four routes, and only the in-CRM one needs Data Hub. - Built as: Built on the API, Zapier, Make or n8n, MCP server - Syncs: One way, in - Moves: Contacts, Companies - Costs to turn on: Metered by usage. Setup: Hours - Requires: A Reverse Contact API key. The in-HubSpot route needs Data Hub Professional. - Full guide: https://www.reversecontact.com/integrations-hub/hubspot-integrations/hubspot-reverse-contact-integration **Verdict.** Give it an email, a domain or a profile URL and it returns the person, their current role and the company behind it on one schema, which is what makes it safe to write into HubSpot properties rather than into a notes field somebody reads later. Four routes get it there, and the one people assume is cheapest usually is not: calling the API from inside a HubSpot workflow needs Data Hub Professional, because both the webhook action and the custom code action live in that hub rather than in Sales Hub. If you already own Data Hub, that route is the cleanest thing on this page. If you do not, Clay and n8n are not the fallback, they are the answer, and they cost less than the hub upgrade by a distance. **What syncs:** - Email to full person record (in): POST /v2/enrich/persons resolves an email into identity, current role, history, education, skills and location. - Domain to company record (in): POST /v2/enrich/companies returns firmographics and metadata for a domain or company name. - Live resolution (in): The /live endpoints return a task id. Poll GET /v2/webhooks/:webhookId until status is succeeded, which is free and off the rate-limit clock. - Anything back to Reverse Contact (out): Nothing. This is a read layer. Your pipeline decides what reaches HubSpot properties. **Which editions carry it** (rows HubSpot, columns Reverse Contact): - Free CRM or Starter with A webhook action in a workflow: Not available - Free CRM or Starter with A custom code action in a workflow: Not available - Free CRM or Starter with The native Clay, Zapier or Make app: Available - Free CRM or Starter with An n8n workflow on the CRM API: Available - Sales Hub Professional, no Data Hub with A webhook action in a workflow: Not available - Sales Hub Professional, no Data Hub with A custom code action in a workflow: Not available - Sales Hub Professional, no Data Hub with The native Clay, Zapier or Make app: Available - Sales Hub Professional, no Data Hub with An n8n workflow on the CRM API: Available - Sales Hub Enterprise, no Data Hub with A webhook action in a workflow: Not available - Sales Hub Enterprise, no Data Hub with A custom code action in a workflow: Not available - Sales Hub Enterprise, no Data Hub with The native Clay, Zapier or Make app: Available - Sales Hub Enterprise, no Data Hub with An n8n workflow on the CRM API: Available - Data Hub Professional with A webhook action in a workflow: Available - Data Hub Professional with A custom code action in a workflow: Available - Data Hub Professional with The native Clay, Zapier or Make app: Available - Data Hub Professional with An n8n workflow on the CRM API: Available - Data Hub Enterprise with A webhook action in a workflow: Available - Data Hub Enterprise with A custom code action in a workflow: Available - Data Hub Enterprise with The native Clay, Zapier or Make app: Available - Data Hub Enterprise with An n8n workflow on the CRM API: Available **How to connect it** (A HubSpot Super Admin for the route that lives inside HubSpot, or whoever owns the Clay workbook or the n8n instance for the routes that do not. Plus whoever can create a Reverse Contact API key.. An afternoon once the licence question is settled. The licence question itself can take a week, which is why it is step one.): 1. Find out whether you own Data Hub, before you design anything [HubSpot: Settings, Account and Billing]. Both the webhook action and the custom code action require Data Hub Professional or Enterprise, which HubSpot sells separately from Sales Hub. A team on Sales Hub Professional has workflows and still cannot call an outside API from one. This is the most expensive surprise on the pair and it is a purchase rather than a setting. 2. Pick the route that matches what you actually own [The five routes on this page]. With Data Hub, a custom code action inside a workflow is the cleanest thing here. Without it, Clay and n8n are not a fallback, they are the answer, and both cost far less than the hub. Deciding this before you build means not discovering the gate halfway through a Flow somebody has already demoed. 3. Create the properties the enrichment is allowed to own [HubSpot: Settings, Properties]. Prefix them, so no rep ever types into one. Nothing in this build decides for you which property a value lands in, which is more work than a marketplace app and is also the reason this route never flattens a field somebody maintains by hand. 4. Store the key as a workflow secret, not in the code [HubSpot: the custom code action, Add secret]. Secrets are managed in the workflow action definition and arrive in the code as environment variables, read with process.env. The one documented ceiling is that the total length of all secret values in an action must not exceed 1,000 characters, which one API key will not trouble and three might. 5. Write the no-match branch before the one that writes [HubSpot: callback() output fields]. Reverse Contact returns null with a confidence score rather than a best guess, so a lookup that matched nobody is a normal outcome. Return a status through callback() and branch the workflow on it, rather than letting the write action run with nothing to write. 6. Keep every person-shaped variable inside exports.main [HubSpot: the custom code action]. HubSpot documents that variables declared outside exports.main may be re-used by future executions of the action, to save memory. For an enrichment action that means one contact can be served another contact's response. Only a connection you genuinely want re-used belongs outside the function. 7. Re-throw rate limits rather than swallowing them [HubSpot: the catch block]. HubSpot only retries a rate-limited call if you throw the error in the catch block in Node.js, or raise it in the except block in Python. A 429 caught and turned into a tidy no_match is a contact silently left un-enriched while the workflow reports success. 8. Test one contact and read the logs rather than the output [HubSpot: the action, Test]. The test logs report how much memory the action used and its total runtime, which are the two numbers the 20-second and 128 MB ceilings are measured against. The output tells you the enrichment worked on one contact, which was never the thing in doubt. **How to check it worked:** - Run the action on a contact whose answer you know, then on an address that resolves to nobody. The second is the test: the workflow should take the empty branch, write nothing, and spend no credits. - Read the test log for memory used and total runtime on a real contact. If a cached lookup is anywhere near 20 seconds, something other than the enrichment is slow and it will not survive a list import. - Set the secret to a deliberately wrong key once and watch what the action does with the 401. If it reports success and writes nothing, your error handling is the thing that needs fixing rather than the key. - Enrol two contacts at once rather than one, and confirm each got its own answer. That is the only test that catches the variable re-use caveat, and a single-contact test never will. Agent skill for this pair: https://www.reversecontact.com/integrations-hub/skills/hubspot-reverse-contact.md **Field mapping:** - Contact email maps to POST /v2/enrich/persons, 2 credits. The usual starting point, because a form submission carries an email and nothing else. Returns identity, the current role, history, education, skills and location on one schema, which is what makes it safe to write into typed properties. - Company domain maps to POST /v2/enrich/companies, 2 credits. Firmographics from a domain or a company name. Run it on the company record rather than once per contact: one call covers every contact associated with it. - A profile URL already on the contact maps to POST /v2/fetch/persons, 1 credit. Half the price, and unmetered from the $249 plan rather than the $699 one. If any part of your stack already captures a profile URL, routing those contacts to this call instead is the largest single saving available on this pair. - A free freshness check first maps to POST /v2/fetch/persons/check, 0 credits. Says whether a profile is cached and when it was last updated, so the workflow chooses a 1-credit read or a 2-credit live refresh on evidence. Free in credits, and one more call inside the same 20 seconds. - A workflow secret maps to process.env.RC_API_KEY. Secrets are managed in the action definition and arrive as environment variables. The total length of all secret values in one action is capped at 1,000 characters. - require("axios") in a custom code action maps to The HTTP call itself. HubSpot pre-loads axios at ^1.2.0 among twelve Node libraries, including @hubspot/api-client at ^10 and lodash, so the action needs no dependency management of its own. - The callback() function maps to Output fields the workflow branches on. The documented way to pass data back into the workflow, and Node.js only. Return a match status alongside the values, because the workflow cannot otherwise tell a miss from a hit. - Anything outbound to Reverse Contact maps to Nothing at all. This is a read layer. No HubSpot property, contact or event is sent anywhere, and there is nothing in the product to send it to. - Does not cross: An App Marketplace listing. There is none, which is consistent rather than an oversight: Reverse Contact maintains apps on Clay, Zapier and Make and nothing inside any CRM or sequencer. - Does not cross: The live endpoints, from a workflow. They answer with a task id, a custom code action has 20 seconds, and Reverse Contact documents a live job as usually seconds and possibly tens of minutes. - Does not cross: Output fields from a webhook action. The documented route for passing data back into a workflow is the callback() function in a custom code action, which is why every example on this page uses that one. - Does not cross: A business email or a direct phone number. Both are separate endpoints at 3 and 20 credits, charged only when one is found, and the email finder is asynchronous as well. **What breaks:** - **There is no app inside HubSpot.** As of 11 October 2026 Reverse Contact has no listing on the HubSpot App Marketplace. It maintains apps on Clay, Zapier and Make, so the shortest route is a step in one of those rather than anything installed in HubSpot. That is an afternoon of work, not a quarter, but it is not a click inside the CRM. - **The in-HubSpot route is a Data Hub feature.** Both the webhook action and the custom code action in workflows require Data Hub Professional or Enterprise, which HubSpot sells separately from Sales Hub. A team on Sales Hub Professional cannot call an external API from a workflow at all. Price the hub before you design around this route, because it is usually more than Clay and n8n cost together. - **Custom code has 20 seconds and 128 MB.** HubSpot caps a custom code action at 20 seconds of execution and 128 MB of memory. A cached enrichment call fits comfortably. The live endpoints, which return a task to poll, do not, which is why live resolution belongs in n8n rather than in a workflow. - **Nothing writes back on its own.** The API returns a record. Deciding which HubSpot property it lands in, and whether it may overwrite what is there, is your pipeline's job. That is more work than a marketplace app and it is also the reason this route never flattens a field a rep owns. - **The credit cost is published, the dollar rate is not.** Each call has a published credit price: 2 for a reverse lookup from an email, 1 for a cached lookup, 2 for a live refresh, free for a freshness check. What a credit costs depends on the pack or plan it came from, the full matrix sits in the dashboard rather than on the pricing page, and credit packs now expire after 3 months. Any cost model here states credits and leaves the conversion to your own plan. - **Live resolution is asynchronous.** The live endpoints hand back a task rather than a record. A HubSpot workflow webhook cannot wait for that, so either use the cached endpoint in the workflow or run the live path in n8n where you can poll. **Failures people hit:** - There is no webhook action in the workflow editor. Why: Both the webhook action and the custom code action require Data Hub Professional or Enterprise, which HubSpot sells separately from Sales Hub. Workflows themselves are a Sales Hub feature and reaching outside them is not. Fix: Price the hub against Clay and n8n before buying it. Full CRM API access is on every tier including the free one, so an external route reads and writes the same records without the upgrade. - The custom code action timed out. Why: An action must finish within 20 seconds and inside 128 MB of memory, and HubSpot returns an error on exceeding either. Fix: Use the cached endpoints, which publish a 500ms P95. Arriving near 20 seconds means you are either calling a live endpoint, which answers with a task rather than a record, or looping over records inside one action. - One contact was written another contact's job title. Why: HubSpot documents that variables declared outside exports.main may be re-used by future executions of the action, to save memory, and many objects can be enrolled at the same moment. Fix: Move every variable holding anything about a person inside exports.main. Only a connection you intend to re-use belongs outside it, which is the case the caveat was actually written for. - Some contacts were quietly left un-enriched. Why: A rate-limited call is only retried if the error is thrown. HubSpot documents that in Node.js you must throw it in the catch block, and in Python raise it in the except block. Fix: Re-throw on a 429 instead of returning a no_match. A swallowed rate limit looks exactly like a real miss in the workflow history, which is what makes this one expensive to find later. - A property a rep maintained has been overwritten. Why: Nothing in this build decides that for you. The API returns a record and the property it lands in is whichever one your action names. Fix: Write to prefixed properties only, then promote a value into a human-maintained property with a separate workflow that fires only where the human property is empty. - The workflow reports success and the property is empty. Why: Reverse Contact returns null with a confidence score rather than a best guess, so a lookup that matched nobody completes normally rather than failing. Fix: Return a match status from callback() as its own output field and branch the workflow on it. The call itself cost nothing, because every 4xx and 5xx is free. - Everything stopped at once, including the calls that were free. Why: Below 2 credits the free Check endpoints are paused too and answer 402 NO_CREDITS, because the fetch a check precedes can itself cost 2. Fix: Read quotas.workspace.credits.left from any response and alert on it. GET /v2/usage keeps answering when the checks do not, so a balance check never fails for the reason the lookup did. - An endpoint that worked last week returns nothing. Why: /v2/resolve was replaced by /v2/enrich and /v2/search/persons by /v2/search/people, with the old pair documented as live only until 13 October 2026. Fix: Open the custom code action and change the path. A workflow action is not version-controlled by default, so the only copy of that string is the one inside it, and nothing will warn you. **What practitioners say** (14 threads from 2024 to 2026, read 2026-10-11): Nobody discusses this pair by name, so the search was for the job: keeping HubSpot records current without reps typing. Two threads are worth more than the rest. One is somebody whose native enrichment matched the wrong person and could not be undone, and one is a HubSpot AMA where a customer asks for confidence scoring and provenance by name. Between them they describe the two things that separate a data layer from a tile in a marketplace. - A best guess cannot be undone, and this is what that looks like (r/hubspot, September 2025, 6 points): https://www.reddit.com/r/hubspot/comments/1njxjyw/hubspot_enrichment_input_incorrect_information/ - The recovery is a property history export, which is worth knowing in advance (r/hubspot, September 2025, 5 points): https://www.reddit.com/r/hubspot/comments/1njxjyw/hubspot_enrichment_input_incorrect_information/ - A HubSpot customer asking HubSpot for a confidence threshold (r/hubspot, September 2025, 2 points): https://www.reddit.com/r/hubspot/comments/1nk31xd/ama_hubspot_data_hub_ask_us_anything/ - Where the enrichment comes from is a question people now ask out loud (r/hubspot, July 2026, 5 points): https://www.reddit.com/r/hubspot/comments/1unpyfs/hubspot_sharing_user_data/ - The reason nobody maintains it by hand, in one sentence (r/CRMSoftware, January 2026, 10 points): https://www.reddit.com/r/CRMSoftware/comments/1qi3mwj/whats_the_best_way_to_enrich_contact_in_hubspot/ Sources: https://docs.reversecontact.com/getting-started | https://docs.reversecontact.com/guides/credits | https://docs.reversecontact.com/guides/rate-limits | https://www.reversecontact.com/delivery-method/mcp | https://www.reversecontact.com/pricing | https://developers.hubspot.com/docs/api-reference/legacy/automation/workflow-actions/custom-code-actions ### HubSpot and ClickUp The rare pair where each vendor built the half that runs inside the other. - Built as: Native, Marketplace app, Zapier, Make or n8n - Syncs: Two-way sync - Moves: Deals, Contacts, Companies, Tasks - Costs to turn on: Needs a higher plan. Setup: Minutes - Requires: HubSpot workflows for the automated direction, so Professional or above - Full guide: https://www.reversecontact.com/integrations-hub/hubspot-integrations/hubspot-clickup-integration **Verdict.** Best in class for the handover problem, and thin exactly where you would expect. ClickUp actions run inside HubSpot workflows and HubSpot actions run inside ClickUp automations, so a closed-won deal can spawn a delivery list and a status change in delivery can move the deal. Companies, contacts, deals, line items, products, tasks and tickets can all be created and linked. Custom fields are where teams fall back to Make. **What syncs:** - Deal to task or list (out): A HubSpot workflow creates ClickUp work with deal context attached. - Task status to deal (in): A ClickUp automation updates the HubSpot record when delivery moves. - Contacts and companies (two-way): Created and linked on either side, so the work item knows whose account it is. - Line items and products (out): What was sold travels with the handover, which is the point of doing this at all. - Tickets (two-way): Support work and delivery work in the same place as the revenue record. **Which editions carry it** (rows HubSpot, columns ClickUp): - Free or Starter with Free Forever: ClickUp Automations only - Free or Starter with Unlimited or Business: ClickUp Automations only - Free or Starter with Enterprise: ClickUp Automations only - Professional with Free Forever: Plus HubSpot workflows - Professional with Unlimited or Business: Plus HubSpot workflows - Professional with Enterprise: Plus HubSpot workflows - Enterprise with Free Forever: Plus HubSpot workflows - Enterprise with Unlimited or Business: Plus HubSpot workflows - Enterprise with Enterprise: Plus HubSpot workflows **How to connect it** (A ClickUp Workspace owner or admin to authenticate, and a HubSpot admin to build the workflow.. Ten minutes to connect. An hour per handover workflow you actually want.): 1. Authenticate from the ClickUp side [ClickUp: App Center, HubSpot, Manage]. Click Add to HubSpot and pick the HubSpot account in the authorisation popup. ClickUp requires a Workspace owner or admin for this, so a team lead cannot do it alone. 2. Decide which direction you are automating before you build anything [A whiteboard]. There are two engines here and they are not equivalent. A HubSpot workflow can create ClickUp work from a deal trigger; a ClickUp Automation can act in either tool and is the only one that maps custom fields. Picking the wrong one means rebuilding rather than reconfiguring. 3. Build the deal-based workflow in HubSpot [HubSpot: Workflows, Create workflow, Deal-based]. Set up triggers with Filter type Deal, then add a ClickUp action. The first time you do this you will be asked to connect the app from inside the workflow editor. 4. Point the action at a place in the ClickUp hierarchy [The ClickUp action panel]. Choose the Workspace, then an existing or new Space, Folder or Subfolder and List. Creating new ones from the workflow is possible and is how a tidy hierarchy turns into hundreds of orphan Spaces, so prefer existing ones and name the pattern now. 5. Use Deal tokens to carry the context across [The task name and description fields]. Click Deal token next to a field to inject HubSpot data such as the deal name, type and amount. This is the only route for deal data into a task created by a HubSpot workflow, because custom field mapping is not supported there. 6. Map custom fields in ClickUp Automations instead, by matching type [ClickUp: Automations]. A HubSpot field can only map to the equivalent ClickUp Custom Field type, so an email field maps to an Email custom field and nothing else. Build the field-level work here rather than in HubSpot. 7. Publish, then check what your automations do to each other [HubSpot: Review and publish, then Turn on]. An object created by a HubSpot Automation will not trigger another HubSpot Automation. A chain that assumes it will looks correct in the editor and silently stops after the first link. **How to check it worked:** - Move a test deal to the stage that fires the workflow and confirm the task lands in the List you intended, not in a newly created one. - Open the task and check the Deal tokens resolved to real values rather than to empty strings. - Change a mapped custom field in HubSpot and confirm the ClickUp field updates. If it does not, the mapping is in the wrong engine. - Deliberately chain two automations and watch the second one not fire. Knowing that is cheaper than discovering it in a live handover. Agent skill for this pair: https://www.reversecontact.com/integrations-hub/skills/hubspot-clickup.md **Field mapping:** - Deal maps to Task, List, Folder, Subfolder or Space. Deal-based triggers can create any of those five, including from a task template. - Deal name, type and amount maps to Task name and description. Carried as Deal tokens rather than as mapped fields, which is why they land as text rather than as structured values. - A HubSpot field maps to The equivalent ClickUp Custom Field. Only within ClickUp Automations, and only to a matching type: an email field maps to an Email custom field. - Task status maps to The deal or ticket record. Driven by a ClickUp Automation rather than by the HubSpot workflow, so delivery progress coming back is a separate build from work going out. - Does not cross: Custom fields, in a HubSpot workflow. ClickUp states that custom field mapping is not supported there, so the HubSpot side can create work and cannot fill it in. - Does not cross: A HubSpot field whose type has no ClickUp equivalent. Mapping is type to type with no coercion. - Does not cross: The second automation in a chain. An object created by a HubSpot Automation does not trigger another one. **What breaks:** - **Custom fields are the ceiling.** The native integration covers common objects well. Workflows that depend on custom fields are where teams move to Make, which has fuller custom-field support on the ClickUp side. Check your specific fields before you design around the native path. - **The automated half needs Professional.** Manual linking works lower down, but "when a deal closes, do this" is a workflow, and fully customisable workflows start at HubSpot Professional. On Starter you get up to 50 simple workflows and should check yours fits. - **Two automation engines, two places to debug.** Half the logic lives in HubSpot workflows and half in ClickUp automations. That is the price of both directions being native. Write down which side owns which rule before you build the second one. **Failures people hit:** - The workflow created the task but every field is empty. Why: Custom field mapping is not supported in HubSpot workflows. Only Deal tokens in the name and description carry anything across. Fix: Put the values you need into the description as tokens, and build real field mapping as a ClickUp Automation instead. - A field will not map even inside an Automation. Why: Mapping is type to type. A HubSpot email field maps only to a ClickUp Email custom field, and there is no conversion. Fix: Create the matching custom field type in ClickUp first, then map. Renaming does not help, the type does. - The second automation in a chain never fires. Why: An object created by a HubSpot Automation does not trigger another HubSpot Automation. Fix: Collapse the chain into one automation, or trigger the second step from something a person does rather than from something an automation made. - Nobody can authenticate the integration. Why: ClickUp requires a Workspace owner or admin to connect HubSpot. Fix: Get the Workspace owner to do the App Center step. It takes a minute and cannot be delegated by permission alone. - ClickUp is full of Spaces nobody meant to create. Why: The workflow action offers to create a Space, Folder or List as well as to pick one, and a trigger that fires on every deal will keep taking it. Fix: Point actions at existing Lists, and decide the naming pattern before the workflow goes live rather than after a quarter of deals have run through it. **What practitioners say** (14 threads from 2023 to 2026, read 2026-10-11): Almost nobody discusses this pair by name, so the search was for the job instead: what people do with work after a deal closes. That turns out to be a well-populated question with no settled answer, and the HubSpot marketplace listing for the ClickUp app tells its own story, sitting at 2.2 out of 5 from 72 ratings with 42 per cent of them one star. Read together, the picture is a real need, a thin native bridge and a lot of people solving it another way. - The question people actually ask is what happens after the deal is won (r/CRM, July 2025, 4 points): https://www.reddit.com/r/CRM/comments/1m1w83l/best_task_manager_for_hubspot_after_the_deal_is/ - People go looking for this pair and find no settled answer (r/hubspot, March 2023, 3 points): https://www.reddit.com/r/hubspot/comments/11sx3li/data_export_and_import_between_hubspot_and_clickup/ - The first thing to check is whether a native app exists at all (r/hubspot, March 2023, 5 points): https://www.reddit.com/r/hubspot/comments/11sx3li/data_export_and_import_between_hubspot_and_clickup/ - The tool is rarely the problem people think it is (r/hubspot, June 2026, 4 points): https://www.reddit.com/r/hubspot/comments/1u1sz1g/im_so_over_our_janky_interim_crm_is_hubspot/ - Several products, or one that does less well (r/CRM, June 2024, 3 points): https://www.reddit.com/r/CRM/comments/1d8um2f/hubspot_vs_clickup_vs_mailchimp_please_advise/ Sources: https://help.clickup.com/hc/en-us/articles/7925934313111-HubSpot-integration | https://ecosystem.hubspot.com/marketplace/apps/clickup ### HubSpot and Clay Read a filtered slice, fill the gaps, write it back, on a schedule. From Clay Growth up. - Built as: Native, Built on the API - Syncs: Two-way sync - Moves: Contacts, Companies, Deals, Lists - Costs to turn on: Needs a higher plan. Setup: Hours - Requires: Clay Growth or above, where CRM integrations start. Nothing extra on HubSpot. - Full guide: https://www.reversecontact.com/integrations-hub/hubspot-integrations/hubspot-clay-integration **Verdict.** Price the Clay plan before anything else, because CRM integrations start on Growth and the HubSpot integration documentation never mentions it. Past that, this is a loop rather than a sync and the framing matters: Lookup actions read without changing anything, while Create and Update write a result every user in the portal sees immediately. The discipline that keeps it safe is the same three rules every time: import a filtered set rather than the portal, keep blank values ignored, and exclude the properties your reps own. **What syncs:** - HubSpot to Clay (in): Lookup actions pull contacts, companies, deals or a list into a table. Read-only, so nothing in HubSpot changes. - Enrichment in between (event): Any provider, including any HTTP API, becomes a column. This is how a tool with no HubSpot app gets one. - Clay to HubSpot (out): Create and Update push real changes. Test on a handful of rows first, because there is no preview of a write at volume. - Refresh (two-way): Auto-update re-runs the table on a schedule, which is what turns a one-time backfill into a maintained field. **Which editions carry it** (rows Clay, columns HubSpot): - Free with Scheduled runs: No access - Free with CRM integrations: No access - Free with HTTP API and webhooks: No access - Free with Sync faster than daily: No access - Launch with Scheduled runs: Full access - Launch with CRM integrations: No access - Launch with HTTP API and webhooks: No access - Launch with Sync faster than daily: No access - Growth with Scheduled runs: Full access - Growth with CRM integrations: Full access - Growth with HTTP API and webhooks: Full access - Growth with Sync faster than daily: No access - Enterprise with Scheduled runs: Full access - Enterprise with CRM integrations: Full access - Enterprise with HTTP API and webhooks: Full access - Enterprise with Sync faster than daily: Full access **How to connect it** (Somebody who can authorise an app on the HubSpot portal, and whoever owns the Clay workbook. One person is often both.. Ten minutes to connect. The hour goes on deciding what to import and what to let it write.): 1. Check the Clay plan before anything else [Clay: pricing]. The plan comparison marks CRM integrations as a Growth feature, not on Free or Launch, and Growth is $446 a month on the page header. Nothing in the HubSpot integration documentation says so, so this is the step that gets skipped and the one that ends the project. 2. Build the static list before you connect [HubSpot: Lists]. Clay's import takes an optional list, and the documented behaviour without one is that every object is pulled. A static list of the records missing the field you care about is the difference between four hundred rows and the whole portal, and it sets what the run costs. 3. Connect the account from inside a workbook [Clay: workbook, + Add]. Click + Add at the bottom of a workbook, search HubSpot, then pick the account or run + Add account. Seven read scopes are mandatory and cannot be refused: contacts, companies, leads, owners and lists, plus the contact and company property schemas. 4. Leave the three custom object scopes off below Enterprise [Clay: the consent screen]. crm.schemas.custom.read, crm.objects.custom.read and crm.objects.custom.write arrive switched off, and Clay documents why: HubSpot grants them on Enterprise portals only, and authorisation stops rather than continuing without them. Switch them on below Enterprise and the connection fails outright. 5. Import the filtered slice as the table source [Clay: Import objects from HubSpot]. The object type list is read from your own portal, so your custom objects sit beside the standard ones. Point it at the list, leave Include Read Only Properties off so you get editable properties rather than every calculated field, and turn Exclude empty properties on if blanks are noise. 6. Run the read columns and look at them [Clay: Add enrichment]. Look up object, Get associated objects and Find owner all read and change nothing in HubSpot. Run the table to the end of those columns and check the values while a mistake is still free, because the next step is not reversible. 7. Write with Update keyed on the HubSpot record ID [Clay: Update object]. Update requires the HubSpot Object ID, and that requirement is what makes the write land on the existing record instead of spawning a copy. Ignore blank values is on by default and should stay on. Create belongs to records that are genuinely new. 8. Put it on Auto-update with a condition [Clay: run settings]. Auto-update re-runs the table and Only run if holds a column back until its condition is met. That pair is what turns a backfill into a maintained property, and what stops every provider re-running against rows that already resolved. Source sync is daily on every plan below Enterprise, where it is 15 minutes. **How to check it worked:** - Open three of the records you wrote to and read the property values in HubSpot against the Clay column. A write is live for every user in the portal the moment it lands, so this is the only preview there is. - Run the import twice and count the records. If the second run creates rather than updates, the write is on Create instead of Update keyed on the record ID. - Read the Added to list output on a handful of rows rather than the row status. A row can succeed with that output false, which means HubSpot took the request and declined the record. - Set the lookup Limit deliberately. It defaults to 10 and caps at 200, so an action that looks like it is missing matches may simply have stopped counting. Agent skill for this pair: https://www.reversecontact.com/integrations-hub/skills/hubspot-clay.md **Field mapping:** - Contacts maps to Look up, Create, Update object. Reading needs crm.objects.contacts.read, which is mandatory. Writing needs the contacts write scope, which is optional and on by default, so a connection made with it unticked reads perfectly and silently cannot write. - Companies maps to The same three, plus a domain switch. Keep subdomains in Company domain is off by default on Create and Update, so shop.example.com is reduced to example.com before it is written. Look up has the matching switch for its Domain filter and the two are set separately. - Deals maps to Look up, Create, Update object. The deal read and write scopes are optional and enabled by default. Choosing Deal as the object type exposes your own pipelines and their stages as mappable fields. - Leads maps to Create object, with Association Fields. Lead is the one type whose Create action associates as it creates, taking an association object type of Company or Contact, an association type, and the target object ID. - Owners maps to Find owner. By owner ID or by email, and supplying both validates the email against the owner found by ID. Clay says the ID is the more reliable input, because an email coming out of an enrichment often belongs to nobody in the portal. - Associations maps to Create association, Get associated objects. Get associated objects defaults to 20 and 20 is also the maximum, so a company with fifty contacts cannot be read in one call. - Static lists maps to Add record to list. Only lists whose membership you can edit are offered. HubSpot recalculates an active list from its own filters, so those never appear in the dropdown and the list has to be created as static first. - Custom objects maps to Every object action, Enterprise only. They appear in the object type dropdown after the standard four. The three scopes behind them are the ones HubSpot will not grant below Enterprise. - Does not cross: Activity. The action list covers objects, associations, owners and lists, and carries nothing that writes to a timeline, so an email Clay found is a property value rather than a line on the record. - Does not cross: Any marker saying a table did it. A Clay write is a property change like any other and shows in HubSpot's own property history as one. Writing to prefixed properties is how teams tell their enrichment from their reps. - Does not cross: Active list membership, which is HubSpot's to compute from the list's filters rather than anybody's to write. **What breaks:** - **Actions are billed on the attempt.** Clay bills per action rather than per result, so a provider that finds nothing still costs you. On a hard segment the effective cost per filled field is the action rate divided by your match rate, and that multiplier is the whole economics of this route. - **A write is immediately live.** Update actions change the record every user in the portal sees. There is no staging environment. The standard protection is a small test set, "ignore blank values" left on, and an explicit exclusion list for properties reps maintain. - **Importing the whole portal is the classic mistake.** Pull a filtered slice: contacts missing a title, companies with no employee count, deals in an open stage. Importing everything costs actions on rows that did not need anything and makes the write step far riskier than it needs to be. **Failures people hit:** - The HubSpot source and the object actions are not there. Why: The workspace is on Free or Launch. Clay's plan comparison marks CRM integrations as included from Growth, and nothing in the HubSpot integration documentation repeats it. Fix: Check the plan before debugging the connection. There is no partial version of this on a lower tier, so the decision is a purchase rather than a setting. - Connecting fails with an unexpected error during the app authorization process. Why: One of the three custom object scopes was switched on against a portal below Enterprise. HubSpot cannot grant them there, and the authorisation stops rather than proceeding without them. Fix: Reconnect with all three off, which is how they arrive. Reconnecting keeps whatever was enabled last time, so an Enterprise portal that already has them on holds onto them. - The List dropdown shows an error asking you to reconnect. Why: The connection does not carry the create and edit lists permission. HubSpot asks for it by default, so this is a connection somebody made with it unticked. Fix: Reconnect the account and select that scope. It is the same flow and the rest of the permissions are unaffected. - A row ran, HubSpot accepted it, and the record is not in the list. Why: Added to list came back false. Clay documents that as HubSpot taking the request and declining the record, because it is already a member or is not eligible for that list. Fix: Read the output rather than the row status. A record ID that does not exist in the portal fails the row instead, which is a different signal and a different fix. - The write created a second copy of a record that already existed. Why: Create was used where Update was meant. Create has no record ID input and no matching step, so it writes a new object every time it runs. Fix: Use Update keyed on the HubSpot Object ID for anything that came out of an import. Clay puts that ID at the top of the Look up filter list for the same reason: it is the only precise match on offer. - A populated HubSpot property came back blank after a run. Why: Ignore blank values was turned off on the Update action. With it off, a blank Clay cell is sent through and overwrites what HubSpot had. Fix: Turn it back on, and keep the properties your reps maintain out of the write entirely. It is on by default, so this is a setting somebody changed on purpose. - A company domain lost its subdomain on the way in. Why: Keep subdomains in Company domain is off by default, so shop.example.com is reduced to example.com before the write lands. Fix: Switch it on in the Create or Update action, and separately in Look up if you are filtering on a subdomain. The two switches do not follow each other. - Credits went roughly twice as far as the row count suggested. Why: Duplicate records in HubSpot arrived as separate rows and every provider ran against both. Actions bill on the attempt, so a duplicate costs exactly what a match costs. Fix: Measure the portal's duplicate rate before the first run and filter the import to the records you mean to pay for. This is the most expensive failure on this pair and all of it happens outside Clay. **What practitioners say** (14 threads from 2024 to 2026, read 2026-10-11): Nobody in these threads argues about whether the connection works. What they argue about is what should be allowed through it, and every complaint lands in one of three places: writes that were too broad, rows that should never have been imported, and activity somebody expected on a timeline and got as a property. The teams reporting it going well describe the same habits, and each of those habits is a switch Clay already ships. - A duplicate rate in the CRM is a Clay bill, not a data problem (r/CRM, April 2026, 1 points): https://www.reddit.com/r/CRM/comments/1sw7f9p/we_spent_800_month_on_clay_apollo_and_hubspot_and/ - Clay writes records, it does not log activity (r/revops, December 2025, 4 points): https://www.reddit.com/r/revops/comments/1pg7scy/need_help_setting_up_our_growth_engine/ - The people who like it limit what it is allowed to overwrite (r/MarketingAutomation, November 2025, 3 points): https://www.reddit.com/r/MarketingAutomation/comments/1ov8zgi/whats_the_best_setup_youve_seen_for_connecting/ - The pattern people land on is one table that writes, not many (r/gtmengineering, December 2025, 3 points): https://www.reddit.com/r/gtmengineering/comments/1pl0kwi/clay_question/ - The HubSpot-native alternative needs a hub most teams never bought (r/hubspot, March 2025, 3 points): https://www.reddit.com/r/hubspot/comments/1j3vcqe/ai_integration_in_hubspot_workflows/ Sources: https://university.clay.com/docs/hubspot-integration-overview | https://www.clay.com/guides/how-to-enrich-hubspot-records | https://www.clay.com/pricing | https://knowledge.hubspot.com/object-settings/create-custom-objects ### HubSpot and Slack Notifications are easy. Routing to the right channel is the part nobody built. - Built as: Native, Marketplace app - Syncs: Events only - Moves: Activities, Messages, Deals, Companies - Costs to turn on: Needs a higher plan. Setup: Minutes - Requires: HubSpot Professional or Enterprise to create a channel from a workflow - Full guide: https://www.reversecontact.com/integrations-hub/hubspot-integrations/hubspot-slack-integration **Verdict.** Install it in five minutes, then meet the gap within a week. The workflow action sends to a channel you pick at design time. There is no built-in option to send to the channel associated with the deal that triggered the workflow, even when that association exists on the record. Teams solve it with one channel per segment, or by routing through n8n and calling the Slack API directly. **What syncs:** - Workflow to channel (out): Send Slack message is a workflow action. Any trigger can fire it: score threshold, stage change, deal gone quiet. - Record to channel association (two-way): A deal or company record can be associated with a Slack channel, with per-activity-type notifications. - Channel creation (out): A workflow can create a channel and associate it with the record. HubSpot Professional or Enterprise. - Slash commands (in): Look up records and log activity from Slack, so the CRM gets updated by people who will not open it. **Which editions carry it** (rows HubSpot, columns Slack): - Free or Starter with Public channel: Notifications and associations - Free or Starter with Private, app added: Notifications and associations - Free or Starter with Slack Connect: Nothing - Professional with Public channel: Plus workflow actions - Professional with Private, app added: Plus workflow actions - Professional with Slack Connect: Nothing - Enterprise with Public channel: Plus workflow actions - Enterprise with Private, app added: Plus workflow actions - Enterprise with Slack Connect: Nothing **How to connect it** (A HubSpot admin for the app and the workflows, and whoever owns the Slack workspace for the app approval.. Twenty minutes to connect it. The rest of the day goes on deciding what should notify.): 1. Install the HubSpot app in Slack [HubSpot: Marketplace, Slack]. Standard marketplace install and a Slack authorisation. If your workspace requires admin approval for apps, that approval is the long pole rather than anything in HubSpot. 2. Add the HubSpot app to every private channel you intend to use [Slack: the channel itself]. Records can only be associated with public channels, and with private channels where the HubSpot app is already a member. A private deal room without the app in it simply will not appear in the picker, which reads as a bug and is not one. 3. Turn on personal notifications [HubSpot: Settings, Notifications, Other apps]. Toggle Slack on under How you get notified, then pick what you want under What you get notified about. This is per user rather than account-wide, so a rollout means telling people to do it rather than doing it for them. 4. Route live chat and help desk conversations to a channel [HubSpot: Connected Apps, Slack, General settings]. Under Bring conversations to Slack, switch on the inboxes whose conversations should appear. Replies can go back through the Slack thread and still log in the inbox, which is the part that makes it worth doing rather than just an alert. 5. Associate channels with the records that matter [A company or deal record, Slack card in the right sidebar]. Associate an existing channel or create one from the record, choosing visibility, a description and exactly which activity types notify. Doing this per record is deliberate: it is the only way to get a notification into the room where the deal is discussed. 6. Build the workflow notifications last, and point each one at a fixed channel [HubSpot: Workflows]. Workflows need Professional or Enterprise. The Slack action sends to a static, pre-selected channel, so if you want the message to land in the deal's own room you either use the record association above or branch the workflow once per channel. **How to check it worked:** - Associate a test deal with a private channel. If it is missing from the dropdown, the app is not in that channel. - Trigger one workflow notification and check it lands in the channel you named rather than in a default one. - Reply to a live chat from the Slack thread and confirm the reply appears in the HubSpot inbox against the same conversation. - Merge two test records where only one has a channel association, and confirm you know which association survives before you do it to a real deal. Agent skill for this pair: https://www.reversecontact.com/integrations-hub/skills/hubspot-slack.md **Field mapping:** - Workflow action maps to A fixed channel you pick. Static only. There is no option to send to the channel associated with the current record, which is the most requested thing on this pair. - Record association maps to The channel attached to that deal or company. Public channels, and private ones where the HubSpot app is a member. Activity types are chosen per association rather than globally. - Live chat and help desk conversation maps to An inbox channel. Routed per inbox, and a reply sent in the Slack thread still logs into the HubSpot inbox. - Personal notification maps to A direct message. Per user, configured by that user, and invisible to an admin who assumes they set it up for the team. - Slash command maps to A record lookup or a logged activity. The one direction that writes back, so the CRM gets updated without anybody leaving the conversation. - Does not cross: The channel associated with the record, as a workflow destination. Documented as unsupported, with branch-per-channel workflows as the workaround. - Does not cross: A channel association on a merged record, unless it was on the primary record. The association follows the primary, so pick the primary deliberately or attach the channel to it first. - Does not cross: Conversations in a Slack Connect channel with a customer. Nothing in this integration logs them. **What breaks:** - **The workflow action cannot follow the record.** The Slack workflow action sends to a static, pre-selected channel. There is no built-in option to send to "the channel associated with this deal", even with the association already on the record. This is the single most requested thing on this pair and it is not there. - **Channel creation is gated.** Using a workflow to create a Slack channel automatically requires a Professional or Enterprise subscription. Associating an existing channel by hand does not, which is the workaround at lower tiers. - **Notifications are a volume problem before they are a feature problem.** The integration will happily post every activity type you tick. A channel that fires forty times a day gets muted, and a muted channel is worse than no integration because everyone believes the alerting works. **Failures people hit:** - A private channel does not appear when associating a record. Why: The HubSpot app is not a member of it. Associations only work with public channels and private channels the app has been added to. Fix: Add the app in that Slack channel, then refresh the record. No HubSpot setting substitutes for it. - The workflow posts to the wrong room. Why: The Slack workflow action takes a static channel. It cannot resolve the channel associated with the record being processed. Fix: Use the record association for per-deal messages, or branch the workflow and give each branch a fixed channel. The second only scales to a handful of channels. - A deal lost its channel after a merge. Why: The Slack channel association comes from the primary record in a merge. Fix: Associate the channel with the record you will keep as primary before merging, or choose the record that already has it as the primary. - Notifications arrive for one person and not the team. Why: Personal notification settings are per user, under Settings, Notifications, Other apps. Fix: Tell people to turn their own on. An admin cannot do it for them, which makes this a rollout communication rather than a configuration task. - The channel is noisy and now everybody has muted it. Why: Every activity type was ticked when the channel was associated. Fix: Re-open the association and uncheck everything that is not acted on. A muted channel is worse than no channel, because the team believes alerting works. - Nothing from a shared channel with a customer is in the CRM. Why: Slack Connect conversations are not covered. Fix: There is no setting. Either keep deal discussion in an internal associated channel, or accept that the customer-facing thread is outside the record. **What practitioners say** (14 threads from 2020 to 2026, read 2026-10-11): The threads split cleanly between people asking how to get one specific event into a channel, and people asking why they should bother when the information is already in HubSpot. The first group runs into the same two walls every time: the workflow action will not follow the record, and some events cannot trigger a workflow at all. The second group is answered by where the reps actually are. - The scepticism is reasonable and has a reasonable answer (r/hubspot, February 2025, 6 points): https://www.reddit.com/r/hubspot/comments/1ilg6e3/has_anyone_tried_to_have_a_hubspot_to_slack/ - Some events cannot trigger a workflow, which caps what you can route (r/hubspot, November 2025, 4 points): https://www.reddit.com/r/hubspot/comments/1pa5fio/has_anyone_successfully_pushed_hubspot_email_open/ - The customer-facing channel is the gap, and products exist to fill it (r/hubspot, April 2025, 6 points): https://www.reddit.com/r/hubspot/comments/1k4dhkc/syncing_shared_slack_channel_conversations_with/ - The most-asked question is the simplest one, and it has been asked for five years (r/hubspot, March 2020, 4 points): https://www.reddit.com/r/hubspot/comments/fna4xg/how_to_configure_hubspot_to_post_to_slack_channel/ - Notification sprawl is the thing that kills these setups (r/Slack, August 2025, 5 points): https://www.reddit.com/r/Slack/comments/1mwigkx/head_of_product_drowning_in_linear_slack_figma/ Sources: https://knowledge.hubspot.com/integrations/manage-your-notifications-in-slack | https://community.hubspot.com/t5/CRM/Slack-notification-in-Workflows-Send-to-the-channel-associated/m-p/1177859 ### HubSpot and Salesforce Two CRMs, one connector, and an edition requirement on both sides. - Built as: Native, Marketplace app - Syncs: Two-way sync - Moves: Contacts, Companies, Deals, Activities, Custom objects - Costs to turn on: Needs a higher plan. Setup: Days - Requires: HubSpot Professional or Enterprise, and a Salesforce edition with API access - Full guide: https://www.reversecontact.com/integrations-hub/hubspot-integrations/hubspot-salesforce-integration **Verdict.** The most capable connector HubSpot ships and the one that punishes a sloppy setup hardest. Contacts, companies, deals and activities sync out of the box, and Enterprise adds up to ten custom object syncs. Selective sync, which is how you stop Salesforce flooding HubSpot, needs a Salesforce Enterprise licence and is explicitly not supported by HubSpot's own support team. Group Edition is not supported at all. **What syncs:** - Contacts and Leads (two-way): The default object, and the one where duplicate rules on the Salesforce side matter most. - Companies and Accounts (two-way): Company sync has its own settings and its own matching behaviour. - Deals and Opportunities (two-way): Stage mapping between two pipelines that were not designed together is most of the setup work. - Activities (two-way): Emails, calls and meetings, which is how each side stops looking half-empty. - Custom objects (two-way): HubSpot Enterprise only, and each direction is configurable per mapping. The HubSpot object needs at least one required field or it cannot sync at all. **Which editions carry it** (rows HubSpot, columns Salesforce): - Free or Starter with Group: Not supported - Free or Starter with Professional: Not supported - Free or Starter with Enterprise or Unlimited: Not supported - Professional with Group: Not supported - Professional with Professional: Two-way sync - Professional with Enterprise or Unlimited: Sync and selective sync - Enterprise with Group: Not supported - Enterprise with Professional: Sync and custom objects - Enterprise with Enterprise or Unlimited: All three **How to connect it** (A HubSpot user with Account Access, and a Salesforce system administrator. The Salesforce half is the long half.. A day for the connection and the first mappings. Weeks if your two pipelines were designed separately, which they were.): 1. Check the Salesforce edition before anything else [Salesforce: Company Information]. You need an edition with API access, or Salesforce Professional. HubSpot documents Government Cloud as supported and Group Edition as not supported, so a Group org ends the project here rather than at the install screen. 2. Decide who the connected user will be, and treat it as a design decision [Salesforce: Users]. Whatever that user can see is what the integration can see. HubSpot states it plainly: if the connected user cannot view the lead object, leads do not sync, and HubSpot cannot create or update leads either. A departing admin's account is the wrong choice, and swapping later requires a user with permissions equal to or greater than the old one, in the same production org. 3. Give that user the four profile permissions [Salesforce: profile, administrative permissions]. API Enabled, View Setup and Configuration, Modify All on every object you intend to sync, and Modify Metadata. Three of the four are easy to miss because the install does not fail, it just syncs less than you asked for. 4. Install the app from the HubSpot marketplace [HubSpot: Marketplace, search Salesforce]. Click Install, and tick "Yes, this will connect to a sandbox" if that is what you are doing. Getting this checkbox wrong points a production sync at test data, or the reverse. 5. Log in as the connected user [The HubSpot pop-up window]. Enter that user's Salesforce credentials rather than your own. The account you authenticate with becomes the connected user, which is why step two came first. 6. Assign the permission set the managed package adds [Salesforce: Permission Sets]. HubSpot Integration Permissions only exists after the HubSpot managed package is installed in the org, so it cannot be assigned in advance however well prepared you are. 7. Map properties to fields, and set a direction on each one [HubSpot: Connected Apps, Salesforce]. Each mapping is two-way, always Salesforce, or always HubSpot. This is where the project actually lives: stage mapping between two pipelines nobody designed together is most of the work, and a mapping set to two-way on a field each side computes differently will fight itself forever. 8. Only then decide whether you need selective sync [Salesforce: sharing settings]. It needs a Salesforce Enterprise licence, a dedicated integration user on a cloned System Administrator profile, a new role at the top of the hierarchy, organisation-wide defaults set to Private and sharing rules that expose exactly the records you want. HubSpot publishes the method and says its support team does not cover it. **How to check it worked:** - Log in as the connected user and open each object you expect to sync. Anything that user cannot see is a silent gap rather than an error. - Create a record in Salesforce and wait a quarter of an hour. The Salesforce to HubSpot sync runs every 10 to 15 minutes, so a record that has not appeared in two minutes is not evidence of anything. - Create one record with no email address and confirm it does not arrive. That is documented behaviour, and knowing it saves a day of debugging later. - Change one mapped field on each side and check which value wins. That tests your direction settings rather than the connection. Agent skill for this pair: https://www.reversecontact.com/integrations-hub/skills/hubspot-salesforce.md **Field mapping:** - Contact maps to Lead or Contact. HubSpot has no Lead object, so one HubSpot contact has to land on one side of a Salesforce distinction HubSpot does not make. Decide the rule before go-live, because this is where the duplicates come from. - Company maps to Account. Its own settings and its own matching behaviour, separate from contact sync. - Deal maps to Opportunity. Stage mapping between two pipelines designed separately is most of the configuration work on this pair. - Activity maps to Task or Event. Emails, calls and meetings, which is what stops each side looking half empty to the team that lives in the other one. - Custom object maps to Custom object. HubSpot Enterprise only. Direction is configurable per mapping and per association, and the HubSpot object must have at least one required field. - Does not cross: A record with no valid email address. HubSpot documents that these do not sync, which reads as a broken rule rather than a missing field. - Does not cross: Anything historic, if you meant to migrate rather than to sync. HubSpot points one-time moves at Smart Transfer and says to turn its syncs off if you used it before. - Does not cross: A field mapping whose Salesforce internal name changed. Mappings survive a move to a new production org only where the internal name matches on both sides. **What breaks:** - **Editions gate it on both sides.** Available on Professional and Enterprise across the HubSpot hubs. On the Salesforce side you need an edition with API access, or Salesforce Professional. Group Edition is not supported, and that is a hard stop rather than a workaround. - **Selective sync is Enterprise and unsupported.** Filtering which Salesforce accounts reach HubSpot requires a Salesforce Enterprise licence, and HubSpot states it is not supported by their Customer Support team. It also assumes deep familiarity with your Salesforce org. Budget for a consultant or accept the full sync. - **The install needs real Salesforce permissions.** Modify Metadata, Download AppExchange Packages and Customize Application. In most organisations that is a Salesforce admin doing it, on their schedule, which is usually the reason this project takes days rather than hours. - **Two systems of record is the actual problem.** The connector will faithfully sync whatever confusion exists between two pipelines nobody reconciled. Decide which side owns each object and each stage before you map a single field, because the integration will not decide it for you. **Failures people hit:** - One object syncs and another does not. Why: The connected user cannot see it. HubSpot performs every action through that user's permissions, so an object outside their profile is invisible in both directions. Fix: Log in as the connected user and look. Then add Modify All on that object to their profile rather than widening the integration settings. - Everything broke after somebody changed the connected user. Why: The replacement has narrower permissions, or belongs to a different Salesforce production org. Fix: Give the new user permissions equal to or greater than the old one, in the same org. Treat the connected user as infrastructure rather than as somebody's login. - Records sync once, then stop. Why: With selective sync, a record has to keep meeting the sharing rule. HubSpot warns specifically that records the integration itself creates in Salesforce will stop syncing unless they also match the criteria. Fix: Write the sharing rule so records created by the integration satisfy it, then test with a form submission rather than with a hand-made record. - A record never arrives in HubSpot at all. Why: No valid email address. HubSpot documents that those do not sync. Fix: Check the email field before suspecting the mapping. If you need the record anyway, it has to arrive by another route. - The sync looks slow or stuck. Why: Salesforce to HubSpot runs on a cycle of roughly 10 to 15 minutes. It is not instant and is not supposed to be. Fix: Wait a cycle before investigating. If it is still missing after that, go to the connected user's permissions first. - Salesforce API limits are being eaten. Why: HubSpot sets its API usage from your Salesforce limit, and a single contact sync can take up to four API calls per record, varying with what changed. Fix: Size the limit against your Salesforce allowance rather than against record count, and use an inclusion list or selective sync to stop syncing records nobody needs. - Custom objects will not sync. Why: Custom object sync is HubSpot Enterprise only, and the HubSpot object needs at least one required field. Fix: Check the tier first, then the required field. Both are cheaper to check than the mapping screen is to debug. - Field mappings disappeared after a Salesforce migration. Why: Mappings survive a move to a new production org only where the Salesforce field keeps the same internal name. Fix: Match internal names before the cutover, or plan to rebuild the mappings and budget for it. **What practitioners say** (14 threads from 2023 to 2026, read 2026-10-11): The threads are not really about the integration. They are about running two CRMs, which is what this integration makes possible and does not make advisable. The practitioners who have lived with it describe the same three things: an object model that does not line up, a configuration surface big enough to drift on its own, and a dependency on one vendor's uptime. Nobody in these threads regrets connecting the two systems; several regret having two. - The object models do not line up, and that is the whole story (r/salesforce, August 2023, 14 points): https://www.reddit.com/r/salesforce/comments/1647ajk/questions_salesforce_and_hubspot_integration/ - The real cost is two systems of record, not the connector (r/salesforce, August 2026, 24 points): https://www.reddit.com/r/salesforce/comments/1vfsw8e/hubspot_x_salesforce_hellscape/ - The configuration drifts, and the logs do not always say who moved it (r/salesforce, August 2026, 5 points): https://www.reddit.com/r/salesforce/comments/1vfsw8e/hubspot_x_salesforce_hellscape/ - The app itself can go missing, and the answer is the status page (r/hubspot, September 2026, 12 points): https://www.reddit.com/r/hubspot/comments/1wp2hp3/salesforce_integration_gone/ - A consulting niche exists purely for this one integration (r/hubspot, September 2024, 5 points): https://www.reddit.com/r/hubspot/comments/1fok09r/hubspot_salesforce_integration_activities_sync/ Sources: https://knowledge.hubspot.com/salesforce/install-the-hubspot-salesforce-integration | https://www.hubspot.com/salesforce-selective-sync | https://knowledge.hubspot.com/salesforce/manage-your-salesforce-integration-settings | https://knowledge.hubspot.com/salesforce/set-up-and-use-salesforce-custom-object-sync ### HubSpot and Apollo Records both ways, sequence activity logged, and a six-hour window you should not miss. - Built as: Native, Marketplace app - Syncs: Two-way sync - Moves: Contacts, Companies, Deals, Activities, Lists - Costs to turn on: Needs a higher plan. Setup: Hours - Requires: Apollo Basic or above. The free plan excludes CRM integrations. - Full guide: https://www.reversecontact.com/integrations-hub/hubspot-integrations/hubspot-apollo-integration **Verdict.** The broadest single connector in this directory: contacts, accounts and deals moving both ways, sequence activity landing on the HubSpot timeline, and HubSpot lists feeding Apollo for targeting. The thing to know before you switch it on is the configuration window. After you enable the integration on a paid plan there is a six-hour period to set sync settings and map fields, after which syncing enables itself. Turn it on at the start of a working day. **What syncs:** - Contacts and accounts (two-way): Push from Apollo into HubSpot with mapped fields, and pull HubSpot records into Apollo. - Deals (two-way): Opportunity data moves both ways, so Apollo can target on pipeline state. - Sequence activity (out): Sends, opens and replies log to the HubSpot contact timeline as calls, emails, meetings, tasks and notes. - HubSpot lists (in): Lists feed Apollo for targeted prospecting, which is the direction teams forget exists. **Which editions carry it** (rows Apollo, columns HubSpot): - Free with HubSpot CRM: Not included - Free with HubSpot Data Enrichment: Not included - Basic or above with HubSpot CRM: Two-way CRM sync - Basic or above with HubSpot Data Enrichment: Enrichment only **How to connect it** (An Apollo admin and a HubSpot Super Admin. Each rep who wants their own records attributed to them links their own HubSpot credentials afterwards.. The clock is six hours and it starts the moment you authorise, so do this when you have the afternoon.): 1. Choose which integration you are authorising [Apollo: Settings, Integrations, HubSpot]. Apollo offers two: HubSpot CRM for a full sync, and HubSpot Data Enrichment for enrichment only. They are different products behind one button, and picking the full sync because it sounds more capable is how prospecting data ends up in a CRM nobody agreed to put it in. 2. Know that a six-hour timer just started [Nowhere. It is not shown as a countdown]. On a paid Apollo plan, enabling the integration opens a six-hour window to configure sync settings and map fields. You cannot manually pull records during it, and when it expires syncing switches itself on. Settings remain editable afterwards, but the first sync will have run on whatever you had at hour six. 3. Set the push conditions before the timer runs out [The HubSpot integration: Edit Conditions]. You can push all new contacts, or restrict by contact stage, email verification status or a custom field. The verification condition is the one worth using: it is the difference between enriching your CRM and filling it with unverified prospecting data. 4. Set the source field deliberately [The contacts sync settings]. Apollo writes a source onto every contact it pushes and defaults it to Apollo. You can point it at a different field, and if that field is a picklist you choose the value. This is your attribution, so decide it rather than inheriting it. 5. Decide how ownership is assigned [Per user, in Apollo]. Ownership of a pushed contact depends on whether the person pushing has linked their own HubSpot credentials in Apollo. Without that link, records land under whatever the shared authentication produces, which is usually one admin owning everything. 6. Map fields, then check the queue rather than the records [The integration: Contacts, Push]. Queue activity shows what is waiting, Sync history shows the runs, and Error logs shows what failed with a retry. That is where a failed push appears, not on the contact. **How to check it worked:** - Push one contact manually and check which HubSpot user owns it. That tells you whether credential linking is set up before 400 contacts arrive under an admin. - Check the source property on that contact. If it says Apollo and you wanted something else, the source field is still at its default. - Set a stage restriction, then deliberately push a record that fails it. A manual push ignores sync settings entirely, which is worth seeing once. - Open Error logs after the first scheduled run rather than waiting for somebody to report a missing contact. Agent skill for this pair: https://www.reversecontact.com/integrations-hub/skills/hubspot-apollo.md **Field mapping:** - An Apollo contact maps to A HubSpot contact. Pushed on your conditions, or all of them if you set none. - Apollo, as a value maps to The source property you choose. Defaults to Apollo. Picklist fields require you to select the value as well as the field. - The pushing user maps to HubSpot record ownership. Determined by whether that person has linked their own HubSpot credentials in Apollo, rather than by a setting on the integration. - A manual push maps to HubSpot, unconditionally. Overrides every sync setting, including stage restrictions and the other push limits you configured. - Push outcomes maps to Queue activity, Sync history and Error logs. Three separate views, and the only place a failed push is visible. - Does not cross: Anything, on the Apollo free plan. CRM integrations are excluded from it. - Does not cross: The sync conditions, when somebody pushes by hand. A manual push bypasses all of them by design. - Does not cross: Records you wanted to pull during the first six hours. Manual pulls are blocked for the length of the configuration window. **What breaks:** - **Six hours to configure.** On a paid plan, enabling the integration starts a six-hour window to configure sync settings and map fields before syncing is automatically enabled. Whatever the defaults are at the end of that window is what runs. Do not enable it on a Friday afternoon. - **The free plan does not include it.** CRM integrations are excluded from Apollo's free tier. Basic, at $49 per user per month on annual billing, is the entry point for this pair. - **It needs Super Admin in HubSpot.** Plus admin or CRM edit permissions in Apollo. Standard for a two-way connector, and worth lining up before the six-hour clock starts. - **Pushing prospecting data into the CRM is a decision.** A two-way sync between a prospecting database and your system of record means Apollo can create records. Decide what qualifies for creation before you map anything, or the CRM fills with people nobody chose to contact. **Failures people hit:** - Syncing started before anybody was ready. Why: The six-hour configuration window expired and Apollo enabled syncing automatically. Fix: Adjust the settings now, in Settings, Integrations, HubSpot. The settings stay editable; what you cannot undo is the first run. - Contacts arrived that should have been filtered out. Why: Somebody pushed them manually. Apollo documents that a manual push overrides the sync settings, including stage restrictions. Fix: Treat the conditions as a default rather than a control, and train the team on what the push button on a profile actually does. - One admin owns every contact Apollo created. Why: The pushing users have not linked their personal HubSpot credentials in Apollo, so ownership falls to the shared authentication. Fix: Have each rep link their own credentials. Reassigning afterwards is possible and tedious. - Every Apollo contact has the same source. Why: The source field defaults to Apollo and was never changed. Fix: Point it at the field your reporting uses, and pick the picklist value if that field is a picklist. - A push silently did nothing. Why: It failed, and the failure lives in the integration views rather than on the record. Fix: Open Error logs under Contacts or Accounts, then Push, and retry from there. Queue activity shows what is still waiting. - The integration is not available at all. Why: Apollo's free plan excludes CRM integrations. Fix: That is a plan question. The extension still works for manual research in the meantime. **What practitioners say** (14 threads from 2024 to 2026, read 2026-10-11): Few people discuss this pair directly, so the search widened to what teams do about enrichment and prospecting data reaching HubSpot. The recurring complaint is duplicates from several sources writing the same records, and the recurring instinct is to consolidate tools rather than to configure the ones they have. Both are relevant here, because this integration offers exactly the controls that prevent the problem and defaults to not using them. - The duplicate problem comes from several sources, not one bad tool (r/CRM, April 2026, 4 points): https://www.reddit.com/r/CRM/comments/1sw7f9p/we_spent_800_month_on_clay_apollo_and_hubspot_and/ - The practical fix somebody landed on was limiting the source side (r/hubspot, May 2025, 4 points): https://www.reddit.com/r/hubspot/comments/1kk0f9p/help_apollo_to_hubspot_automation/ - The reason people look at this at all is a stale database (r/CRMSoftware, January 2026, 10 points): https://www.reddit.com/r/CRMSoftware/comments/1qi3mwj/whats_the_best_way_to_enrich_contact_in_hubspot/ - Teams add tools faster than they integrate them (r/hubspot, April 2026, 13 points): https://www.reddit.com/r/hubspot/comments/1sgutfg/what_hubspot_integrations_are_actually_worth_it/ - The consolidation instinct is real and goes the other way (r/microsaas, April 2026, 18 points): https://www.reddit.com/r/microsaas/comments/1sthi1r/i_replaced_apollo_clay_instantly_hubspot_with_one/ Sources: https://knowledge.apollo.io/hc/en-us/articles/19745130546573-HubSpot-Integration-Overview | https://knowledge.apollo.io/hc/en-us/articles/4416606988941-Configure-HubSpot-Sync-Settings ### HubSpot and n8n The cheapest way out of the Data Hub trap, and the trigger needs a public app. - Built as: Zapier, Make or n8n, Built on the API - Syncs: Two-way sync - Moves: Contacts, Companies, Deals, Custom objects - Costs to turn on: Metered by usage. Setup: Hours - Requires: An n8n instance and a HubSpot service key. The trigger needs a registered public app. - Full guide: https://www.reversecontact.com/integrations-hub/hubspot-integrations/hubspot-n8n-integration **Verdict.** HubSpot gives away the API and charges for calling out of it, which is the single fact that shapes this pair. Workflows that reach an external service need Data Hub Professional, and n8n sits on the other side of that wall: it reads and writes a free HubSpot CRM perfectly well, so the automation that HubSpot would gate behind a hub upgrade becomes an instance you already run. The surprise is on the trigger rather than the actions. Writing to HubSpot needs a service key; reacting to a HubSpot change needs the trigger node, and that means registering a public app in a developer account even for a workflow only you will use. **What syncs:** - Contacts (two-way): Create or update, delete, get, get all, get recently created or updated, and search. - Companies and deals (two-way): Full create, update, delete, search and recently-modified reads on both. - Custom objects (two-way): Through the HTTP Request node on the same credential, which is how anything the node does not list gets done. - Engagements and tickets (two-way): Engagements create, delete and read; tickets create, update, delete and read. - Form submissions (two-way): Read all fields from a form, and submit data to one. - Record changes out to n8n (out): The HubSpot Trigger node on HubSpot's webhooks API, which requires a registered public app and the developer API key. **Which editions carry it** (rows HubSpot, columns n8n): - Free or Starter with Per 10 seconds, per app: 100 calls - Free or Starter with Per day, per account: 250,000 calls - Free or Starter with Per day, with limit increases: plus 1,000,000, twice at most - Professional with Per 10 seconds, per app: 190 calls - Professional with Per day, per account: 625,000 calls - Professional with Per day, with limit increases: plus 1,000,000, twice at most - Enterprise with Per 10 seconds, per app: 190 calls - Enterprise with Per day, per account: 1,000,000 calls - Enterprise with Per day, with limit increases: plus 1,000,000, twice at most **How to connect it** (A HubSpot super admin, or a user with Developer tools access, plus whoever owns the n8n instance.. Twenty minutes for the node. An afternoon the first time you need the trigger.): 1. Decide first whether you need the trigger at all [Design, before any settings page]. The HubSpot node needs one service key. The HubSpot Trigger node needs a registered public app with four separate values. If a HubSpot form or a schedule can start the workflow instead, you have just saved the longest step on this page. 2. Create a service key for the HubSpot node [HubSpot: Development, Keys, Service Keys]. Also reachable through Settings, Account Management, Integrations, Service Keys. Name it, pick the scopes, confirm with Update, then Create. Open the key's detail page, click Show, and paste the value into the App Token field in n8n rather than into a field called service key. 3. Register a public app if the trigger is in the design [HubSpot developer account: Apps]. Get the developer API key from Apps, then Create app. The Auth tab carries the App ID, Client ID and Client Secret, all three of which n8n asks for. Paste n8n's OAuth Redirect URL into the app as its Redirect URL before you click Create app. 4. Give the app the scopes the trigger needs [HubSpot: the app's Auth tab, Scopes]. n8n publishes a recommended starting set rather than a minimum, and the oauth scope is on it alongside the CRM object scopes. A scope added after the app is created needs the connection re-authorised, so overshoot slightly rather than iterating. 5. Make the n8n instance reachable over valid HTTPS [Your host]. HubSpot has to reach n8n for a webhook to fire, so a self-hosted instance needs a public endpoint and a certificate that validates. Practitioners on r/n8n report a Cloudflare tunnel as the fix when a self-hosted instance looked correctly configured and simply never received anything. 6. Activate one trigger, and only one [n8n: the HubSpot Trigger node]. HubSpot allows one webhook, so n8n registers one when the trigger is activated. Activating a second trigger stops the first one working. Fan out inside a single workflow instead of running two trigger nodes. 7. Use the HTTP Request node for anything the node does not list [n8n: HTTP Request]. The HubSpot node covers contacts, contact lists, companies, deals, engagements, forms and tickets. Custom objects, file uploads and newer endpoints are not on that list, and n8n's own documentation points at the HTTP Request node on the same credential for them. 8. Watch the account-wide daily limit, not your own workflow [HubSpot: Development, Monitoring, API call usage]. The burst limit is per app and the daily limit is shared across every app in the account. The page lists usage for apps you built and third-party apps you installed, which is the only place the competition between them is visible. **How to check it worked:** - Run the HubSpot node once against a single contact before building anything. A wrong scope fails here in a way that is readable, and fails inside a long workflow in a way that is not. - Activate the trigger, change a record, and watch for the execution. Then deactivate it, activate a second trigger, and confirm the first one has stopped: that is the documented single-webhook behaviour and it is better to see it than to meet it. - Check the API call usage page after a full run and compare it against your daily allowance. If an n8n backfill consumed most of it, the thing that breaks next is another integration rather than this one. - If you built a public app, re-authorise the credential after adding any scope. A scope that is present in the app and absent from the connection fails with a permissions error that names the endpoint rather than the scope. Agent skill for this pair: https://www.reversecontact.com/integrations-hub/skills/hubspot-n8n.md **Field mapping:** - Contact maps to Create or update, delete, get, get all, get recent, search. Create and update are one operation, so the node will not tell you which of the two it did. If that matters, search first and branch. - Contact list maps to Add contact to a list, remove a contact from a list. Static lists only in practice, because an active list's membership is computed from its filters rather than written. - Company maps to Create, delete, get, get all, get recent created, get recent modified, search by domain, update. Search is by domain specifically rather than a general property search, which is a narrower operation than the contact one of the same name. - Deal maps to Create, delete, get, get all, get recent created, get recent modified, search, update. The most complete resource on the node. Pipelines and stages are properties here rather than their own operations. - Engagement maps to Create, delete, get, get all. No update. An engagement that needs changing is deleted and recreated, which changes its ID and anything pointing at it. - Form maps to Get all fields from a form, submit data to a form. Submitting to a form is a useful way into HubSpot's own automation, because a form submission can start a HubSpot workflow that an API write does not. - Ticket maps to Create, delete, get, get all, update. The only Service Hub object on the node, and the reason some teams run this pair without a sales use case at all. - Custom objects and everything else maps to HTTP Request node, same credential. n8n's own answer when an operation is not supported. It costs the convenience of the node and nothing else, because the authentication is already in place. - Does not cross: A file uploaded through a HubSpot form. HubSpot's webhook sends text fields, so the file has to be fetched with a separate API call from n8n rather than read out of the payload. - Does not cross: A second simultaneous trigger. HubSpot allows one webhook per app, and activating another one silently stops the first. - Does not cross: Anything from a HubSpot workflow reaching out to n8n without Data Hub. The webhook action in a HubSpot workflow needs Data Hub Professional, which is the gate this whole pair exists to route around. **What breaks:** - **The trigger is a different credential from the node.** n8n documents the service key, entered as App Token, as the recommended method for the HubSpot node, and the developer API key for the HubSpot Trigger. The trigger method needs a public app with a client ID, client secret, app ID and developer API key, registered in a HubSpot developer account. Teams who expected to paste one token and start listening lose an afternoon here. - **Service keys are in public beta.** n8n notes that service keys are in public beta and may change, that private apps created in the UI are now legacy, and that HubSpot has deprecated the plain API key with a migration guide. Three auth methods in flight at once is a reason to write down which one each workflow uses, because the one that breaks will be the one nobody documented. - **The daily API cap is shared across every app.** HubSpot allows 190 requests per 10 seconds per app and a daily cap shared across the whole account: 625,000 on Professional and 1,000,000 on Enterprise. An n8n workflow that loops row by row competes with your native connectors for the same allowance, and the symptom of exhausting it is somebody else's integration returning 429. - **Somebody has to own the instance.** This is not a documented limit and it is the one that actually ends these projects. A self-hosted instance carries credentials, upgrades and uptime. n8n must also be reachable by HubSpot for webhook triggers to fire at all, which rules out a laptop and means a real host. Decide who owns it before you build on it. **Failures people hit:** - The first trigger stopped firing when a second one was activated. Why: HubSpot allows one webhook. n8n registers it on activation, and activating another trigger takes the registration with it. Fix: Run one trigger node and branch inside the workflow. If two workflows genuinely need the same event, have the first one call the second. - Authentication credentials not found. This API supports OAuth 2.0 authentication. Why: A developer API key was used against a test account. HubSpot documents that developer API keys do not work for test accounts. Fix: Use OAuth or a private app token for anything pointed at a test account. This is also worth knowing before you build the whole workflow against a sandbox. - A self-hosted instance never receives the webhook. Why: HubSpot has to reach n8n over a valid HTTPS endpoint. An instance behind a self-signed certificate or no public address looks correctly configured from inside n8n and receives nothing. Fix: Put it behind a real certificate. Practitioners on r/n8n report a Cloudflare tunnel fixing exactly this after every guide had been followed. - A form submission arrived without the file somebody uploaded. Why: HubSpot's webhook sends text fields. The file is not in the payload and never was. Fix: Call HubSpot's API from n8n with the HTTP Request node to fetch the file URL. That call needs a token, so the webhook alone will not do it. - OUTPUT_VALUES_TOO_LARGE from a HubSpot custom code action. Why: A string data output exceeded 65,000 characters. This is the HubSpot side of the pair rather than the n8n side, and it is the usual reason a working action starts failing on one record. Fix: Truncate or split the output. Remember the harder ceilings on the same action: 20 seconds of runtime, 128 MB of memory, and a maximum of 50 properties passed in. - This action has been paused to stay within the configured rate limit. Why: Rate limiting was turned on for a HubSpot custom code action. It is off by default, and when on it also delays every action after it in the workflow. Fix: Read the workflow action log, which names the resume time. If the limit is not what you wanted, it is configured per action under Configure rate limit rather than globally. - A retry never happens after a 429. Why: HubSpot only retries a custom code action if the error is thrown. Catching it quietly means HubSpot treats the execution as a success. Fix: Throw the error in the catch block in Node.js, or raise it in the except block in Python. Swallowing it is the behaviour that turns a transient limit into missing data. - The node does not have the operation the workflow needs. Why: The HubSpot node covers seven resources and no custom objects. That is the documented scope of it rather than a gap to work around. Fix: Use the HTTP Request node on the same credential, which is n8n's own recommendation. Everything HubSpot exposes is reachable that way, and the authentication is already configured. **What practitioners say** (14 threads from 2025 to 2026, read 2026-10-11): Two kinds of thread, and they disagree productively. In r/n8n people are debugging a specific thing, and it is nearly always the webhook rather than the node: self-hosted instances that look right and receive nothing, payloads missing the file somebody uploaded, scopes that match the documentation and still fail. In r/hubspot the same question gets a different answer, which is to learn HubSpot workflows and custom code actions instead and stop bolting on tools. Both are right, and which one applies to you is decided by whether you own Data Hub. - The HubSpot half is not straightforward and people say so plainly (r/n8n, February 2025, 2 points): https://www.reddit.com/r/n8n/comments/1iy8ciw/has_anyone_successfully_connected_free_hubspot/ - The fix for a silent webhook is usually the certificate (r/n8n, February 2025, 2 points): https://www.reddit.com/r/n8n/comments/1iy8ciw/has_anyone_successfully_connected_free_hubspot/ - The webhook payload is text, so a file needs a second call (r/n8n, September 2025, 2 points): https://www.reddit.com/r/n8n/comments/1noelrz/hubspot_and_n8n/ - The node is limited on purpose, and people hit the edge quickly (r/n8n, May 2025, 2 points): https://www.reddit.com/r/n8n/comments/1kt6de9/is_anyone_having_success_with_hubspot_workflows/ - The r/hubspot answer is to not use n8n at all (r/hubspot, January 2026, 6 points): https://www.reddit.com/r/hubspot/comments/1qmqukh/zapier_vs_make_vs_n8n_longterm_specialization/ Sources: https://docs.n8n.io/integrations/builtin/app-nodes/n8n-nodes-base.hubspot | https://docs.n8n.io/integrations/builtin/credentials/hubspot | https://docs.n8n.io/integrations/builtin/trigger-nodes/n8n-nodes-base.hubspottrigger | https://developers.hubspot.com/docs/developer-tooling/platform/usage-guidelines | https://developers.hubspot.com/docs/api-reference/legacy/automation/workflow-actions/custom-code-actions ### HubSpot and Zapier The widest surface on this site, metered by the minute your plan polls at. - Built as: Zapier, Make or n8n, Marketplace app - Syncs: Two-way sync - Moves: Contacts, Companies, Deals, Custom objects - Costs to turn on: Metered by usage. Setup: Minutes - Requires: A Super Admin in HubSpot and a Zapier plan sized to your task volume. No HubSpot upgrade. - Full guide: https://www.reversecontact.com/integrations-hub/hubspot-integrations/hubspot-zapier-integration **Verdict.** This is the widest integration surface in the directory: 27 triggers and 66 actions against contacts, companies, deals, tickets, line items and custom objects, on a HubSpot free plan if that is what you hold. What you are buying is not access, it is latency and throughput. Polling runs every 15 minutes on Zapier's free plan and every minute on Team, tasks are counted on successful actions rather than on polls, and the one HubSpot limit that will actually find you is the shared daily cap of 625,000 requests on Professional. Zapier's own help page quotes a different daily figure, so size against HubSpot's published numbers rather than Zapier's. **What syncs:** - Contacts, companies and deals (two-way): Create, update, find and find-or-create on each, in either direction. The core of what most teams build here. - Custom objects (two-way): Create, update, find and delete, which is more than several native connectors in this directory manage. - Tickets and line items (two-way): Full create, update and search. Useful where the CRM is doing service work as well as sales. - List membership (two-way): Static lists only; active lists do not appear in the dropdown, and the contact has to exist first. Needs Marketing Hub Starter or above. - Property change events (out): Triggers on a named property changing, which is how most useful Zaps start. - Anything in under a minute (event): Not on a poll. The fastest documented interval is one minute, on Team and Enterprise. **Which editions carry it** (rows Zapier, columns HubSpot): - Free with Free or Starter: Core objects, default polling - Free with Professional: Plus the paid-plan triggers - Free with Enterprise: Plus the paid-plan triggers - Professional with Free or Starter: Plus polling control - Professional with Professional: Both - Professional with Enterprise: Both - Team or Enterprise with Free or Starter: Plus polling control - Team or Enterprise with Professional: Both - Team or Enterprise with Enterprise: Both **How to connect it** (A HubSpot Super Admin. Zapier requires that permission level, so a marketing ops manager without it cannot connect the app.. Five minutes to connect. The rest depends on how many Zaps you are about to not document.): 1. Check you have Super Admin, and that nobody else has already connected [HubSpot: Users and Teams]. Zapier documents Super Admin as the requirement, and separately that only one app connection to a HubSpot account can exist at a time. Connecting a second invalidates the first, so a colleague quietly reconnecting is enough to break every Zap you own. 2. Add the connection from Zapier, not from HubSpot [Zapier: Apps, Add connection]. Search for HubSpot, click Add connection, log in in the new tab and grant access. There is no install on the HubSpot side, which is also why nothing in HubSpot tells you it exists. 3. Pick an instant trigger if one exists for your event [The Zap editor: trigger step]. HubSpot offers both. Deal Property Change is instant; New Company and most of the recently-created triggers poll. Instant means the event arrives when it happens rather than on a schedule, and choosing it costs nothing. 4. Set the polling interval if you are on a paid Zapier plan [Zap editor: Advanced settings]. Polling interval control is unavailable on Zapier Free and available on Professional, Team and Enterprise. The intervals on offer depend on both your plan and the trigger app, and the setting is hidden entirely for instant triggers because they do not poll. 5. Map fields with the date behaviour in mind [The Zap editor: action step]. HubSpot wants dates as UNIX timestamps, and Zapier documents that date and time values sent to HubSpot are rounded down to UTC midnight. If a time of day matters to your process, it is gone by the time the record is written. 6. Decide how contacts created this way will be attributed [Before the first Zap goes live]. A contact created by a Zap arrives with Zapier as its source rather than the form or campaign that produced it. Practitioners report losing original-source reporting exactly this way, and the fix is to decide now whether the native form or the Forms API should be creating the record instead. **How to check it worked:** - Fire the trigger and time the gap. If it is minutes rather than seconds you are on a polling trigger, which may be fine and should be deliberate. - Send a date with a time on it and read it back in HubSpot. It will be UTC midnight. - Try the Add Contact to List action and look for your list. If it is missing, it is an active list, and only static lists appear. - Create one test contact through the Zap and check its original source property before you build twenty more Zaps on the same pattern. Agent skill for this pair: https://www.reversecontact.com/integrations-hub/skills/hubspot-zapier.md **Field mapping:** - Contacts, companies, deals, tickets, line items maps to Create, update, find or find-or-create. In either direction, with custom objects included, which is more than several native connectors manage. - A date or date-time value maps to A HubSpot date property. Sent as a UNIX timestamp and rounded down to UTC midnight. Time of day does not survive the trip. - Add Contact to List maps to A static list only. Active lists are membership rules rather than containers, so they do not appear in the dropdown and cannot be written to. - A named property changing maps to An instant trigger. Deal Property Change fires on the event. Most other triggers poll, so the choice of trigger is the choice of latency. - A contact created by a Zap maps to A record sourced to Zapier. Original source attribution follows the thing that created the record, which is now the automation rather than the campaign. - Does not cross: Active lists, as a destination. Only static lists are writable. - Does not cross: The time of day on any date value. It is rounded down to UTC midnight on the way in. - Does not cross: A second Zapier connection to the same HubSpot account. Adding one invalidates the existing connection rather than running alongside it. **What breaks:** - **Latency is a line item.** Polling intervals are 15 minutes on the free plan, 2 minutes on Professional and 1 minute on Team and Enterprise, and a Zap can never poll faster than the greater of its plan minimum and the app minimum. Nothing you configure in HubSpot changes this. If the use case is speed to lead, read the interval as part of the price, because a 15 minute poll on a new inbound form is not speed to lead by any definition. - **Dates round down to UTC midnight.** Zapier sends dates to HubSpot as UNIX timestamps and rounds date and time values down to UTC midnight, so a value entered west of UTC can land in HubSpot a day early. It is documented and it will not be fixed by mapping, so normalise the date in a formatter step before the HubSpot action. - **One connection per HubSpot account.** Zapier allows a single HubSpot app connection per account at a time, and connecting another invalidates the previous one. In a team where two people have each wired up their own Zaps, the second person to reconnect silently breaks the first person's work, and nothing announces it. - **The daily cap is shared, the burst limit is not.** HubSpot allows 190 requests per 10 seconds per app, and a daily cap of 625,000 requests on Professional and 1,000,000 on Enterprise that is shared across every app on the account. A chatty Zap therefore spends an allowance your native connectors also need, and the symptom is somebody else's integration returning 429. Zapier's help page quotes 650,000 a day for Professional, which does not match HubSpot's published figure; plan against HubSpot's. **Failures people hit:** - Every Zap broke at once and nothing changed on your side. Why: Somebody added a second Zapier connection to the same HubSpot account, which invalidates the previous one. Fix: Reconnect, then agree who owns the connection. There is no way to run two, so this is a people problem with a technical symptom. - Dates arrive a day early, or at midnight. Why: HubSpot takes dates as UNIX timestamps and Zapier rounds date-time values down to UTC midnight. Fix: Store the precise value in a separate property if you need it. Nothing in the mapping screen prevents the rounding. - The list you want is missing from Add Contact to List. Why: It is an active list. Only static lists appear. Fix: Write a property instead and let an active list pick the contact up by rule, which is what active lists are for. - The Zap is slow and it is not Zapier's fault. Why: A polling trigger on an account without polling control, or an app-imposed minimum interval. Fix: Switch to an instant trigger if one covers your event. Deal Property Change is instant; most of the created-or-updated triggers are not. - Original source reporting is full of Zapier. Why: A record created by an automation is attributed to that automation. Fix: Create the contact through the native form or the Forms API where attribution matters, and use the Zap for everything after creation. - Requests start failing in bursts. Why: HubSpot allows 190 requests per 10 seconds regardless of tier, so a Zap that fans out hits the rate limit before the daily cap. Fix: Add a delay step or batch the work. A HubSpot upgrade raises the daily ceiling and leaves the burst limit where it was. **What practitioners say** (14 threads from 2024 to 2026, read 2026-10-11): Two uses dominate and they pull against each other. One is deliberate: people using Zapier to buy automation they would otherwise have to upgrade HubSpot for, which works and is the main reason this pair exists. The other is accidental: Zapier quietly becoming the thing that creates contacts, which is where attribution goes to die. Nobody in these threads complains that the integration is unreliable. - The reason people reach for it is to avoid a HubSpot upgrade (r/hubspot, January 2026, 4 points): https://www.reddit.com/r/hubspot/comments/1qm42tf/hubspot_workflow_bypass_with_zapier_or_make/ - Somebody has done it, and describes where the logic ended up (r/hubspot, January 2026, 3 points): https://www.reddit.com/r/hubspot/comments/1qm42tf/hubspot_workflow_bypass_with_zapier_or_make/ - Attribution is the quiet casualty (r/hubspot, May 2024, 4 points): https://www.reddit.com/r/hubspot/comments/1cna8pc/original_drill_downs_show_zapier_integration/ - The suggested fix is to stop using Zapier for that one job (r/hubspot, May 2024, 3 points): https://www.reddit.com/r/hubspot/comments/1cna8pc/original_drill_downs_show_zapier_integration/ - People do reach for it to beat HubSpot at its own automation (r/hubspot, September 2024, 5 points): https://www.reddit.com/r/hubspot/comments/1feahmh/you_can_automate_deal_insights_using_hubspot_crm/ Sources: https://help.zapier.com/hc/en-us/articles/8495919882253-How-to-get-started-with-HubSpot-on-Zapier | https://knowledge.hubspot.com/integrations/how-to-use-zapier-and-hubspot | https://help.zapier.com/hc/en-us/articles/8495924437005-Control-when-your-Zap-runs | https://developers.hubspot.com/docs/developer-tooling/platform/usage-guidelines ### HubSpot and Make A Super Admin has to approve it, and a scope added to a connection can never be removed. - Built as: Zapier, Make or n8n - Syncs: Two-way sync - Moves: Contacts, Companies, Deals, Custom objects - Costs to turn on: Metered by usage. Setup: Hours - Requires: A HubSpot Super Admin to approve the app, and a developer account for webhook modules - Full guide: https://www.reversecontact.com/integrations-hub/hubspot-integrations/hubspot-make-integration **Verdict.** Make reaches further into HubSpot than most orchestration tools: CRM objects and custom objects, contacts, deals, companies, tickets and tasks, engagements, calls, notes, emails and meetings, products, line items, orders, quotes and invoices, workflows, subscriptions and associations. The cost is a setup with three one-way doors: a Super Admin must approve the app and must approve again if Make adds scopes, a scope added to a connection can never be removed, and webhook subscription types are fixed at creation, on a custom app that supports exactly one webhook URL. None of that is hard; all of it is expensive to undo. **What syncs:** - Contacts, companies and deals (two-way): Create, read, update, search and watch, plus the generic CRM object modules that cover anything with a HubSpot object type. - Custom objects (two-way): Full record modules, which is more than several native connectors in this directory manage at all. - Engagements and activity (two-way): Calls, notes, emails, meetings and communications as first-class modules rather than as a generic write. - Commerce objects (two-way): Products, line items, orders, quotes and invoices, which is the part teams doing revenue operations actually come for. - Record changes into Make (out): Watch Notifications, on a webhook. Needs a HubSpot developer account and a connection built through advanced settings. - Timeline events (in): Create a timeline event and list templates, same developer-account requirement, which is how Make writes a custom activity onto a record. **Which editions carry it** (rows Make, columns HubSpot): - An ordinary action or search with An OAuth connection: Required - An ordinary action or search with Scopes chosen by hand: Not required - An ordinary action or search with A HubSpot developer account and custom app: Not required - Make an API Call with An OAuth connection: Required - Make an API Call with Scopes chosen by hand: Required - Make an API Call with A HubSpot developer account and custom app: Not required - An instant module, such as Watch Notifications with An OAuth connection: Required - An instant module, such as Watch Notifications with Scopes chosen by hand: Required - An instant module, such as Watch Notifications with A HubSpot developer account and custom app: Required **How to connect it** (Whoever builds the scenario, plus a HubSpot Super Admin to approve the app, twice if you need a webhook.. Five minutes for a normal connection. An hour the first time you need an instant module.): 1. Work out whether any module you need is instant [Make: the module picker]. A module tagged instant needs a webhook, and a webhook needs the advanced path: a HubSpot developer account, a custom application and a developer API key. Everything else is one OAuth connection. This is the fork, and taking it late means redoing the connection. 2. Create the connection and let Make request the scopes [Make: add a HubSpot CRM module, Create a connection]. Make automatically requests whatever scopes the module needs. The exception is Make an API Call, where you choose the scopes yourself under Connection, Custom Scopes, because Make cannot know what endpoint you are about to call. 3. Add every scope you will ever need on this connection [The same screen]. Make states it plainly: once you add scopes to a connection, you cannot remove them, and needing fewer means creating a new connection. Scopes only ever accumulate, so a connection used for experiments becomes a connection nobody should keep. 4. Create the HubSpot custom app if you need the webhook [HubSpot developer account: Apps, Create an app]. Leave the Install URL blank and set the Redirect URL to https://www.integromat.com/oauth/cb/hubspotcrm, which is still the pre-rename domain. Add scopes here only if you are using Watch Notifications; otherwise the section can stay empty. 5. Copy the developer API key and user ID [HubSpot developer account: Apps]. Click Show key on an existing key, or Create key and store it somewhere safe. The advanced connection asks for the key alongside the app's client details, which is a different set of credentials from the ordinary OAuth path. 6. Add every subscription now, because you cannot add one later [Make: the Watch Notifications module, Subscriptions]. Make warns that this field cannot be updated at a later time. Add all the subscription types you intend to watch in one go, with their matching scopes in both the custom app and the connection. 7. Accept one webhook URL per custom application [HubSpot: the custom app]. Make documents the constraint: each HubSpot custom application can be associated with only one webhook URL. Watching several events means several subscriptions on that one webhook, not several webhooks. 8. Check how many custom apps your HubSpot subscription allows [HubSpot: your subscription]. Make defers to HubSpot on this rather than stating a number, and since one app carries one webhook URL, the app allowance is effectively the ceiling on how many separate Make webhook scenarios you can run. **How to check it worked:** - Run one simple module before building anything. A connection that works proves the OAuth path, and nothing about the webhook path. - Try to remove a scope you added. You cannot, and discovering that on a test connection is better than discovering it on the one your scenarios depend on. - Activate the Watch Notifications module and change a record in HubSpot. If nothing fires, check the scopes exist in both places, the custom app and the connection custom scopes, because the module needs them in both. - Count the custom applications you already have against what your HubSpot subscription allows, before you design a second webhook scenario. Agent skill for this pair: https://www.reversecontact.com/integrations-hub/skills/hubspot-make.md **Field mapping:** - CRM Objects, Records, Custom Objects maps to Create, read, update, search. The generic object modules, which is where custom objects are reached. Broader than the n8n node, which has no custom object support at all. - Contacts, Companies maps to Their own dedicated module groups. Separate from the generic record modules, which is why the picker lists what look like two ways to do the same thing. - Engagements, Meetings, Communications maps to Activity on the timeline. Three separate groups. Worth checking which one holds the activity type you mean before building around it. - Tickets maps to Service Hub objects. Present, and the reason some teams run this pair with no sales use case at all. - Products, Line Items, Invoices maps to The commerce objects. Not in most orchestration tools' HubSpot coverage. If quoting or invoicing is the workflow, this is the differentiator. - Workflows, Associations, Subscriptions maps to Structural modules. Associations are how a contact gets linked to its company, and subscription modules cover email subscription state. - Events and Notifications maps to The instant modules. Where Watch Notifications lives, and the only group that needs a developer account, a custom app and a webhook URL. - Make an API Call maps to Anything HubSpot exposes. The escape hatch, and the one module where you pick the scopes yourself under Connection, Custom Scopes, because Make cannot infer them. - Does not cross: Removing a scope from a connection. Make states it outright, so a connection's permissions only ever grow and the only correction is a replacement. - Does not cross: Adding a subscription to a webhook module after it is built. Make warns the field cannot be updated later, so the list is decided once. - Does not cross: A second webhook URL on the same HubSpot custom application. One app carries one URL, which makes the app allowance on your HubSpot subscription the real ceiling. **What breaks:** - **Scopes are permanent on a connection.** Make states that once scopes are added to a connection they cannot be removed, and that holding fewer means creating a new connection. Add the minimum you need rather than everything that looks useful, because the audit question later is what this integration can reach and the honest answer will be whatever was ticked on the first day. - **Two Super Admin approvals, not one.** A HubSpot Super Admin has to pre-approve the Make app before a connection can be created, and has to approve again if Make adds new scopes before the connection can be reauthorised. The second one arrives without warning, on somebody else's release schedule, and presents as a scenario that has stopped working. - **One webhook URL per custom app, fixed at setup.** Each custom HubSpot application supports one webhook URL, and the subscription types on a webhook module cannot be changed after it is created. So every event type you will ever want has to be added during setup, and discovering a missing one means building another custom app rather than editing the first. - **Deprecated modules are still in the picker.** Make's contact-list modules carry a deprecation date and several of its integration pages list modules that are no longer current. A scenario built on one works until it does not. Check the app's own documentation page rather than the integration marketing pages, which Make itself notes are partly outdated. **Failures people hit:** - A scope needs removing and there is no way to do it. Why: Make states that once scopes are added to a connection they cannot be removed. Fix: Create a new connection with only the scopes you want and repoint the scenarios at it. Treat an experimental connection as disposable from the start. - Watch Notifications never fires. Why: The scopes are needed in two places with two different names: on the HubSpot custom app and again as connection custom scopes in Make. Fix: Check both against Make's subscription table. A module missing one of the pair does not error, it simply never triggers, which is why this is hard to spot. - A subscription needs adding to an existing webhook module. Why: Make warns that the Subscriptions field cannot be updated at a later time. Fix: Rebuild the module with the full list. This is the one setting on this pair worth over-specifying at the start. - A second webhook will not attach to the custom app. Why: Each HubSpot custom application can be associated with only one webhook URL. Fix: Add more subscriptions to the existing webhook rather than creating a second one, or create a separate custom app if your HubSpot subscription allows another. - The OAuth redirect fails on the advanced connection. Why: The Redirect URL has to be exactly https://www.integromat.com/oauth/cb/hubspotcrm, which is the pre-rename domain and looks wrong to anybody who knows Make by its current name. Fix: Use it as documented, and leave the Install URL blank. Typing the make.com equivalent is the obvious mistake here. - Make an API Call returns a permissions error. Why: Make cannot infer the scopes for an arbitrary endpoint, so this is the one module where you select them yourself. Fix: Add them under Connection, Custom Scopes in the module settings, remembering that they then cannot be removed from that connection. - A contact cannot be subscribed to an email address. Why: Make documents it as a plain constraint: you cannot subscribe a contact to an email address that is already subscribed. Fix: Check the subscription state first and branch, rather than treating the error as a failure to handle. - Somebody else's HubSpot integration started hitting limits. Why: HubSpot's daily API cap is shared across every app in the account, and a Make scenario looping record by record spends from the same pool. Fix: Batch where the modules allow it, and check API call usage in HubSpot under Development, Monitoring. The burst limit is per app; the daily one is everybody's. **What practitioners say** (14 threads from 2024 to 2026, read 2026-10-11): The threads about this pair are the same argument that runs through every orchestration tool against HubSpot: whether to build the automation inside the CRM or outside it. In r/hubspot the answer is to learn workflows and custom code actions, and in the automation subreddits it is to pick a tool and keep the logic portable. Both are right for different licences, which is the fact neither side mentions. - The in-CRM answer, from the people who prefer it (r/hubspot, January 2026, 6 points): https://www.reddit.com/r/hubspot/comments/1qmqukh/zapier_vs_make_vs_n8n_longterm_specialization/ - Consolidating onto HubSpot is a real motivation, not just marketing (r/hubspot, January 2026, 3 points): https://www.reddit.com/r/hubspot/comments/1qmqukh/zapier_vs_make_vs_n8n_longterm_specialization/ - Make sits in the middle on purpose, and people use it that way (r/hubspot, January 2026, 2 points): https://www.reddit.com/r/hubspot/comments/1qmqukh/zapier_vs_make_vs_n8n_longterm_specialization/ - Understanding the API matters more than the tool (r/hubspot, January 2026, 2 points): https://www.reddit.com/r/hubspot/comments/1qmqukh/zapier_vs_make_vs_n8n_longterm_specialization/ - The speed argument for a no-code tool is about who does the work (r/hubspot, January 2026, 2 points): https://www.reddit.com/r/hubspot/comments/1qmqukh/zapier_vs_make_vs_n8n_longterm_specialization/ Sources: https://apps.make.com/hubspotcrm | https://developers.hubspot.com/docs/developer-tooling/platform/usage-guidelines ### HubSpot and Outreach Contacts both ways, email one way, and HubSpot rather than Outreach owns it. - Built as: Native, Marketplace app - Syncs: Two-way sync - Moves: Contacts, Activities - Costs to turn on: Paid add-on or licence. Setup: Hours - Requires: An Outreach contract, and Super Admin or App Marketplace permissions in HubSpot. Custom field mappings need Data Hub. - Full guide: https://www.reversecontact.com/integrations-hub/hubspot-integrations/hubspot-outreach-integration **Verdict.** The thing to understand before anything else is who built this: Outreach wrote a deep native plugin for Salesforce and did not write one for HubSpot; the HubSpot pairing runs on HubSpot data sync, so HubSpot owns the code and Outreach points sync problems at HubSpot support. Read that as a scoping fact rather than a complaint. You get a contact sync whose direction you choose and email activity flowing one way into HubSpot, which covers what most teams want. You do not get per-object polling, per-field outbound control or task and event mapping, and if your evaluation was based on how this works against Salesforce you are comparing two different products. **What syncs:** - Contacts (two-way): One way or two way, set in HubSpot. Matched on email address, and contacts with no email are excluded unless you turn that off. - Email activity (in): Outreach to HubSpot only, and only for email sent from Outreach or a client running its extension. - Engagement events (in): Opens and clicks flow one way from the app into HubSpot, and only for contacts HubSpot already holds. - Deals (two-way): Only where you map pipelines and stages, and only deals sitting in a mapped stage. - HubSpot email into Outreach (out): Nothing. Email sync is one directional by design, not by configuration. - A single record on demand (event): Not supported. Outreach documents that it cannot sync individual records on demand with HubSpot. **Which editions carry it** (rows HubSpot, columns Outreach): - Any plan, no Data Hub with Standard field mappings: Included - Any plan, no Data Hub with Custom field mappings: Needs Data Hub - With Data Hub with Standard field mappings: Included - With Data Hub with Custom field mappings: Included **How to connect it** (A HubSpot Super Admin, or somebody with App Marketplace permissions. The Outreach side needs nothing beyond a contract.. Twenty minutes to configure. Then days, potentially, for the first pass to finish.): 1. Connect the app from the marketplace or the imports page [HubSpot: Marketplace, or Import on any object home page]. Both routes reach the same place. Super Admin or App Marketplace permissions are required, which is the only permission gate on this pair. 2. Set the direction per object, not globally [The sync configuration: the arrows dropdown]. Each object sync is bi-directional, app to HubSpot, or HubSpot to app. Contacts can be two-way while everything else is one-way, and that is usually the right answer rather than a compromise. 3. Decide now whether you need custom field mappings [The field mapping screen]. Standard mappings work on every HubSpot plan. Custom field mappings need a Data Hub subscription, sold separately from Sales Hub. You can build and test a mapping without the subscription, which is the cheapest way to find out whether yours genuinely needs it. 4. Set filters understanding what they do not do [The sync configuration: filters]. A filter limits which records sync initially. A record that has already crossed keeps syncing on its field mappings whatever the filter says afterwards, which is not what most people assume a filter means. 5. Save once, then leave it alone [The sync configuration]. The initial sync indexes every record on both sides, and HubSpot says millions of records can take several days. Saving the configuration again restarts that pass, so the instinct to tweak and re-save is expensive here. 6. Check the Excluded column before declaring success [The sync overview]. Records without an email address are excluded by default rather than failed, and they appear in a column nobody opens unless they already suspect something. Look at it on day one, while you still remember what you expected. **How to check it worked:** - Create an Outreach prospect without an email address and confirm it never arrives, and that it appears in the Excluded column. - Send an email from a mail client without the Outreach extension and check neither system logs it. That is the gap this integration does not close. - Change a mapped field on each side and confirm which direction wins, per object. - Wait out the initial sync before judging coverage. Several days is documented, not a fault. Agent skill for this pair: https://www.reversecontact.com/integrations-hub/skills/hubspot-outreach.md **Field mapping:** - Contacts maps to Contacts, matched on email address. Direction configurable per object. Email is the match key, which is why records without one go nowhere. - Email sent with Outreach maps to HubSpot activity. One way only, and only email sent from Outreach or from a mail client running the Outreach extension. - Opens and clicks maps to HubSpot, for contacts it already holds. Event sync applies only to existing HubSpot contacts, so engagement on a prospect who has not crossed yet is invisible. - Deals maps to Opportunities, where you map pipelines and stages. Mapping stages between two pipelines designed separately is the work on this half. - A custom field mapping maps to Only with Data Hub. Standard mappings are included on every HubSpot plan; custom ones are a separate subscription. - Does not cross: HubSpot email into Outreach. The email sync is one directional by design, so Outreach is never a complete record of what a prospect received. - Does not cross: A prospect with no email address. Excluded by default, listed rather than errored. - Does not cross: A single record on demand. Outreach documents that it cannot sync one record on request. **What breaks:** - **Email sync is one way and narrow.** Only email sent with Outreach, from the app or from a mail client running the Outreach extension, reaches HubSpot. A rep who replies from Gmail without the extension has sent an email that exists in neither system's timeline, and nothing flags it. HubSpot email never travels to Outreach, so Outreach is not a complete record of what a prospect received. - **Custom field mappings are a Data Hub feature.** Data sync runs on every HubSpot plan and custom field mappings need a Data Hub subscription. You can build and test one without the subscription, which is the cheapest way to find out whether your mapping genuinely needs it. If it does, price Data Hub before you commit to a go-live date, because it is the same hub that gates the webhook and custom code workflow actions and it is sold separately from Sales Hub. - **No contact, no sync, and no error.** HubSpot matches contacts on email address and excludes records without one by default, and event sync only applies to contacts HubSpot already holds. So an Outreach prospect with no email, or engagement on somebody who has not reached HubSpot yet, simply does not appear. Records excluded this way are listed in the sync's Excluded column rather than raised as failures, and nobody looks at that column unless they already suspect something. - **Saving the sync restarts the initial pass.** The initial sync indexes every record on both sides and HubSpot states that millions of records can take several days. Saving the configuration again starts that over. Filters only limit which records sync initially, so a record that has already come across keeps syncing on its field mappings whatever the filter now says, which is not what most people assume a filter does. **Failures people hit:** - Prospects are missing and nothing failed. Why: They have no email address. HubSpot matches contacts on email and excludes records without one by default. Fix: Open the Excluded column on the sync. These are listed there rather than raised as errors, which is why nobody finds them. - Opens and clicks are missing for some people. Why: Event sync only applies to contacts HubSpot already holds, so engagement on a prospect who has not synced yet has nowhere to land. Fix: Get the contact across first. The events do not backfill once it arrives. - A rep insists they emailed somebody and neither system shows it. Why: They sent it from a mail client without the Outreach extension. Only email sent through Outreach or through a client running the extension reaches HubSpot. Fix: This is a training and extension-deployment problem rather than a sync one. Nothing flags the gap. - The initial sync seems to have started over. Why: Somebody saved the configuration again. HubSpot restarts the full index when you do. Fix: Decide the configuration, save once and wait. Several days is documented for large record counts. - A filter is not keeping records out. Why: Filters limit which records sync initially. A record already synced keeps syncing on its field mappings regardless. Fix: Filter before the first pass, or unsync the records individually. Changing the filter later does not reach back. - A field will not map. Why: It is not a standard mapping, and custom field mappings need a Data Hub subscription. Fix: Confirm by building the mapping, which you can do without the subscription. If it needs Data Hub, price that before committing to a go-live date. **What practitioners say** (14 threads from 2024 to 2026, read 2026-10-11): Nobody writes about configuring this pair, so the search was for the decision in front of it: which outreach tool to put next to HubSpot. The threads are full of people choosing, and the criterion they name is not features but whether the connection holds. That is a reasonable thing to ask of this pair, whose answer is that it holds and is narrower than you expect. - The selection criterion people state is reliability of the join (r/CRMSoftware, November 2025, 5 points): https://www.reddit.com/r/CRMSoftware/comments/1owwrw1/whats_the_best_outreach_tool_that_actually_works/ - The connection quality is what separates otherwise similar products (r/hubspot, March 2024, 5 points): https://www.reddit.com/r/hubspot/comments/1b86cst/using_hubspot_as_our_crm_looking_to_bring_on_a/ - Running outbound from HubSpot is now the normal case (r/hubspot, January 2025, 5 points): https://www.reddit.com/r/hubspot/comments/1hsgv5z/what_are_the_best_tools_to_integrate_with_hubspot/ - People pick where they want to work, then look for the bridge (r/salesforce, May 2025, 7 points): https://www.reddit.com/r/salesforce/comments/1kc5oar/salesforce_and_hubspot_integration/ - The tooling question gets asked constantly and answered generically (r/hubspot, January 2025, 12 points): https://www.reddit.com/r/hubspot/comments/1hsgv5z/what_are_the_best_tools_to_integrate_with_hubspot/ Sources: https://support.outreach.io/support/solutions/articles/159000425625 | https://support.outreach.io/support/solutions/articles/159000426013-can-i-connect-outreach-and-hubspot-via-data-sync-by-hubspot- | https://knowledge.hubspot.com/integrations/connect-and-use-hubspot-data-sync ### HubSpot and Gong Six hours before a call appears, and the transcript never does. - Built as: Native, Marketplace app - Syncs: Two-way sync - Moves: Activities, Deals, Contacts, Companies - Costs to turn on: Paid add-on or licence. Setup: Hours - Requires: A Gong contract, a HubSpot tech admin, and a dedicated integration user - Full guide: https://www.reversecontact.com/integrations-hub/hubspot-integrations/hubspot-gong-integration **Verdict.** Gong reads your HubSpot accounts, contacts and deals, and writes call and meeting activity back onto the record, which is the point: the deal review happens where the deal lives. Three documented facts decide whether people trust it: the transcript is never exported, so HubSpot holds a summary and a link rather than the conversation; export can take up to six hours, so same-day reporting is always short; and if anything else already writes meetings, calls or emails to HubSpot, this will duplicate them unless you pick the object type deliberately. **What syncs:** - Companies, contacts and deals (out): Read out of HubSpot into Gong. Required fields include company domain, contact email and title, and deal name, stage, amount and close date. - Meetings and web conference calls (in): As meetings, calls or notes. You choose one type and both use it. A meeting invite needs at least one external participant matching a HubSpot record. - Telephony calls (in): As HubSpot call objects, carrying the Gong link, the spotlight brief, highlights, outline, action items and call metadata. - Emails (in): Associated with HubSpot contacts, and only from the export date forward. Nothing is backfilled. - Engage activity (in): Engage tasks and LinkedIn messages and connection requests, exported once the to-do is completed. - The transcript (event): Never. Gong documents that the call transcript is not exported, so the link back to Gong is the only route to it. **Which editions carry it** (rows Gong, columns HubSpot): - Meeting invites and conference calls with No: the wide setting is safe - Meeting invites and conference calls with Yes: narrow it or get duplicates - Telephony calls with No: the wide setting is safe - Telephony calls with Yes: narrow it or get duplicates - Emails with No: the wide setting is safe - Emails with Yes: narrow it or get duplicates - Engage tasks and LinkedIn with No: the wide setting is safe - Engage tasks and LinkedIn with Yes: the wide setting is safe **How to connect it** (A Gong tech admin, and somebody in HubSpot who can create the integration user and sign in as it. Gong names the tech admin role explicitly for every step.. An afternoon of settings, then up to six hours before you can tell whether it worked.): 1. Create a dedicated HubSpot integration user first [HubSpot: Settings, Users and Teams]. Gong can access exactly what the connecting user can access, and it recommends a dedicated user for that reason. The permissions on that account are the boundary of the integration, and deactivating a normal employee account later disconnects it. 2. Audit what already writes activity to HubSpot [HubSpot: Settings, Integrations, Connected Apps]. A calendar sync, a dialler or an email tool already filling the timeline is what turns this install into duplicates. Write down which activity types each one creates before you choose Gong's, because the grid below is the decision and it does not undo cleanly. 3. Connect HubSpot and choose which fields Gong imports [Gong: Admin center, Settings, CRM settings]. Gong imports from Account, Contact and Opportunity, and a tech admin picks the fields per object including custom ones. The required set is fixed: company domain, name and last modified date; contact name, title, phone, email and associated company ID; deal name, stage, amount, close date, owner ID and account ID. 4. Pick one object type for meetings and conference calls [Gong: the Export tab]. Meetings, Calls or Notes, and both streams must use the same type because a meeting invite is updated with the call details afterwards. Gong documents that exporting as meetings alongside a HubSpot and Google Calendar setup may duplicate them, and names calls or notes as the alternative. 5. Narrow the telephony and email exports if anything else sends them [Gong: the Export tab]. All calls covers telephony calls imported into Gong plus Gong Dialer calls, and Gong says another application sending calls makes that option duplicate them. Gong Dialer calls only is the narrow setting. Emails have the same pair: All emails, or Gong composer emails only. 6. Set the activity update period deliberately [Gong: HubSpot activity update period]. This is how many months after an activity Gong keeps updating the HubSpot record as new information arrives. Gong's own example: with three months set, a January activity is still updated in February and not in April. A long period keeps records fresher and consumes CRM resources doing it. 7. Grant the opt-out permission separately if you run Engage [Gong: Enable update of opt out field in HubSpot]. Prospects marked Do not contact in Gong Engage only reach HubSpot if you click Give permission and sign in again as the integration user. Gong states this is in addition to the regular integration permissions, so it is a second consent screen rather than a checkbox. 8. Read the export status report rather than the timeline [Gong: CRM export status report]. It shows which activities exported, which failed and which were never set to export. With a six hour delay on the pipeline, this is the only way to tell a misconfiguration from a wait. **How to check it worked:** - Wait six hours before concluding anything. Gong documents up to six hours to export, and the most common false alarm on this pair is somebody checking ten minutes after a call. - Take a call with one external participant who is not in HubSpot and confirm nothing is created. Gong needs at least one external participant matching a HubSpot record before it will create an activity from a meeting invite. - Open one exported call object and check what is on it: the call name, participants, the Gong link, the spotlight brief, highlights and outline, the action items and the metadata. If you expected the transcript, it is not coming. - Generate the CRM export status report after the first full day and read the failures. A failure there is a permission on the integration user far more often than it is a Gong problem. Agent skill for this pair: https://www.reversecontact.com/integrations-hub/skills/hubspot-gong.md **Field mapping:** - Company maps to Domain, Name, Last Modified Date. The required minimum Gong accesses. Domain is the matching key, which is why an account with no domain never associates with anything Gong recorded. - Contact maps to Name, Title, Phone number, Email address, Associated Company Id. Email is what matches a meeting participant to a record, and the associated company ID is what rolls an activity up to the account. - Deal maps to Deal Name, Deal Stage, Amount, Close Date, Owner ID, Account ID, Last Modified Date. The forecasting set. Everything Gong says about a deal rests on these six fields being populated and current in HubSpot. - Custom fields, any object maps to Imported if a tech admin selects them. Fully supported fields are two-way: a value changed in Gong is written back to HubSpot. That is worth knowing before you let Gong edit a field your reps own. - Single-line text and dropdown select maps to Supported, truncated at 120 characters. Gong displays a maximum of 120 characters and trims longer picklist options. A long option reads as a different value rather than as a truncated one. - Date fields maps to Supported, epoch in milliseconds. Gong states the format requirement outright. A date arriving in any other format is the first thing to check when one field in an otherwise working import is empty. - Rich text maps to Limited support, formatting dropped. Viewable and editable in Gong, and an edit saves back to HubSpot without the formatting. So a round trip through Gong flattens the field permanently. - Multiple checkboxes, File, HubSpot user maps to No support. Three types Gong will not import at all. An owner-style HubSpot user field is on that list, which surprises teams who assumed owner data crosses as a user rather than as the deal's Owner ID. - Does not cross: The transcript. Gong states it is not exported, so the Gong link on the record is the only route to the conversation and HubSpot is not where anybody reads a call. - Does not cross: Seven kinds of calendar email. Anything tagged MEETING_ACCEPTED, MEETING_DECLINED, MEETING_TENTATIVE, MEETING_INVITATION, MEETING_INVITATION_CANCEL, MEETING_NEEDS_ACTION or SCHEDULING is excluded. - Does not cross: History, in most cases. If the email or telephony integration was connected before the CRM one, those calls and emails count as existing activities and are not exported unless they fall inside the update period and change. **What breaks:** - **Up to six hours before anything appears.** Gong documents that exporting its data to HubSpot can take up to six hours. Any dashboard built on today's activity is therefore incomplete all day, and the usual first report that the integration is broken comes from somebody who checked a few minutes after a call. Say the number out loud when you launch it. - **Duplicates are the default if anything else writes activity.** Exporting as HubSpot meetings while Google Calendar also syncs them creates duplicates; export as calls or notes instead. Exporting all telephony calls when another application also sends them duplicates those; choose Gong Dialer calls only. Emails behave the same way. Changing the object type later does not convert what is already there, and re-exporting recreates records as the new type. - **Some HubSpot field types will not come across.** Multiple checkboxes, file fields and HubSpot user fields are unsupported. Rich text arrives without formatting and edits made in Gong save back without it. Single-line text and dropdown fields display a maximum of 120 characters, so longer picklist options are trimmed. Date fields have to be epoch in milliseconds. - **A deactivated user is an outage.** Gong recommends a dedicated integration user because deactivating a regular one disconnects the integration, and Gong can only access the HubSpot data that the connecting user can access. Both facts argue for a service account created before the install rather than migrated to afterwards, and for writing down what it can see. **Failures people hit:** - Every meeting appears twice in HubSpot. Why: Calls are being exported as HubSpot meetings while HubSpot is also syncing Google Calendar. Gong documents this combination as producing duplicate meetings. Fix: Export as calls or notes instead. Note that changing the type does not convert the records already there, so you will be cleaning up the first batch by hand. - Telephony calls appear twice. Why: All calls was selected while another application also exports calls to HubSpot. All calls covers telephony calls imported into Gong as well as Gong Dialer ones. Fix: Switch to Gong Dialer calls only. This narrows what Gong claims rather than disabling the other tool, which is usually the easier conversation. - A call happened and nothing is on the record after an hour. Why: Nothing is wrong. Gong documents that exporting its data to HubSpot can take up to six hours. Fix: Wait, then read the CRM export status report rather than the timeline. It distinguishes failed from not yet exported, which the record cannot. - A meeting created no HubSpot activity at all. Why: No external participant matched a HubSpot record. Gong requires at least one match before it creates an activity from a meeting invite. Fix: Check whether the attendee exists in HubSpot with that email. This is also why Gong distinguishes participants, who joined, from attendees, who joined and have a contact record. - One imported field is permanently empty in Gong. Why: The field type is unsupported or the format is wrong. Multiple checkboxes, file fields and HubSpot user fields are not imported at all, and date fields have to be epoch in milliseconds. Fix: Check the type before the mapping. A long single-line text or dropdown value is a different case: those import and display only the first 120 characters. - A rich text field lost its formatting after somebody edited it in Gong. Why: Rich text has limited support. It displays without formatting, and an edit made in Gong writes back to HubSpot without it. Fix: Keep rich text fields out of the imported set if anybody edits in Gong. The flattening is not recoverable from the HubSpot side. - The integration stopped working and nobody changed anything. Why: The connecting HubSpot user was deactivated, which is what the dedicated integration user recommendation exists to prevent. Fix: Reconnect with a service account rather than reactivating the person who left. Remember Gong sees exactly what that account sees, so check its permissions rather than assuming parity. - Do not contact in Gong Engage never reaches the HubSpot contact. Why: The opt-out permission is a separate authorisation, in addition to the regular integration permissions. Fix: Click Give permission under Enable update of opt out field in HubSpot and sign in as the integration user again. Only relevant if you have Gong Engage, and a compliance problem rather than a cosmetic one if you do. **What practitioners say** (14 threads from 2024 to 2026, read 2026-10-11): The striking thing about searching this pair in the words a HubSpot customer would use is how rarely Gong is the answer. Threads asking which conversational intelligence tool works with HubSpot return Fathom, Fireflies, HubSpot's own feature and a long tail, with Gong named as the expensive option. The one comment in fourteen threads that describes running both in production is about a duplicate problem, and the fix it reports is the one Gong documents. Read the set as a statement about who buys this pair rather than about whether it works. - A team running both pushes everything as notes, for the documented reason (r/hubspot, December 2025, 1 points): https://www.reddit.com/r/hubspot/comments/1pkw39m/reviews_for_the_native_note_taker/ - On HubSpot, Gong is usually named as the expensive option rather than the choice (r/hubspot, November 2024, 1 points): https://www.reddit.com/r/hubspot/comments/1h18rql/which_conversational_intelligence_tool_call/ - HubSpot's own feature is the live comparison, and it is tier-gated (r/hubspot, November 2024, 3 points): https://www.reddit.com/r/hubspot/comments/1h18rql/which_conversational_intelligence_tool_call/ - The native note taker is in beta and people are already planning around it (r/hubspot, December 2025, 1 points): https://www.reddit.com/r/hubspot/comments/1pkw39m/reviews_for_the_native_note_taker/ - What people want from this category is a property, not a timeline entry (r/hubspot, February 2025, 1 points): https://www.reddit.com/r/hubspot/comments/1iurnhd/what_platform_do_you_use_for_aigenerated/ Sources: https://help.gong.io/docs/export-data-to-hubspot | https://help.gong.io/docs/required-hubspot-fields-that-gong-accesses | https://help.gong.io/docs/the-benefits-of-integrating-hubspot-and-gong ### HubSpot and Smartlead The campaign-level sync is creation-time only. SmartAgents is the way around it. - Built as: Native, Built on the API - Syncs: One way, in - Moves: Contacts, Activities - Costs to turn on: Metered by usage. Setup: Hours - Requires: A Smartlead plan and a HubSpot account that can authorise OAuth. A campaign not yet live for the native sync, or SmartAgents access for the other route. - Full guide: https://www.reversecontact.com/integrations-hub/hubspot-integrations/hubspot-smartlead-integration **Verdict.** The narrowest CRM integration on the HubSpot hub, and the one with the sharpest timing constraint. HubSpot is connected inside the campaign creation flow, after the leads are uploaded, and Smartlead documents that it cannot be added to a campaign that is already running. Every campaign needs it enabling again, with the list, the group and the field mapping chosen each time, and the actual on switch is a toggle that reads like a deduplication setting. Get those three things right and it does what you want; miss any of them and the campaign runs perfectly while the CRM learns nothing. **What syncs:** - New leads (in): Created in HubSpot when they do not already exist, into the list and group chosen during campaign setup, across the fields you mapped. - Field mapping (in): Set per campaign in the import step. All the fields in the HubSpot column have to be mapped before the sync is confirmed. - Replies, bounces and unsubscribes (in): Through webhooks rather than the campaign sync, posted to an endpoint you control and scoped by user, client or campaign. - An existing HubSpot contact (event): The documented behaviour covers creating leads that do not exist. How existing contacts are treated is not stated, so verify it on a test campaign. - Anything out of HubSpot (out): Nothing on this path. Smartlead is fed from its own lead import, not from a HubSpot list. **Which editions carry it** (rows Smartlead, columns HubSpot): - Push leads from a brand new campaign with The campaign-level sync: Works - Push leads from a brand new campaign with A SmartAgent: Works - Add syncing to a campaign already running with The campaign-level sync: Not possible - Add syncing to a campaign already running with A SmartAgent: Works - Update an existing HubSpot contact rather than duplicate it with The campaign-level sync: Not possible - Update an existing HubSpot contact rather than duplicate it with A SmartAgent: Works - React in real time to a reply with The campaign-level sync: Not possible - React in real time to a reply with A SmartAgent: Works **How to connect it** (Somebody in Smartlead, plus a HubSpot account with permission to authorise OAuth integrations. No HubSpot admin, and no developer anything.. Ten minutes either way. The decision about which route to take is the part worth thinking about.): 1. Decide which of the two routes you are taking [Design, before either settings screen]. There are two and they behave differently. The campaign-level sync is a toggle inside the campaign creation flow and cannot be added later. SmartAgents is an agent you build, triggered on a schedule or a campaign event, and it works against campaigns that already exist. 2. For the native route, connect HubSpot to Smartlead first [Smartlead: the CRM connection]. Smartlead is explicit that connecting a HubSpot CRM does not automatically sync with all campaigns in the account. The connection is the prerequisite and enables nothing on its own. 3. Enable it inside the campaign creation flow, every time [Smartlead: creating a campaign]. Toggle the HubSpot connection on while the campaign is being created, then select the HubSpot list and the HubSpot group that leads should be pushed to when they do not already exist. Smartlead states this cannot be integrated midway through an active campaign. 4. For the SmartAgents route, connect from Integrations [Smartlead: SmartAgents, Integrations]. Find HubSpot, click Connect, authorise on HubSpot's OAuth page and confirm the status shows Connected. Smartlead notes tool connections are one-time and need no reconnecting unless you disconnect manually. 5. Start from a template rather than a blank prompt [Smartlead: SmartAgents, Home]. Two exist. Scheduled CRM Sync pushes leads who replied, runs daily at 9am, processes only unsynced leads and reports to Slack. Inbox Reply Sync with Upsert syncs interested leads and prevents duplicates with upsert logic. 6. Choose the trigger carefully, because it is permanent [SmartAgents: trigger configuration]. Schedule-based takes a time, timezone, frequency and a skip-weekends toggle. Event-based takes a scope of account, client or campaign level and an event such as email reply or lead category update. Smartlead states event-based triggers cannot be edited after the agent is created. 7. Add the SmartAgents app to the Slack channel if the workflow uses one [Slack]. Both templates end in a Slack summary, and Smartlead states the agent cannot be deployed until the SmartAgents app is in the target channel. A Configuration Required notice that will not clear is usually this. 8. Test run before deploying, and read every step [SmartAgents: the workflow canvas]. Click Test Run and confirm the HubSpot Upsert Contact step returns what you expect on both the create and the update path. If it is wrong you give feedback in the prompt field and the simulation reruns. **How to check it worked:** - On the native route, try to enable HubSpot on a campaign that is already running. You cannot, and confirming it once is how a team learns to do it at creation time. - On the SmartAgents route, run the test and watch both paths: a lead that exists in HubSpot and one that does not. Upsert is only proven when you have seen it update as well as create. - Push a lead with an empty company name and check what HubSpot holds afterwards. Smartlead states empty fields in Smartlead will not overwrite existing values in HubSpot. - Check the run logs after the first scheduled execution. It is the only place that distinguishes an agent that ran and found nothing from an agent that did not run. Agent skill for this pair: https://www.reversecontact.com/integrations-hub/skills/hubspot-smartlead.md **Field mapping:** - Email address maps to The HubSpot contact email. The match key for the SmartAgents upsert, and the field a lead must have for the agent to do anything. A lead without one is the first thing to check in the run logs. - First name, last name maps to The HubSpot contact name. Synced only when present on the Smartlead lead record. - Company name maps to The HubSpot company field. The fourth and last field. Anything richer than these four has to reach HubSpot from somewhere else. - An empty Smartlead field maps to Leaves HubSpot alone. Smartlead states empty fields will not overwrite existing values, which is the safe default and worth knowing before anybody worries about a thin lead record. - A HubSpot list and group maps to Chosen at campaign creation. On the native route you select both, and they decide where a lead is pushed when it does not already exist in HubSpot. - Lead sync status maps to Updated back in Smartlead. A step in the Scheduled CRM Sync template, and what lets it process only unsynced leads on the next run rather than everything again. - A Slack summary maps to The configured channel. The last node in both templates. Optional in principle and required in practice, because the agent will not deploy until the app is in the channel. - Replies, opens, clicks, unsubscribes maps to Webhooks, not this integration. Smartlead publishes email_sent, email_reply, email_open, email_link_click, lead_unsubscribed and lead_category_updated as webhook events for a server to consume. - Does not cross: Anything beyond email, first name, last name and company name. That is the documented sync list for the SmartAgents route and nothing suggests the native one is wider. - Does not cross: Retrospective enablement on the native route. Smartlead states it can only be integrated while creating the campaign and not midway through an active one. - Does not cross: An edit to an event-based SmartAgents trigger. Smartlead states it cannot be changed after the agent is created, so the agent has to be rebuilt. **What breaks:** - **The window is the campaign creation flow.** HubSpot can only be connected while a campaign is being created, in the pop-up after the lead upload. Smartlead states it cannot be integrated into an active campaign. There is no retrofit, so the cost of forgetting is rebuilding the campaign, and the only way to check is the HubSpot integrated column in the import leads section. - **Per campaign, every time.** The connection does not carry to new campaigns. Each one needs the toggle, the HubSpot list, the HubSpot group and the full field mapping again. That is a process problem rather than a technical one and it is the usual reason a team's CRM has data from three campaigns and not from the other nine. - **The on switch is disguised as a dedupe option.** Data syncs only if the create-the-lead-if-they-do-not-exist toggle is on. Nothing about the label suggests it governs whether anything syncs at all, so it is routinely left off by somebody being careful about duplicates, and the campaign then runs with an integration that is connected and silent. - **The scope of the sync is not well documented.** Smartlead's marketing describes leads, deals, updates and activities, while its SmartAgents guide lists four contact fields and its campaign article does not enumerate them. Do not plan reporting on the marketing description. Run a test campaign with two leads, look at what reaches HubSpot, and design from that. **Failures people hit:** - A campaign is running and HubSpot cannot be switched on. Why: Smartlead states the campaign-level integration can only be set up while creating the campaign and not midway through an active one. Fix: Either recreate the campaign, or build a SmartAgent instead, which works against campaigns that already exist. The second is almost always the better answer. - The CRM is connected and no campaign is syncing. Why: Connecting HubSpot to the Smartlead account does not sync it with any campaign. It has to be enabled per campaign, every time. Fix: Enable the toggle in each new campaign's creation flow, and select the HubSpot list and group while you are there. - HubSpot shows as disconnected after authorising. Why: Smartlead lists this as its first troubleshooting case: the OAuth account may lack the necessary CRM permissions. Fix: Re-authorise from SmartAgents, Integrations, with an account that has CRM permissions. Tool connections are one-time otherwise and do not need periodic reconnection. - The Configuration Required notice will not clear. Why: Slack is the usual culprit. The SmartAgents app has to be present in the target channel before the agent can be deployed. Fix: Add the app to the channel using the in-app link, then return to the workflow. Connecting Slack as an integration is not the same as adding it to the channel. - The agent ran and the contact is not in HubSpot. Why: Three documented causes: check the run logs for that execution, confirm the lead has a valid email address, and confirm the HubSpot OAuth connection is still active. Fix: Work through all three in that order. The email is the match key for the upsert, so a lead without one cannot produce a contact. - The agent runs but contacts are never updated. Why: The Upsert Contact step is not receiving the right lead data, or the connection logic between the fetch step and the HubSpot step is wrong. Fix: Open the connector between the two steps, choose Edit Connection Logic, and check what is being passed. Reset to Default is there if you changed it and want it back. - The trigger is wrong and cannot be changed. Why: Smartlead states that event-based triggers cannot be edited after the agent is created. Fix: Create a new agent. This is the one irreversible decision in the SmartAgents flow, so it is worth being deliberate about scope and event type before clicking Proceed. - Nothing about replies or opens is reaching anywhere. Why: Those are webhook events rather than part of this integration: email_sent, email_reply, email_open, email_link_click, lead_unsubscribed and lead_category_updated. Fix: Point them at a server. Smartlead retries failed deliveries, marks an event failed after three attempts, and exposes a Retrigger Webhooks endpoint for the failures. **What practitioners say** (14 threads from 2024 to 2026, read 2026-10-11): Hardly anyone names this pair, so the search was for the job: getting cold email activity into a CRM without the CRM punishing you for it. Two themes run through the threads. HubSpot actively discourages cold outreach from inside HubSpot, which is why the sequencer exists in the first place. And the people doing this well treat the CRM as the destination for qualified leads rather than for everything a campaign touches. - HubSpot does not want you sending cold email from HubSpot (r/hubspot, July 2023, 4 points): https://www.reddit.com/r/hubspot/comments/14vezqr/prospecting_emails/ - Qualify before the CRM, not after (r/UseApolloIo, December 2025, 2 points): https://www.reddit.com/r/UseApolloIo/comments/1u3u58x/when_to_sync_apollo_to_your_crm_and_when_you/ - The stale-list problem is upstream of this integration (r/microsaas, April 2026, 3 points): https://www.reddit.com/r/microsaas/comments/1sthi1r/i_replaced_apollo_clay_instantly_hubspot_with_one/ - Smartlead's API is not the easy route for most teams (r/hubspot, February 2025, 2 points): https://www.reddit.com/r/hubspot/comments/1ita4n1/tool_to_automate_lead_uploads_to_cold_email_campaigns_smartlead_alternatives/ - Six tools and an ops person is the alternative being compared against (r/microsaas, April 2026, 1 points): https://www.reddit.com/r/microsaas/comments/1sthi1r/i_replaced_apollo_clay_instantly_hubspot_with_one/ Sources: https://helpcenter.smartlead.ai/en/articles/225-how-to-sync-leads-with-hubspot | https://api.smartlead.ai/guides/webhook-integration | https://helpcenter.smartlead.ai/en/articles/445-smartlead-x-hubspot-integration-guide-smartagents ### HubSpot and lemlist Opens and clicks arrive as notes, because HubSpot will not let a third party write them. - Built as: Native, Marketplace app - Syncs: Two-way sync - Moves: Contacts, Companies, Activities - Costs to turn on: Included on both sides. Setup: Hours - Requires: A paid lemlist plan (there is no free tier), plus admin access on both sides - Full guide: https://www.reversecontact.com/integrations-hub/hubspot-integrations/hubspot-lemlist-integration **Verdict.** A genuinely native two-way integration configured once at team level, which is a better deal than it sounds: contacts and companies sync with a direction you choose per field, and campaign activity lands on the HubSpot timeline without anybody wiring a webhook. The thing to understand before you judge it is that most of that activity arrives as notes. HubSpot does not let third-party applications write to its open and click objects, so only sent and replied emails become Email objects. That is a HubSpot restriction, it applies to every tool in this category, and it decides what your reporting can count. **What syncs:** - Contacts and companies (two-way): Direction set per field: two-way, HubSpot priority, lemlist priority, or off. Every contact needs an email, a LinkedIn URL or a company domain to match on. - Sent and replied emails (in): As HubSpot Email objects, which is the only campaign activity that becomes one. - Opens, clicks, bounces and failures (in): As Notes. HubSpot does not permit third-party applications to write to its dedicated open and click objects. - LinkedIn messages (in): Sent and replied become LinkedIn Message objects. Profile visits, invites and opens become Notes. - Calls (in): As Call engagements with direction, duration, outcome and the owner resolved through user mapping. The contact must exist in HubSpot first or the call waits. - Campaign state (in): Paused, resumed, step skipped, meeting booked and interested or not interested, all as Notes. **Which editions carry it** (rows lemlist, columns HubSpot): - A built-in lemlist status with HubSpot's factory outcomes: maps correctly - A built-in lemlist status with Outcomes deleted and recreated: falls back to Connected - A custom status your team created with HubSpot's factory outcomes: falls back to Connected - A custom status your team created with Outcomes deleted and recreated: falls back to Connected **How to connect it** (One person with admin on both sides. The integration is configured once at team level rather than per user, which is the nicest thing about it.. An hour, and the order of it decides whether you do it twice.): 1. Create the HubSpot properties before you open lemlist [HubSpot: Settings, Properties]. lemlist can only map to a property that already exists, and field mapping is not retroactive. Every custom field you want filled has to be in HubSpot first, which makes this the step that has to come before the interesting ones. 2. Decide whether lemlist may create records, and on what trigger [lemlist: HubSpot integration, General settings]. Contact and company creation is a setting with a trigger you choose, so you can let lemlist create a HubSpot record on a reply rather than on an import. A team that does not want cold leads in the CRM turns this off here rather than managing it campaign by campaign. 3. Set the mandatory properties that gate creation [lemlist: Advanced settings]. Mandatory property rules decide which leads are allowed to become HubSpot records. A contact that does not meet the conditions is not created, which is the documented reason records go missing and looks identical to a broken sync. 4. Set default values for anything lemlist creates [lemlist: Advanced settings, per object]. Add a default value per object for Contact, Company or Deal, so a record created by lemlist always carries a lifecycle stage or a lead source. This is the lever that makes lemlist-created records distinguishable in a HubSpot report later. 5. Map the fields, with a direction on each [lemlist: Field Mapping]. Per field you choose two-way, HubSpot priority, lemlist priority or off, and you can create a lemlist custom field and map it to a HubSpot property. Changes propagate in two to ten minutes once mapped. Nothing already imported is backfilled. 6. Map users, and set the fallback owner per direction [lemlist: User Mapping]. Match each lemlist user to a HubSpot user so activity keeps its owner, with auto-map as a shortcut. Define default ownership separately for each sync direction, because an unmapped CRM owner falls back rather than failing, and the fallback is what every unowned activity gets. 7. Decide on call recordings before the first call [lemlist: Settings, CRM, Activities, Calls]. Four toggles are on by default: Calls note, Calls recording, Calls transcript, Calls summary. The recording link lemlist writes into the HubSpot note is public, needs no lemlist account and cannot be revoked. Switch it off now or accept that permanently. 8. Map every call status by hand if you invented any [lemlist: the same Calls screen]. Built-in statuses map to HubSpot's factory outcomes. A custom status, or a portal whose outcomes were deleted and recreated, falls back to Connected. Map each status explicitly rather than spot-checking, because the failure is silent and flattering. **How to check it worked:** - Send one email to a test contact and look for it in the Email object. Then open one and look for the open in Notes. If you expected both in the same place, the reporting conversation has to happen now rather than after launch. - Place one call and open the HubSpot note. Click the recording link in a private browser window with no lemlist session. If it plays, that is what anybody with the link can do, permanently. - Mark a call with every status your team uses and read the HubSpot outcome on each. Any that says Connected when it should not is an unmapped status rather than a bad call. - Open Logs for the last day and read the failures. It takes a date range and a refresh, and it is the only place the integration tells you it did not do something. Agent skill for this pair: https://www.reversecontact.com/integrations-hub/skills/hubspot-lemlist.md **Field mapping:** - Contacts maps to lemlist leads, per-field direction. Two-way, HubSpot priority, lemlist priority or off, chosen field by field. Matching needs an email, a LinkedIn URL or a company domain on the lead. - Companies maps to lemlist company records. Same four directions. Default values can be set for companies lemlist creates, separately from contacts. - Deals maps to Created by lemlist, with defaults. Deal creation triggers are the one setting that is per campaign rather than team-level, and default property values for new deals are set in Advanced settings. - Custom properties maps to Mapped if they already exist. A lemlist custom field can be created and mapped to a HubSpot property. The HubSpot side has to exist first, and mapping is never retroactive. - Mandatory properties maps to A gate on record creation. Rules that decide which leads become HubSpot records at all. A lead failing them is simply not created, with no error on the lead. - Users maps to HubSpot owners, with a fallback. Mapped so activity keeps its owner, with auto-map available and a default owner configured per sync direction. - Call statuses maps to HubSpot call outcomes. Built-in statuses map to the factory outcomes. Custom ones, and portals whose outcomes were recreated, fall back to Connected until mapped by hand. - A manual unsubscribe maps to Nothing. lemlist pushes an unsubscribe only when the lead unsubscribed themselves from the campaign. Somebody moved into the Unsubscribe section by hand does not reach HubSpot. - Does not cross: Opens and clicks as engagement. They are notes, so a HubSpot report built on email engagement does not count them, and lemlist says plainly that this is HubSpot's restriction rather than theirs. - Does not cross: A recording, transcript or summary on a call that came through Aircall or Ringover. Those four extras are for calls placed with lemlist calling only. - Does not cross: An AI summary that does not already exist. lemlist pushes the summary if the call has one and syncing never triggers one to be generated. **What breaks:** - **Most activity is a note, by HubSpot's rule.** Only sent and replied emails become Email objects. Opens, clicks, bounces, failures, campaign state changes and most LinkedIn actions become Notes, because HubSpot does not allow third-party applications to write to its open and click objects. Notes are visible on the timeline and are not countable in the reports built on email engagement, which is the thing to check before promising anybody a dashboard. - **Field mapping is not retroactive.** Fields mapped after you import leads or launch a campaign do not backfill, and custom properties have to exist in HubSpot before lemlist can map to them at all. The order is create the properties, map the fields, then import. Doing it the other way round means re-importing, which is the single most common support thread on this pair. - **Manual unsubscribes do not reach the CRM.** lemlist only pushes an unsubscribe when the lead unsubscribes themselves from the campaign. Somebody moved into the Unsubscribe section by hand is not pushed to HubSpot. In a team that manages opt-outs manually, that is a compliance gap rather than an inconvenience, and it needs a process on the HubSpot side. - **Custom call statuses fall back to Connected.** lemlist's built-in call statuses map to HubSpot's standard outcomes, so No answer stays No answer. A status your team invented has no default mapping and lands as Connected until somebody maps it by hand in the activities settings. The same happens if your portal's call outcomes were deleted and recreated, because the default mapping targets HubSpot's factory outcomes by id. Every call therefore looks successful until you notice. - **The call recording link is public and permanent.** lemlist states it outright: anyone who opens the recording link from the HubSpot record can listen to the call with no lemlist account, and the link never expires and cannot be revoked. Calls recording is one of four toggles that are on by default. This is the one setting on the page to decide before go-live rather than after, because a link already written into a note cannot be withdrawn. - **The call note is rebuilt rather than merged.** The activity is created when the call ends with whatever exists at that moment, rewritten when the transcript arrives and rewritten again when the AI summary is generated, always in the same order: the rep's note, the summary, the recording link, then the transcript. An edit made by hand in HubSpot is replaced on the next refresh, and the note caps at 65,000 characters with anything longer cut from the end, so a long transcript is what disappears. **Failures people hit:** - Every call shows as Connected whatever the rep marked. Why: The status has no mapping. Either it is a custom lemlist status, or your portal's call outcomes were deleted and recreated so the default mapping targets ids that no longer exist. Fix: Map each status explicitly in Settings, CRM, Activities, Calls. Do it for all of them rather than the ones that look wrong, because a correct-looking outcome may be a coincidence. - Opens and clicks are nowhere in the Email object. Why: HubSpot does not allow third-party applications to write open and click data to its dedicated email objects. lemlist stores them as Notes because that is the only place available. Fix: Look in Notes, and filter the Activity tab by type to find them. There is no configuration that moves them, and every tool in this category faces the same wall. - A field mapped last week is still empty on older contacts. Why: Field mapping is not retroactive. It applies from the moment it is set, not to records already imported. Fix: Re-import the affected leads, and from now on create the HubSpot property, map the field, then import. That order is the single most common support thread on this pair. - A contact is not being created in HubSpot at all. Why: Mandatory properties are enabled and the lead does not meet the required field conditions, so lemlist declines to create the record. Fix: Check the mandatory property rules in Advanced settings against the lead. Also confirm the lead has an email, a LinkedIn URL or a company domain, since matching needs one of the three. - Activity is landing with the wrong owner. Why: User mapping is missing or incorrect, so the fallback owner is being used. The fallback is configured per sync direction and applies to everything unmapped. Fix: Map the lemlist user to the HubSpot user in User Mapping, then check the Define default ownership section for each direction rather than just one. - A call has no transcript or summary on the HubSpot record. Why: Neither exists when the call ends: they arrive on a later refresh. The call may have no summary at all, or it came from Aircall or Ringover rather than lemlist calling. Fix: Reopen the record later, confirm the call in lemlist actually has both, and check Calls transcript and Calls summary are on. Syncing never generates a summary that does not already exist. - Somebody edited a call note in HubSpot and it reverted. Why: lemlist rebuilds the note on every refresh rather than merging it, so a manual edit is replaced. Fix: Write call notes in lemlist on the call record. Also note the 65,000 character cap: longer content is cut from the end, which means the transcript goes first with no warning. - A manual unsubscribe never reached HubSpot. Why: lemlist only pushes the unsubscribe when the lead unsubscribed themselves from the campaign. A lead added to the Unsubscribe section by hand is not pushed. Fix: Handle manual opt-outs on the HubSpot side as well, as a process rather than a setting. In a team that manages opt-outs by hand this is a compliance gap rather than a nuisance. **What practitioners say** (14 threads from 2023 to 2026, read 2026-10-11): The threads are two years older than the integration they describe, which is the useful thing about them. In 2024 people complained that the fields were not customisable, and the documentation now describes per-field direction, custom fields, mandatory properties and default values, so that complaint has been answered. What has not changed is the reason people run lemlist against HubSpot rather than using HubSpot sequences, and that comes up repeatedly: deliverability controls HubSpot does not offer. One thread is about a reporting problem this integration contributes to rather than causes. - The 2024 complaint was that nothing was customisable, and that has changed (r/CRM, October 2024, 1 points): https://www.reddit.com/r/CRM/comments/1fzsnn5/lemlist_to_hubspot_mapping/ - Removing a contact from a HubSpot list actually stops the campaign (r/hubspot, October 2024, 2 points): https://www.reddit.com/r/hubspot/comments/1ft1e9e/cold_email_integrations/ - The reason people keep a sequencer is send limits, not features (r/sales, January 2025, 1 points): https://www.reddit.com/r/sales/comments/1hafp7q/should_i_kill_lemlist_and_use_hubspot_or/ - HubSpot buckets every integration under one source label (r/hubspot, April 2026, 5 points): https://www.reddit.com/r/hubspot/comments/1t07hcu/hubspot_groups_every_offline_contact_under_one/ - HubSpot discourages the thing this integration is for (r/hubspot, July 2023, 4 points): https://www.reddit.com/r/hubspot/comments/14vezqr/prospecting_emails/ Sources: https://help.lemlist.com/en/articles/10308771-how-to-configure-the-hubspot-integration-in-lemlist | https://help.lemlist.com/en/articles/8735296-map-lemlist-activities-to-hubspot | https://www.lemlist.com/pricing ### HubSpot and Google Workspace Four integrations under one name, all free to connect, each gated somewhere else. - Built as: Native, Marketplace app - Syncs: Two-way sync - Moves: Contacts, Activities, Messages, Tasks - Costs to turn on: Included on both sides. Setup: Minutes - Requires: Nothing on either side to connect. Click tracking needs an assigned Sales Hub seat; meeting prep needs Sales Hub Professional. - Full guide: https://www.reversecontact.com/integrations-hub/hubspot-integrations/hubspot-google-integration **Verdict.** This is four separate integrations wearing one name, which is why two people can both be right and disagree completely about what it does. A connected inbox, the Sales Chrome extension, calendar sync and the Google Sheets workflow action are different pieces with different requirements, and all four are free to turn on. What is not free is the half of each one teams assume comes with it: open tracking is on every plan and click tracking needs an assigned Sales Hub seat, calendar sync is on every plan and preparing for a meeting from inside Google Calendar needs Sales Hub Professional. Connect the inbox first, then buy a seat for the one feature you actually named. **What syncs:** - Sent and received email (two-way): A connected inbox sends one-to-one and sequence email from the CRM and logs replies back to the record. Available on all products and plans. - Email opens (in): Tracked by the Chrome extension on Gmail web. With data privacy settings on, opens are tracked only for contacts carrying a legal basis for processing. - Link clicks (in): Requires an assigned Sales Hub seat. Open tracking does not, and this is the only line on the table that separates them. - Calendar events (two-way): Primary calendar only. Description edits made on the CRM record reach attendees on Google Calendar and on no other provider. - Tasks to the calendar (out): HubSpot tasks appear on the connected calendar. Needs an assigned Sales or Service seat. - Rows into Google Sheets (out): A workflow action writes up to 20 cells per row. Nothing in the sheet comes back to HubSpot. **Which editions carry it** (rows HubSpot, columns Google Workspace): - Free or View-Only with Gmail or Workspace: Connect and log - Free or View-Only with Workspace with Advanced Protection: Not supported - Free or View-Only with Any inbox over IMAP: Connect and log - Assigned Sales Hub seat with Gmail or Workspace: Plus open and click tracking - Assigned Sales Hub seat with Workspace with Advanced Protection: Not supported - Assigned Sales Hub seat with Any inbox over IMAP: Plus open and click tracking - Sales Hub Professional or Enterprise with Gmail or Workspace: Plus meeting prep and follow-up - Sales Hub Professional or Enterprise with Workspace with Advanced Protection: Not supported - Sales Hub Professional or Enterprise with Any inbox over IMAP: Plus meeting prep and follow-up **How to connect it** (Each user connects their own inbox. Nobody can do it for them, and a View-Only seat cannot do it at all.. Five minutes per person, plus one decision an admin should make first.): 1. Decide which inboxes are personal and which are shared, before anybody connects [A conversation, not a screen]. HubSpot will not let one email account be both an individual work email and a team email. Connecting support@ as somebody's personal inbox is the mistake that is annoying to undo, because the fix is disconnecting it and reconnecting it as a shared inbox after people have been logging against it. 2. Check the account is one HubSpot can take [Google admin console]. A Gmail account enrolled in Google's Advanced Protection Program is not supported for an individual work email. Neither is a View-Only HubSpot seat, which is a licensing answer rather than a Google one. 3. Connect the inbox [HubSpot: Settings, General, Email, Connect personal email]. Personal email access permission is required. Choosing Gmail runs OAuth against Google; choosing IMAP instead limits what HubSpot receives to the address, the password, server details, metadata and message bodies, and connects none of your other Workspace apps. 4. Install the Chrome extension for the people who want tracking [Chrome Web Store]. The extension is what puts logging and tracking into the Gmail window. Email tracking and logging do not work with customised Gmail layouts, which is worth knowing before a rep tells you the extension is broken. 5. Connect the calendar, and know it reads one [HubSpot: Settings, General, Calendar]. The calendar integration syncs a single calendar, so a rep who runs a second shared calendar for customer sessions gets nothing from it. 6. Set what logs by default, then check the aliases [HubSpot: the extension settings]. For an email to log and create a contact, the sending address has to be a user in the account, a connected address, or a properly configured alias. A rep sending from an unregistered alias gets silence rather than an error. **How to check it worked:** - Send a tracked email to yourself from a rep account and confirm both the log and the open register. Logging and tracking are separate features and they fail separately. - Check that the contact timeline shows the message against the right contact rather than creating a second one. - Put a meeting in the connected calendar with an external attendee and confirm it lands on the contact record. - If your account has data privacy settings on, test with a contact that has a legal basis set, because opens are only tracked for those. Agent skill for this pair: https://www.reversecontact.com/integrations-hub/skills/hubspot-google.md **Field mapping:** - Gmail message maps to Logged activity on the contact. Needs the sender to be a user, a connected address or a configured alias, or the message logs against nobody. - Open and click maps to Tracking events on the timeline. A separate feature from logging, needing an assigned Sales Hub seat, and it stops working on a customised Gmail layout. - Google Calendar event maps to Meeting on the record. One calendar only, matched by attendee. An attendee who is not a contact creates no association. - HubSpot task maps to Calendar event. Goes out to Google rather than coming back, so the calendar is a view of the task list rather than a second place to manage it. - Workflow output maps to A row in Google Sheets. A one-way pipe of up to 20 cells per action, not a sync. The sheet does not read back. - Does not cross: Anything from an account on Google's Advanced Protection Program, which HubSpot does not support for an individual work email. - Does not cross: Opens from contacts with no legal basis for processing, once data privacy settings are on in the account. - Does not cross: A second calendar. The integration reads exactly one. **What breaks:** - **Calendar sync reads exactly one calendar.** Only the primary or default calendar syncs. A rep with a separate client calendar gets nothing from it, and there is no setting that adds a second one. You also choose between the Google calendar sync and the Outlook one; HubSpot will not run both at once, which is a real constraint in companies that have half migrated. - **A meeting with a stranger logs against nobody.** HubSpot will not create a contact record for a calendar guest who is not already a contact, and a guest only receives the meeting if the address on the invite matches the Email property on their contact record. So the first meeting with a new prospect, the one you most want on a timeline, is the one most likely to land nowhere. Private events never sync, and a recurring series brings across the next five upcoming events up to a year in advance rather than the whole series. - **Tracking stops at the browser.** Opens and clicks are tracked by the Chrome extension on Gmail web. Mail sent from the Gmail mobile app or any other client is not tracked, though the BCC address still logs it. Emails using customised Gmail layouts are not supported at all. Attachments over 50 MB are delivered and do not log, and turning logging on does not log anything you sent before you turned it on. - **The Sheets action is a 20 cell pipe, not a sync.** Each workflow action adds up to 20 cells of data per row, the header row must begin in the first column of the first row, and unlabelled columns receive nothing. HubSpot recommends a single workflow per sheet because two writing the same one duplicate data, and warns that formula-heavy sheets slow the action down or make it error. Formatting a date before it is written needs the Format data action, which is Data Hub Professional. **Failures people hit:** - A rep cannot connect their inbox at all. Why: A View-Only seat, or a Gmail account enrolled in Google's Advanced Protection Program. Neither is supported for an individual work email. Fix: Check the seat type first, since it is the one you can change. Advanced Protection is a Google policy decision and there is no HubSpot setting that works around it. - Emails from the shared address stopped logging properly. Why: The same account is being used as both an individual work email and a team email, which HubSpot does not allow. Fix: Disconnect it and reconnect it as a shared inbox. Decide which it is before the rollout, because the switch loses the arrangement people have got used to. - Logging works and tracking does not. Why: They are separate features. Tracking needs an assigned Sales Hub seat, and it does not work with customised Gmail layouts. Fix: Check the seat, then have the rep turn off the custom layout in Gmail and retest. - An email logged against nobody. Why: It was sent from an address that is not a user, a connected address or a configured alias. Fix: Add the alias in the connected inbox or in Profile and Preferences. Nothing errors when this is wrong, so it has to be checked rather than waited for. - Opens are not registering for some contacts. Why: Data privacy settings are on, and opens are only tracked for contacts with an assigned legal basis for processing. Fix: That is a legal configuration rather than a bug. Your legal team decides the basis; the tracking follows it. - Meetings from the second calendar never arrive. Why: The integration syncs one calendar. Fix: Move the meetings that matter onto the connected calendar, or accept that the other one is invisible to the CRM. **What practitioners say** (14 threads from 2022 to 2026, read 2026-10-11): Two kinds of thread. One is people discovering that the native path already does what they were about to build with Zapier, which is the recurring theme on the cheapest integration in this directory. The other, newer one is about the HubSpot connector for Gemini, which is a different product entirely and is being discussed as though it were part of this integration. - The shared support address is the thing people get wrong (r/hubspot, November 2023, 3 points): https://www.reddit.com/r/hubspot/comments/185xmg1/proper_way_to_connect_gmail_hubspot_for_a_company/ - People reach for Zapier for something that is already native (r/hubspot, November 2025, 4 points): https://www.reddit.com/r/hubspot/comments/1p67rs2/how_i_automated_new_gmail_leads_straight_into/ - The working setup is two pieces, and people describe it as one (r/hubspot, December 2023, 5 points): https://www.reddit.com/r/hubspot/comments/18hinzd/gmail_to_hubspot_contact_integration/ - The Gemini connector is a different product, and the threads do not say so (r/hubspot, September 2025, 26 points): https://www.reddit.com/r/hubspot/comments/1n7r2tn/hubspot_connector_for_gemini_amazing/ - The honest summary from a sysadmin thread: expect about 80 percent (r/sysadmin, January 2022, 6 points): https://www.reddit.com/r/sysadmin/comments/s2xgao/google_as_email_server/ Sources: https://knowledge.hubspot.com/connected-email/connect-your-inbox-to-hubspot | https://knowledge.hubspot.com/connected-email/track-and-log-emails-with-the-hubspot-sales-chrome-extension | https://knowledge.hubspot.com/integrations/use-hubspots-integration-with-google-calendar-or-outlook-calendar | https://knowledge.hubspot.com/connected-email/manage-your-meetings-in-google-calendar-with-the-hubspot-sales-chrome-extension | https://knowledge.hubspot.com/workflows/add-data-to-google-sheets-with-workflows ### HubSpot and Attio Not an integration. A one-time migration, and it will not update what it finds. - Built as: Native, Built on the API - Syncs: One way, out - Moves: Contacts, Companies, Deals - Costs to turn on: Needs a higher plan. Setup: Days - Requires: Attio Plus, Pro or Enterprise, a workspace admin, and a decision to leave HubSpot - Full guide: https://www.reversecontact.com/integrations-hub/hubspot-integrations/hubspot-attio-integration **Verdict.** The honest headline is that this is not an integration and treating it as one wastes a week: Attio's Import2 reads HubSpot and writes into Attio once, as a migration, with a sample run to check the mapping and an undo if it goes wrong. There is no sync in either direction and no supported way to run both CRMs in step. If that is what you need, the answer is the orchestration layer and a field-by-field decision about which system owns what, which is a project rather than a connector. Read this page as migration documentation, because that is the only sanctioned path between these two tools. **What syncs:** - People (out): Read out of HubSpot and matched into Attio by email address. Existing Attio records keep their attribute values. - Companies (out): Matched by domain, same rule: an existing record is not updated, it is matched. - Deals (out): Only if the Deals standard object is enabled in Attio first. Otherwise opportunities have nowhere to go. - Notes and tasks (out): Added even to records Attio already holds, which is the one thing that does reach an existing record. - Custom objects (out): Created by Import2 during the migration, so they do not have to exist in Attio beforehand. - Anything back to HubSpot (in): Nothing, ever. This is a one-time read of HubSpot and a write into Attio. **Which editions carry it** (rows Attio, columns HubSpot): - Free with CSV import: Available - Free with The Migrate CRM tool: Not available - Plus with CSV import: Available - Plus with The Migrate CRM tool: Available - Pro or Enterprise with CSV import: Available - Pro or Enterprise with The Migrate CRM tool: Available **How to connect it** (An Attio workspace admin, and somebody who can export from HubSpot. Import2 runs the migration itself, so there is a third party in the loop.. A day, spread over a sample migration, a review and the full run. Not an afternoon.): 1. Confirm the plan carries the migration tool [Attio: your plan]. Attio documents Migrate CRM as available on plus, pro and enterprise plans, and Import2 as usable on any paid Attio plan. A free workspace is doing this by CSV, which is a different job with different rules. 2. Fix the formatting in HubSpot before you export anything [HubSpot: your data]. Attio validates two things strictly. Phone numbers need a country code in the form plus country code then the subscriber number including area code, and Attio checks that country and area codes are real. Domains must be valid and Attio stores only the root, so a full URL with a path will fail. 3. Understand the two identifiers you cannot change [Attio: how records match]. Companies are keyed on Domain and people on Email address, and each value can only belong to one record. That is a deduplication rule and a constraint at once: two HubSpot contacts sharing an email cannot both exist in Attio. 4. Enable the objects you intend to bring across [Attio: object settings]. Attio asks which types of data to migrate, and some objects such as Deals have required attributes that must be present for the import to succeed. Enabling an object after the migration means doing part of it again. 5. Start the migration from the workspace menu [Attio: workspace name, Migrate CRM]. Click your workspace name at the top of the left sidebar, then Migrate CRM, find HubSpot in the list and click Migrate. From here Import2 is driving, and Attio is the destination rather than the operator. 6. Run the sample first and actually read it [Attio: the sample migration]. Verify the sample succeeded and review any new attributes that appeared, updating or archiving them as needed. Attributes created by a migration are the thing teams find six months later and cannot explain. 7. Request and run the full migration [Attio: Request full migration]. If prompted, click Request full migration and refresh the page, after which a button to start the full run appears. The gap between sample and full is where the review is supposed to happen. 8. Know how to start over, because it is brutal [Attio: Companies and People]. A clean redo means deleting all person and company records: clear all filters, tick the header checkbox, then More and Delete records. That is the documented reset, and it is the reason the sample step exists. **How to check it worked:** - Check the sample for attributes you did not expect. Attio tells you to review and archive them, and that advice is easy to skim past when the record counts look right. - Pick ten records you know well and compare them field by field against HubSpot. A migration that reports success and loses a field is the failure mode worth catching before the full run. - Test a phone number without a country code and a domain with a path. Both should fail, and seeing the validation work tells you what the full run will reject. - Count the records that did not arrive. Two HubSpot contacts sharing an email address become one Attio person, which is correct behaviour and still a number somebody should know. Agent skill for this pair: https://www.reversecontact.com/integrations-hub/skills/hubspot-attio.md **Field mapping:** - Company maps to Keyed on Domain. Each domain can only be associated with a single company record. Two HubSpot companies on the same domain become one Attio company, whether or not you meant them to. - Person maps to Keyed on Email address. Each email can only be linked to one person record. The same merge happens, and it is the main reason the record count on the other side is lower. - Domains maps to Root only, validated. attio.com and www.attio.com are accepted. Attio stores only the root domain, not full URLs or page paths, and an invalid format causes an error rather than being cleaned up. - Phone numbers maps to Plus country code, then the number. Attio validates country and area codes, so a wrong one errors. Hyphens are optional, which is the only forgiving part of the rule. - Deals maps to May have required attributes. Attio notes some objects have attributes that must be included for the import to succeed. Worth checking per object rather than assuming a contact-shaped rule applies. - Objects you did not enable maps to Not migrated. Selected at the start under Objects. Adding one later is another migration rather than an adjustment. - New attributes Attio creates maps to Yours to review or archive. Attio tells you to check them after the sample and update or archive as needed, which is the step that keeps a migrated workspace from looking like somebody else's. - Anything after the migration maps to Nothing. This is a one-time move. Attio does not keep reading HubSpot afterwards, and a record changed in HubSpot the next day stays changed only there. - Does not cross: Any ongoing sync. This is a migration tool, so nothing in HubSpot is read again once the run is finished and nothing is written back. - Does not cross: HubSpot marketing. Attio's own co-founder says in public that marketing is not something Attio has an offering for yet, which is the gap to plan around rather than discover. - Does not cross: Records that fail validation. A bad phone number or domain is an error rather than a cleaned value, so the data quality work happens in HubSpot before the export. **What breaks:** - **It is a migration, and migrations are one-time.** There is no ongoing sync, no scheduled run and no two-way option. Teams that import to evaluate Attio while still working in HubSpot end up with two CRMs drifting apart from the moment the import finishes, which is a worse position than not having imported. Decide whether you are migrating or evaluating before you run it. - **Existing records are matched, not merged.** Attribute values on records already in Attio are not updated. Notes and tasks are added; everything else on the record stays as it was. Attio's documented workaround is to delete the existing records first or import them separately by CSV, so a partial prior import makes the real migration harder rather than easier. - **Undo leaves the structure behind.** Undoing removes the imported records but not the lists, attributes and other structures the migration created. A second attempt therefore runs into a workspace that is already shaped by the first, which is usually fine and occasionally confusing when attribute names were auto-created from HubSpot properties you have since renamed. - **Admins only, and a plan gate.** Only workspace admins can run Import2 and it is available on Plus, Pro and Enterprise. Attio's free tier cannot do it, so the evaluation path many teams want, import a copy and have a look, requires buying a plan first. **Failures people hit:** - The migration fails on phone numbers. Why: Attio validates country and area codes and expects the format plus country code followed by the subscriber number including the area code. Fix: Normalise them in HubSpot before exporting. Hyphens are fine; a missing or wrong country code is not. - Domain values are rejected. Why: Attio verifies that domains are valid and stores only the root. A full URL or a malformed prefix errors rather than being tidied up. Fix: Strip to the root domain in HubSpot first. attio.com and www.attio.com are both accepted formats. - Fewer people arrived than HubSpot had. Why: Email address is the unique identifier for a person and each email can only be linked to one record, so duplicates in HubSpot merge on the way in. Fix: Expect it and count it. If those were genuinely different people sharing a mailbox, that has to be fixed in HubSpot before the migration rather than after. - A deal import failed with everything apparently present. Why: Attio notes that some objects, Deals among them, have required attributes that must be included for a successful import. Fix: Check the required attributes for each object you enabled, rather than assuming the rules that worked for contacts apply. - There are attributes in the workspace nobody created. Why: The migration creates attributes to hold what it found. Attio tells you to review them after the sample migration and update or archive as needed. Fix: Do that review at the sample stage. After a full run they are mixed in with everything else and much harder to attribute. - The migration needs redoing from scratch. Why: There is no partial undo. Attio documents a bulk delete as the way back. Fix: Navigate to Companies or People, clear all filters, tick the first checkbox next to the column header, then More and Delete records. This is why the sample run exists. - An error appears mid-migration with no obvious cause. Why: Import2 is running the migration, not Attio, so the diagnostic path leaves Attio. Fix: Email help@import2.com with Attio support copied at support@attio.com, including the migration ID and a screenshot of the error. That is the documented route. - Something in HubSpot changed after the migration and Attio does not know. Why: By design. This is a one-time move with no ongoing sync in either direction. Fix: Pick a cutover date and stop writing to HubSpot. Running both as systems of record is the failure this pair makes easy and nothing here prevents it. **What practitioners say** (14 threads from 2024 to 2026, read 2026-10-11): This pair gets discussed as a choice rather than a procedure, and the most useful thread is an AMA where Attio's own co-founder answers questions about where HubSpot is still ahead. The honest summary of the set: Attio is widely described as the cleaner product, the integration surface and the marketing side are the acknowledged gaps, and the practitioners who hit those gaps hit them trying to connect the tools this directory covers. - Attio's co-founder names marketing as a gap, unprompted (r/CRM, December 2025, 3 points): https://www.reddit.com/r/CRM/comments/1pd8fde/im_the_cofounder_of_attio_crm_we_just_raised_a_50/ - The integration surface is the acknowledged difference, and the answer is an SDK (r/CRM, December 2025, 3 points): https://www.reddit.com/r/CRM/comments/1pd8fde/im_the_cofounder_of_attio_crm_we_just_raised_a_50/ - Practitioners hit the integration gap on exactly these tools (r/CRMSoftware, January 2026, 2 points): https://www.reddit.com/r/CRMSoftware/comments/1qgbhkb/what_made_you_switch_crms_and_what_almost_made/ - The product preference is real and so is the onboarding cost (r/gtmengineering, December 2025, 3 points): https://www.reddit.com/r/gtmengineering/comments/1plfyrf/attio_vs_hubspot/ - Attio says the security and support investment is plan-independent (r/CRM, December 2025, 3 points): https://www.reddit.com/r/CRM/comments/1pd8fde/im_the_cofounder_of_attio_crm_we_just_raised_a_50/ Sources: https://attio.com/help/reference/imports-exports/migrate-data-from-another-crm | https://attio.com/help/reference/attio-101/introduction-to-data-importing ### Salesforce and LinkedIn Sales Navigator The original CRM Sync target, with the same Advanced Plus gate. - Built as: Native, Marketplace app - Syncs: Two-way sync - Moves: Contacts, Companies, Deals, Activities - Costs to turn on: Paid add-on or licence. Setup: Hours - Requires: Sales Navigator Advanced Plus, and a Salesforce edition with API access - Full guide: https://www.reversecontact.com/integrations-hub/salesforce-integrations/salesforce-linkedin-integration **Verdict.** Sales Navigator's CRM Sync was built for Salesforce first and the Salesforce side is the more mature of the two. The edition requirement is identical to HubSpot's: Advanced Plus, not Advanced. What you get for it is leads and accounts auto-saved into Sales Navigator lists, InMail and message activity written back as Salesforce activities, and CRM badges on search results so reps can see what is already owned. **What syncs:** - Leads and Contacts (two-way): Auto-Save imports them into Sales Navigator lists; new records can be created from Sales Navigator. - Accounts (two-way): Matched, so account pages carry CRM context and searches can filter on ownership. - Opportunities (in): Open pipeline visible in Sales Navigator, and the basis for revenue attribution reporting. - Sales Navigator activity (out): InMails, messages and notes logged as Salesforce activities. **Which editions carry it** (rows Salesforce, columns LinkedIn Sales Navigator): - Professional with Core: Nothing - Professional with Advanced: Nothing - Professional with Advanced Plus: Only with API access and Chatter - Enterprise or Unlimited with Core: Nothing - Enterprise or Unlimited with Advanced: Nothing - Enterprise or Unlimited with Advanced Plus: The whole integration - Performance or Developer with Core: Nothing - Performance or Developer with Advanced: Nothing - Performance or Developer with Advanced Plus: The whole integration **How to connect it** (A Salesforce admin and a Sales Navigator contract admin. LinkedIn recommends connecting as a dedicated integration user rather than as a person.. A day of admin work, then up to a week before the first full import finishes.): 1. Check the Salesforce edition and turn on My Domain [Salesforce Setup]. Enterprise, Performance, Unlimited and Developer are supported outright. Professional works only if API Access and Chatter are enabled, which LinkedIn notes may carry an extra Salesforce fee. My Domain has to be on before the Lightning install, not after it. 2. Create a dedicated integration user to connect as [Salesforce: Users]. LinkedIn recommends this over a personal admin account, and the troubleshooting guide says why: when that person changes role or loses the permission, the sync disconnects and the fix is to un-sync and re-sync as a service user. Do it now rather than after an incident. 3. Pick the install option before you install anything [Salesforce: Quick Find, LinkedIn Sales Navigator]. The AppExchange Package is the recommended one: it carries data validation, the Not at Company flag, and works in Classic. The Native Integration is only needed if you want InMail or connection-request steps inside Salesforce Engagement cadences. Choosing the second and then wanting data validation means installing the first anyway. 4. Install, and choose who gets it [The AppExchange Package tab]. Install for All Users or for specific profiles, then finish the page layouts. On Classic you add the LinkedIn Member and Company sections to Lead, Contact, Account and Opportunity layouts by hand, with the Visualforce components set to 100% width and 675 height. 5. Assign the two permission sets, and clone them if they fight you [Salesforce: Permission Sets]. LinkedIn Sales Navigator Standard User goes to every non-admin who needs the embedded profile; Setup User goes to a non-CRM admin doing the install. Managed permission sets cannot be edited, so an insufficient-access error means cloning the set and adding field-level access: Website, Industry and BillingAddress on Account, and ConvertedAccountId, Company, Website, Industry and Address on Lead. 6. Connect the CRM from the Sales Navigator side [Sales Navigator: Admin, Admin Settings, CRM, Production]. Select Salesforce, sign in as the integration user, choose Business account, then set what imports and what exports: auto-save, creating and updating leads and contacts, and activity logging. ROI reporting is on the Advanced Settings page, where you also name the field holding won opportunity value and its currency. 7. Turn on writeback, and warn people about the 90 days [Admin Settings: CRM, Exported to CRM]. Switch on logging for messages and InMails, notes, calls and Smart Links. Each user then authenticates with Salesforce individually and has to do it again roughly every 90 days, which arrives as a surprise sign-in prompt a quarter after go-live. Calls only log from the Sales Navigator mobile app. 8. Turn on data validation last, and check your validation rules first [Admin Settings: CRM, Production, Exported to CRM]. Check the Contact validation rules in Object Manager before enabling Validate CRM Data, because a rule that blocks the bulk update makes the Not at Company flag land on some contacts and not others. Jobs can be scheduled from the LinkedIn Sales Navigator Assistant, which also shows what else is already running at that hour. **How to check it worked:** - Open a Lead, a Contact, an Account and an Opportunity and confirm the embedded profile appears on all four. It is page-layout work, and it is normal for three to work and one to be missed. - Check the last sync timestamp in Admin Settings. The first ingestion can take up to a week depending on the size of the org, and after that updates land every 12 hours, so "nothing has synced" on day one is expected rather than broken. - Send one InMail with Add to CRM selected and find it in Salesforce. That tests writeback, matching and the user authentication in a single action. - Have a non-admin do the same thing. An admin-only Sales Navigator licence can configure the integration and cannot verify that it works for the team, which LinkedIn states explicitly. Agent skill for this pair: https://www.reversecontact.com/integrations-hub/skills/salesforce-linkedin.md **Field mapping:** - Lead and Contact maps to Sales Navigator lead. Matched automatically with a confidence score, correctable by hand through Match Correction. A LinkedIn profile links to exactly one CRM record, so with duplicates in Salesforce only one of them gets the integration. - Account maps to Sales Navigator account. Badged the same way, and the badge shows on records the user cannot actually open, which is expected rather than a permission leak: the content stays restricted. - Opportunity maps to Pipeline context and ROI reporting. Flows one way, into Sales Navigator, and is what the revenue attribution report is built on. You pick the field holding won value during setup. - InMail, message, note, Smart Link maps to Salesforce Task or Note. Writeback lands only on Account, Contact and Lead records, and on Accounts only notes are supported. Calls log only from the mobile app. - Not at Company flag maps to A field on the Contact. Data validation writes it in bulk, which is why a Contact validation rule that blocks the update silently halves your coverage. - Does not cross: Anything a seller did before 23 June 2021. LinkedIn documents retroactive writeback as covering only data from that date on. - Does not cross: Activity on an Opportunity. Only Account, Contact and Lead receive writeback at all. - Does not cross: The old LinkedIn Task record type. It is retired, activity now writes as a standard Task, and reports built on the custom type return nothing. **What breaks:** - **Advanced Plus or nothing, and the Salesforce gate is stricter than the HubSpot one.** LinkedIn's admin setup guide for Salesforce requires Advanced Plus for CRM Sync, Embedded Profiles and data validation alike. On the HubSpot pair the embedded card runs a tier down on Advanced; on this one it does not, so a team that compared notes with a HubSpot shop will have been told something that is true over there and false here. - **API access is an edition feature.** Salesforce editions without API access cannot run this, which rules out the lower editions regardless of what Sales Navigator edition you hold. - **Install touches Salesforce metadata.** Expect a Salesforce admin, a sandbox pass and a change window. This is not a marketplace click on the Salesforce side. **Failures people hit:** - The embedded profile does not appear on a record page. Why: LinkedIn lists five causes in order, and page layouts are the usual one: the layout is not activated for that object, the Standard User permission set is missing, Apex classes and Visualforce pages beginning with LID are not enabled on a profile-restricted install, the licence is not Advanced Plus, or the browser is at fault. Fix: Work down that order rather than guessing. Try another browser first because it costs nothing, then check the layout on all four objects. - The sync disconnected after somebody changed role. Why: The refresh token belonged to a personal admin account that was revoked or had its permissions changed. Fix: Un-sync and re-sync using a dedicated integration user. This is the failure the integration-user recommendation exists to prevent. - Everything stopped and there was no warning. Why: A CRM auto-disconnect error. An inactive admin user, an expired refresh token, an inactive org or an IP restriction range that excludes LinkedIn all start a three-day buffer during which nothing syncs, after which the CRM disconnects itself. Fix: Fix the cause, then click Disconnect and Connect. Three days is the whole warning you get, so put the integration user on the list of accounts nobody deactivates. - The first import looks half finished. Why: Initial ingestion is still running. It can take up to a week depending on the size of the org, and only then does the 12-hour update cycle start. Fix: Check the last sync timestamp in Admin Settings rather than counting records. Do not re-run the setup, which restarts the clock. - Insufficient access despite holding the permission set. Why: Managed package permission sets cannot include certain standard fields used as URL parameters. Fix: Clone the set and add field-level access: Website, Industry and BillingAddress on Account, and ConvertedAccountId, Company, Website, Industry and Address on Lead. - A record is matched to the wrong person. Why: Matching is score-based and picks a best guess, which is occasionally the wrong one. Fix: Use Match Correction from the embedded profile. The correction is shared across the contract, so one person fixing it fixes it for everybody. - Only some contacts get the Not at Company flag. Why: Contact validation rules are failing the bulk API update for the rest. Fix: Adjust the rules to allow the field update, or exclude the batch job owner from triggering them. Allow 48 hours before concluding anything, and expect a sandbox never to finish a full run. - Reports credit every activity to one person. Why: The licence holder owns the shared information, so activity reports attribute to them rather than to the seat that did the work. Fix: Report on the creator field instead. If your old reports return nothing at all, they are probably built on the retired LinkedIn Task record type and need moving to the standard Task with a subject-line filter. **What practitioners say** (14 threads from 2021 to 2026, read 2026-10-11): The threads are mostly people trying to get LinkedIn data into Salesforce by some route other than this one, which is the useful signal. What they want is almost always the same thing: current employment on records that are going stale. The integration answers part of that through data validation, and the part it does not answer is why these threads keep ending in a discussion of scraping, waterfalls and manual work. - The constraint is deliberate, and practitioners name it as such (r/salesforce, May 2026, 5 points): https://www.reddit.com/r/salesforce/comments/1ts4jlq/has_anyone_used_linkedin_sales_navigator_with/ - The real job is keeping employment current, not seeing a profile (r/salesforce, February 2025, 7 points): https://www.reddit.com/r/salesforce/comments/1iv9rzi/current_linkedin_sales_navigatorsf_integration/ - Nobody gets there with one source (r/salesforce, November 2025, 7 points): https://www.reddit.com/r/salesforce/comments/1otc5yc/how_to_integrate_linkedin_data_into_salesforce/ - The reason people want it has not changed in five years (r/sales, June 2021, 5 points): https://www.reddit.com/r/sales/comments/o6iflp/salesforcelinkedin_sync/ - Sellers live in LinkedIn and the CRM shows none of it (r/salesforce, July 2022, 6 points): https://www.reddit.com/r/salesforce/comments/vp46ah/asking_for_insight_salesforce_and_linkedin/ Sources: https://www.linkedin.com/help/sales-navigator/answer/a8037044 | https://www.linkedin.com/help/sales-navigator/answer/a16260001 | https://www.linkedin.com/help/sales-navigator/answer/a16656004 ### Salesforce and Clay The same read, enrich, write loop, against an org with stricter rules. - Built as: Native, Built on the API - Syncs: Two-way sync - Moves: Contacts, Companies, Deals, Lists - Costs to turn on: Needs a higher plan. Setup: Hours - Requires: Clay Growth or above, a Salesforce edition with API access, and a full user licence to authenticate - Full guide: https://www.reversecontact.com/integrations-hub/salesforce-integrations/salesforce-clay-integration **Verdict.** Mechanically this is the HubSpot pair again: Lookup reads, enrichment fills, Update writes, a schedule keeps it current. What changes is the environment. Salesforce orgs carry validation rules, required fields, duplicate rules and triggers that will reject a write the table thought succeeded, so the first hour goes on reading what the org enforces rather than on building the table. The second thing that changes is matching: Salesforce has no single clean key for a company, which is why the useful action on this pair is the SOQL lookup rather than the object lookup. **What syncs:** - Salesforce to Clay (in): Read a filtered set of leads, contacts, accounts or opportunities into a table. - Enrichment (event): Any provider or HTTP API as a column, including ones with no AppExchange listing. - Clay to Salesforce (out): Create and Update write back. Validation rules and required fields apply, and will reject rows. - Refresh (two-way): Auto-update on a schedule turns the backfill into a maintained field. **Which editions carry it** (rows Salesforce, columns Clay): - Full user licence with User Sign In (OAuth): a working connection - Full user licence with Client Credentials: a working connection - Integration User licence with User Sign In (OAuth): an approval error - Integration User licence with Client Credentials: a working connection - API Only licence with User Sign In (OAuth): an approval error - API Only licence with Client Credentials: a working connection **How to connect it** (A Salesforce admin, plus whoever owns the Clay workbook. The admin half is not optional here, because three of the settings are org-level.. An afternoon, most of it in Salesforce Setup rather than in Clay.): 1. Check the Clay plan and the Salesforce edition together [Clay: pricing, and Salesforce: your contract]. CRM integrations start on Clay Growth, which the Salesforce integration documentation does not mention. On the Salesforce side you need an edition with API access, because every read and write here spends from the org's daily API allocation. 2. Decide which licence Clay will authenticate as [Salesforce: Setup, Users]. Clay documents that Integration User and API Only licences cannot complete the OAuth sign-in flow. Either authenticate with a full user licence, or use the Client Credentials flow with Run As set to the integration user. Picking this wrong is the one failure that looks like a Clay bug. 3. Grant the profile permission before the first attempt [Salesforce: Setup, Profiles]. The authenticating user's profile needs Approve uninstalled connected apps. Without it the approval screen refuses, and the error Salesforce returns names nothing about the permission. 4. Pre-approve the connected app at the org level [Salesforce: Setup, Connected Apps OAuth Usage]. Set IP Relaxation to Relax IP Restrictions and Permitted Users to All users may self-authorize. If you are using Client Credentials instead, enable the flow in two places: the app's Settings tab and the org's Policies tab. One without the other fails. 5. Import from a list view rather than a report [Clay: Import records from a Salesforce list]. Reports are capped at 2,000 records and only tabular and matrix reports are supported. A list view that is not SOQL-compatible carries the same 2,000 cap. Clay recommends list views for anything larger, and a report import without uniqueness fields uses the whole row as the identifier, which duplicates rows. 6. Build the match before you build the enrichment [Clay: Lookup records via SOQL]. The object Lookup action has an Exact match switch and nothing more. The SOQL lookup is where a real match goes, with LIKE and wildcard operators against a domain you have normalised first. This is the step practitioners describe rebuilding, and the order above is what saves it. 7. Write with Upsert where you have an external ID, Update where you have the record ID [Clay: Upsert object, Update record]. Upsert requires an external ID on the Salesforce object, which is what a normalised domain is for. Update takes the record ID and has the Ignore blank values switch. Create takes a Duplicate rule override, which is a decision rather than a default. 8. Run it against a sandbox, read the errors, then schedule it [Clay: run settings]. Validation rules, required fields, duplicate rules and Apex triggers all still apply, and a rejected row is quieter in Clay than it is in Salesforce. Ten rows in a sandbox tells you what the org enforces, which is the thing the table has to be designed around. **How to check it worked:** - Authenticate once with the licence you intend to use in production. A full user licence that works tells you nothing about the integration user you were planning to switch to later. - Import a list view you know holds more than 2,000 records and count what arrives. That tells you whether the view is SOQL-compatible, which is not stated anywhere in the view itself. - Write ten records in a sandbox and read the error column, not the run status. A completed run with ten rejected rows looks exactly like a successful one from the table. - Run your SOQL match against twenty accounts you know the answer for and count the false positives. A matcher that is right 50% of the time is the documented starting point rather than a misconfiguration. Agent skill for this pair: https://www.reversecontact.com/integrations-hub/skills/salesforce-clay.md **Field mapping:** - A list view maps to Import records from a Salesforce list. Takes the object and the view. A view that is not SOQL-compatible is capped at 2,000 records, and nothing on the view says which kind it is. - A report maps to Import records from a Salesforce report. Tabular and matrix reports only, 2,000 records maximum. Set Uniqueness fields, because without them Clay identifies a row by the whole row and near-identical rows arrive twice. - Any object, by query maps to Lookup records via SOQL. A full SOQL query as the input. This is the action people end up using for account matching, with LIKE and wildcards doing the work Salesforce's own fuzzy matching does badly. - Accounts, contacts, leads maps to Lookup record. Takes the object and an optional Exact match switch. Exact match on a normalised domain is reliable; anything looser is where the false positives come from. - Any object with an external ID maps to Upsert object. The external ID is required, which is the whole reason teams write a cleaned domain back to the account first. Without one, this action has nothing to match on. - Any object, by record ID maps to Update record. Takes the record ID, the object, and an optional Ignore blank values switch. The record ID is the only key here that cannot be ambiguous. - Any object maps to Create record. Takes the object and a Duplicate rule override. Overriding your own duplicate rules from a table is a decision somebody should make deliberately. - Leads maps to Convert lead. Takes the lead ID and a converted status, with optional account ID, contact ID, an opportunity switch, opportunity ID and name. Leave the name blank and the lead's name is used. - Does not cross: The org's rules. Validation rules, required fields, duplicate rules and Apex triggers are enforced on the Salesforce side and reported quietly on the Clay side, so a run that completed is not a run that landed. - Does not cross: Picklist labels. A picklist takes the API name rather than the display label, and multi-select values are separated with semicolons rather than commas. - Does not cross: More than 2,000 records from a report, or from a list view that is not SOQL-compatible, however many the view itself shows you. **What breaks:** - **The org will reject writes.** Validation rules, required fields, duplicate rules and Apex triggers all still apply. A write that fails in Salesforce is not always loud in Clay, so check the error column rather than assuming a run that completed also succeeded. - **API calls are an allocation.** Salesforce meters daily API requests by edition and licence count. A large table writing row by row consumes that allocation alongside every other integration in the org. - **Actions bill on the attempt.** Same economics as everywhere else in Clay: a miss costs the same as a hit, so effective cost per filled field is the action rate divided by your match rate. **Failures people hit:** - OAUTH_APPROVAL_ERROR_GENERIC on sign in. Why: Clay documents four causes for this one message: an Integration User or API Only licence, a connected app that is not pre-approved, SSO enforcement blocking the approval screen, or a profile missing Approve uninstalled connected apps. Fix: Work through all four rather than guessing, because the error names none of them. If the licence is the cause, Client Credentials with Run As is the documented route rather than a licence upgrade. - Bad value for restricted picklist. Why: The text Clay sent does not match a picklist option. Spelling and case both count. Fix: Match the option exactly. If the value came from an enrichment, map it through a formula column rather than writing the provider's wording straight into a restricted field. - A multi-select picklist writes only the first value. Why: The wrong delimiter. Salesforce expects semicolons between values and Clay will happily send commas. Fix: Use semicolons. This is the one error on the list where the symptom looks like a truncation rather than a format problem. - A field refuses a value that looks correct. Why: A display label was used where the API name is required. The two are different strings and only one of them works. Fix: Read the API name in Salesforce Setup and use that. A field somebody renamed years ago is the usual case. - A report import stopped at 2,000 rows. Why: That is the documented cap, and it applies to a list view that is not SOQL-compatible as well. Fix: Import from a SOQL-compatible list view instead. For anything larger than that, the SOQL lookup action is the route rather than a second report. - The same records arrived twice from a report. Why: No uniqueness fields were set, so Clay identified each row by the entire row. Two rows differing in one whitespace character are two records. Fix: Set Uniqueness fields on the report source. The account ID or a normalised domain is what belongs there. - The run completed and Salesforce has none of it. Why: Validation rules, required fields, duplicate rules or an Apex trigger rejected the rows. The rejection is loud in Salesforce and quiet in Clay. Fix: Read the error column on the write action rather than the run status, and rehearse in a sandbox. A Create action carries a Duplicate rule override, which is sometimes the right answer and should never be the default. - Lead conversion associated the wrong account. Why: The match was fuzzy rather than exact. Practitioners put Salesforce's own matching at roughly half right on an org with naming variations and older imports. Fix: Score the match in Clay and only auto-convert above a threshold, with everything below it going to a review queue. The alternative is normalising a domain on every account first and matching on that exactly. **What practitioners say** (14 threads from 2024 to 2026, read 2026-10-11): Two subjects dominate, and neither is whether the connection works. The first is matching: Salesforce's own fuzzy account matching is described as roughly half right, and every practitioner who solved it moved the matching into Clay as a SOQL query with a confidence score in front of it. The second is the plan, raised by somebody implementing on Starter and building a proof of concept for Growth, which is the gate above seen from the inside. The jokes about pottery outscore both. - The native fuzzy matching is about half right, so people replace it (r/gtmengineering, November 2025, 2 points): https://www.reddit.com/r/gtmengineering/comments/1p2zjkv/account_matching_and_lead_conversion_with/ - Moving the match into Clay is the answer the thread converges on (r/gtmengineering, November 2025, 11 points): https://www.reddit.com/r/gtmengineering/comments/1p2zjkv/account_matching_and_lead_conversion_with/ - The working pattern is a score and a threshold, not a match (r/gtmengineering, November 2025, 1 points): https://www.reddit.com/r/gtmengineering/comments/1p2zjkv/account_matching_and_lead_conversion_with/ - The answer Clay's own team gives is also a SOQL query (r/gtmengineering, November 2025, 1 points): https://www.reddit.com/r/gtmengineering/comments/1p2zjkv/account_matching_and_lead_conversion_with/ - The plan gate is something people plan around rather than discover (r/gtmengineering, April 2026, 1 points): https://www.reddit.com/r/gtmengineering/comments/1shu76k/learning_clay_httpwebhooks_without_growth_plan/ Sources: https://university.clay.com/lessons/importing-from-your-crm-crm-enrichment | https://university.clay.com/docs/salesforce-integration-overview | https://www.clay.com/pricing | https://resources.docs.salesforce.com/latest/latest/en-us/sfdc/pdf/salesforce_app_limits_cheatsheet.pdf ### Salesforce and Slack The one pair where the same company owns both sides. - Built as: Native, Marketplace app - Syncs: Events only - Moves: Deals, Activities, Messages, Contacts - Costs to turn on: Needs a higher plan. Setup: Minutes - Requires: Sales Cloud, plus a Slack workspace you can install apps into - Full guide: https://www.reversecontact.com/integrations-hub/salesforce-integrations/salesforce-slack-integration **Verdict.** Salesforce owns Slack, and this is the only integration in the directory where that is true. It shows in the depth: record search and updates from inside Slack, channel-to-record association, alerts driven by Flow, and Slack as a surface for approvals rather than only for notifications. It does not show in the setup, which is still a Salesforce admin project rather than a toggle. **What syncs:** - Record search and updates (two-way): Find and edit Salesforce records from Slack, so updates happen where the conversation is. - Flow to channel (out): Flow can post to Slack on any record event, which is the general-purpose alerting path. - Channel to record (two-way): Channels associated with opportunities or accounts, so the deal room and the record are the same thing. - Approvals (two-way): Approval requests actioned in Slack and written back, which is the feature that changes cycle time. **Which editions carry it** (rows Salesforce, columns Slack): - Professional with Free: Check API access first - Professional with Pro or Business+: Check API access first - Professional with Enterprise Grid: Check API access first - Enterprise with Free: One org - Enterprise with Pro or Business+: Up to 21 orgs - Enterprise with Enterprise Grid: Up to 21 orgs - Unlimited or Performance with Free: One org - Unlimited or Performance with Pro or Business+: Up to 21 orgs - Unlimited or Performance with Enterprise Grid: Up to 21 orgs **How to connect it** (A Slack workspace owner or admin and a Salesforce system admin, passing it back and forth. Neither can finish it alone.. An afternoon for the connection and the permission sets, longer if you are activating flows.): 1. Request the connection from the Slack side [Slack: workspace name, Tools and settings, Manage Salesforce Organizations]. Click Connect Salesforce Org, enter your org URL, and choose whether accounts map on Email or on SAML NameID. Pick the mapping field deliberately: it decides which Slack member becomes which Salesforce user, and changing your mind later means remapping everybody. 2. Approve it from the Salesforce side [Salesforce Setup: Platform tools, Slack, Manage Slack Connection]. Select the same mapping field under User Configuration, accept the terms, and click Approve. The admin doing this needs Modify All Data and the Connect Salesforce with Slack permission. 3. Activate the pending connection back in Slack [Slack: Manage Salesforce Organizations]. Select the pending connection, review it and click Activate. Until this third step, the first two look finished and nothing works, which is where most of the confusion on this pair starts. 4. Decide how members get mapped [Slack: Manage Salesforce Organizations, Users tab]. Automatic mapping matches on the field you chose. Otherwise add people individually or by CSV, and export the User Mapping CSV from the same tab to see who is still unmatched. Anyone on a Unified Employee license can only be mapped automatically, so turn automatic mapping on if your org uses it. 5. Give each user the Salesforce permission they need [Salesforce Setup: permission sets]. Every Slack user, including the workspace owner who installs the app, needs a permission set on their Salesforce licence carrying Connect Salesforce with Slack. Using Sales Cloud for Slack needs the Slack Sales User permission on top. If the licence does not support the permission, Salesforce throws an error when you try to assign the set rather than when the user tries to work. 6. Enable the app and its features in Salesforce [Salesforce Setup]. Turn on Slack apps, then turn on Sales Cloud for Slack and configure the features you want. Users who will create sales channels from Slack need access to the Swarms object; creating them from Salesforce takes further setup. 7. Have your Slack admin install the app in the workspace [Slack App Directory]. Installing for everyone needs administrative access to the Slack account. Some workspaces only let admins authorise apps at all, and some require admin approval per request, so check which of those you are before promising a date. 8. Activate the notification flows you actually want [Salesforce Flow Builder]. Notifications are flows, and they ship as templates you copy and activate. Two feed channels are predefined, Deals to Watch and Deals Won. Editing a copied flow after saving it can stop the notification firing or leave its text describing something it no longer does, and Deals to Watch is the one flow Salesforce documents as safe to customise. **How to check it worked:** - Check the connection reads as active in Manage Salesforce Organizations rather than pending. A pending connection is the single most common cause of "we installed it and nothing happened". - Export the User Mapping CSV and count the unmapped members. Those people will see nothing, and they will report it as the integration being broken. - Have one non-admin open a record from Slack and change a field. That tests the permission set rather than your own access. - Trigger one activated flow deliberately and confirm the message arrives in the channel you expected rather than in a default one. Agent skill for this pair: https://www.reversecontact.com/integrations-hub/skills/salesforce-slack.md **Field mapping:** - Slack member maps to Salesforce user. Matched on Email or SAML NameID, whichever you picked at setup, or mapped by hand or CSV. An unmapped member gets none of the app, which looks like a broken install rather than a missing row. - Opportunity maps to Channel, with the record attached. The deal room and the record become the same thing, which is the feature most teams are actually buying. - Account maps to Channel, with the record attached. Same mechanism at account level, for teams that run a named-account motion rather than a deal motion. - Approval request maps to Slack message with the actions on it. Actioned in Slack and written back to the record, which is the half that changes cycle time rather than visibility. - Any record event, through Flow maps to A channel or direct message. The general-purpose path. Flow decides what fires, so anything you can express in Flow you can send. - Does not cross: Slack Connect channels. Sales Cloud for Slack does not support them, so a shared channel with a customer in it is outside this integration. - Does not cross: Government Cloud orgs. Salesforce documents that you cannot connect Slack to one. - Does not cross: More than one org per workspace on Slack Free. The connection itself is available on every Slack plan, but additional orgs are not. **What breaks:** - **Still a Salesforce admin project.** Common ownership has not made this a self-serve install. Flow work, permission sets and a change window are all still required. - **Alert volume is the real constraint.** The same failure mode as every CRM-to-Slack pair: a channel that fires constantly gets muted, and a muted channel is worse than no alerting because everyone assumes it works. - **The connection is a three-step handshake across two consoles.** Slack requests it, a Salesforce admin approves it, and Slack activates it. The first two steps report success on their own, so a connection that is still pending looks exactly like a finished install that does nothing. - **One workspace to one org, and Slack Free stops there.** Sales Cloud for Slack pairs a single Slack workspace with a single Salesforce org. Up to 20 additional orgs can be connected on Slack Pro, Business+ and Enterprise Grid, and on Free you get the one. - **Slack Connect channels and Government Cloud are out.** Sales Cloud for Slack does not support Slack Connect, so a shared channel with a customer in it is outside the integration, and Salesforce documents that Slack cannot be connected to a Government Cloud org at all. Neither is a setting. **Failures people hit:** - Everything is set up and nothing happens in Slack. Why: The connection is still pending. It takes three moves in two consoles, and the Slack-side Activate is the one people miss because the first two steps report success. Fix: Open Manage Salesforce Organizations in Slack, select the connection and click Activate. Confirm it reads active before you debug anything else. - The app works for admins and not for the team. Why: Each user needs a permission set on their Salesforce licence carrying Connect Salesforce with Slack, and Sales Cloud for Slack needs Slack Sales User on top. An admin testing with their own access never sees this. Fix: Assign the permission sets, then test as a non-admin. If assigning the set throws an error, the user licence does not support the permission, which is a licensing answer rather than a configuration one. - Some members are not matched to a Salesforce user. Why: Automatic mapping matches on Email or SAML NameID only. Anyone whose Slack email differs from their Salesforce username falls out, and Unified Employee licence users cannot be mapped any other way. Fix: Export the User Mapping CSV from the Users tab, map the stragglers individually or by CSV, and switch automatic mapping on if you use Unified Employee licences. - Features fail intermittently for no visible reason. Why: Salesforce IP restrictions. Slack documents them as a cause of features not working as expected, which presents as flakiness rather than as a permission error. Fix: Check the org IP restrictions against the Slack connection before spending a day in debug logs. - The connection broke after a Salesforce change. Why: The org URL changed. The stored connection still points at the old one. Fix: Update the connection in Slack with the new org URL. - A notification stopped firing, or says the wrong thing. Why: A copied flow template was edited after it was saved. Salesforce documents that this can stop the notification or leave its text describing behaviour it no longer has. Fix: Re-copy the template and apply your change in the one place it is supported, the Deals to Watch feed channel flow, or keep the edit outside the template. - A shared channel with a customer gets none of this. Why: Sales Cloud for Slack does not support Slack Connect channels. Fix: Keep the record-linked channel internal and treat the customer channel as a separate surface. There is no setting that changes this. **What practitioners say** (14 threads from 2020 to 2026, read 2026-10-11): Two things come through across these threads and they pull in opposite directions. People who use both products daily want exactly what this integration already does, and describe it as something they wish existed. People who have set it up describe a Salesforce admin project. Common ownership is read by practitioners as a reason to expect depth rather than ease, and the licensing question comes up unresolved more than any other. - The people who want it most do not know it already ships (r/salesforce, November 2025, 18 points): https://www.reddit.com/r/salesforce/comments/1ox8clr/did_slacks_acquisition_help_sales_force/ - Nobody is sure what licence it needs, including people recommending it (r/salesforce, November 2025, 25 points): https://www.reddit.com/r/salesforce/comments/1ox8clr/did_slacks_acquisition_help_sales_force/ - Setting it up surprised somebody who builds on Salesforce for a living (r/salesforce, November 2023, 55 points): https://www.reddit.com/r/salesforce/comments/184nmk5/made_a_quick_tutorial_on_how_to_setup_a_direct/ - Owning both companies is not the same as integrating them (r/salesforce, November 2025, 31 points): https://www.reddit.com/r/salesforce/comments/1ox8clr/did_slacks_acquisition_help_sales_force/ - Running Slack and Teams at once is normal, not a transition state (r/salesforce, November 2025, 18 points): https://www.reddit.com/r/salesforce/comments/1otsqgp/slack_and_teams/ Sources: https://slack.com/help/articles/30754346665747-Connect-Salesforce-and-Slack | https://help.salesforce.com/s/articleView?id=sf.slack_apps_sales_review_considerations_for_sales_cloud_for_slack.htm&language=en_US&type=5 | https://help.salesforce.com/s/articleView?id=sf.slack_apps_sales_enable_sales_cloud_for_slack_in_salesforce.htm&language=en_US&type=5 | https://slack.com/help/articles/30754346665747-Connect-Salesforce-and-Slack ### Salesforce and Reverse Contact No AppExchange listing, and the callout limits are the real design constraint. - Built as: Built on the API, Zapier, Make or n8n, MCP server - Syncs: One way, in - Moves: Contacts, Companies - Costs to turn on: Metered by usage. Setup: Hours - Requires: A Reverse Contact API key and a Salesforce edition with API access - Full guide: https://www.reversecontact.com/integrations-hub/salesforce-integrations/salesforce-reverse-contact-integration **Verdict.** Salesforce is the CRM in this directory where the route is least constrained and the limits are most specific. A Flow with an HTTP Callout keeps the whole thing inside the org with the key in a Named Credential; Apex does the same with more control; Clay or n8n take it outside when a non-engineer owns the logic or the volume is a backfill rather than a trigger. What decides it is rarely the enrichment. It is the callout ceiling of 100 per transaction and 120 seconds cumulative, which quietly rules out doing a database backfill the same way you do a record trigger. **What syncs:** - Email to full person record (in): POST /v2/enrich/persons resolves an email into identity, current role, history, education, skills and location. 2 credits. - Domain to company record (in): POST /v2/enrich/companies returns firmographics for a domain or a company name. 2 credits. - The callout (out): A Flow HTTP Callout or an Apex callout, authorised by a Named Credential. Outbound, so it does not touch the inbound API allocation. - Anything back to Reverse Contact (out): Nothing. This is a read layer, and your Flow decides which fields it may write. **Which editions carry it** (rows Salesforce, columns Reverse Contact): - A Flow HTTP Callout inside the org with Free of the daily inbound allocation: Yes - A Flow HTTP Callout inside the org with Unbound by the 100-callout ceiling: No - A Flow HTTP Callout inside the org with Can handle the live endpoints: No - A Flow HTTP Callout inside the org with Keeps the key in a Named Credential: Yes - Apex, queued or batched with Free of the daily inbound allocation: Yes - Apex, queued or batched with Unbound by the 100-callout ceiling: With a caveat - Apex, queued or batched with Can handle the live endpoints: With a caveat - Apex, queued or batched with Keeps the key in a Named Credential: Yes - Clay reading and writing through the API with Free of the daily inbound allocation: No - Clay reading and writing through the API with Unbound by the 100-callout ceiling: Yes - Clay reading and writing through the API with Can handle the live endpoints: No - Clay reading and writing through the API with Keeps the key in a Named Credential: No - An n8n workflow with the Salesforce node with Free of the daily inbound allocation: No - An n8n workflow with the Salesforce node with Unbound by the 100-callout ceiling: Yes - An n8n workflow with the Salesforce node with Can handle the live endpoints: Yes - An n8n workflow with the Salesforce node with Keeps the key in a Named Credential: No - A Zap or a Make scenario with Free of the daily inbound allocation: No - A Zap or a Make scenario with Unbound by the 100-callout ceiling: Yes - A Zap or a Make scenario with Can handle the live endpoints: With a caveat - A Zap or a Make scenario with Keeps the key in a Named Credential: No **How to connect it** (A Salesforce admin for the Named Credential and the External Service, plus whoever can create a Reverse Contact API key. A developer only if the job is a backfill.. Half a day for the Flow route. The edition check and the trigger-or-backfill decision are the two things to settle before any of it.): 1. Confirm the edition carries API access, because everything here rests on it [Salesforce: Setup, Company Information]. API access is included from Enterprise and is a paid add-on on Professional. The allocation that comes with it is worth reading at the same time: Developer Edition gets a flat 15,000 inbound calls a day, while Enterprise gets 100,000 plus 1,000 for each Salesforce licence plus any API Call Add-Ons purchased. 2. Decide whether this is a trigger or a backfill, because it changes the architecture [A whiteboard, not Setup]. One callout when a Lead is created is comfortable. The same logic running inside a bulk import meets the 100-callout ceiling on a single Apex transaction, and that is a count rather than a duration, so no timeout setting fixes it. A backfill belongs in Queueable or Batch Apex, or outside the org. 3. Create the fields the enrichment is allowed to own [Salesforce: Object Manager, Fields and Relationships]. Prefix them and leave the ones your reps type into alone. This is the step that cannot be undone quietly: a Flow pointed at a field somebody maintains by hand will keep overwriting it, and the damage only surfaces when a rep notices their own entry has gone. 4. Put the key in a Named Credential, never in a Flow variable [Salesforce: Setup, Named Credentials]. A key pasted into a Flow variable or an Apex constant is metadata, and metadata travels through change sets and version control. A Named Credential holds it in org configuration and lets the callout reference it by name, which is the part a security review actually asks about. 5. Register the endpoint so a Flow gets an action [Salesforce: Setup, External Services]. External Services turns the registered endpoint into an HTTP Callout action a Flow can call, which is what keeps this route in the hands of an admin rather than a developer. Apex is the alternative and buys control rather than capability. 6. Build the no-match path before the happy path [Flow: a Decision element after the callout]. Reverse Contact returns null with a confidence score rather than a best guess, so a lookup that matched nobody is a normal outcome. Decide what the Flow does on that branch, which is usually nothing at all, before you wire the branch that writes. 7. Turn on API Usage Notifications while you remember [Salesforce: Setup, API Usage Notifications]. It emails a named user when inbound API requests pass a percentage of the allocation you set. Worth doing whichever route you pick, because calls from installed managed packages count against the same number and the thing that exhausts it is rarely the thing you just built. 8. Test in a sandbox and watch the limits rather than the result [Salesforce: Developer Console, or the debug log]. The question is not whether one record enriches, which it will. It is how many callouts the transaction used and how close the cumulative time came to 120 seconds, because those are the numbers that decide whether this survives an import. **How to check it worked:** - Run the Flow once on a Lead whose answer you know, and once on an address that resolves to nobody. The second is the real test: the Flow should take the empty path, write nothing, and cost no credits. - Import 150 rows into a sandbox with the trigger active. If you are going to meet the 100-callout ceiling, this is where it should happen, rather than in production on the morning of a list upload. - Read the org API usage in Setup before and after a hundred records are enriched from Clay or n8n, then do the same hundred from a Flow. The first moves the number and the second does not, which is the whole argument for the in-org route. - Search your metadata for the key string after everything works. Finding it anywhere is the failure the Named Credential step exists to prevent, and it is easier to find now than in a change set. Agent skill for this pair: https://www.reversecontact.com/integrations-hub/skills/salesforce-reverse-contact.md **Field mapping:** - Lead or Contact Email maps to POST /v2/enrich/persons, 2 credits. The usual starting point, and the dearer of the two person calls. Returns identity, the current role, history, education, skills and location on one schema, which is what makes it safe to write into typed fields rather than into a note. - Account Website, or a domain on the Lead maps to POST /v2/enrich/companies, 2 credits. Firmographics from a domain or a company name. Worth running on the Account rather than per Contact, because one call covers every Contact attached to it. - A profile URL already on the record maps to POST /v2/fetch/persons, 1 credit. Half the price, and unmetered from the $249 plan rather than the $699 one. If any part of your stack already collects a profile URL, routing those records to this call instead is the single largest saving available on this pair. - The free freshness check maps to POST /v2/fetch/persons/check, 0 credits. Says whether a profile is cached and when it was last updated. One extra callout against a 100-callout ceiling, in exchange for not paying to refresh a record that was updated last week. - A Named Credential maps to Authorization: Bearer rc_your_api_key. Referenced by name from the callout, so the key is never in the Flow, the Apex or the change set. This is the specific reason this route can clear a security review that an external one cannot. - An External Services registration maps to The endpoint, as a Flow action. What turns the API into something an admin can drag into a Flow. Register the path you actually intend to call: a registration made against a path that later changes fails at runtime rather than at save. - Queueable or Batch Apex maps to One callout per transaction instead of 200. The documented way around the ceiling rather than a workaround. Each record becomes its own transaction, so neither the 100-callout count nor the 120-second cumulative timeout binds. - Anything outbound to Reverse Contact maps to Nothing at all. This is a read layer. No Salesforce record, field or event is sent anywhere, and there is nothing in the product to send it to. - Does not cross: An AppExchange package. There is no managed package and no listing, which is consistent rather than an oversight: Reverse Contact maintains apps on Clay, Zapier and Make and nothing inside any CRM or sequencer. - Does not cross: The live endpoints, from a Flow. They answer with a task id rather than a record, a Flow cannot wait, and holding a transaction open to poll would spend the 120-second cumulative callout budget on waiting. - Does not cross: A business email or a direct phone number. Both are separate endpoints at 3 and 20 credits, charged only when one is found, and the email finder is asynchronous as well. - Does not cross: Any field mapping shipped by the vendor. There is no mapping screen, because there is no app: your Flow decides which field each value lands in and whether it may overwrite what is there, which is more work and is also why this route never flattens a field a rep owns. **What breaks:** - **100 callouts and 120 seconds per transaction.** Salesforce caps a single Apex transaction at 100 callouts, with a cumulative timeout of 120 seconds across all of them and 10 seconds by default on each. One call on record creation is comfortable. A trigger firing over a 200-record bulk update is not, and the fix is Queueable or Batch Apex rather than a larger timeout. - **The daily API allocation is shared and finite.** Salesforce meters inbound daily API requests by edition and licence count across the whole org. The write-back half of this build competes with every other connected tool for the same number. Outbound callouts are exempt, which is a meaningful difference between doing the enrichment inside the org and doing it from Clay. - **Professional needs the API add-on.** API access is included from Enterprise and is a paid add-on on Professional. Every route on this page except a manual CSV depends on it, so confirm the edition before designing anything. - **Live resolution will not fit a Flow.** The live endpoints return a task id to poll rather than a record. A Flow cannot wait, and holding a transaction open to poll would spend the 120-second cumulative budget. Run live resolution in n8n and let it write back through the Salesforce node. - **The key belongs in a Named Credential.** An API key pasted into a Flow variable or an Apex constant travels in metadata, change sets and version control. A Named Credential keeps it in the org configuration where it belongs and lets the callout reference it by name. **Failures people hit:** - System.LimitException: Too many callouts: 100. Why: Salesforce caps a single Apex transaction at 100 callouts. A trigger that calls out once per record meets it the moment more than a hundred rows arrive in one transaction, which an import does by default. Fix: Move the work into Queueable or Batch Apex so each record is its own transaction, or run the backfill outside the org. Raising a timeout changes nothing, because this is a count and not a duration. - The transaction died partway through a batch of records. Why: There is a cumulative timeout of 120 seconds across every callout in one transaction, on top of the 10-second default on each individual call. Fix: Reduce the callouts per transaction rather than lengthening each one. Reverse Contact publishes a 500ms P95 on the cached endpoints, so arriving anywhere near 120 seconds means the count is the problem. - You have exceeded your daily API call limit. Why: Salesforce meters total inbound API requests per 24 hours per org: 15,000 on Developer Edition, and on Enterprise 100,000 plus 1,000 for each Salesforce licence plus any add-ons. Calls made from installed managed packages count against the same number. Fix: Turn on API Usage Notifications so somebody is told at a percentage rather than at the wall, and batch the write-backs. The outbound call to Reverse Contact is not an inbound request and is not what spent it. - REQUEST_LIMIT_EXCEEDED while nowhere near the daily number. Why: That is the concurrent limit rather than the daily one. A production org or sandbox allows 25 simultaneous inbound requests lasting 20 seconds or longer, and Developer Edition or a trial allows 5. Fix: Find the slow caller rather than the busy one. There is no limit at all on concurrent requests shorter than 20 seconds, so this is almost always one long-running integration instead of volume. - The Flow failed on a contact who is not in the database. Why: A confident null is the documented answer rather than an error: Reverse Contact returns null rather than a best guess and attaches a confidence score to every response. Fix: Add a Decision element on the field being present and write nothing on the empty path. The call cost no credits either way, because every 4xx and 5xx is free. - The API key turned up in a change set. Why: A key pasted into a Flow variable or an Apex constant is metadata, and metadata travels through change sets, retrieves and version control. Fix: Move it into a Named Credential and reference it by name from the callout. That is also the answer a security review is looking for, and it is the reason this route can pass one that an external route cannot. - A live refresh never came back. Why: The live endpoints are asynchronous: the response carries a webhookId rather than a record, and Reverse Contact documents the wait as usually seconds and possibly tens of minutes. Fix: Do not run live resolution from a Flow at all. Run it in n8n, which polls with a Wait node, and let the Salesforce node write the answer back when it arrives. - An endpoint that worked last week returns nothing. Why: /v2/resolve was replaced by /v2/enrich and /v2/search/persons by /v2/search/people, with the old pair documented as live only until 13 October 2026. Fix: Search the org for both old paths: in Apex, in every External Services registration, and in any Named Credential URL. A registration made against the old path fails at runtime rather than when you save it. **What practitioners say** (14 threads from 2018 to 2026, read 2026-10-11): Nobody discusses this pair by name, so the search was for the job: keeping Salesforce records accurate without reps typing. The threads are almost entirely about ownership rather than tooling, which is the finding: every participant agrees the data is bad, and the argument is about whose job it is. An external call that fills a field nobody owns is a way out of that argument rather than a contribution to it. - The clearest answer anybody gives on who owns what (r/salesforce, January 2026, 4 points): https://www.reddit.com/r/salesforce/comments/1qme1j6/who_actually_owns_salesforce_data_quality/ - Input quality is a permanent battle, which is the case for not relying on inputs (r/salesforce, February 2024, 52 points): https://www.reddit.com/r/salesforce/comments/1b260v6/how_do_you_deal_with_poor_data_quality_in_a_crm/ - The prescription people give starts with an enrichment tool and an owner (r/salesforce, February 2024, 26 points): https://www.reddit.com/r/salesforce/comments/1b260v6/how_do_you_deal_with_poor_data_quality_in_a_crm/ - Deleting fields beats enriching them, and the test is utilisation (r/salesforce, February 2024, 19 points): https://www.reddit.com/r/salesforce/comments/1b260v6/how_do_you_deal_with_poor_data_quality_in_a_crm/ - The accountability has to sit above the person asking (r/salesforce, January 2026, 5 points): https://www.reddit.com/r/salesforce/comments/1qme1j6/who_actually_owns_salesforce_data_quality/ Sources: https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_callouts_timeouts.htm | https://resources.docs.salesforce.com/latest/latest/en-us/sfdc/pdf/salesforce_app_limits_cheatsheet.pdf | https://docs.reversecontact.com/getting-started | https://docs.reversecontact.com/guides/credits | https://docs.reversecontact.com/guides/rate-limits | https://www.reversecontact.com/pricing ### Salesforce and ZoomInfo Enrichment on creation and on a schedule, and a sandbox that charges you to test. - Built as: Native, Marketplace app - Syncs: One way, in - Moves: Contacts, Companies, Lists - Costs to turn on: Paid add-on or licence. Setup: Hours - Requires: ZoomInfo Sales with Enrich, the AppExchange package, and a Salesforce edition with API access - Full guide: https://www.reversecontact.com/integrations-hub/salesforce-integrations/salesforce-zoominfo-integration **Verdict.** This is the deepest enrichment integration in the directory and the one with the most ways to spend money you did not plan to. The capability is real: Instant Enrich fills a lead, contact or account as it is created, Scheduled Enrich keeps the back catalogue current, and you control matching, accuracy thresholds and field-level overwrite behaviour. What decides whether the project goes well is three documented details nobody mentions in a demo: a sandbox run charges credits exactly like production, the Person Has Moved setting rewrites employers unless you turn it off, and Instant Enrich spends two Salesforce API calls on every record it touches. That last allocation is shared with every other integration in the org, which is why this one usually gets discovered from somewhere else. **What syncs:** - New leads, contacts and accounts (in): Instant Enrich appends ZoomInfo data as the record is created, optionally filtered by a SOQL query so only the right teams' records are enriched. - Existing records (in): Scheduled Enrich jobs run on a cadence over all records, a list view, or criteria you define. Jobs begin at 12:00 AM Eastern on the scheduled day. - Intent and Scoops (in): Written to a ZoomInfo custom object rather than onto the standard record. - Buying committee contacts (in): Creates and enriches new contacts on matched accounts, charged as credits and reported separately on the dashboard. - Anything back to ZoomInfo (out): Nothing on this integration. Enrich is a one-way pipe into Salesforce. **Which editions carry it** (rows ZoomInfo, columns Salesforce): - Instant Enrich, on create with Production: Two API calls per record - Instant Enrich, on create with Sandbox: Credits charged anyway - Scheduled Enrich, 200 per batch with Production: Most Bulk API calls - Scheduled Enrich, 200 per batch with Sandbox: Credits charged anyway - Scheduled Enrich, 10K per batch with Production: Fewest Bulk API calls - Scheduled Enrich, 10K per batch with Sandbox: Credits charged anyway **How to connect it** (A Salesforce admin who can install a package, and a ZoomInfo admin with the Admin Portal. Plus one dedicated Salesforce user that nobody logs in as.. An hour to connect. The field mapping and the accuracy threshold are the decisions, and they deserve a meeting.): 1. Install the package, and pick the environment deliberately [Salesforce AppExchange: ZoomInfo, GTM Intelligence Platform]. Click Get It Now and choose Production or Sandbox. ZoomInfo documents that running Enrich in a sandbox still consumes credits, so a sandbox trial is a real purchase rather than a free rehearsal. 2. Create a Salesforce user that exists only to run Enrich [Salesforce: Users]. ZoomInfo asks you to connect as a user dedicated to Enrich. That user's permissions become the integration's permissions, and a named person's account takes the integration down with them when they leave. 3. Connect from the ZoomInfo side [ZoomInfo Admin Portal: Integrations, Connect Enrich]. Under Scheduled Enrich, click Connect on the Salesforce tile, choose the environment and click Grant Access. The authorisation opens in a popup, so a popup blocker makes this look like a failed connection rather than a blocked window. 4. Create one job per object, not one job for everything [Admin Portal: Manage, New Job]. A job takes a single Object Type of Accounts, Contacts or Leads. Name it, decide whether you want email alerts, and set the recurrence; jobs start at midnight, so a daily job is an overnight job. 5. Set a credit limit on the job before you run it once [The job: Credit Usage Limits]. The default is No limit, which enriches every record in the run and charges for all of it. Limiting credits per job run is the setting that turns a misconfigured filter into a small mistake instead of a month of budget. 6. Choose the batch size with your Salesforce API allowance in mind [The job: Batch Size]. The options are 10K, 1K, 500 and 200 records per Bulk API call. A larger batch means fewer calls; reducing it increases Salesforce API consumption, which matters because that allowance is shared with every other integration in the org. 7. Set the accuracy score, and agree the number with whoever reads the dashboard [The job: Accuracy Score for Enrichment]. Records matched below the threshold are not enriched and are marked No Match with the reason Below selected Accuracy Score. That is a better outcome than a confident guess, and it is also the number somebody will use to judge the integration later. 8. Map fields last, and decide overwrite per field [The job: field mapping]. Each row pairs a ZoomInfo field with a Salesforce field, custom fields included, and each has an Update Option of overwrite or complete only if missing. Default to complete if missing on anything a human types into. **How to check it worked:** - Run one job against a filtered list of ten records and read the credit charge before scheduling anything recurring. - Check a record that came back No Match and confirm the reason reads Below selected Accuracy Score rather than something else. - Pick a field a rep typed into and confirm it survived the run. If it did not, the Update Option on that mapping is wrong. - Watch your Salesforce API consumption over the first full cycle, not the first job. Batch size and Instant Enrich both draw on the same allowance as everything else in the org. Agent skill for this pair: https://www.reversecontact.com/integrations-hub/skills/salesforce-zoominfo.md **Field mapping:** - A ZoomInfo data point maps to Any Salesforce field, custom included. Chosen row by row, so nothing lands anywhere you did not pick. - Update Option maps to Overwrite, or complete only if missing. Set per mapping. This single column is the difference between enrichment that reps trust and enrichment they work around. - Intent and Scoops maps to A ZoomInfo custom object. Deliberately not written onto the standard record, so your reporting has to reach into the custom object to use them. - Buying committee contacts maps to New contacts on the matched account. Created rather than matched, and chargeable. A hard limit of up to 10 contacts per account is available and worth setting. - Anything at all maps to Back to ZoomInfo. Nothing. Enrich is a one-way pipe into Salesforce, so your corrections stay yours and never improve the source. - Does not cross: Any record below your accuracy threshold. It is marked No Match with the reason given, which is a feature rather than a gap. - Does not cross: A contact with no account relationship, usefully. Salesforce treats an account-less contact as private to its creator, so a created contact that lands without an account is invisible to the rest of the team. - Does not cross: Anything flowing back. There is no return path, so a field a rep corrects is corrected only in Salesforce. **What breaks:** - **The sandbox is not free.** ZoomInfo states that running Enrich in a Salesforce sandbox incurs bulk credit charges in the same way as production, and recommends testing in small batches. Teams used to rehearsing data projects against a full sandbox copy should not do that here. Size your test as a sample, and get your implementation specialist involved before any job points at the whole database. - **Person Has Moved rewrites employers by default.** The setting is enabled unless you turn it off, so a contact who changed jobs is enriched to their new organisation inside your CRM. Turn it off and the company fields are still enriched as though no move happened, with the enrich status set to Company Match Only. Either choice is defensible; not making the choice means your CRM quietly disagrees with your historical reporting about who worked where. - **Instant Enrich costs two API calls a record.** ZoomInfo documents two Salesforce API calls per record enriched: one to read the existing field values so the update option can be honoured, and one to write. Salesforce allocates 100,000 requests plus 1,000 per Salesforce licence per 24 hours on Enterprise and on Professional with API access, shared across every integration in the org, so a busy inbound week is measurable against that number rather than invisible. - **A smaller batch size costs more API calls.** Scheduled Enrich queries through the Bulk API in batches of 10,000 by default, and you can reduce that to 1,000, 500 or 200. ZoomInfo is explicit that reducing it increases Salesforce API consumption. The instinct to be gentle on the org by shrinking batches therefore does the opposite, and the right lever for caution is the credit limit per job run, not the batch size. **Failures people hit:** - The connection window never appeared. Why: A popup blocker. ZoomInfo opens the Salesforce authorisation in a popup and says so. Fix: Disable the blocker for the Admin Portal and reconnect. Nothing is wrong with the credentials. - Credits went in a single run. Why: Credit Usage Limits defaults to No limit, so the job enriched every record it matched. Fix: Set a per-run credit limit before the next schedule, and test any new filter against ten records first. - Created contacts are invisible to everybody except one user. Why: A Salesforce contact with no account relationship is private to its creator, which is Salesforce behaviour rather than ZoomInfo behaviour. Fix: Make sure created contacts attach to an account. Practitioners use a placeholder account everyone can see, or route to the Lead object instead. - Records come back as No Match in bulk. Why: They matched but fell below the accuracy threshold, and the reason field says so. Fix: Read the reason before lowering the threshold. A lower score buys coverage with confidence, and that trade should be a decision rather than a reflex. - Reps say the data is wrong and they fixed it last week. Why: An Update Option set to overwrite on a field people type into, or Person Has Moved rewriting an employer. Fix: Switch those mappings to complete only if missing, and check the Person Has Moved setting, which is on unless somebody turned it off. - Other integrations in the org started failing. Why: Salesforce API consumption. Instant Enrich costs two calls per record and a small batch size multiplies scheduled calls, all drawn from one shared daily allowance. Fix: Raise the batch size, narrow the job filters, and check the org's API usage rather than ZoomInfo's job log, because the failure appears somewhere else entirely. - A feature in the guide is missing from your org. Why: Some capabilities need the ZoomInfo Sales native application at version 1.33 or higher. Fix: Upgrade the AppExchange package before raising a support ticket about a missing screen. **What practitioners say** (14 threads from 2018 to 2026, read 2026-10-11): Two topics dominate and neither is the integration itself. One is Salesforce's own object model getting in the way of contacts ZoomInfo creates. The other is commercial: what the data costs, what you are allowed to keep, and whether the account manager has to be in the room for you to get what you are paying for. The mechanics, by contrast, barely come up, which fits a package install that works. - A created contact with no account is invisible to the team (r/salesforce, May 2024, 5 points): https://www.reddit.com/r/salesforce/comments/1d0537i/how_do_i_let_zoominfo_create_contacts_in/ - One person reports a contract term worth checking in your own (r/salesforce, February 2025, 4 points): https://www.reddit.com/r/salesforce/comments/1iyu4g5/is_it_possible_to_have_zoom_info_automatically/ - What you can do is partly a conversation, not a setting (r/sales, September 2025, 4 points): https://www.reddit.com/r/sales/comments/1nfa931/best_zoominfo_alternatives_for_enriching/ - The install is not where the months go (r/salesforce, February 2018, 5 points): https://www.reddit.com/r/salesforce/comments/7zjkhz/is_it_hard_to_integrate_zoominfo_with_sfdc/ - People reach for enrichment because the alternative is two months of typing (r/salesforce, April 2021, 4 points): https://www.reddit.com/r/salesforce/comments/mnjgl5/new_account_executive_trying_to_import_contacts/ Sources: https://tech-docs-library.zoominfo.com/enrich-for-salesforce-integration-guide.pdf | https://resources.docs.salesforce.com/latest/latest/en-us/sfdc/pdf/salesforce_app_limits_cheatsheet.pdf ### Salesforce and Outreach Per-object, per-field control in both directions, and Essentials cannot run it at all. - Built as: Native, Marketplace app - Syncs: Two-way sync - Moves: Contacts, Companies, Deals, Activities - Costs to turn on: Paid add-on or licence. Setup: Days - Requires: An Outreach contract, a Salesforce edition with REST API calls, and a Salesforce admin - Full guide: https://www.reversecontact.com/integrations-hub/salesforce-integrations/salesforce-outreach-integration **Verdict.** This is the integration Outreach was built around, and it shows: per-object polling, per-field outbound toggles, conditions on what pushes and manual stage mapping. It is also the one project on this site where the connector is the easy part. The edition question comes first and is absolute, because Essentials has no REST API access even with an add-on and Professional has to buy the Web API package, and behind it sit the permissions, the sandbox and the admin's change window. Budget days rather than hours, and spend the first of them on the API allocation rather than on field mapping. **What syncs:** - Leads, contacts and accounts (two-way): Salesforce is the source of truth for creation. Updates run both ways, with outbound update enabled only on the fields you choose. - Opportunities (two-way): Bidirectional where in-line editing is on. Without it, Outreach recommends every push and outbound toggle off, so updates happen in Salesforce only. - Opportunity contact roles (two-way): Including outbound delete, which few integrations in this directory will do at all. - Tasks, calls and emails (out): Always one way, Outreach into Salesforce. Outreach recommends conditions so only completed or delivered activity pushes. - Events (out): One way, which is why polling does nothing for them. Condition them or a connected calendar pushes historical internal meetings. - Users (in): Updates in only, with polling off. Polling here imports every CRM user, and a user cannot be deleted afterwards. **Which editions carry it** (rows Salesforce, columns Outreach): - Essentials with Any Outreach contract: Not possible - Professional with Any Outreach contract: Needs the API package - Enterprise or Unlimited with Any Outreach contract: REST API included **How to connect it** (A Salesforce administrator, connecting as a dedicated integration user rather than as themselves.. A day to connect and map. Longer if nobody has agreed which fields Outreach is allowed to own.): 1. Confirm the Salesforce edition has REST API calls [Salesforce Setup: Company Information, Organization Edition]. Outreach is explicit: Enterprise and Unlimited include REST API; Professional needs the Web API package and purchased API call bundles; Essentials does not support REST API access even with an add-on. The last one ends the project rather than delaying it. 2. Build the integration user before you connect anything [Salesforce: profile and user]. That profile needs create, read and edit on every object Outreach will show, including accounts, contacts, leads, opportunities and user roles, field-level security that permits viewing and modifying every mapped field, and API Enabled under System Permissions. The last one is the single most common thing missing. 3. Connect with administrator credentials [Outreach: the Salesforce plugin]. Outreach lists admin credentials as a common connection error for a reason. Connect to the sandbox or production deliberately, and know which you are on before you start mapping. 4. Set the API call budget before the first full sync [The plugin: Limits]. An admin can cap how many calls Outreach may make per day. Outreach recommends setting global usage to 70 to 80 per cent of your total allocation, which leaves room for every other integration drawing on the same org. 5. Map objects and fields, and decide who owns each one [The plugin: Object Setup, Set Field Mapping]. This is the bulk of the work and the part that decides whether reps trust either system. Conflict resolution scans field by field rather than locking a row, so a field both sides write to will flip rather than fail, which is harder to notice. 6. Export the configuration once it works [The plugin: the three dots, Export CRM Sync Configuration]. Outreach supports exporting and importing the sync configuration, which is how you move a validated setup from sandbox to production and how you recover one after a sandbox refresh. Doing it at the end of a good day is cheaper than rebuilding it after a bad one. **How to check it worked:** - Create a record in Salesforce and watch it arrive. Inbound is a bulk poll, so minutes is normal. - Complete a task in Outreach and watch it land in Salesforce. Outreach documents 30 to 45 seconds for outbound, so this one should feel immediate. - Check the Outreach-specific API usage figure against your Salesforce allocation after a full day, not after an hour. - Open Activity, filter on System Update, Plugins, Plugin Sync Error, and confirm the list is empty. That filter is where failures surface, not the record itself. Agent skill for this pair: https://www.reversecontact.com/integrations-hub/skills/salesforce-outreach.md **Field mapping:** - Accounts, contacts, leads, opportunities maps to The Outreach equivalents. Create, read and edit, bounded by the integration user's profile and field-level security. - A field changed on both sides at once maps to A field-by-field merge. Outreach scans the record field by field rather than taking a row lock or letting one system win wholesale. - Completed activity in Outreach maps to Salesforce, in near real time. Usually visible in 30 to 45 seconds, slower during a high-volume force sync. - New and updated Salesforce records maps to Outreach, in bulk. Polling detects up to 2,000 changed records in one API call and imports 200 per call after that, which is a Salesforce limit rather than an Outreach choice. - The whole sync configuration maps to An exportable file. Importable into another environment, which is the supported route from sandbox to production. - Does not cross: Anything the integration user cannot see. Field-level security on that profile is the ceiling for the entire plugin. - Does not cross: Anything historic. Nothing backfills, so the go-live date is a decision rather than a detail. - Does not cross: Any object on Salesforce Essentials, which has no REST API access even with an add-on. **What breaks:** - **Essentials cannot run this, at any price.** Outreach documents that Enterprise and Unlimited include the REST API calls the sync needs, that Professional requires the Web API Package and API Call Bundles, and that Essential has no REST API access even with an add-on. Confirm the edition in Setup, Company Information before anything else, and ask your Salesforce representative rather than reading API usage statistics, because usage figures do not reveal whether the package was purchased. - **Polling Users is a one-way door.** Outreach recommends leaving polling off for the User object, because polling imports every user in the CRM and a user cannot subsequently be deleted from Outreach. The same advice applies to Leads until setup is complete. This is the clearest example on the pair of a default that is cheap to get right and expensive to undo. - **The API allocation is a budget you have to set.** Outreach advises setting the global API limit to 70 to 80 percent of your total calls and the Outreach-specific limit to 20 to 30 percent, and notifies admins as the limit approaches. When the limit is reached, syncing stops, and the window is a rolling 24 hours rather than a daily reset at midnight. Salesforce allocates 100,000 calls plus 1,000 per Salesforce licence on Enterprise, shared with every other integration in the org. - **Nothing backfills, and conflicts resolve per field.** Only new and updated records move during polling, so history needs a separate import and your switch-on date is the start of the record. Conflicts are resolved field by field rather than by a winning system, which means the governance question is per field too: decide which side owns each one before you enable an outbound toggle, because the connector will implement whatever you hand it. **Failures people hit:** - The connection refuses admin credentials. Why: Outreach lists this first among connection errors: the credentials used must be a Salesforce administrator, for sandbox and production alike. Fix: Connect with an admin account, ideally the dedicated integration user rather than a person. - The connection drops every day or two. Why: Salesforce session timeout settings, which Outreach calls out specifically for sandboxes breaking every 24 to 48 hours. Fix: Check the session timeout in Salesforce rather than reconnecting repeatedly, which treats the symptom. - Records sync for some users and not others. Why: Incorrect user mappings, one of the five errors Outreach lists as common, alongside unmapped lead queues. Fix: Open the plugin logs, which export the last 10,000 errors, and fix the mappings rather than the records. - Writes fail with no obvious pattern. Why: Validation errors or required fields missing on the Salesforce side, which the plugin surfaces rather than the record does. Fix: Filter Activity by System Update, Plugins, Plugin Sync Error. The failures are there and nowhere else. - A field keeps changing back. Why: Both systems are writing it. Conflict resolution merges field by field, so the last writer wins quietly rather than erroring. Fix: Decide an owner for that field and stop one side writing it. Nothing in the plugin will flag the fight. - The org ran out of API calls overnight. Why: An unbounded Outreach budget against a shared allocation, often triggered by a bulk change in Salesforce that the poll then imported 200 records at a time. Fix: Set the limit to 70 to 80 per cent of total as Outreach recommends, and treat large Salesforce updates as API events in their own right. **What practitioners say** (14 threads from 2022 to 2026, read 2026-10-11): This is the angriest set of threads in the directory. Salesforce admins who inherited Outreach describe the integration as the hard part of the platform, and the specific failure they describe is the one the documentation tells you to prevent: an API allocation consumed overnight. The alternatives people reach for are consistently native-to-Salesforce rather than API-based, which is a comment on the architecture rather than on the product. - Troubleshooting it is a known rite of passage (r/salesforce, February 2024, 5 points): https://www.reddit.com/r/salesforce/comments/1aljthd/anyone_here_a_salesforce_admin_that_also/ - The admins who inherit it struggle, and say so publicly (r/salesforce, February 2024, 11 points): https://www.reddit.com/r/salesforce/comments/1aljthd/anyone_here_a_salesforce_admin_that_also/ - The alternatives people name are native rather than API-based (r/salesforce, November 2022, 5 points): https://www.reddit.com/r/salesforce/comments/yjq95n/outreach_salesforce_integration_fix/ - Salesforce now competes with the thing it is integrating (r/salesforce, December 2022, 6 points): https://www.reddit.com/r/salesforce/comments/zy8nlw/outreach_or_salesloft_whats_your_experience/ - Where reps actually work is a design decision, not an accident (r/salesforce, November 2022, 5 points): https://www.reddit.com/r/salesforce/comments/ytmbm7/how_does_your_sales_team_use_outreach_whats_best/ Sources: https://support.outreach.io/support/solutions/articles/159000426522 | https://support.outreach.io/support/solutions/articles/159000426014 | https://resources.docs.salesforce.com/latest/latest/en-us/sfdc/pdf/salesforce_app_limits_cheatsheet.pdf ### Salesforce and Gong Take a field off the integration user and Gong deletes what it already imported. - Built as: Native, Marketplace app - Syncs: Two-way sync - Moves: Activities, Deals, Contacts - Costs to turn on: Paid add-on or licence. Setup: Hours - Requires: A Gong contract, a Salesforce edition with API access, and a dedicated integration user - Full guide: https://www.reversecontact.com/integrations-hub/salesforce-integrations/salesforce-gong-integration **Verdict.** Gong reads your CRM and writes call intelligence back onto the opportunity, which is the whole argument for it: the forecast conversation happens where the deal lives rather than in a second dashboard. The setup is a permissions exercise and almost nothing else, and it has one rule that no other integration in this directory shares. Remove a field from the integration user and Gong removes the data it had already imported for that field. That makes the permission set a live dependency rather than a one-off install step, and it is the single thing to document before anybody tidies up a profile. **What syncs:** - Accounts, contacts, leads and opportunities (out): Read out of Salesforce into Gong, with the fields chosen by an admin. Required fields are documented per object and recommended ones improve deal boards and call filters. - Calls and meetings (in): Written back into Salesforce as Tasks or Events. Either one task carrying every participant and association, or separate tasks on each matched contact, the account and the opportunity. - Recordings and transcripts (in): Into the Gong Conversation object in Salesforce, which arrives with the Gong for Salesforce package rather than with the base integration. - Engage activity (in): Engage tasks, LinkedIn connection requests and messages, and flow activity, where you run Engage and have an Engage licence. - Opportunity stages and amounts (out): Read out of Salesforce for the deal board and the forecast. Whether a team member can edit a Salesforce field from inside Gong is a separate question from the integration user's permissions. **Which editions carry it** (rows Salesforce, columns Gong): - Neither with Importing Salesforce data to Gong: Does not work - Neither with Creating tasks and events: Does not work - Salesforce API Integration only with Importing Salesforce data to Gong: Does not work - Salesforce API Integration only with Creating tasks and events: Works - Both licences with Importing Salesforce data to Gong: Works - Both licences with Creating tasks and events: Works **How to connect it** (A Salesforce administrator who can create a user and assign two permission set licences, and a Gong admin.. An afternoon, most of it spent deciding which fields the integration user may see.): 1. Enable API access in Salesforce first [Salesforce Setup]. Gong states it plainly: without API access enabled you cannot connect Gong to Salesforce at all. This is an edition question before it is a configuration one. 2. Create a dedicated integration user [Salesforce: Users]. Gong supports Salesforce's dedicated integration user licence and recommends one per integration. A named person's account means that when they are deactivated the integration stops, which is a bad way to find out who owned it. 3. Assign both licences, because they do different jobs [Salesforce: permission set licences]. The Salesforce API Integration licence carries the system permissions needed to create tasks and events. The Salesforce Integration licence carries the field-level permissions needed to import Salesforce data into Gong. One without the other produces an integration that half works, and the half that fails is silent. 4. Tick API Enabled on that profile or permission set [System permissions]. Gong uses it to check your API limits and keep its own requests underneath them. Without it Gong cannot see the ceiling it is supposed to respect. 5. Give record access deliberately, object by object [The integration user's permission set]. View All Records on an object overrides whatever the role hierarchy would have allowed. Gong is explicit that permissions which are too limited leave activities missing until somebody adjusts the setup, so this is the setting that decides completeness. 6. Choose the fields Gong imports, and leave them alone afterwards [Gong: Salesforce field configuration]. Removing a field from the configuration deletes the data Gong already imported through it. Adding fields is cheap; removing one is destructive, and the time to decide is now. **How to check it worked:** - Check a call recorded today appears on the right opportunity, not just in Gong. - Check a task or event created by Gong exists in Salesforce. That tests the API Integration licence specifically. - Open a record the integration user should not see and confirm Gong has no activity for it, so you know the access boundary is where you think. - Look at a long picklist value in Gong. Anything over 120 characters is trimmed on display, which matters if your stage names are sentences. Agent skill for this pair: https://www.reversecontact.com/integrations-hub/skills/salesforce-gong.md **Field mapping:** - Accounts, contacts, leads and opportunities maps to Gong, as context on a call. Out of Salesforce. This is the half that needs the Salesforce Integration licence and field-level permissions. - Calls, meetings, recordings and transcripts maps to Salesforce activity on the record. Into Salesforce, which is the half everybody means when they say Gong exports to the CRM. - Gong objects such as Conversations maps to Reportable Salesforce objects. Available to report on, which is what makes Gong data usable in a Salesforce dashboard rather than only in Gong. - A picklist or string value maps to Gong, trimmed at 120 characters. Gong displays a maximum of 120 characters for both, so longer values are cut rather than wrapped. - A field removed from the configuration maps to Deleted imported data. Not merely stopped. The data Gong imported through that field goes with it. - Does not cross: Anything the integration user cannot see. Gong warns that overly limited permissions leave activities missing rather than erroring. - Does not cross: The tail of a value longer than 120 characters, on display. - Does not cross: Anything at all, once the integration user is deactivated. Gong treats that as the outage it is. **What breaks:** - **Removing a field deletes its imported data.** Gong documents that if a field is removed from the integration user, Gong also removes that field's previously imported data. A routine permission tidy-up therefore destroys history rather than pausing collection, and nothing about the change in Salesforce suggests that is about to happen. Record which fields the integration user holds and why, and treat that permission set as production configuration. - **Private calls are not simply hidden.** A call marked private in the calendar is never visible to Gong and never imported. A call marked private in Gong can still be exported if a tech admin has set that up, and the exported task carries the subject "Private call" with comments saying so, while the Conversation object replaces the brief, highlights and key points with a privacy notice and ticks the Is Private field. That is three different behaviours for one word, and the one that catches people is the middle one. - **Two licences, not one.** The integration user's permission sets need both the Salesforce API Integration licence, which carries the system permissions required to create tasks and events, and the Salesforce Integration licence, which carries the field-level permissions required to import. Teams that assign one of the two get a connection that authenticates and then half works, which reads like a sync fault rather than a licensing one. - **A deactivated user is an outage.** Gong recommends a dedicated integration user because deactivating a regular user disconnects the integration. The failure arrives whenever somebody leaves, which is to say long after the install, and by then nobody remembers whose credentials the integration was set up with. The multi-currency case has a similar shape: if you run multiple currencies, the integration user's personal currency has to match the corporate currency. **Failures people hit:** - Activities are missing and nothing errored. Why: The integration user's permissions are too limited. Gong says exactly this: activities may be missing until the setup is adjusted. Fix: Widen record access on the objects concerned, using View All Records where the role hierarchy is the constraint. - Calls log but Gong has no CRM context. Why: The Salesforce Integration licence, which carries field-level permissions for importing Salesforce data, is not assigned. Fix: Assign both permission set licences. The symptom points at Gong and the cause is a Salesforce licence. - Gong cannot create tasks or events. Why: The other licence. The Salesforce API Integration licence carries the system permissions for that. Fix: Same fix from the other direction, which is why the grid above lists them separately. - The whole integration stopped on a Monday. Why: The integration user was deactivated, most often in a routine leavers process. Fix: Use a dedicated integration user on the licence Salesforce provides for the purpose, and add it to whatever list protects service accounts from deactivation. - Historic Gong data disappeared from a field. Why: That field was removed from the Gong field configuration, which deletes the data imported through it. Fix: There is no undo in the configuration screen. Treat field removal as a data decision requiring the same care as a Salesforce field delete. - Long picklist values look truncated. Why: Gong displays a maximum of 120 characters for picklists and strings. Fix: Shorten the values, or accept the trim. This is display rather than storage, so the data is intact in Salesforce. **What practitioners say** (14 threads from 2020 to 2026, read 2026-10-11): Almost nobody posts about configuring this integration, which fits a native package that works. What people post about is whether Gong is worth what it costs, and the answer that recurs is not about the product: teams buy it, use a fraction of it, and have nobody with the bandwidth to own it. There is also a useful thread about why vendors build deep Salesforce integrations at all. - The common complaint is under-use, not malfunction (r/SalesOperations, February 2025, 5 points): https://www.reddit.com/r/SalesOperations/comments/1iruhko/gong_replacement/ - Gong objects are reportable in Salesforce, and few people know (r/salesforce, January 2023, 3 points): https://www.reddit.com/r/salesforce/comments/10kf8ku/sfdc_gong_integration/ - There is an economic reason some integrations are deep and others are not (r/salesforce, November 2025, 18 points): https://www.reddit.com/r/salesforce/comments/1ovwwj0/do_big_players_like_gong_or_zoominfo_really_pay/ - Integration quality varies wildly within a category (r/salesforce, October 2020, 7 points): https://www.reddit.com/r/salesforce/comments/j5sri9/which_telephony_system_would_you_recommend_to/ - When three tools touch the same record, somebody should ask why (r/CustomerSuccess, November 2025, 3 points): https://www.reddit.com/r/CustomerSuccess/comments/1ow9zck/gong_salesforce_custify/ Sources: https://help.gong.io/docs/salesforce-fields-the-integration-user-needs-access-to | https://help.gong.io/docs/set-up-requirements | https://help.gong.io/docs/view-gong-activities-in-salesforce ### Salesforce and Zapier Five access tokens per org, and the sixth app silently revokes the first. - Built as: Zapier, Make or n8n, Marketplace app - Syncs: Two-way sync - Moves: Contacts, Companies, Deals, Custom objects - Costs to turn on: Metered by usage. Setup: Minutes - Requires: A paid Zapier plan, a Salesforce edition with API access, and an admin to approve the app - Full guide: https://www.reversecontact.com/integrations-hub/salesforce-integrations/salesforce-zapier-integration **Verdict.** Of the three Zapier pairs in this directory, this is the one where the glue costs more than the endpoint. Salesforce is a premium Zapier app, so a paid Zapier plan is mandatory, and the Salesforce side needs My Domain configured, an admin to approve Zapier as an External Client App and an edition that genuinely carries API access. Get through that and you have the same broad surface the other Zapier pairs offer, against the strictest org in the directory. The limit that will find you is not throughput: it is the five access tokens Salesforce allows across every third-party app you own. **What syncs:** - Leads, contacts and accounts (two-way): Create, update, find and find-or-create in either direction, subject to the connecting user's object and field permissions. - Opportunities (two-way): Created and updated from outside, and usable as a trigger when a field changes. - Custom objects and fields (two-way): Supported, though newly created ones can take time to appear in Zapier's dropdowns. Reloading the field list is the documented workaround. - Record updates as triggers (out): The Updated Field on Record trigger returns the most recently updated record. Its test records do not filter by the object you selected, which makes testing misleading rather than broken. - Marketing Cloud (event): Not supported. Marketing Cloud accounts cannot be connected on this integration at all. **Which editions carry it** (rows Zapier, columns Salesforce): - Free or Starter with Essentials: Premium app, not included - Free or Starter with Professional: Premium app, not included - Free or Starter with Enterprise or above: Premium app, not included - Professional with Essentials: The vendors disagree - Professional with Professional: Two-minute polling - Professional with Enterprise or above: Two-minute polling - Team or Enterprise with Essentials: The vendors disagree - Team or Enterprise with Professional: One-minute polling and static IP - Team or Enterprise with Enterprise or above: One-minute polling and static IP **How to connect it** (A Salesforce administrator for the org-level work, and whoever owns the Zapier account. The two are rarely the same person and the Salesforce half comes first.. Minutes once the org is ready. The org being ready is the project.): 1. Count the connected apps before you add another [Salesforce: connected apps, third-party access]. Salesforce allows five access tokens per account across every third-party application, and when a sixth is generated the oldest is revoked automatically and without notification. Zapier is about to take one. Knowing which five you already have is the difference between a clean install and silently logging out another integration. 2. Configure My Domain, and check it is not a custom domain [Salesforce Setup: My Domain]. Zapier requires My Domain configured and states that custom domains are not supported. This is org-level work with its own change window in most companies. 3. Get Zapier approved as an External Client App [Salesforce Setup]. Connected apps can no longer be created in Setup, so if your organisation requires a custom app a Salesforce administrator follows Zapier's administrator prerequisites to create one. In a locked-down org this is the step that takes a fortnight. 4. Check the connecting user has the permissions the Zaps will need [Salesforce: profile and field-level security]. Zapier is explicit that user, object and field permissions can prevent triggers and actions from working. The Zap does not fail loudly; the trigger simply never sees the record. 5. Add the connection on a paid Zapier plan [Zapier: Apps, Add connection]. Salesforce is a premium app on Zapier, so there is no free path at all. Authenticate, grant access, and pick sandbox only if your account actually has one. 6. Use a static IP if your org restricts by address [Zapier: Professional, Team or Enterprise]. Zapier offers a static IP on those plans, which is what makes this work against an org that enforces IP allowlisting. On a Free or Starter Zapier plan that option does not exist and neither does the integration. 7. Pick your trigger knowing only one of them is instant [The Zap editor]. Every Salesforce trigger Zapier lists polls, except New Outbound Message, which is instant. If you need immediacy, the path is a Salesforce outbound message rather than a faster Zapier plan. **How to check it worked:** - Create a record and time the trigger. Two minutes on Zapier Professional and one on Team or Enterprise is expected, not slow. - Have a non-admin run the Zap. Field-level security on the connecting user is the usual reason a trigger sees nothing. - Add a custom field in Salesforce and look for it in the Zap editor. It may not appear immediately, and that is documented rather than broken. - Count your Salesforce connected apps again afterwards, so the next person adding one knows the number. Agent skill for this pair: https://www.reversecontact.com/integrations-hub/skills/salesforce-zapier.md **Field mapping:** - Leads, contacts, accounts, opportunities maps to Create, update, find or find-or-create. In either direction, with custom objects and fields supported. - A new or updated record maps to A polling trigger. Every Salesforce trigger polls except one, so latency is your Zapier plan rather than Salesforce's speed. - A Salesforce outbound message maps to An instant trigger. The only instant path on this pair. It is configured in Salesforce, not in Zapier. - A field changing maps to Updated Field on Record, with old and new values. Field History Tracking gives you both values. Useful, and it is also the trigger whose test data ignores your selected object. - A newly created custom field or object maps to The Zap editor dropdown, eventually. Zapier documents delays before new Salesforce fields and objects appear. - Does not cross: Marketing Cloud. Zapier states the Salesforce integration does not support those accounts at all. - Does not cross: Anything at all on a free Zapier plan. Salesforce is a premium app. - Does not cross: Reliable test records. If the org has no live data Zapier supplies test data, and the Updated Field on Record trigger returns the most recently updated record regardless of the object you chose. **What breaks:** - **Five access tokens across every third-party app.** Salesforce permits five access tokens per account across all third-party apps, and generating new ones revokes the older ones automatically. In an org that already has a sequencer, a conversation tool, an enrichment vendor and a reporting tool authenticated, adding Zapier can log one of them out. Nothing warns you, and the symptom on the victim is a connection that reports it is no longer working. - **The two vendors disagree on Essentials.** Zapier lists Essentials among the supported Sales and Service editions. Salesforce's own allocation table grants API calls to Professional with API access enabled, Enterprise, Unlimited, Performance and Developer Edition, and Outreach documents Essential as having no REST API access even with an add-on. Treat API access as the real requirement and verify it on your org, because the supported-editions list is not the thing that decides whether a call succeeds. - **Admin work before any Zap.** My Domain must be configured and custom domains are not supported. Zapier has to be approved as an External Client App, and because connected apps can no longer be created in Setup, an org that requires a custom app needs an administrator to create one. None of this is difficult and all of it sits in somebody else's queue, which is why a ten minute Zap can take two weeks to go live. - **Latency is your Zapier plan.** Polling runs every 2 minutes on Professional and every minute on Team and Enterprise, and a Zap can never poll faster than the greater of its plan minimum and the app minimum. Salesforce's own allocation is the other half of the arithmetic: 100,000 calls plus 1,000 per Salesforce licence per 24 hours on Enterprise, shared across every integration in the org, with no limit on concurrent requests shorter than 20 seconds and 25 concurrent long-running ones in production. **Failures people hit:** - This connection to Salesforce appears to no longer be working. Why: Zapier names this one precisely: you have exceeded the connected app access limit. Salesforce allows five access tokens per account across all third-party apps and revokes the oldest without notification. Fix: Audit third-party connected apps in Salesforce and remove what is unused. Adding another tool will revoke another token, so this returns until somebody prunes. - Please check your username and password, on a connection that is correct. Why: Sandbox was selected and the account does not support a sandbox environment. Zapier quotes this exact message for that case. Fix: Connect to production instead. The credentials are not the problem. - A trigger never fires for certain records. Why: User, object or field permissions on the connecting user. Zapier documents these as able to prevent triggers and actions from working. Fix: Check field-level security as well as object permissions, and test as the connecting user rather than as an admin. - A new custom field is missing from the Zap editor. Why: Zapier documents a delay before newly created Salesforce fields and objects appear in its dropdowns. Fix: Refresh the fields from the trigger step, and wait before rebuilding anything. - The Zap worked in testing and misbehaves live. Why: Test data. If the org has no live data Zapier supplies its own, and the Updated Field on Record trigger returns the most recently updated record without filtering on the object you chose. Fix: Test against a real record of the right object before turning the Zap on. - Marketing Cloud will not connect. Why: The Salesforce integration does not support Marketing Cloud accounts. Fix: There is no setting. Marketing Cloud needs its own route entirely. **What practitioners say** (14 threads from 2023 to 2026, read 2026-10-11): The thread that matters is an admin being asked to approve Zapier and asking the subreddit whether it is safe. The answers are strikingly consistent from consultants, ISVs and customers: it is solid, widely used, and the right tool below a certain volume. Nobody defends it at scale, and nobody attacks it below that, which is a more useful verdict than either side alone. - The volume question is the whole answer (r/salesforce, August 2024, 18 points): https://www.reddit.com/r/salesforce/comments/1f4ccqg/is_anyone_using_zapier/ - The consultants in the room vouch for it (r/salesforce, August 2024, 38 points): https://www.reddit.com/r/salesforce/comments/1f4ccqg/is_anyone_using_zapier/ - The question being asked is usually procurement, not engineering (r/salesforce, August 2024, 26 points): https://www.reddit.com/r/salesforce/comments/1f4ccqg/is_anyone_using_zapier/ - The admin knew they were being rushed (r/salesforce, August 2024, 7 points): https://www.reddit.com/r/salesforce/comments/1f4ccqg/is_anyone_using_zapier/ - What people actually build with it is more interesting than the sync (r/salesforce, February 2023, 95 points): https://www.reddit.com/r/salesforce/comments/1178yvo/chatgptopenai_zapier_enters_prompt_response_into/ Sources: https://help.zapier.com/hc/en-us/articles/8496020790925-How-to-get-started-with-Salesforce-on-Zapier | https://help.zapier.com/hc/en-us/articles/8495924437005-Control-when-your-Zap-runs | https://resources.docs.salesforce.com/latest/latest/en-us/sfdc/pdf/salesforce_app_limits_cheatsheet.pdf ### Salesforce and ClickUp Two integrations, both on Business Plus, and only the names sync both ways. - Built as: Native, Marketplace app - Syncs: Two-way sync - Moves: Tasks, Deals, Companies - Costs to turn on: Needs a higher plan. Setup: Hours - Requires: ClickUp Business Plus or Enterprise, a Salesforce admin, and beta access for the sync - Full guide: https://www.reversecontact.com/integrations-hub/salesforce-integrations/salesforce-clickup-integration **Verdict.** Two integrations share this pair and both sit on ClickUp Business Plus or Enterprise, which rules it out for most of the teams who ask about it. Salesforce Sync turns accounts and opportunities into ClickUp tasks in a dedicated Space, which is genuinely useful for a delivery team working off closed deals. What makes or breaks it is the field model: names and opportunity statuses sync both ways and everything else is dumped into the task description as text. If your delivery process needs to filter on close date or amount, that is a text blob rather than a field, and this is not the integration you wanted. **What syncs:** - Account names (two-way): The only account field that is a field on both sides. Accounts only sync at all if they are related to an opportunity. - Opportunity names and statuses (two-way): Edit the task in ClickUp and the change reaches Salesforce. - Every other account and opportunity field (out): Written into the ClickUp task description as text. Readable, not filterable, not automatable. - Salesforce records into search (out): Connected Search covers tasks, opportunities, contacts, leads, accounts, quotes, contracts and cases. It previews rather than syncs. - New Salesforce tasks and leads (in): Created from ClickUp's command bar through Connected Search, without opening Salesforce. **Which editions carry it** (rows ClickUp, columns Salesforce): - Free, Unlimited or Business with Package installed only: Nothing - Free, Unlimited or Business with Package installed and user connected: Nothing - Business Plus or Enterprise with Package installed only: Nothing - Business Plus or Enterprise with Package installed and user connected: Previews, search and creation **How to connect it** (A Salesforce admin to install the package, then each ClickUp user individually. There is no workspace-wide connection here.. Twenty minutes for the admin, then a minute per person.): 1. Check the ClickUp plan first [ClickUp: billing]. Both halves, Connected Search and Salesforce Sync, are Business Plus and Enterprise features. Below that there is nothing to configure, and ClickUp notes that pricing and packaging are subject to change. 2. Have a Salesforce admin install the managed package [The ClickUp install package link, logged in as a Salesforce admin]. Only Salesforce admins can install or upgrade it. If an earlier version is present the button says Upgrade rather than Install, and upgrading keeps the existing data. 3. Connect from the ClickUp App Center, per person [ClickUp: App Center, Salesforce]. Click Connect and follow the authorisation. Only personal connections are supported, which means every user who wants this does it themselves and an admin cannot do it for the team. 4. Paste a Salesforce link and watch the preview appear [A task description, comment, Doc or Chat message]. Link previews work in all four surfaces. After the first Salesforce link in a task, a Salesforce icon appears in the task sidebar listing every link posted there, which is the part that makes the task a place to work from rather than a reference. 5. Use the AI Command Bar for creation [ClickUp: AI Command Bar]. Create New Salesforce Task and Create New Salesforce Lead are commands rather than buttons, so they are discoverable only if somebody tells the team they exist. **How to check it worked:** - Paste a Salesforce record link into a task and confirm it renders as a preview rather than a URL. - Check the Salesforce icon appears in that task's sidebar afterwards. - Have a second person open the same task. If they see a bare link, they have not made their own connection, which is expected. - Try Create New Salesforce Lead from the AI Command Bar and confirm it reaches Salesforce. Agent skill for this pair: https://www.reversecontact.com/integrations-hub/skills/salesforce-clickup.md **Field mapping:** - A Salesforce record URL maps to A dynamic preview in ClickUp. In task descriptions, comments, Docs and Chat messages alike. The preview type can be changed by hand from the ellipsis menu. - Every Salesforce link in a task maps to The Salesforce panel in the task sidebar. Appears after the first link is pasted, and collects the rest. - An AI Command Bar command maps to A new Salesforce task or lead. Create New Salesforce Task and Create New Salesforce Lead, typed rather than clicked. - Salesforce content maps to ClickUp Connected Search. Searchable from ClickUp, on the same Business Plus and Enterprise gate as the rest. - Does not cross: Anything, for a user who has not made their own connection. Only personal connections are supported. - Does not cross: Anything, below ClickUp Business Plus. - Does not cross: Fields, in either direction. This is a context and creation integration rather than a sync. **What breaks:** - **Business Plus is the floor, for both halves.** Salesforce Sync and Salesforce Connected Search are each documented as Business Plus and Enterprise features. ClickUp's free and lower paid plans carry neither. Guests and limited members cannot use Connected Search at all, which matters in any workspace where clients hold those roles. - **Only names and statuses are really synced.** Account names sync both ways and opportunity names and statuses sync both ways. Everything else on both objects is added to the ClickUp task description. A description is not a field: you cannot build a view, a filter or an automation on the close date if the close date is a line of text inside a paragraph. - **No opportunity, no account.** Accounts only sync if they are related to a Salesforce opportunity. If you expected ClickUp to hold your account list, it will hold the subset with open or closed deals against it and nothing else, and there is no setting that changes this. - **The sync is in beta and gated behind a form.** ClickUp documents the sync integrations as beta, and the setup instructions tell you to click Contact Us and submit the beta form before you can proceed. The first sync can take several hours depending on volume, and failures arrive as task comments from the admin who set it up rather than in a log, so nobody sees them unless they open the task. **Failures people hit:** - One person sees previews and another sees a bare link. Why: Only personal connections are supported. The second person has not authorised their own. Fix: Have them connect from the ClickUp App Center. No admin action will do it on their behalf. - The integration is not available in the App Center. Why: The ClickUp plan is below Business Plus. Fix: That is a plan question for both halves, Connected Search and Salesforce Sync alike. - A Salesforce URL does not render as a preview. Why: Not every Salesforce URL type generates a dynamic preview, and the preview type can be set by hand. Fix: Hover over the link and change the type from the ellipsis menu before concluding it is unsupported. - Nobody uses the creation commands. Why: They live in the AI Command Bar as typed commands rather than as visible buttons. Fix: Tell the team the exact phrases. Discoverability is the whole problem here. - A Salesforce admin cannot find the upgrade. Why: With an earlier version installed, the button reads Upgrade rather than Install. Fix: Use it. ClickUp documents that upgrading keeps the existing data. **What practitioners say** (14 threads from 2021 to 2026, read 2026-10-11): This pair is barely discussed. The one on-topic thread is somebody weighing ClickUp against a Salesforce-native project tool, and the rest of the search surfaced teams asking a bigger version of the same question: how much of the work should live inside the CRM. That is the decision this integration is downstream of, and it is the one worth having first. - The real comparison is against a Salesforce-native tool (r/clickup, April 2021, 4 points): https://www.reddit.com/r/clickup/comments/mp6b1u/clickup_salesforce/ - Teams keep asking how to query the CRM from somewhere else (r/salesforce, February 2025, 4 points): https://www.reddit.com/r/salesforce/comments/1io0gp7/ai_integration/ - Opening CRM data to another tool is a security conversation (r/salesforce, February 2025, 8 points): https://www.reddit.com/r/salesforce/comments/1io0gp7/ai_integration/ - The instinct to reach for the newest thing gets pushback (r/salesforce, February 2025, 6 points): https://www.reddit.com/r/salesforce/comments/1io0gp7/ai_integration/ - What people actually want is one place to look (r/salesforce, February 2025, 4 points): https://www.reddit.com/r/salesforce/comments/1io0gp7/ai_integration/ Sources: https://help.clickup.com/hc/en-us/articles/29231790107031-Salesforce-Sync-integration | https://help.clickup.com/hc/en-us/articles/24113074235927-Salesforce-Connected-Search-integration ### Salesforce and n8n Connected Apps are on the way out, and n8n Cloud needs a permission admins lack by default. - Built as: Zapier, Make or n8n, Built on the API - Syncs: Two-way sync - Moves: Contacts, Companies, Deals, Tasks, Custom objects - Costs to turn on: Metered by usage. Setup: Hours - Requires: An n8n instance, a Salesforce edition with API access, and an External Client App - Full guide: https://www.reversecontact.com/integrations-hub/salesforce-integrations/salesforce-n8n-integration **Verdict.** The node covers more of Salesforce than any other orchestration tool in this directory: accounts, contacts, leads, opportunities, cases, tasks, attachments, documents, users, custom objects, flows you can invoke, and a raw SOQL search that returns everything in one response. The work is all on the Salesforce side and almost none of it is difficult, but two details decide whether the first afternoon is pleasant. Build an External Client App rather than a Connected App, because Salesforce is retiring the latter. And if you are on n8n Cloud, grant the connecting profile Approve Connected Apps for Non-Admins, which is off by default even for administrators. **What syncs:** - Leads, contacts and accounts (two-way): Create, upsert, get, get all, update, delete, add a note, and add a lead to a campaign. - Opportunities (two-way): Create, upsert, get, get all, update, delete and add a note, plus the metadata overview for the object. - Cases and tasks (two-way): Full create, read, update and delete, and a comment on a case. More of the service object than most connectors touch. - Custom objects (two-way): Create, upsert, get, get all, update and delete, with custom fields added through Additional Fields. - SOQL (out): The Search resource executes a SOQL query and returns all results in a single response, which is the fastest route to anything the resources do not model. - Flows (in): Get all and invoke, so n8n can hand work back to logic that already lives in Salesforce rather than reimplementing it. **Which editions carry it** (rows n8n, columns Salesforce): - JWT with Require Secret for Web Server Flow: Unchecked - JWT with Require Secret for Refresh Token Flow: Unchecked - JWT with Require PKCE Extension: Unchecked - OAuth2 with Require Secret for Web Server Flow: Checked - OAuth2 with Require Secret for Refresh Token Flow: Checked - OAuth2 with Require PKCE Extension: Checked **How to connect it** (A Salesforce admin who can create an External Client App and edit a profile, plus whoever runs n8n. Two people on two teams in most companies.. An hour for OAuth2. Longer for JWT, because a certificate has to exist first.): 1. Pick JWT or OAuth2 before you open Salesforce Setup [Design, not a settings page]. n8n supports both and their Salesforce-side settings are deliberate opposites. OAuth2 is the shorter path and gives a user-context connection. JWT needs a self-signed certificate and a private key, and gives a connection that does not depend on a browser session. 2. Create an External Client App, not a Connected App [Salesforce: Setup, App Manager, New External Client App]. Salesforce is deprecating Connected Apps in favour of External Client Apps, existing ones keep working, and n8n says to use the new kind for anything new. Enter a name and a contact email, then tick Enable OAuth under API. 3. Set the callback URL to something Salesforce will accept [Salesforce: the app's Callback URL box]. n8n documents http://localhost:1717/OauthRedirect, or your instance URL if you are self-hosting. Salesforce only permits plain HTTP on localhost, so a self-hosted instance on a bare IP address has to be reachable over valid HTTPS with a DNS name behind it before this field can be filled in at all. 4. Enable the right flow and set the three policy checkboxes [Salesforce: Flow Enablement and OAuth Policies]. For JWT, enable the JWT Bearer Flow, upload the certificate, and leave Require Secret for Web Server Flow, Require Secret for Refresh Token Flow and Require PKCE all unchecked. For OAuth2, enable the Authorization Code and Credentials Flow and leave all three checked. The grid below is this step. 5. Copy the consumer details into n8n [Salesforce: Manage Consumer Details]. The Consumer Key becomes the Client ID in n8n. For OAuth2 the Consumer Secret becomes the Client Secret; for JWT you paste the contents of the private key file instead, along with your Salesforce username. Set Environment Type to Production or Sandbox to match the org you are pointing at. 6. Grant the profile permission that is off by default [Salesforce: Setup, Profiles, Administrative Permissions]. Enable Approve Connected Apps for Non-Admins on the profile of the user who will authorise, which may appear as approving apps connected but not installed depending on your language. n8n states it is not enabled by default even for administrator profiles, and without it authentication fails. 7. Set the policies Salesforce recommends rather than the defaults [Salesforce: Manage Connected Apps, Edit Policies]. Salesforce recommends expiring the refresh token after 90 days, a session timeout of 15 minutes, and Permitted Users set to admin approved users are pre-authorized. None is required to connect and all three change what happens three months later. 8. Decide where logic lives before you build anything [n8n: the Flow resource]. The node can list and invoke Salesforce flows, so logic that belongs in the org can stay there and be called. Deciding this up front is what stops the same rule existing in two places, which is the failure this pair produces most often. **How to check it worked:** - Authorise once and then wait for the token to refresh rather than declaring it done. A connection that authorises and then fails in 90 days is a refresh token policy rather than a credential problem. - Run the Search resource with a one-line SOQL query before using any of the object resources. It is the cheapest proof that the scopes and the environment type are right. - Invoke one Salesforce flow from n8n and confirm it ran in the org's own logs. That is the test of whether this pair can hand work back, which is the half most builds skip. - Check the org's API usage after a full run. The allocation is shared with every other integration, and the way you find out you exhausted it is somebody else's connector failing. Agent skill for this pair: https://www.reversecontact.com/integrations-hub/skills/salesforce-n8n.md **Field mapping:** - Account maps to Create, upsert, get, get all, update, delete, add note, metadata overview. Upsert is a distinct operation from create, which matters: it is the only one that will not duplicate a record you already have. - Contact maps to The same eight, plus add lead to a campaign. The campaign operation appears on both Contact and Lead, which reads like a duplicate and is two different Salesforce calls. - Lead maps to Create, upsert, get, get all, update, delete, add note, add to campaign. No convert operation. A lead conversion has to go through the Search resource or the HTTP Request node, which is the one obvious gap on an otherwise complete list. - Opportunity maps to Create, upsert, get, get all, update, delete, add note, metadata overview. Stages and amounts are fields rather than operations, so a stage change is an update with the right picklist value in it. - Case maps to Create, get, get all, update, delete, add comment, metadata overview. The only Service Cloud object on the node, and the reason some teams run this pair with no sales use case at all. - Custom object maps to Create, upsert, get, get all, update, delete. Custom fields are reached through Additional Fields, then Custom Fields in the dropdown. This is the part that makes the node usable against a real org rather than a demo one. - Flow maps to Get all flows, invoke a flow. The most underused pair of operations here. Logic that already exists in Salesforce can be called rather than rewritten, which is how this pair avoids duplicating business rules. - Search maps to Execute a SOQL query, all results in one response. Anything the resources above do not model. All results in a single response is convenient and is also how a workflow accidentally pulls a hundred thousand records. - Does not cross: Lead conversion. There is no operation for it, so it goes through SOQL and an update, or through the HTTP Request node on the same credential. - Does not cross: Anything your edition does not include. API access is the gate in front of every operation above, and no orchestration tool can supply it. - Does not cross: The org's own rules. Validation rules, required fields, duplicate rules and Apex triggers all apply to every write the node makes, exactly as they apply to any other API client. **What breaks:** - **Connected Apps are deprecated.** Salesforce is moving to External Client Apps and n8n recommends them for new integrations. Existing Connected Apps keep working and new ones should not be created. Pre-authorising profiles and permission sets is still a step on the legacy path, which is one more reason to take the new one. - **A permission admins do not have by default.** On n8n Cloud, the connecting user's profile needs Approve Connected Apps for Non-Admins. n8n documents that this is not enabled by default even for administrator profiles. The failure arrives as a refusal to authorise with nothing useful in the message, and it is the first thing to check before anybody rebuilds the credential. - **The two auth methods have opposite settings.** JWT wants the secret and PKCE requirements turned off under OAuth Policies and a certificate uploaded; OAuth2 wants both requirements left on. Both need the Full access and refresh token scopes and a callback URL that differs between self-hosted and n8n Cloud. Read the half of the page that matches your choice, because following both produces a configuration that authorises on neither. - **The API allocation is shared and finite.** Salesforce allows 100,000 requests plus 1,000 per Salesforce licence per 24 hours on Enterprise and on Professional with API access, 5,000 per licence on Unlimited and Performance, across every integration in the org. A workflow looping row by row is competing with your existing connectors, and there is a separate cap of 25 concurrent requests running 20 seconds or longer in production. **Failures people hit:** - Authentication fails from n8n Cloud with nothing useful in the message. Why: The connecting user's profile is missing Approve Connected Apps for Non-Admins. n8n states this is not enabled by default even for administrator profiles. Fix: Enable it under Administrative Permissions on that profile. It may be labelled as approving apps connected but not installed, depending on your org's language. - External client app is not installed in this org. Why: An External Client App has a distribution state. One created as Local can only be used in the org that created it, so the same OAuth flow that works internally refuses for anybody else. Fix: For an app other orgs will use, either authorise with a user holding the approval permission, or package the app and have each org install it. Practitioners report sandbox profiles missing the permission even on standard System Administrator, which Salesforce resolved by matching sandbox licences to production. - The callback URL will not save, or the redirect 404s. Why: Salesforce permits plain HTTP only on localhost. A self-hosted instance on a dedicated IP address has to use HTTPS, and a free certificate needs a DNS name rather than an address. Fix: Put a DNS name and a valid certificate in front of the instance before filling in the callback URL. This is a hosting job rather than a Salesforce one, and it is where the setup stalls on a locked-down network. - The credential authorises and stops working months later. Why: The refresh token policy expired it. Salesforce recommends expiring refresh tokens after 90 days, which is advice rather than a default, so somebody probably took it. Fix: Check Edit Policies on the app before blaming the credential. The same page holds the session timeout and the permitted users setting, and all three were set once by somebody who has moved on. - A write failed and the workflow reported success. Why: Validation rules, required fields, duplicate rules or an Apex trigger rejected the record. The node is an API client and the org refuses it the same way it refuses any other. Fix: Read the node's error output rather than the execution status, and rehearse against a sandbox with Environment Type set to match. Upsert rather than create is also what stops a retry producing a second record. - A SOQL search returned far more than expected and the workflow stalled. Why: The Search resource returns all results in a single response by design. There is no paging to protect you from a query without a LIMIT clause. Fix: Put the LIMIT in the query. Salesforce also caps concurrent long-running requests, at 25 running 20 seconds or longer in production, which is what a few of these at once will hit. - Nothing the workflow needs is in the resource list. Why: Lead conversion and anything newer than the node are not modelled. That is the documented scope of it rather than a bug. Fix: Use the Search resource for reads and the HTTP Request node for writes, selecting Predefined Credential Type and the Salesforce credential you already made. No second authentication is involved. - Someone else's integration started returning errors after your backfill. Why: The API allocation is shared across the org: 100,000 requests plus 1,000 per licence per 24 hours on Enterprise and on Professional with API access, and 5,000 per licence on Unlimited and Performance. Fix: Batch the reads, use SOQL rather than a loop of gets, and schedule a backfill outside business hours. This is the most socially expensive failure on the page because the symptom appears on somebody else's system. **What practitioners say** (14 threads from 2025 to 2026, read 2026-10-11): In r/n8n the threads are specific and the problem is almost always authentication, usually the callback URL on a self-hosted instance that has no public HTTPS. In r/salesforce the conversation is about something else entirely: whether this is allowed. The objections are compliance and data residency rather than capability, and they come from people who like the tool. Both are worth reading, because the second set decides whether the first set matters at you. - The callback URL is the step that stops a locked-down instance (r/n8n, March 2025, 1 points): https://www.reddit.com/r/n8n/comments/1jh5hkb/using_n8n_behind_a_firewall_connecting_to/ - The permission that blocks authorisation is new and not always granted (r/salesforce, November 2025, 1 points): https://www.reddit.com/r/salesforce/comments/1otmk17/pushing_data_to_salesforce_new_integration/ - The objection in r/salesforce is compliance, not capability (r/salesforce, June 2025, 7 points): https://www.reddit.com/r/salesforce/comments/1l9w37h/whats_the_consensus_on_using_thirdparty_ai_agent/ - It is a batch tool, and the concurrency limit is where that shows (r/salesforce, June 2025, 3 points): https://www.reddit.com/r/salesforce/comments/1l9w37h/whats_the_consensus_on_using_thirdparty_ai_agent/ - The reason people reach for it is not having to buy more Salesforce (r/n8n, January 2025, 1 points): https://www.reddit.com/r/n8n/comments/1iae6oq/use_case_help/ Sources: https://docs.n8n.io/integrations/builtin/app-nodes/n8n-nodes-base.salesforce | https://docs.n8n.io/integrations/builtin/credentials/salesforce | https://resources.docs.salesforce.com/latest/latest/en-us/sfdc/pdf/salesforce_app_limits_cheatsheet.pdf ### Clay and Reverse Contact Four native actions on Clay credits, and no Reverse Contact account needed to start. - Built as: Native, Built on the API - Syncs: One way, in - Moves: Contacts, Companies - Costs to turn on: Metered by usage. Setup: Minutes - Requires: A Clay account. Your own Reverse Contact key is optional and changes which meter you spend. - Full guide: https://www.reversecontact.com/integrations-hub/clay-integrations/clay-reverse-contact-integration **Verdict.** This is the shortest path in the directory between Reverse Contact and a CRM, and the only one that needs no Reverse Contact account to try. The app is one of four enrichment actions you pick from a menu, and from there Clay's own CRM integrations carry the result the rest of the way. It is also the right place to put Reverse Contact in a waterfall, because returning null with a confidence score gives the next step something honest to branch on. Build the HTTP column instead when you want an endpoint the four actions do not expose, or the raw response in front of you while you tune the request. **What syncs:** - Clay to Reverse Contact (out): The native action takes the row's email, name, company or profile URL. An HTTP API column POSTs to /v2/enrich/persons or /v2/enrich/companies instead. - Record back to the column (in): The full structured profile lands as JSON, and you map the fields you want into their own columns. - Confidence and nulls (in): A miss returns null with a confidence score rather than a guess, so a conditional run can decide what happens next. - Onward to the CRM (out): Clay's HubSpot or Salesforce Update action writes the mapped fields back. **Which editions carry it** (rows Clay, columns Reverse Contact): - Free with Run the four Reverse Contact actions: Included - Free with Schedule recurring enrichment runs: Not included - Free with Reach an endpoint the actions miss, over HTTP: Not included - Free with Write the result into HubSpot or Salesforce: Not included - Launch with Run the four Reverse Contact actions: Included - Launch with Schedule recurring enrichment runs: Included - Launch with Reach an endpoint the actions miss, over HTTP: Not included - Launch with Write the result into HubSpot or Salesforce: Not included - Growth with Run the four Reverse Contact actions: Included - Growth with Schedule recurring enrichment runs: Included - Growth with Reach an endpoint the actions miss, over HTTP: Included - Growth with Write the result into HubSpot or Salesforce: Included - Enterprise with Run the four Reverse Contact actions: Included - Enterprise with Schedule recurring enrichment runs: Included - Enterprise with Reach an endpoint the actions miss, over HTTP: Included - Enterprise with Write the result into HubSpot or Salesforce: Included **How to connect it** (Whoever owns the Clay workbook. No admin on either side, and no Reverse Contact account at all unless you want the lookups on your own key.. Ten minutes for the column. The two decisions in front of it are the part worth taking slowly.): 1. Check which Clay plan you are on, because the enrichment is not the gated part [Clay: pricing]. Clay's catalogue marks every Reverse Contact action Included in All Plans, so the lookup runs on a Free workspace. Its plan comparison puts CRM integrations and HTTP API integrations on Growth, listed at $446 a month. You can therefore measure the match rate for nothing and still have nowhere to deliver the answer. 2. Decide which meter the lookups bill to, before you add a column [Clay: Add enrichment, Select Reverse Contact account]. The modal asks you to pick an account. Leave it on the Clay-provided key and the lookups spend Clay credits. Click + Add account and authenticate, and they bill your own Reverse Contact workspace instead. Both work on every plan, and the choice decides which bill grows and whose usage dashboard shows the calls. 3. Pick the action that matches the identifier you already hold [Clay: Integrations, Reverse Contact]. Find Professional Profile starts from an email, Find company professional profile from a domain, and the two Enrich actions from a profile URL. Clay documents a different required input and a different output list for each, so they are not interchangeable, and the wrong one returns a thinner record rather than an error. 4. Write to columns nothing else owns [Clay: column names]. Prefix them, the way the CRM pairs prefix a property. The column a later Update action maps into your CRM is what decides whether a rep ever loses a field they typed, and renaming columns after the write step is mapped is tedious rather than hard. 5. Run ten rows and open the raw response on one of them [Clay: the cell, Expand]. This is the whole reason to use a table rather than a pipeline. The response carries an update date and a confidence score alongside the fields, and reading those on ten real rows of your own list tells you more than any published match rate can. 6. Chain the second action if you need history [Clay: a second enrichment column]. Find Professional Profile returns identity, the current title and the current company. Experience, education and skills come from Enrich professional profile, run on the LinkedIn URL the first action returned. Two columns, and 3 credits in total on your own key. 7. Put Only run if on every column that costs money [Clay: run settings, Only run if]. This is what makes a waterfall a waterfall: the next provider touches only the rows this one left empty. Reverse Contact returning null rather than a best guess is what gives the condition something honest to test, so the two features suit each other exactly. 8. Turn on Auto-update last [Clay: run settings, Auto-update]. Clay documents it as re-running the enrichment when the source data changes, so an edit to any column it reads is a re-run and a 2-credit action becomes a standing cost. Turn it on once the upstream columns have stopped moving. **How to check it worked:** - Run Find Professional Profile on your own work email. You already know the right answer, so it is the one row where a wrong match is obvious rather than plausible. - Run it on an address you know resolves to nobody, a role mailbox like info@ or a personal alias. The cell should come back empty rather than populated with a confident stranger, and watching that happen once is what tells you the null is real. - Open the raw response on a matched row and find the update date. That one field decides whether you ever need the live endpoints, and it is the one nobody checks before buying a refresh. - Note your balance, run ten rows, note it again, then count how many rows actually matched. The two numbers will not agree on Clay credits, because Clay bills the attempt, and the gap is your real cost per filled field. Agent skill for this pair: https://www.reversecontact.com/integrations-hub/skills/clay-reverse-contact.md **Field mapping:** - Find Professional Profile maps to Reverse lookup from an email, 2 credits. Takes any combination of Email, Full name, Company name and Company domain, and Clay states that more fields improve match accuracy. Returns the ID, Public ID, LinkedIn URL, first and last name, headline, current position title, current company name and ID, and an update date. - Find company professional profile maps to Reverse lookup from a domain, 2 credits. Company domain is the only required input. Returns the company ID and name, industry, tagline, website URL, employee count and count range, follower count, an update date, and a city and country. - Enrich professional profile maps to Cached lookup from a profile URL, 1 credit. Clay lists ID, Public ID, Member ID, LinkedIn URL, first and last name, headline and summary, while the action description also promises experience, education and skills. Open the action in your own table before designing a column around the longer list. - Enrich company profile maps to Cached lookup from a profile URL, 1 credit. The fullest output of the four: description, tagline, logo and background URLs, employee count and range, followers, headquarter, specialities, locations, founded date and a phone number. - An HTTP API column maps to Any endpoint, on your own key. The route to everything the four actions do not expose, including the free freshness check and the live endpoints. Clay's plan comparison puts HTTP API integrations on Growth and above, so this is the one half of the pair with a real tier gate. - Only run if maps to A condition, not a field. Where the waterfall is actually built. The column runs only where the condition holds, so a second provider is charged for the rows this one left empty rather than for the whole table. - The write into a CRM maps to Not Reverse Contact's job. Clay's own HubSpot or Salesforce Update action carries the mapped columns the rest of the way, and Clay marks CRM integrations as a Growth feature. Nothing travels back to Reverse Contact from here at all. - A phone number or a verified email maps to Separate endpoints, not Clay actions. Reverse Contact prices a direct phone at 20 credits and a business email at 3, each charged only when one is found. Neither is one of the four actions, so both need an HTTP column or a different route entirely. - Does not cross: The live endpoints. They answer with a webhookId to poll rather than a record, and a column has nothing to poll with. Reverse Contact aims to deliver a live result in under 15 seconds and documents that it can take tens of minutes, which is why this belongs in a workflow rather than in a table. - Does not cross: The free freshness check. It is not one of the four actions, so the only route to it from Clay is an HTTP API column, which needs Growth. - Does not cross: Anything travelling the other way. This is a read layer: no Clay column writes to Reverse Contact, and there is nothing in the product for it to write to. **What breaks:** - **Clay bills the attempt, whichever meter you chose.** The native app spends Clay credits by default and your own Reverse Contact credits once you connect a key, so this is one meter rather than two unless you build the HTTP column and bring your own key to it. What does not change is that Clay bills the attempt rather than the result, so rows that miss still cost. Put the cheapest, highest-hit-rate source first in any waterfall for that reason. - **Live resolution returns a task.** The /live endpoints are asynchronous: they hand back a task id to poll. Inside a Clay column the cached endpoints are the straightforward choice, and the live path belongs in n8n where polling is natural. - **The credit cost is published, the dollar rate is not.** Reverse Contact publishes 2 credits for a reverse lookup from an email and 1 for a cached profile lookup, and no dollar rate per lookup. On the native app you are usually spending Clay credits rather than theirs, so the number that decides this route is Clay's price per action. - **An unconfident match is an empty cell.** Reverse Contact returns the best-scored profile first where there are namesakes, with the associated profiles alongside it, and leaves the cell empty when it is not confident. That is the behaviour you want from a data layer and it means your table needs a rule for empty, not just for wrong. - **HTTP columns and the CRM write both start at Growth.** Clay's plan comparison puts HTTP API integrations and CRM integrations on Growth, listed at $446 a month, while the four Reverse Contact actions are Included in All Plans. So the enrichment runs on a Free workspace and neither the endpoints the actions miss nor the write-back into HubSpot or Salesforce is reachable from one. Evaluate on Free, budget for Growth. **Failures people hit:** - The column came back empty on somebody you know is real. Why: Reverse Contact returns null rather than a best guess when it is not confident, and puts a confidence score on every response. An empty cell is the documented answer rather than a failure. Fix: Treat empty as a branch instead of an error. Put Only run if on the next provider's column so it picks up exactly the rows this one left blank, which is the whole mechanism of a waterfall. - Find Professional Profile returned a person with no work history. Why: Clay documents a different output list per action, and the one that starts from an email returns identity, the current title and the current company rather than experience, education and skills. Fix: Chain Enrich professional profile onto the LinkedIn URL the first action returned. Two columns, and 3 credits in total once you are on your own key. - The enrichment works and nothing ever reaches the CRM. Why: Clay's plan comparison marks CRM integrations as a Growth feature while the Reverse Contact actions are Included in All Plans, so the lookup and the delivery are gated at different tiers. Fix: Check the plan before you debug the mapping. On Free or Launch the write action is not there to configure, which presents as a broken column rather than as a missing tier. - The bill is bigger than the number of rows that got enriched. Why: Clay states that each record enriched or exported counts as 1 Action regardless of data source or provider, so a miss costs the same Action as a hit. Fix: Filter the import step down to the rows actually missing the field, and connect your own Reverse Contact key if misses dominate: a 4xx costs 0 credits there, so on that meter a miss is free. - There is no freshness check in the action list. Why: The Clay listing carries four actions, the two Find and the two Enrich ones. The free check endpoints are not among them. Fix: Reach them through an HTTP API column, which Clay puts on Growth and above. Checking first and fetching second is the sequence Reverse Contact's own documentation recommends for saving credits. - A live call never returns a record. Why: The live endpoints are asynchronous by design. They reply with a webhookId and deliver the result afterwards, and Reverse Contact documents that this usually takes seconds and can take tens of minutes. Fix: Keep the cached actions in the table and run live resolution where a poll loop is ordinary. Polling is free and off the rate-limit clock wherever you do it, so the cost of moving it is the workflow rather than the call. - Everything stopped at once, including the calls that were free. Why: When a Reverse Contact workspace drops below 2 credits the free Check endpoints are paused too and answer 402 NO_CREDITS, because the fetch a check precedes can itself cost 2. Fix: Watch quotas.workspace.credits.left, which rides on every response. GET /v2/usage and webhook polling keep working whatever the balance, so a balance check never fails for the same reason the lookup did. - The table re-ran and spent credits on rows that were already done. Why: Auto-update is documented as re-running the enrichment whenever the source data changes, so an edit to any column it reads counts as a change. Fix: Turn auto-update on last, after the upstream columns have settled, and leave Only run if on the column so even a re-run stays conditional. **What practitioners say** (14 threads from 2023 to 2026, read 2026-10-11): Nobody discusses this pair by name, so the search was for the job instead: what a Clay table needs underneath it, and whether the data already in it is any good. The threads are blunter than any vendor page and they agree on one thing, which is that Clay is a workflow engine rather than a data source. The arguments are about price and about freshness, and both of those have a published answer rather than an opinion. - Clay is not a data source, and its own users say so first (r/LeadGeneration, May 2025, 3 points): https://www.reddit.com/r/LeadGeneration/comments/1kzrclf/clay_company_and_prospect_data_seems_limited/ - Practitioners pick a provider with a bake-off, not a datasheet (r/gtmengineering, December 2025, 3 points): https://www.reddit.com/r/gtmengineering/comments/1pd3odj/can_clay_be_my_main_enrichment_tool_instead_of/ - The lever is the condition on the column, not the provider (r/gtmengineering, January 2026, 16 points): https://www.reddit.com/r/gtmengineering/comments/1q592xw/what_are_the_best_alternatives_to_clay_that_are/ - Your own key removes one markup and leaves the other (r/techsales, April 2026, 3 points): https://www.reddit.com/r/techsales/comments/1sahaaq/how_are_you_managing_enrichment_costs_with_clay/ - Why the four actions need no Reverse Contact account at all (r/sales, September 2024, 13 points): https://www.reddit.com/r/sales/comments/1fegpn3/can_you_tldr_what_clay_does_why_is_it_all_the/ Sources: https://docs.reversecontact.com/getting-started | https://docs.reversecontact.com/guides/credits | https://docs.reversecontact.com/guides/rate-limits | https://www.reversecontact.com/pricing | https://www.clay.com/integrations/data-provider/reversecontact | https://university.clay.com/docs/reverse-contact-integration | https://www.clay.com/pricing | https://university.clay.com/docs/hubspot-integration-overview ### Clay and Apollo A native provider column, and the cheapest first step in most waterfalls. - Built as: Native - Syncs: One way, in - Moves: Contacts, Companies - Costs to turn on: Metered by usage. Setup: Minutes - Requires: Any Clay plan, plus your own Apollo account. Clay's catalogue marks every Apollo action as needing one. - Full guide: https://www.reversecontact.com/integrations-hub/clay-integrations/clay-apollo-integration **Verdict.** Apollo is a native Clay provider, so this is a column rather than an integration project, and Clay lists the integration as included on all plans rather than behind Growth like the CRM ones. Its place in a stack is almost always the same: first step in a waterfall, because it resolves a large share of a normal list at the lowest unit cost of anything here, and whatever it misses goes to a specialist. What changed in 2026 is the metering: bringing your own Apollo key removes the Data Credit cost and still spends an Action per record, so the key is no longer the way to make a wide table cheap. **What syncs:** - Clay to Apollo (out): A native enrichment column, configured in the table rather than through an API. - Records back (in): Contact and company data into columns, ready to route into a CRM write. - Credits (event): Either drawn from Clay credits or from your own Apollo key, which changes the economics. **Which editions carry it** (rows Apollo, columns Clay): - Enrich a person or company with Your own Apollo account: Required first - Enrich a person or company with The contact already in Apollo: Not required - Enrich a person or company with The contact already enrolled: Not required - Enrich a person or company with A sending mailbox in Apollo: Not required - Find people, jobs or saved contacts with Your own Apollo account: Required first - Find people, jobs or saved contacts with The contact already in Apollo: Not required - Find people, jobs or saved contacts with The contact already enrolled: Not required - Find people, jobs or saved contacts with A sending mailbox in Apollo: Not required - Find or create a contact with Your own Apollo account: Required first - Find or create a contact with The contact already in Apollo: Not required - Find or create a contact with The contact already enrolled: Not required - Find or create a contact with A sending mailbox in Apollo: Not required - Add a contact to a sequence with Your own Apollo account: Required first - Add a contact to a sequence with The contact already in Apollo: Required first - Add a contact to a sequence with The contact already enrolled: Not required - Add a contact to a sequence with A sending mailbox in Apollo: Required first - Change a sequence status with Your own Apollo account: Required first - Change a sequence status with The contact already in Apollo: Required first - Change a sequence status with The contact already enrolled: Required first - Change a sequence status with A sending mailbox in Apollo: Not required **How to connect it** (Whoever owns the Clay workbook, plus somebody with an Apollo account to connect. No admin on either side.. Five minutes to connect. The thinking is about where in the waterfall it goes.): 1. Connect your own Apollo account first [Clay: + Add account]. Clay's integration catalogue marks all fourteen Apollo actions as needing your own account, and the setup is one click and an authentication. The integration itself is listed as included on all Clay plans, unlike the CRM integrations, which start on Growth. 2. Decide whether the key or Clay's credits pay for the data [Clay: Settings, Connections]. A key added in Settings under Connections, or from Add Account in the enrichment panel, removes the Data Credit cost for that provider. The Action is charged either way, which is the part that changed when Clay split one meter into two. 3. Put Apollo at the front of the waterfall, not the middle [Clay: column order]. A waterfall is only cheap if the cheap provider runs first. Apollo resolves a large share of a North America heavy list at the lowest unit cost here, so a specialist ahead of it inverts the economics of the table without changing anything a reader of the interface would notice. 4. Qualify before you enrich [Clay: run settings, Only run if]. Clay's own credit guide puts this first: reorder so disqualified rows are filtered out before the enrichment runs, and use Only run if on the column. A filtered view enriches only the rows in view, which is the same lever with less setup. 5. Use Enrich Person for a known individual and Find People to discover them [Clay: Add enrichment]. Enrich Person takes any of name, email, company or Apollo ID, all optional, and returns contact details, employment history and firmographics. Find People from Apollo takes job titles and optional domains with a limit of 1 to 1,000, and is a table source rather than a column. 6. Run Find or Create Contact before anything touches a sequence [Clay: Find or Create Contact]. It dedupes by default, on email, LinkedIn URL, or name plus organisation, and returns a was_existing flag telling you which happened. That flag is what a sequence step should branch on, because Add Contact to Sequence requires a contact that already exists. 7. Give the sequence action a sending mailbox [Clay: Add Contact to Sequence]. Sequence ID, Contact ID and Send Email From Email Account ID are all required. Five override flags default to false: add without email, add unverified email, add with job change, add active in other campaigns, add finished in other campaigns. Leaving them off is why rows come back skipped. 8. Test on ten rows before auto-update [Clay: Auto-run]. Clay recommends about ten rows for a new integration, and recommends turning auto-run off while building so rows added too early do not spend anything. The toolbar button reads Manual once it is off. **How to check it worked:** - Check the was_existing flag on a Find or Create Contact run. If every row comes back as new, the dedupe is matching on nothing useful and you are creating duplicates in Apollo rather than in Clay. - Add one contact to a sequence and read the output rather than the row status. The action returns the reason a contact was skipped, which is usually a missing email or an existing enrolment. - Run Enrich Person on twenty rows you know the answer for and count the hits. That number is your match rate, and the Action cost of the full table divides by it. - Open the Clay billing view after the test and check which meter moved. If Data Credits went down on a provider you brought a key for, the key is not attached to that action. Agent skill for this pair: https://www.reversecontact.com/integrations-hub/skills/clay-apollo.md **Field mapping:** - Find People from Apollo maps to Job titles, optional domains, limit 1 to 1,000. A table source rather than an enrichment column. This is the only Apollo action here that creates rows instead of filling them. - Enrich Person maps to Any of name, email, company, Apollo ID. Every input is optional, which means it will run on almost nothing and return almost nothing. Returns contact details, employment history, firmographics, department and seniority. - Enrich Company maps to Company domain, required. The one action with a single required input. Returns headcount by department, revenue, tech stack, offices, founded year and company type. - Find People at Company By Job Title maps to Job titles and company domains, limit up to 10. A tighter limit than Find People. Include Contacts prioritises people already linked to your CRM when a limit is set, which changes what comes back rather than how much. - Find Open Jobs maps to Company ID or job search terms. Returns a postings array with title, URL, location, posted date and last seen date, plus a total count. Last seen is the field that makes this a signal rather than a snapshot. - Find Saved Contacts maps to Keywords, limit 1 to 10. Searches your own Apollo workspace rather than the database. Clay recommends an email address as the keyword, and the output includes sequence enrolment status. - Find or Create Contact maps to Run Dedupe on by default, plus the fields. Dedupes on email, LinkedIn URL, or name plus organisation, and returns a was_existing flag. That flag is the only thing that tells you which of the two things the action did. - Add Contact to Sequence maps to Sequence ID, Contact ID, sending account ID. All three required, and the contact must already exist in Apollo. Five override flags default to false, and the output names the reason a contact was skipped. - Does not cross: Anything about a CRM. Apollo in Clay returns columns, and getting those columns into HubSpot or Salesforce is a separate write action on a separate integration with its own plan gate. - Does not cross: An Apollo ID you have not fetched. Find Account by ID and Find Contact by ID both require one, so they belong after a search rather than at the start of a table. - Does not cross: A sequence enrolment for somebody Apollo has never seen. The action will not create the contact for you, which is what Find or Create Contact is for. **What breaks:** - **Your own key saves credits, not actions.** Clay documents it in one sentence: connecting your API keys eliminates the Data Credit cost, and an Action is still consumed. So an Apollo key removes the data half of the bill and leaves the platform half, which is the half that scales with the number of rows rather than the number of hits. - **One Action per record, whatever the provider.** Clay's own wording is that each record enriched or exported counts as 1 Action regardless of data source or provider, and that CRM syncs and HTTP calls count too. A miss costs the same Action as a hit, so the effective cost of a wide table is set by the row count rather than the match rate. - **Actions do not roll over and cannot be topped up.** Unused Actions expire at the end of the month and there is no top-up to buy, while unused Data Credits accumulate to twice the monthly limit on a monthly plan and can be topped up at a 30% premium. The two meters behave differently enough that running out of one is a different problem from running out of the other. - **Coverage is a geography question.** Apollo is strongest on North American data. On a European list the same waterfall wants a different first step, and assuming otherwise is how a table returns half-empty. - **The sequence actions have prerequisites, not defaults.** Add Contact to Sequence needs the contact to exist in Apollo already and takes a sending email account ID as a required input. Update Contact Status in Sequence needs the contact to be enrolled as well. Neither will create what it is missing. **Failures people hit:** - Enrich Person returns almost nothing on a lot of rows. Why: Every input on that action is optional, so it runs on whatever is populated. A row carrying only a first name is a valid call that cannot resolve. Fix: Require a column before the action runs, with Only run if. An email or a company domain plus a full name is the combination that resolves; a name alone is an Action spent on nothing. - Rows come back skipped from Add Contact to Sequence. Why: The output names the reason, and it is usually one of two: the contact has no email address, or they are already in that sequence. Five override flags govern the edge cases and all five default to false. Fix: Read the skip reason rather than the row status, and decide each override deliberately: add without email, add unverified email, add with job change, add active in other campaigns, add finished in other campaigns. - Add Contact to Sequence will not run at all. Why: Send Email From Email Account ID is a required input and it is the one people leave blank. The contact also has to exist in Apollo before this action, which is a separate prerequisite. Fix: Fetch the sending account ID once and hold it in a column, then run Find or Create Contact ahead of the sequence step and branch on its was_existing flag. - Apollo filled up with duplicate contacts. Why: Run Dedupe was turned off, or the rows carry none of the three things it matches on: email, LinkedIn URL, or name plus organisation. Fix: Leave Run Dedupe on, which is the default, and make sure one of those three is populated before the action. The was_existing flag in the output is how you check whether it is working. - A Find Account by ID or Find Contact by ID column is empty. Why: Both require an Apollo ID, and nothing earlier in the table produced one. These are follow-up actions rather than entry points. Fix: Run a search or an enrichment first and carry the ID forward. If you only have an email, Find Saved Contacts with the email as the keyword is the documented route into your own workspace. - The bill went up after bringing your own Apollo key. Why: A key removes the Data Credit cost and not the Action. Clay's documentation says an Action is still consumed, and Actions neither roll over nor can be bought as top-ups. Fix: Cut the row count rather than the data cost. Filtered views, Only run if, and a Lookup column against a table you already enriched are the three levers Clay documents for this. - Find People at Company By Job Title returns fewer people than expected. Why: That action caps the limit at 10, where Find People from Apollo goes to 1,000. They read like the same action and are not. Fix: Use Find People from Apollo as a table source for discovery, and keep the per-company action for filling in a list you already have. - A table stopped mid-run and the credits are gone. Why: Clay documents that requests already sent still consume their Data Credits when actions are stopped partway through. Fix: Stop by turning auto-run off before adding rows rather than by halting a running table. The toolbar reads Manual when it is off, which is the state to build in. **What practitioners say** (14 threads from 2024 to 2026, read 2026-10-11): This is the one pair where the vendors and the threads are arguing about the same thing, and the subject is not the integration. Apollo announced the improvements in its own subreddit in 2025 and the replies are about Clay's pricing change rather than about the actions. The recurring complaint is specific and checkable: Actions used to be free if you brought your own key, and they are not any more, which changes who the integration is cheap for. The older threads are mostly people asking what Clay is for when they already pay Apollo, which is a fair question and has a clear answer. - Apollo announced the sequence action itself, with the workflow it expects (r/UseApolloIo, November 2025, 2 points): https://www.reddit.com/r/UseApolloIo/comments/1r9ef6c/apollo_and_clay_integration_improvements_are_now/ - Bringing your own key stopped being the way to keep the cost down (r/UseApolloIo, March 2026, 4 points): https://www.reddit.com/r/UseApolloIo/comments/1rv97r6/clay_just_changed_their_pricing_heres_how_it/ - The teams it hit hardest are the ones running many steps per row (r/UseApolloIo, March 2026, 4 points): https://www.reddit.com/r/UseApolloIo/comments/1rv97r6/clay_just_changed_their_pricing_heres_how_it/ - Clay without other people's APIs is not the product (r/LeadGeneration, July 2024, 2 points): https://www.reddit.com/r/LeadGeneration/comments/1eev7vx/why_use_clay_over_apollo/ - Duplicates upstream are paid for twice, on both meters (r/CRM, April 2026, 4 points): https://www.reddit.com/r/CRM/comments/1sw7f9p/we_spent_800_month_on_clay_apollo_and_hubspot_and/ Sources: https://university.clay.com/docs/apollo-io-integration-overview | https://university.clay.com/docs/actions-data-credits | https://university.clay.com/docs/clay-credit-conservation | https://www.clay.com/integrations/data-provider/apollo-io | https://university.clay.com/lessons/importing-from-your-crm-crm-enrichment ### Clay and LinkedIn Sales Navigator An enriched audience pushed into Campaign Manager, people or whole accounts. - Built as: Native - Syncs: One way, out - Moves: Contacts, Companies - Costs to turn on: Needs a higher plan. Setup: Minutes - Requires: Clay Growth or above, a LinkedIn Ads account with billing set up, and a role on that ad account above viewer - Full guide: https://www.reversecontact.com/integrations-hub/clay-integrations/clay-linkedin-integration **Verdict.** Not the integration most people searching for it expect. Clay does not import a Sales Navigator search, and no documented Clay source does: this pair is Clay pushing an enriched audience into LinkedIn Campaign Manager, for targeting or for exclusion. Taken on those terms it is the strongest ads destination Clay has, because LinkedIn is the only one that accepts account audiences as well as people. The constraints are a 300 record floor, a 300,000 ceiling that is the tightest of any destination, a 48 hour wait before the audience is usable, and a Growth plan. **What syncs:** - A people audience (out): Email, first and last name, company, title and country. Clay hashes the email before upload, so Campaign Manager never receives the address itself. - An account audience (out): Company name, domain, website, page URL, stock symbol, city, state, country, zip and up to three industries. LinkedIn is the only Clay Ads destination that takes these. - An exclusion list (out): The same audience, used the other way round in Campaign Manager, so you stop paying to advertise to existing customers. Same mechanism, different setting at the LinkedIn end. - Refreshed membership (out): Clay keeps audiences current as the underlying data changes, so a row that stops qualifying leaves the audience without anybody rebuilding it. - Nothing at all (in): There is no inbound half. No ad engagement, no impressions, no clicks and no leads come back into Clay from this integration, which is why attribution has to be assembled somewhere else. **Which editions carry it** (rows Clay, columns LinkedIn Sales Navigator): - Free with Build an audience: Not included - Free with Push it to LinkedIn Ads: Not included - Free with Build it from CRM data: Not included - Launch with Build an audience: Included - Launch with Push it to LinkedIn Ads: Not included - Launch with Build it from CRM data: Not included - Growth with Build an audience: Included - Growth with Push it to LinkedIn Ads: Included - Growth with Build it from CRM data: Capped - Enterprise with Build an audience: Included - Enterprise with Push it to LinkedIn Ads: Included - Enterprise with Build it from CRM data: Included **How to connect it** (Somebody with a role above viewer on the LinkedIn ad account, which means admin or campaign manager, plus a Clay builder. The account you authenticate with has to have access to that specific ad account.. Twenty minutes to set up, then about 48 hours of LinkedIn processing before you can target anything.): 1. Check the Clay plan and the LinkedIn billing [Clay: pricing]. Push audiences to ad platforms reads not included on Free and not included on Launch, and unlimited ad audiences on Growth and Enterprise. On the LinkedIn side you need an active Ads account with billing set up. Both are prerequisites rather than things you can work around, and the LinkedIn one catches teams who have an ad account but have never run a campaign. 2. Decide people or accounts, because the sync is built around it [Clay: Ads]. Go to Ads, click Create ad sync and pick People or Companies. This is where the record type is set for the whole sync. Companies is only worth choosing for LinkedIn, because no other Clay ads destination accepts account audiences, so if this audience is going anywhere else as well you are building two syncs. 3. Choose the segment [Clay: Select an audience]. Pick from the People list or the Company list tab. Check the size here against the 300 minimum and the 300,000 maximum before going further, because those are the two numbers that decide whether the rest of this works. 4. Add LinkedIn Ads and authenticate [Clay: Sync destinations]. Add LinkedIn Ads under Sync destinations and authenticate when prompted, granting Clay permission to create and manage matched audiences. Then pick the destination under Select account. If the connection lapses later, the platform card shows Connection issue or Reconnection required and you reconnect from there. 5. Turn on Enhanced matching, and shorten the titles [Clay: the field mapping]. Enhanced matching adds a hashed personal email and takes the typical match rate from 60 to 70% up to 90 to 95%. While you are in the mapping, add a formula column to shorten long job titles, because some fields have character limits and a truncated title matches nothing useful. 6. Wait, and then check the right number [LinkedIn: Campaign Manager]. The audience appears under matched audiences and takes about 48 hours to process. When it lands, expect LinkedIn's count to be lower than Clay's Matched count: LinkedIn dedupes to member profiles and does not count records that resolve to nobody. That difference is normal and is not a failed sync. **How to check it worked:** - Confirm the segment clears 300 matchable records, not 300 rows. A list of 400 rows matching at 60% does not clear it, and Clay tells you the produced count when it stops. - Check the audience reached matched audiences in Campaign Manager rather than assuming the sync status is the whole story. The 48 hour processing window sits between the two. - Compare LinkedIn's member count with Clay's Matched count once, so the permanent gap between them stops being alarming. - Run one audience as an exclusion before trusting it for targeting. An exclusion list that is wrong costs you nothing, and a targeting list that is wrong spends money. Agent skill for this pair: https://www.reversecontact.com/integrations-hub/skills/clay-linkedin.md **Field mapping:** - People audience maps to LinkedIn matched audience, member. Email, first name, last name, company, title and country. Match rate 60 to 70% on work emails alone. - Enhanced matching maps to Hashed email 1. Returns up to three ranked candidate personal emails. Only the top-ranked one is sent to LinkedIn, because an upload is one row per email and three would triple the person. - Company audience maps to LinkedIn matched audience, account. Company name, domain, website, page URL, stock symbol, city, state, country, zip and up to three industries. The only Clay ads destination that takes this. - Company page URL and domain maps to The account match. Clay states these match far more reliably than company name alone, so map them when you have them rather than relying on the name. - Job title maps to The title field, possibly truncated. Some fields have character limits. Clay's own advice is a formula column to shorten long titles before mapping. - Does not cross: Any ad engagement. Impressions, clicks, form fills and leads do not come back into Clay from this integration, so attribution lives elsewhere. - Does not cross: Hashed email 2 and 3. They appear as locked chips and are shared with other destinations in the sync, but LinkedIn receives only the first. - Does not cross: The raw email address. Clay hashes before upload, which is the point: the addresses themselves are not part of what Campaign Manager receives. - Does not cross: A fourth industry. Company audiences take up to three. **What breaks:** - **300 matchable records minimum.** LinkedIn will not build an audience below 300 matchable records, and Clay checks it before uploading rather than after. A sync that comes in short stops with a message telling you how many records it produced and to widen the segment or map more identifier fields. That is the better failure, but it does mean a narrow ABM list of fifty accounts is not a LinkedIn audience. - **300,000 records maximum, and it is the tightest cap Clay has.** Anything above the cap is trimmed rather than rejected, so a larger list has to be split across separate syncs. Clay states this is the tightest limit of any of its ad destinations, with the others taking up to 1,000,000, which makes LinkedIn the one to plan the segmentation around. - **48 hours before the audience is usable.** LinkedIn takes about two days to finish processing a matched audience. Clay documents this as the answer to an audience that never leaves Building, and specifically notes it will not be the 300 record minimum, because that is checked before upload. Budget it into any campaign date you have promised somebody. - **Only one hashed email is sent.** Enhanced matching returns up to three candidate personal emails, ranked by how many providers agree. Hashed email 1, 2 and 3 all appear as locked chips and the mapping is shared across every destination in the sync, but LinkedIn receives only the top-ranked one. Clay's reason is sound: an upload carries one row per email, so sending all three would enter the same person in the audience three times. - **Long job titles truncate silently.** Some fields have character limits, and Clay's advice is to add a formula column to shorten long job titles before you map them. Nothing reports the truncation, so a title-based segment can quietly match on a cut-off string. - **The count LinkedIn shows is not the count you sent.** LinkedIn reports a deduped member count, below Clay's Matched figure, excluding records that resolve to no profile. Two systems reporting different sizes for the same audience is correct behaviour here, which makes it a poor place to look for evidence that a sync worked. **Failures people hit:** - The sync stops and says the audience is too small. Why: Fewer than 300 matchable records. LinkedIn will not build an audience below that, and Clay checks before uploading rather than after. Fix: Widen the segment or map more identifier fields, which is what the message tells you. Enhanced matching is usually the faster of the two, because it raises the match rate on the rows you already have rather than needing more rows. - The audience never leaves Building. Why: LinkedIn processing, which takes about 48 hours. Clay notes specifically that it will not be the 300 record minimum, because that fails before upload. Fix: Wait out the full window before investigating. If it is still building after that, reconnect from the platform card, which shows Connection issue or Reconnection required when the authorisation has lapsed. - The match rate is far lower than expected. Why: Work emails with no enrichment. Clay publishes 60 to 70% for work emails alone against 90 to 95% with a hashed personal email added. Fix: Turn on Enhanced matching. For company audiences, map company page URL and domain rather than relying on company name, which Clay states matches far less reliably. - LinkedIn shows a smaller audience than Clay sent. Why: Nothing is wrong. LinkedIn reports a deduped member count and does not count records that resolve to no member profile. Fix: Compare against Clay's Matched count once to learn the size of the gap, then stop using audience size as the health check. It will always read lower. - A list larger than 300,000 arrived incomplete. Why: The cap trims rather than rejects, so the sync looks successful and the audience is short. Fix: Split the segment across separate syncs. This is the tightest cap of any Clay ads destination, so a list that fits Meta or Google will not necessarily fit here. - Title-based targeting is matching the wrong people. Why: Long job titles were truncated by a field character limit, silently, so the value LinkedIn received is a cut-off string. Fix: Add a formula column to shorten titles before mapping them, which is Clay's own documented advice. Check a long title end to end rather than trusting the preview. **What practitioners say** (14 threads from March 2026 to August 2026, read 2026-10-28): Finding these took a fix to the research tooling rather than a wider search. Queries are built from the tool record's display name, which is LinkedIn Sales Navigator, so every harvest of this pair searched prospecting and returned threads about Sales Navigator with not one mention of a matched audience. Searching it as Clay plus LinkedIn Ads found the right threads immediately, and they are small: this is a feature people are still deciding about rather than one they have war stories from. - The CRM may already do this, which is the real alternative (r/SaaSMarketing, March 2026, 1 points): https://www.reddit.com/r/SaaSMarketing/comments/1rnn2r1/clay_ads/ - Two destinations, and people keep asking for a third (r/gtmengineering, March 2026, 1 points): https://www.reddit.com/r/gtmengineering/comments/1rnn2i1/clay_ads/ - Match rate is the currency, not the connection (r/gtmengineering, March 2026, 1 points): https://www.reddit.com/r/gtmengineering/comments/1rnn2i1/clay_ads/ - Somebody is already sceptical of the headline number (r/PaidSocialAdvertising, August 2026, 1 points): https://www.reddit.com/r/PaidSocialAdvertising/comments/1vg0wpp/anyone_using_clay_ads_for_linkedin_ads/ - The recurring objection to Clay, applied to ads (r/gtmengineering, March 2026, 1 points): https://www.reddit.com/r/gtmengineering/comments/1rnn2i1/clay_ads/ Sources: https://university.clay.com/docs/linkedin-ads-in-clay | https://university.clay.com/docs/sources | https://www.clay.com/pricing ### Clay and Smartlead Push, look up, update and remove, on a campaign Clay cannot create. - Built as: Native, Built on the API - Syncs: One way, out - Moves: Contacts, Lists - Costs to turn on: Metered by usage. Setup: Minutes - Requires: Clay Launch or above, a Smartlead API key, and a campaign that already exists - Full guide: https://www.reversecontact.com/integrations-hub/clay-integrations/clay-smartlead-integration **Verdict.** The most complete of the three sending-tool integrations on the Clay hub, because it closes a loop the others leave open: as well as pushing an enriched lead into a campaign, it can look the lead up, update it and remove it. That makes the table a place where disqualification happens rather than only qualification, which matters more than it sounds. The constraints are the familiar ones. The campaign has to exist in Smartlead first, authentication is an API key rather than OAuth, and no reply or bounce data comes back into the table. **What syncs:** - New leads (out): Add lead to campaign, with the campaign chosen from a dropdown populated from your Smartlead account, plus email, name, phone, website and LinkedIn URL. - Existing leads (out): Update lead details on a lead already in a campaign, across the same field set. - Lead status (in): Look up a lead to read its status and details, which is how a table checks state before acting again. - Disqualified leads (out): Remove a lead from a campaign, in the same pass as the enrichment that disqualified them. The capability the other sending pairs here lack. - Campaigns (event): Not created from Clay. Every action requires an existing Smartlead campaign. - Replies, bounces and opens (event): Not returned to the table. Smartlead's webhooks post those to an endpoint you control instead. **Which editions carry it** (rows Clay, columns Smartlead): - Free with Data providers, like Apollo: Included - Free with Sequencers: Smartlead, lemlist, Outreach: Not included - Free with CRMs: HubSpot, Salesforce: Not included - Launch with Data providers, like Apollo: Included - Launch with Sequencers: Smartlead, lemlist, Outreach: Included - Launch with CRMs: HubSpot, Salesforce: Not included - Growth with Data providers, like Apollo: Included - Growth with Sequencers: Smartlead, lemlist, Outreach: Included - Growth with CRMs: HubSpot, Salesforce: Included - Enterprise with Data providers, like Apollo: Included - Enterprise with Sequencers: Smartlead, lemlist, Outreach: Included - Enterprise with CRMs: HubSpot, Salesforce: Included **How to connect it** (Whoever owns the Clay workbook, plus somebody who can generate a Smartlead API key. No admin on either side.. Ten minutes, once the Smartlead campaign exists. Building the campaign is the longer half.): 1. Check the Clay plan first [Clay: pricing]. Clay's integration catalogue puts Smartlead at Included in Launch+, so the Free plan does not carry it. That is a gentler gate than the CRM integrations, which start on Growth, and it still means a workspace on Free cannot run this at all. 2. Build the campaign in Smartlead before you open Clay [Smartlead: Campaigns]. Clay states it plainly: all Smartlead actions require an existing campaign, and campaigns cannot be created from within Clay. Every action takes a Campaign ID from a dropdown populated by your account, so an empty Smartlead means an empty dropdown. 3. Generate the API key and paste it into Clay [Smartlead: app.smartlead.ai/app/settings/profile]. Add enrichment, search Smartlead, then + Add account and enter the key. This is an API key rather than OAuth, so it carries whatever the key carries and it is revoked in Smartlead rather than disconnected in Clay. 4. Qualify in the table before anything is pushed [Clay: run settings, Only run if]. Clay's own best practice for this integration is to enrich and score first and push only what passes. The action costs the same whether the lead was worth sending to or not, so the condition on the column is where the money is saved. 5. Decide the two duplicate switches deliberately [Clay: Add lead to campaign]. Allow Duplicate Leads Across Campaigns is off by default, so a lead already in another Smartlead campaign is not added. Allow Leads from Community Bounce List is on by default, so leads on Smartlead's shared bounce list are added unless you turn it off. 6. Run a lookup before any update or removal [Clay: Lookup lead in campaign]. Update, Update category and Remove all need Smartlead's internal Lead ID, which is not a Clay row ID. Lookup takes an email and returns the Id, so it is the column the other three read from. 7. Use the status action to close the loop you can close [Clay: Lookup lead status in campaign]. It returns the number of campaign steps, the number of emails sent so far and a status such as IN_PROGRESS. That is not reply data, and it is the only visibility into the campaign that comes back to the table. 8. Turn on Auto-update once the conditions are right [Clay: run settings]. Clay recommends it for trigger-based workflows so new rows push automatically. Turn it on after the filters are correct rather than before, because a row added by mistake is an action spent and a lead sent. **How to check it worked:** - Push one lead and confirm it appears in the Smartlead campaign. The action reports success and returns no fields, so the campaign is the only confirmation there is. - Push a lead you know is already in a different campaign with the duplicate switch off. It should not be added, and seeing that once is cheaper than wondering why a batch came up short. - Run Lookup lead in campaign on that lead and read Lead Campaign Data, which lists every campaign it is enrolled in. That is the field that tells you whether your table is competing with another campaign. - Check Is Unsubscribed on a few rows before a bulk push. It comes back on the lookup and it is the one piece of suppression data this integration can see. Agent skill for this pair: https://www.reversecontact.com/integrations-hub/skills/clay-smartlead.md **Field mapping:** - Add lead to campaign maps to Campaign ID and email, everything else optional. Takes first and last name, phone, website, LinkedIn URL, location, company name and company URL, plus arbitrary custom fields as key-value pairs. Confirms success and returns no fields. - Lookup lead in campaign maps to Email address. The entry point for everything else. Returns the Smartlead Id, the created date, custom fields, Is Unsubscribed, and Lead Campaign Data listing every campaign the lead is in. - Lookup lead status in campaign maps to Campaign ID and email. Returns number of campaign steps, number of sent emails and a status such as IN_PROGRESS. Progress rather than engagement. - Update lead in campaign maps to Campaign ID and Lead ID. Every other field optional. The Lead ID has to come from a lookup, because it is Smartlead's identifier and not a Clay row ID. - Update lead category maps to Campaign ID, Lead ID and Category ID. The category list is a dropdown populated from your Smartlead account, so categories are defined there rather than typed here. - Remove lead from campaign maps to Campaign ID and Lead ID. Returns Ok as true when the lead was removed. The only action on this integration that returns a usable boolean. - Custom fields maps to Key-value pairs on the add and update actions. The field name on the left and the value on the right. This is how a Clay-written personalisation line reaches the campaign as a merge variable. - Anything about replies maps to Not an action. Smartlead publishes webhooks for email_sent, email_reply, email_open, email_link_click, lead_unsubscribed and lead_category_updated, and consuming them is a job for a server rather than for a Clay column. - Does not cross: Campaign creation. Clay states that all Smartlead actions require an existing campaign and that campaigns cannot be created from Clay, so the campaign is always built in Smartlead first. - Does not cross: Replies, opens, clicks and bounces. The status action returns steps and sends; everything else is a Smartlead webhook rather than a column. - Does not cross: A Clay row ID used as a Lead ID. Clay calls this out as its own troubleshooting entry, because the two look interchangeable and are not. **What breaks:** - **No campaign creation, by design.** Clay states that all Smartlead actions require an existing campaign and that campaigns cannot be created from Clay. The campaign dropdown reads from your Smartlead account, so a table is always pointed at something somebody built elsewhere, and a campaign that is renamed or deleted breaks the column rather than failing loudly. - **An API key held in another product.** Authentication is a Smartlead API key from your profile settings, pasted into Clay. It is long-lived, it is revocable only in Smartlead, and rotating it breaks every table that uses it simultaneously. Keep a note of which tables hold it, which is advice nobody follows until the first rotation. - **Engagement does not come back.** Replies, bounces, opens and unsubscribes are not returned to the table. Smartlead exposes them through webhooks to an endpoint you control, scoped by user, client or campaign, so the loop closes through infrastructure you build rather than through Clay. Plan that if suppression on engagement matters. - **The expensive part is above the action.** Pushing, updating and removing are cheap. The waterfall that decided whether a lead qualified is where the credits go. Use the conditional run setting so the enrichment stops on rows that already failed a cheaper test, and test on ten rows before five hundred. **Failures people hit:** - Leads are not being added to the campaign. Why: Clay's first documented troubleshooting entry: all Smartlead actions need a campaign that exists and is active in Smartlead. Fix: Confirm the campaign before re-running. The Campaign ID dropdown is populated from your account, so a campaign that is missing there is missing in Smartlead rather than in Clay. - Some leads were skipped and they are all in other campaigns. Why: Smartlead will not add a lead that already exists in a different campaign, which is the default and is a deliverability protection rather than a fault. Fix: Turn on Allow Duplicate Leads Across Campaigns only when you intend somebody to be in two sequences. A lead can still only be added once per individual campaign either way. - Update or Remove will not run. Why: They need Smartlead's internal Lead ID, and a Clay row ID is not it. Clay documents this as its own troubleshooting entry because the two are easy to confuse. Fix: Run Lookup lead in campaign first and map its Id output into the Lead ID field. The same applies to Update lead category. - Bounced addresses are reaching the campaign. Why: Allow Leads from Community Bounce List is on by default, so leads on Smartlead's shared list are added unless you switch it off. Fix: Turn it off for a cold list. Clay recommends leaving it on for most use cases, which is a judgement about your list rather than about the setting. - The personalisation column did not reach the campaign. Why: Anything beyond the named fields has to be sent as a custom field key-value pair, and the key has to match the merge variable in the Smartlead sequence. Fix: Add it under Custom Fields on the add or update action, with the field name exactly as the campaign expects it. - A push succeeded and you cannot tell what it did. Why: Add lead to campaign and Update lead in campaign both confirm success and return no output fields, by design. Fix: Follow with Lookup lead in campaign if you need proof in the table. Remove is the one action that returns a usable value, Ok set to true. - The table pushed rows you were still working on. Why: Auto-update was on while the filters were still being built, so rows added to the table went straight out. Fix: Turn auto-update on last, and pair it with Only run if. Clay recommends auto-update for trigger-based workflows, which assumes the conditions are already right. - Nothing about replies is coming back. Why: There is no reply action. Smartlead delivers engagement over webhooks for email_sent, email_reply, email_open, email_link_click, lead_unsubscribed and lead_category_updated. Fix: Point those at a server rather than at Clay. Smartlead retries failed deliveries, marks an event failed after three attempts, and has a Retrigger Webhooks endpoint for the ones that failed. **What practitioners say** (14 threads from 2024 to 2026, read 2026-10-11): Nobody discusses this pair by name, so the search was for the job instead: building a list in one tool and sending from another. What comes back is an argument about whether the modular stack is worth its overhead, and the most useful contributions are from people who have run it and costed it. The recurring correction is that Clay is not a sequencer and was never meant to be, which is exactly why this integration exists and exactly what people keep having to explain. - The clearest statement of what Clay is not (r/Entrepreneur, June 2024, 2 points): https://www.reddit.com/r/Entrepreneur/comments/1d45ik0/im_a_clay_expert_making_cold_email_great_again_in/ - The modular stack has a staffing cost people leave out (r/microsaas, April 2026, 1 points): https://www.reddit.com/r/microsaas/comments/1sthi1r/i_replaced_apollo_clay_instantly_hubspot_with_one/ - The sending side is where the real limits live (r/revops, December 2025, 4 points): https://www.reddit.com/r/revops/comments/1pg7scy/need_help_setting_up_our_growth_engine/ - Clay's own database is a secondary source, and dated (r/Emailmarketing, May 2024, 2 points): https://www.reddit.com/r/Emailmarketing/comments/1b8cuy6/how_does_claycom_works_what_are_the_alternatives/ - The overhead complaint is specific and worth answering (r/Emailmarketing, November 2024, 10 points): https://www.reddit.com/r/Emailmarketing/comments/1b8cuy6/how_does_claycom_works_what_are_the_alternatives/ Sources: https://university.clay.com/docs/smartlead-integration-overview | https://www.clay.com/integrations/data-provider/smartlead-ai | https://www.clay.com/pricing | https://api.smartlead.ai/guides/webhook-integration ### Clay and Attio Write to objects you defined yourself, rather than to contacts and deals. - Built as: Native - Syncs: Two-way sync - Moves: Contacts, Companies, Custom objects - Costs to turn on: Needs a higher plan. Setup: Hours - Requires: Clay Growth or above, an Attio workspace, and an Attio workspace admin to authorise the connection - Full guide: https://www.reversecontact.com/integrations-hub/clay-integrations/clay-attio-integration **Verdict.** The cleanest CRM pair on the Clay hub, because Attio has no fixed object model to fight: the Object dropdown is populated from your workspace, so a custom object is as reachable as People or Companies. Clay provides two import sources and four write actions, three of which cost a credit and one of which, the lookup, is free and is the one the vendor tells you to run first. The real constraints are not features. They are who is allowed to authorise the connection, a write budget on Attio's side that a single request can spend three times over, and the fact that none of this exists below Clay Growth. **What syncs:** - Attio records (in): Import records pulls from any object, narrowed by a saved View or a JSON filter query, sorted, and capped by a Limit whose maximum is 50,000 records. - An Attio list (in): Import records from list is the second source, taking a list rather than an object, with the same filter, sort and 50,000 limit. - New records (out): Create record writes into any object and costs 1 credit per run. It does not check for an existing match, which is what makes Upsert the safer default. - Updated records (out): Update record needs the Attio Record ID, costs 1 credit, and carries a Multiselect Behavior switch that decides whether multiselect values are appended or overwritten. - Matched records (out): Upsert record matches on a unique attribute you choose from the writable unique attributes on that object, then updates or creates. 1 credit, and the action to reach for when you are not certain. - A lookup (out): Lookup records is free and returns up to 10 matching records. It is a read performed from Clay, so it counts as a call out even though nothing changes in Attio. **Which editions carry it** (rows Clay, columns Attio): - Free with Import Attio records: Not included - Free with Write back to an object: Not included - Free with Import beyond 250,000: Not included - Launch with Import Attio records: Not included - Launch with Write back to an object: Not included - Launch with Import beyond 250,000: Not included - Growth with Import Attio records: Included - Growth with Write back to an object: Included - Growth with Import beyond 250,000: Not included - Enterprise with Import Attio records: Included - Enterprise with Write back to an object: Included - Enterprise with Import beyond 250,000: Included **How to connect it** (A Clay builder, plus an Attio workspace admin. The admin is not optional: Clay documents that only workspace admins can authorise the connection.. An hour, most of it deciding the matching attribute rather than connecting anything.): 1. Confirm the Clay plan [Clay: pricing]. CRM integrations read not included on Free and not included on Launch in Clay's plan comparison, and included from Growth. Attio counts as a CRM here. Check this first, because both the import sources and the write actions are behind the same gate and there is no half-build to start on a cheaper plan. 2. Get an Attio admin to authorise the connection [Clay: a workbook]. In a workbook click Add, search for Attio, and you will be asked to Select Attio account. Adding an account runs an OAuth flow that only an Attio workspace admin can complete. Line this up before you start: it is the step most likely to stall a build for a day. 3. Choose the source, and choose View or Filter but not both [Clay: Import records]. Import records takes an Object, with an optional saved View, an optional JSON Filter, a Sort and a Limit of up to 50,000. A View takes precedence and the Filter is then ignored, so pick one deliberately. If you set neither, every record in the object is returned up to the limit. 4. Decide the matching attribute before any write [Attio: the object's attributes]. Upsert record matches on a unique attribute chosen from the writable unique attributes on that object, typically an email address or a domain. This is the single decision that determines whether this integration creates duplicates for the next year, so make it explicitly rather than accepting the first option in the dropdown. 5. Look up before you create [Clay: Lookup records]. The vendor's own best-practice note says to run the free Lookup records action first to check for duplicates before creating new records. It returns up to 10 matches. Build the table so the write action only runs when the lookup came back empty. 6. Add a conditional run, then turn on auto-update [Clay: run settings]. Only run if gates the enrichment on conditions you set, and Auto-update syncs new rows back to Attio as they arrive. Add the condition before the auto-update, or the first unattended run writes every row including the ones the enrichment failed on. **How to check it worked:** - Run Lookup records on a person you know exists and confirm it returns them. It is free, so this is the cheapest possible proof that the connection and the object selection are both right. - Upsert the same record twice and confirm Attio still holds one. If you get two, the matching attribute is not unique in the way you assumed, and every write after this point will have the same problem. - Update a multiselect attribute and check whether the existing values survived. Multiselect Behavior decides between appending and overwriting, and the wrong setting removes data silently rather than failing. - Import with a Filter while a View is selected, and confirm you get the View's rows rather than the Filter's. Seeing the precedence once is the only reliable way to remember it. Agent skill for this pair: https://www.reversecontact.com/integrations-hub/skills/clay-attio.md **Field mapping:** - Import records maps to Rows in a Clay table. Takes an Object, an optional View, an optional JSON Filter ignored when a View is set, a Sort and a Limit of up to 50,000. - Import records from list maps to Rows in a Clay table. Takes an Attio list rather than an object, with the same filter, sort and 50,000 limit. - Create record maps to A new record in an Attio object. Object plus Object Schema attributes. 1 credit per run. Performs no match, so it will happily create a second copy. - Lookup records maps to Up to 10 matching records. Free. Takes a Record ID or Object Schema filters, and optional JSON path filters to trim the response. Required before a create if you care about duplicates. - Update record maps to An existing record, by Record ID. 1 credit. Requires the Attio Record ID, so it follows a lookup or an import. Multiselect Behavior appends or overwrites multiselect values. - Upsert record maps to A matched or new record. 1 credit. Matches on a writable unique attribute such as email or domain, then updates or creates. The safe default when you are unsure. - Does not cross: Anything Attio does not expose as a writable attribute. The Object Schema is populated from your workspace, so if it is not an attribute there it is not a field here. - Does not cross: Deletion. None of the four actions removes a record, so a row that should no longer exist in Attio has to be handled in Attio. - Does not cross: More than ten lookup results. The lookup is a check rather than a query, and reconciling a large set means importing it and comparing in the table. **What breaks:** - **Only an Attio workspace admin can connect it.** Clay's documentation states plainly that only Attio workspace admins can authorise the OAuth connection. That makes the first step of this integration an access request rather than a configuration task, and it is the most common reason a Clay builder cannot finish the setup on their own. Find out who the admins are before you book time to build. - **A lookup returns ten records and no more.** The Lookup records action returns up to 10 matching records. That is enough to check whether a person exists and not enough to reconcile a list, so a deduplication pass over thousands of rows is not a lookup, it is an import followed by a comparison in the table. - **Attio allows 25 writes a second, and one request can cost three.** The published ceiling is 100 requests a second for reads and 25 a second for writes. The part that surprises people is that a single write can count as several: writing a record reference with target_record_reference set to create means every referenced record Attio creates counts as another write, so creating a person with two new companies attached spends 3 of the 25. Identical references in one request are merged and counted once. - **An import stops at 50,000 records.** Both sources take an optional Limit and Clay documents the maximum as 50,000 records. Above that the import is not a single source, it is several, narrowed by view or by filter, which is a modelling decision rather than a setting you can raise. - **A View silently beats a Filter.** If a source has both a saved View and a JSON Filter, Clay documents that the View takes precedence and the Filter is ignored. Nothing reports this. A table that returns the wrong rows after somebody adds a view is the shape of the bug, and the only tell is that your filter appears to do nothing. - **Attio can lower the limit without you changing anything.** Attio states it may occasionally reduce the rate limit as part of incident response, and may permanently lower it for specific APIs that handle a lot of data, documented on the endpoint. So a backfill that worked last quarter is not a guarantee, and anything bulk should read the 429 and its Retry-After header rather than assume a fixed budget. **Failures people hit:** - The OAuth flow will not complete and Attio is never connected. Why: The person connecting is not an Attio workspace admin. Clay documents that only workspace admins can authorise this connection. Fix: Have an Attio workspace admin run the Add account step. There is no delegated permission for this in Clay, so it has to be them in the browser rather than a scope you can be granted. - The filter on an import is doing nothing. Why: A saved View is selected on the same source. Clay documents that the View takes precedence and the Filter is ignored when both are present. Fix: Remove the View if you want the Filter to apply, or move the logic into the View. Nothing warns you about this, so check it first whenever an import returns the wrong rows. - The import returned the entire object. Why: Neither a View nor a Filter was set. Clay documents that all records are returned when neither is provided. Fix: Set one of them, and set the Limit as well. The Limit maximum is 50,000, which is also the point at which an import becomes a modelling problem rather than a configuration one. - Attio is filling up with duplicates. Why: Create record is being used where Upsert record is wanted. Create performs no match and will write a second copy of a record that already exists. Fix: Switch to Upsert record and choose the matching attribute deliberately, or run the free Lookup records first and make the create conditional on it returning nothing. Neither fixes duplicates already there. - Multiselect values disappeared after an update. Why: Multiselect Behavior was set to overwrite rather than append, so the incoming values replaced the existing ones. Fix: Set it to append on any attribute where Attio is the system of record for values Clay does not know about. This fails silently, so check one record after changing the setting rather than waiting for somebody to notice. - 429 Too Many Requests from Attio during a bulk write. Why: The write budget is 25 requests a second, and a request that creates referenced records spends more than one: a person with two new companies attached counts as 3. Fix: Read the Retry-After header rather than retrying immediately, and reduce the fan-out by creating referenced records first so later writes only reference existing ones. Identical references within one request are merged and counted once. - A backfill that worked before now hits limits. Why: Attio states it may reduce the rate limit during incident response, and may permanently lower it for specific APIs that handle a lot of data. Fix: Treat the ceiling as variable rather than fixed. Anything bulk should back off on a 429 and read the endpoint documentation for a lower published limit, rather than assuming last quarter's throughput. **What practitioners say** (14 threads from October 2024 to May 2026, read 2026-10-28): Nobody discusses this pair by name, so the search was the job rather than the pairing: getting enriched records into a CRM and keeping them clean. That turns out to be the right question, because almost every complaint in these threads is about duplicates and data quality rather than about either product. One caution on the cache behind this section: the highest-scoring Attio thread is an AMA by the company's co-founder, so most of its replies are the vendor rather than practitioners, and none of them are quoted here. - What people expect to buy is the CRM round trip (r/sales, October 2024, 51 points): https://www.reddit.com/r/sales/comments/1g1guqj/what_is_the_deal_with_clay/ - Duplicates are the failure, and they arrive from everywhere (r/CRM, April 2026, 4 points): https://www.reddit.com/r/CRM/comments/1sw7f9p/we_spent_800_month_on_clay_apollo_and_hubspot_and/ - Enrichment multiplies whatever the data already is (r/CRM, May 2026, 2 points): https://www.reddit.com/r/CRM/comments/1sw7f9p/we_spent_800_month_on_clay_apollo_and_hubspot_and/ - Attio is chosen for flexibility rather than depth (r/gtmengineering, February 2026, 3 points): https://www.reddit.com/r/gtmengineering/comments/1qu621n/crm_recommendations_for_cold_outreach_pipeline/ - The honest check before building any of this (r/sales, October 2024, 3 points): https://www.reddit.com/r/sales/comments/1g1guqj/what_is_the_deal_with_clay/ Sources: https://university.clay.com/docs/attio-integration | https://docs.attio.com/rest-api/guides/rate-limiting | https://docs.attio.com/docs/objects-and-lists | https://www.clay.com/pricing ### Clay and n8n Webhook out of the table, into a workflow that can wait for an async job. - Built as: Built on the API, Zapier, Make or n8n - Syncs: Two-way sync - Moves: Contacts, Companies - Costs to turn on: Needs a higher plan. Setup: Hours - Requires: An n8n instance, and Clay Growth or above, because both halves of this pair are Growth features - Full guide: https://www.reversecontact.com/integrations-hub/clay-integrations/clay-n8n-integration **Verdict.** The pair you build when a step takes longer than Clay will wait. Clay has no n8n node and n8n has no Clay node, so both directions are plain HTTP: Clay calls out through an HTTP API integration, and n8n posts results back into a webhook source that becomes a table. What you are buying is n8n's Wait node, which parks an execution in the database and resumes it on an interval or on a callback URL, and that is the one thing a Clay column cannot do. The cost is that you are now paying for orchestration twice and running a server, which is the trade practitioners describe rather than regret. **What syncs:** - Enriched rows (out): An HTTP API integration on the table calls your n8n webhook with whatever columns you map into the body. A Growth feature, and the same gate as every other HTTP call out of Clay. - A job to wait on (out): Anything asynchronous: a live enrichment, a scrape, a model call. Clay sends the request and stops caring, which is the point of handing it to n8n rather than to a column. - Finished results (in): n8n posts JSON to a Clay webhook source. The keys of the body become the columns, so the shape of the table is decided by what n8n sends rather than configured in Clay. - A resume callback (in): The Wait node generates $execution.resumeUrl at runtime, unique to that execution, and n8n documents handing it to a third party. Whatever finishes the slow job calls it, and the workflow carries on from there. - Nothing on a schedule (out): There is no polling of Clay from n8n, because Clay has no node and no documented read API on these plans. If n8n needs to know a table changed, Clay has to tell it. **Which editions carry it** (rows Clay, columns n8n): - Free with Receive rows by webhook: Not included - Free with Call n8n over HTTP: Not included - Free with Pass 50,000 submissions: Not included - Launch with Receive rows by webhook: Not included - Launch with Call n8n over HTTP: Not included - Launch with Pass 50,000 submissions: Not included - Growth with Receive rows by webhook: Included - Growth with Call n8n over HTTP: Included - Growth with Pass 50,000 submissions: Not included - Enterprise with Receive rows by webhook: Included - Enterprise with Call n8n over HTTP: Included - Enterprise with Pass 50,000 submissions: Included **How to connect it** (Whoever owns the Clay workbook, plus whoever owns the n8n instance. No admin on either side, but somebody has to be willing to run a server.. An hour or two for the first one, most of it deciding the JSON shape rather than clicking.): 1. Check the Clay plan before anything else [Clay: pricing]. Webhook automation and HTTP API integrations are both listed as Growth features, and the plan comparison shows webhooks as not included on Free and not included on Launch. If you are below Growth, stop here: there is no partial version of this pair and no volume at which it becomes available. 2. Create the webhook source in Clay [Clay: a workbook]. In a workbook, click Add at the bottom, search for Webhooks and choose Monitor webhook. Clay gives you a URL and an equivalent cURL command. The URL is the one you paste into n8n; the cURL is there so you can send a row by hand before any workflow exists, which is the fastest way to see what the table does with your JSON. 3. Add the auth token and write it down [Clay: the webhook source]. Optionally secure the webhook with a token sent in the request header. Copy it immediately: Clay states that tokens are only accessible once, so this is the one step in the sequence that cannot be undone by looking it up again later. 4. Post to it from n8n with the HTTP Request node [n8n: HTTP Request node]. There is no Clay node, so this is a plain POST with a JSON body and the token as a header. Send one row first and look at the table: the keys of the body become the columns, so this request is where you are deciding the schema whether you mean to or not. 5. Add the Wait node where the slow step is [n8n: Wait node]. Choose the resume condition: after a time interval, at a specified time, or on a webhook call. For a job that reports back, use On Webhook Call and pass $execution.resumeUrl to whatever is doing the work. Turn on Limit Wait Time so an execution cannot sit waiting forever for a callback that is never coming. 6. Call back out of Clay, if the pair is two-way [Clay: HTTP API integration]. To start the chain from Clay rather than from n8n, add an HTTP API integration to the table and point it at an n8n webhook trigger. This is the Growth feature from step one, and it is the half that lets a Clay row ask for work rather than only receive it. **How to check it worked:** - Send one row into Clay before building anything on top. A new row should appear with a column per key in your JSON body. If it arrives as a single column holding the whole payload, the body was sent as a string rather than as JSON, and that is the fix rather than anything in the table. - Call out of Clay once and read the n8n execution list. The run should carry the columns you mapped into the request body, which is the only place in this pair where Clay decides the shape rather than n8n. - Test the Wait node with a deliberately slow job rather than a fast one. A workflow that resumes correctly in two seconds tells you nothing about one that has to resume in twenty minutes, and the resume URL is unique per execution. - Check the submission count on the webhook source while it is still new, so you know where the 50,000 ceiling sits relative to your volume. The number only goes up and deleting rows does not move it, so this is a capacity decision rather than a maintenance one. Agent skill for this pair: https://www.reversecontact.com/integrations-hub/skills/clay-n8n.md **Field mapping:** - JSON body keys, out of n8n maps to Columns in the Clay table. Clay creates the table from the payload, so the keys are the schema. Send a key once and the column exists; change the key later and you have two columns. - Auth token maps to A request header on the webhook. Optional, and shown only once when the source is created. Clay documents no way to read it back. - Mapped columns, out of Clay maps to The HTTP API integration body. A Growth feature. You choose which columns go into the request, which is the only place in this pair where Clay decides the shape rather than n8n. - $execution.resumeUrl maps to Whatever is doing the slow work. Generated at runtime and unique to one execution. n8n documents sending it to a third-party service, which is how a job that finishes in twenty minutes restarts the workflow. - Does not cross: Clay rows, read from outside. There is no Clay node in n8n and no documented read API on these plans, so n8n cannot ask what a table contains. The table has to push. - Does not cross: The webhook submission counter. It only goes up, it survives deleting rows, and nothing in the product exposes a reset. - Does not cross: Anything schema-like. Neither side validates the payload, so a missing key is a blank cell rather than an error, in both directions. **What breaks:** - **A webhook source stops at 50,000 submissions, for good.** Clay documents the cap per webhook source and states that it persists even after deleting rows, so a table you have emptied is still full as far as the counter is concerned. On Enterprise you can turn on Auto-delete, also called passthrough tables, and one webhook then takes unlimited submissions. On every other plan the documented remedy is to create a new webhook once you hit the number, which means the URL in your n8n workflow changes. - **Neither tool has a node for the other.** n8n publishes no Clay node: there is no entry in its documentation sitemap and n8n.io/integrations/clay returns a 404. Clay has no n8n integration in its catalogue either. Both directions are therefore the generic HTTP Request node and a generic webhook, which is why this pair is hours rather than minutes and why nothing about it upgrades itself when either vendor ships something. - **Both halves are Growth features.** Clay's plan comparison marks "Automate any signal via webhooks" as not included on Free and not included on Launch, and lists HTTP API integrations among the things Growth adds. So the inbound half and the outbound half are gated by the same plan, and a team on Launch at $185 a month cannot run either direction at any volume. - **The auth token is shown once.** A webhook source can be secured with a token sent in the request header, and Clay's guide says to copy it immediately because tokens are only accessible once. There is no documented way to read it back, so losing it means a new token and an edit to the n8n credential. - **Waiting is cheap, but it is yours to bound.** The Wait node offloads execution data to the database while paused, so a long wait costs storage rather than a held connection. It resumes after a time interval, at a specified time, or on a webhook call, and Limit Wait Time is what stops an execution waiting forever for a callback that never arrives. Nobody sets that until the first job hangs. **Failures people hit:** - The webhook accepted rows for months and has quietly stopped. Why: The source has reached 50,000 submissions. Clay documents the cap per webhook source and states it persists even after deleting rows, so an empty-looking table can still be at the limit. Fix: On Enterprise, enable Auto-delete on the source so Clay processes and deletes rows and the webhook takes unlimited submissions. On every other plan, create a new webhook source and change the URL in the n8n workflow. There is no reset. - There is no Clay node to add in n8n. Why: n8n does not publish one. Its documentation sitemap has no Clay entry and n8n.io/integrations/clay returns a 404, whatever a forum answer says. Fix: Use the HTTP Request node for anything going to Clay and a webhook trigger for anything coming from it. If you want the work to look like a node, build it once as a sub-workflow and call that. - Clay has no option to call an external URL. Why: HTTP API integrations are a Growth feature. On Free and Launch the capability is absent rather than limited. Fix: Upgrade to Growth, or invert the direction so that n8n starts the chain on a schedule and posts into a Clay webhook source, which needs the same plan. If neither is possible the pair cannot be built. - The row arrives in Clay as a single column holding everything. Why: The body reached Clay as a string rather than as JSON, so there was one value to make a column from. Fix: Send the body as JSON from the HTTP Request node and set the content type accordingly. Clay builds columns from the keys of a JSON object, so the fix is in the request rather than in the table. - The webhook returns an authentication error after working yesterday. Why: The token on the source was rotated or the header was dropped. Clay shows a webhook token once and documents no way to read it again. Fix: Generate a new token on the source, paste it into the n8n credential, and store it where the rest of your secrets live. Nothing can recover the old one. - An execution has been waiting for days. Why: A Wait node set to resume On Webhook Call, with no Limit Wait Time, and a callback that never came. The execution is parked in the database rather than failed. Fix: Turn on Limit Wait Time with an interval or a maximum date so the workflow resumes and can take the failure branch. Then make the slow job report failure as well as success, because an absent callback and a failed job look identical from n8n. **What practitioners say** (14 threads from June 2025 to April 2026, read 2026-10-28): This is one of the few Reverse Contact adjacent pairs that practitioners do discuss by name, because Clay's Actions pricing made moving steps into n8n a live question in 2026. The useful threads are not the ones arguing about whether Clay is overpriced. They are the ones where somebody has already done it and is describing what it cost them. - The savings are real and so is the maintenance (r/gtmengineering, April 2026, 4 points): https://www.reddit.com/r/gtmengineering/comments/1six5pp/is_clay_still_worth_it_after_the_new_pricing/ - The hybrid is what survives, not the rip-out (r/gtmengineering, April 2026, 3 points): https://www.reddit.com/r/gtmengineering/comments/1six5pp/is_clay_still_worth_it_after_the_new_pricing/ - The obvious question, asked by somebody reading a build (r/n8n, June 2025, 1 points): https://www.reddit.com/r/n8n/comments/1kz1gjr/how_i_use_n8n_clay_to_autoqualify_route_inbound/ - A native node people believe in, which does not exist (r/n8n, August 2025, 1 points): https://www.reddit.com/r/n8n/comments/1mv6rr2/trying_to_build_a_workflow_that_webhooks_into_a/ - What the missing read path actually looks like in practice (r/n8n, November 2025, 1 points): https://www.reddit.com/r/n8n/comments/1m4pknc/n8n_with_claycom/ Sources: https://university.clay.com/docs/webhook-integration-guide | https://docs.n8n.io/integrations/builtin/core-nodes/n8n-nodes-base.httprequest | https://docs.n8n.io/integrations/builtin/core-nodes/n8n-nodes-base.wait | https://www.clay.com/pricing ### Clay and Outreach Four actions, and the one that matters adds an enriched row to a sequence. - Built as: Native, Built on the API - Syncs: One way, out - Moves: Contacts, Lists - Costs to turn on: Metered by usage. Setup: Minutes - Requires: Clay Launch or above, an Outreach contract, and twelve read-write scopes you cannot refuse - Full guide: https://www.reversecontact.com/integrations-hub/clay-integrations/clay-outreach-integration **Verdict.** A deliberately small integration that closes the most useful loop in outbound: a Clay table builds and enriches the row, scores it, writes the personalisation, and then pushes it straight into an Outreach sequence without a CSV ever existing. Four actions cover it, create, update, look up and add to sequence, and all four are added as enrichment columns rather than configured in a settings screen. What it is not is a sync. Nothing comes back from Outreach, so reply and meeting data lives there and the table is a one-way feed. **What syncs:** - New prospects (out): Create prospect, taking email plus optional name, company, title, address, contact preferences, social links and campaign fields. - Existing prospects (out): Update prospect, keyed on id or email, across the same field set. - Sequence enrolment (out): Add to sequence, which is the action most tables are built to reach. Mailbox ids are looked up with their own action. - Prospect lookups (in): Look up prospect by email or id, optionally including the sequences they are already in, which is how a table avoids re-enrolling somebody. - Personalised copy (out): Email templates on the table send with custom field inputs, so the column that wrote the line is the thing that delivers it. - Replies, opens and meetings (event): Nothing comes back. Outreach is where performance lives and the table never learns what happened. **Which editions carry it** (rows Clay, columns Outreach): - Free with Data providers, like Apollo: Included - Free with Sequencers: Outreach, Smartlead, lemlist: Not included - Free with CRMs: HubSpot, Salesforce: Not included - Launch with Data providers, like Apollo: Included - Launch with Sequencers: Outreach, Smartlead, lemlist: Included - Launch with CRMs: HubSpot, Salesforce: Not included - Growth with Data providers, like Apollo: Included - Growth with Sequencers: Outreach, Smartlead, lemlist: Included - Growth with CRMs: HubSpot, Salesforce: Included - Enterprise with Data providers, like Apollo: Included - Enterprise with Sequencers: Outreach, Smartlead, lemlist: Included - Enterprise with CRMs: HubSpot, Salesforce: Included **How to connect it** (Whoever owns the Clay workbook, and somebody willing to grant Outreach scopes across the whole org. In a governed Outreach instance that is a conversation, not a click.. Ten minutes. The scope review is the part that should take longer.): 1. Read the twelve required scopes before you authenticate [Clay: the consent screen]. Clay lists them as permissions that cannot be disabled and are always requested: users, stages, sequenceSteps, sequenceStates, sequences, roles, recipients, prospects, opportunityStages, opportunities, mailboxes and events. Every one is the .all variant, meaning read and write. 2. Check the Clay plan band [Clay: pricing]. Clay's catalogue puts Outreach at Included in Launch+, so the Free plan does not reach it. Every action is also marked Bring Your Own Account Required, which here means your own Outreach contract rather than anything Clay resells. 3. Connect the Outreach account from the enrichment panel [Clay: Add enrichment, Outreach]. Search Outreach, pick one of the actions under Integrations, then Select Outreach account or + Add account to authenticate. The connection is made where the column is built rather than in a workspace settings screen. 4. Make sure the target sequence is active [Outreach: Sequences]. Clay notes it on the action itself: sequences must be Active in Outreach for a lead to be added successfully. A paused sequence takes the call and does not enrol anybody. 5. Fetch the mailbox ID once and hold it in a column [Clay: Lookup mailbox by email address]. Add to sequence requires a Mailbox ID alongside the prospect and sequence, and that action exists purely to turn a sending address into one. Resolve it once rather than per row. 6. Look up before you create [Clay: Lookup prospect]. It takes an email or a prospect ID, both optional, and has an Include Sequences switch that tells you what the person is already enrolled in. That switch is the one thing standing between your table and double-enrolling somebody. 7. Create or update, then enrol as a separate column [Clay: Create prospect, Update prospect]. Create takes an email plus optional basics, address, contact preferences, social links, extra phone numbers, campaign and source fields, and personal details. Update takes the same plus an ID. Neither enrols anybody; Add to sequence is its own action. 8. Put the condition on the enrolment column, not the enrichment [Clay: run settings, Only run if]. The expensive columns are upstream and the irreversible one is downstream. Gating the enrolment on the score keeps the research you paid for and stops the email you would regret. **How to check it worked:** - Enrol one prospect into an active sequence and confirm it in Outreach. Then pause the sequence and try again: the failure is the one most teams meet in production. - Run Lookup prospect with Include Sequences on somebody you know is already being worked. If the table cannot see that, it will enrol them a second time. - Check the mailbox ID resolves to the address you expect. Add to sequence sends from whatever mailbox that ID names, and a wrong one is a rep sending from a colleague's address. - Have an Outreach admin review the granted scopes after connecting. All twelve are read and write, and opportunities and roles are on the list. Agent skill for this pair: https://www.reversecontact.com/integrations-hub/skills/clay-outreach.md **Field mapping:** - Lookup prospect maps to Email or prospect ID, both optional. Include Sequences is the input worth setting: it returns what the person is already enrolled in, which is the only duplicate protection on this pair. - Create prospect maps to Email, everything else optional. Optional groups cover basics, address, contact preferences, social and websites, additional phone numbers, campaign and source fields like tags and event name, and personal details. - Update prospect maps to ID and email. The same optional groups as Create. The ID is required, so this action lives downstream of a lookup. - Add to sequence maps to Prospect ID, Sequence ID and Mailbox ID. All three required, and the sequence must be Active in Outreach. This is the action the integration exists for and the one with the most prerequisites. - Lookup mailbox by email address maps to An email address. Exists only to supply the third required input above. Its presence in a five-action integration tells you how often that input is the blocker. - Email templates maps to Columns on the table, sent with Create prospect. Clay documents adding templates to the table and sending them with custom field inputs, which is how the personalisation written in Clay reaches the first touch. - Replies, opens, meetings maps to Nothing comes back. There is no read action for engagement. Outreach holds performance and the table holds the list, and joining them is a job for the CRM both write to. - Sequence creation maps to Not an action. Like every sequencer pair on the Clay hub, the campaign is built in the sending tool first and Clay only populates it. - Does not cross: Any way to refuse a scope. Clay describes these as permissions that cannot be disabled and are always requested, which is unusual: its HubSpot integration makes most scopes optional and ships three of them switched off. - Does not cross: A sequence that is paused. Clay states sequences must be Active for a lead to be added successfully. - Does not cross: Anything coming back from Outreach. The integration is a feed in one direction, so reply handling and meeting booking stay where they happen. **What breaks:** - **It is a feed, not a sync.** Clay writes to Outreach and reads only what you explicitly look up. No reply, open, bounce or meeting data returns to the table, so a Clay table cannot suppress on engagement unless you build the lookup yourself. Any reporting that spans list quality and sequence performance has to happen somewhere both tools write, which usually means the CRM. - **Check before you enrol, or you will double-enrol.** The lookup action can include the sequences a prospect is already in, and it exists because the create and add-to-sequence actions will happily act again on somebody already being sequenced. A table that pushes without that check produces the duplicate-outreach problem the integration is supposed to prevent. - **Credits are spent above the action, not on it.** Pushing to Outreach is cheap; filling the row is not. A waterfall that tries several providers for an email and a phone number is where a Clay bill comes from, so test on ten rows before running five hundred and decide what a row is worth before you decide what a sequence is worth. - **Authentication is per table, not per workspace.** The Outreach account is selected inside the enrichment modal, so different tables can point at different Outreach accounts and nothing warns you that they do. In a team running several tables that is a real source of prospects landing in the wrong place, and it is worth a naming convention rather than a discovery in week three. **Failures people hit:** - The lead was not added to the sequence. Why: The sequence is not Active in Outreach. Clay states this requirement on the Add to sequence action itself. Fix: Activate the sequence, then re-run the column. A paused sequence is the most common cause and it produces no obvious error on the Clay side. - Add to sequence will not run at all. Why: It needs three inputs and most tables only have two. Prospect ID, Sequence ID and Mailbox ID are all required. Fix: Run Lookup mailbox by email address once to resolve the mailbox, and carry the prospect ID forward from Create or Lookup prospect. - The same person was enrolled twice. Why: Nothing in the push checks existing enrolment unless you ask. Lookup prospect has an Include Sequences switch and it is not on by default. Fix: Add a lookup column with Include Sequences on, and gate the enrolment column on what it returns. There is no de-duplication setting to turn on instead. - Update prospect is failing on rows that have an email. Why: Update requires the ID as well as the email. An email alone is enough for Create and not for Update. Fix: Look the prospect up first and map its ID into the Update column. This is the same lookup-before-write shape every Clay sequencer pair needs. - Emails went out from the wrong address. Why: Add to sequence sends from whatever mailbox the Mailbox ID names, and a single hard-coded ID applies to every row. Fix: Resolve the mailbox per owner rather than once for the table if reps send from their own addresses. The lookup action takes an email, so the owner column can drive it. - An Outreach admin is asking why Clay can see opportunities. Why: Because it can. opportunities.all and opportunityStages.all are in the required scope list, alongside users.all and roles.all, and Clay documents all twelve as not disableable. Fix: There is no configuration answer. Either the grant is acceptable or the integration is not, and that is a decision to take before connecting rather than after. - Nothing is coming back from Outreach. Why: By design. The five actions write and look up; there is no engagement read. Fix: Read performance in Outreach, and join it to the list in whichever CRM both tools already write to. - Credits went on rows that were never enrolled. Why: The enrichment columns upstream run before the enrolment column decides anything, and each one spends an Action per record. Fix: Move the qualifying condition as far up the table as it will go. Clay bills per record enriched regardless of what happens downstream. **What practitioners say** (14 threads from 2023 to 2026, read 2026-10-11): The pair by name returns nothing, so this is a search for the job: using a table to build and enrich a list that something else sends. The threads are an argument about whether Clay earns its price, and the useful part is that both sides agree on the division of labour. Clay is not a sequencer, people say so repeatedly and sometimes irritably, and the integration on this page is the seam that creates. One comment from 2025 says Clay was starting to roll out sequencing of its own, which has since shipped as the Clay Sequencer and does not change what this pair is for. - The correction people keep having to make (r/sales, June 2024, 3 points): https://www.reddit.com/r/sales/comments/1dgmeil/what_is_the_point_of_clay_over_say_apollo_or_lusha/ - Clay was not a sequencer, and now partly is (r/gtmengineering, September 2025, 2 points): https://www.reddit.com/r/gtmengineering/comments/1npnp3u/claycom_alternative/ - The price objection, stated at its strongest (r/Emailmarketing, November 2024, 10 points): https://www.reddit.com/r/Emailmarketing/comments/1b8cuy6/how_does_claycom_works_what_are_the_alternatives/ - What the sequencing side is actually constrained by (r/revops, December 2025, 4 points): https://www.reddit.com/r/revops/comments/1pg7scy/need_help_setting_up_our_growth_engine/ - The spaghetti complaint, which this integration is a response to (r/sales, October 2024, 23 points): https://www.reddit.com/r/sales/comments/1g1guqj/what_is_the_deal_with_clay/ Sources: https://university.clay.com/docs/outreach-integration-overview | https://www.clay.com/integrations/data-provider/outreach | https://www.clay.com/pricing | https://support.outreach.io/support/solutions/articles/159000426014 ### Clay and lemlist Three actions, an API key, and a campaign that has to exist first. - Built as: Native, Built on the API - Syncs: One way, out - Moves: Contacts, Lists - Costs to turn on: Metered by usage. Setup: Minutes - Requires: Clay Launch or above, a lemlist API key, and a campaign that already exists - Full guide: https://www.reversecontact.com/integrations-hub/clay-integrations/clay-lemlist-integration **Verdict.** A small, well-scoped integration that does the one thing a CSV cannot: it carries the thinking with the lead. Three actions, add, update and look up, each keyed on a campaign that already exists in lemlist, with the personalisation written in a Clay column delivered as part of the push. The conditional run setting is the part worth using properly, because it turns the table into the thing that decides who is worth a campaign slot rather than a list that fills one. What it is not is a sync: nothing comes back, so engagement lives in lemlist. **What syncs:** - New leads (out): Add lead to campaign, taking a campaign id plus email, LinkedIn URL, name, phone number and the rest of your mapped fields. - Existing leads (out): Update lead in campaign, keyed on the email address or the lead id, across the same field set. - Duplicate checks (in): Look up lead in campaign by email, which is how a table avoids adding somebody who is already being sequenced. - Personalised copy (out): Per-lead data including the email copy written in a Clay column, so the personalisation is part of the lead rather than a later edit. - Campaigns themselves (event): Not created from Clay. The campaign, its steps, its schedule and its sending identities are all set up in lemlist first. - Replies, opens and bookings (event): Nothing returns to the table. lemlist is where performance lives, and its [HubSpot integration](pair:hubspot+lemlist) is how that reaches a CRM. **Which editions carry it** (rows Clay, columns lemlist): - Free with Data providers, like Apollo: Included - Free with Sequencers: lemlist, Smartlead, Outreach: Not included - Free with CRMs: HubSpot, Salesforce: Not included - Launch with Data providers, like Apollo: Included - Launch with Sequencers: lemlist, Smartlead, Outreach: Included - Launch with CRMs: HubSpot, Salesforce: Not included - Growth with Data providers, like Apollo: Included - Growth with Sequencers: lemlist, Smartlead, Outreach: Included - Growth with CRMs: HubSpot, Salesforce: Included - Enterprise with Data providers, like Apollo: Included - Enterprise with Sequencers: lemlist, Smartlead, Outreach: Included - Enterprise with CRMs: HubSpot, Salesforce: Included **How to connect it** (Whoever owns the Clay workbook, plus somebody who can generate a lemlist API key. The key is shown once and never again.. Ten minutes, assuming the lemlist campaign already exists.): 1. Check the Clay plan band [Clay: pricing]. Clay's catalogue puts lemlist at Included in Launch+, so a Free workspace cannot run it. Every action is also marked Bring Your Own Account Required, which here means your own lemlist subscription. 2. Create the campaign in lemlist first [lemlist: Campaigns]. Clay states the requirement directly: you must already have a campaign set up in lemlist to use this integration. All three actions take a Campaign ID, and there is no create-campaign action. 3. Generate the API key and store it immediately [lemlist: Settings, Integrations]. Profile picture, Settings, the Integrations tab, Generate a new API key. lemlist warns that you will not be able to see it again, so it goes into Clay or a password manager in the same minute it is created. 4. Connect the account from the enrichment panel [Clay: Add enrichment, lemlist]. Search lemlist, pick an action under Integrations, then + Add account and paste the key. Note what this key is: lemlist authenticates with HTTP Basic using an empty username and the key as the password, so it is a password in the literal sense. 5. Look up before you add [Clay: Lookup Lead in Campaign]. It checks whether a lead exists in a campaign by email or lead ID. The add action creates and never updates, so without this column the table has no way to tell a new lead from one it is about to be refused for. 6. Decide what the company fields are allowed to touch [Clay: the mapped columns]. Company name, company domain, company industry and any company-prefixed key reach the shared company record the lead is matched to, not that lead alone. Every other lead linked to the same company reads what you wrote. 7. Name custom variables the way lemlist will keep them [Clay: additional fields]. Any extra key-value pair you send is stored as a custom variable usable in the campaign as a merge tag. Only letters, digits, underscore, hyphen, space and hash survive; anything else, a full stop or a dollar sign, is replaced with an underscore. 8. Put the condition on the add column [Clay: run settings, Only run if]. All three actions take Auto-update and Only run if. The add is the one that cannot be undone from the table, so that is the column the score belongs on. **How to check it worked:** - Add one lead, then add the same lead again. The second attempt should be refused rather than updating anything, which is the documented behaviour and worth seeing once. - Add a lead whose company already exists in lemlist with a company field deliberately wrong. Then open another lead at that company and check what it now reads. - Send a custom variable with a full stop in its name and look at what lemlist stored. The character is replaced with an underscore, so the merge tag in your campaign has to match the stored name. - Check the rate headers if you are pushing in bulk. lemlist allows 20 requests per 2 seconds per API key and returns Retry-After, X-RateLimit-Limit, X-RateLimit-Remaining and X-RateLimit-Reset on every response. Agent skill for this pair: https://www.reversecontact.com/integrations-hub/skills/clay-lemlist.md **Field mapping:** - Add Lead to Campaign maps to Campaign ID required, the rest optional. Email, LinkedIn URL, name, phone and more. lemlist documents the underlying endpoint as creating and never updating, so this is not an upsert however it is used. - Update Lead in Campaign maps to Campaign ID, plus email or lead ID. The action for changing an existing lead. Pairing it with the lookup is what turns the two into the upsert that the add action is not. - Lookup Lead in Campaign maps to Email address or lead ID. Checks whether the lead exists in a campaign. The cheapest column on the table and the one that makes the other two safe. - Company fields maps to The shared company record. companyName, companyDomain, companyIndustry and any company-prefixed key reach the company the lead is matched to, which every other lead linked to it reads. Not scoped to the lead. - Any other key you send maps to A custom variable on the lead. Usable in the campaign as a merge tag. Letters, digits, underscore, hyphen, space and hash are kept; every other character becomes an underscore, and values are stored as text. - The API key maps to HTTP Basic, empty username. lemlist uses Basic rather than Bearer, with the key as the password and a leading colon before it. Clay handles the encoding; what it means for you is that the key is a credential, not a token with scopes. - Campaign creation maps to Not an action. The campaign has to exist in lemlist first. lemlist's own API can create one, but Clay does not expose that. - Replies, opens, meetings maps to Nothing comes back. There is no read action for engagement, so performance lives in lemlist and the table is a feed. - Does not cross: An upsert. The add endpoint creates and never updates, so a lead that already exists is an error rather than a refresh, and the Update action is a separate column. - Does not cross: Company data scoped to one lead. lemlist documents company-prefixed fields as reaching the shared company record, with a separate Upsert Company endpoint for editing one on purpose. - Does not cross: Any character outside letters, digits, underscore, hyphen, space and hash in a custom variable name. They are replaced, silently, before storage. **What breaks:** - **An API key, not OAuth.** The connection is a lemlist API key pasted into Clay, taken from lemlist's settings. That means a long-lived credential sitting in another product, revocable only from lemlist, and rotating it breaks every table using it at once. It is the normal arrangement for this class of tool and it is worth knowing which tables hold it. - **The campaign has to exist first.** Every action takes a campaign id and Clay cannot create a campaign. So the sequence design, the sending mailboxes and the schedule are lemlist decisions made before the table runs, and a table pointed at a campaign that was paused or deleted fails per row rather than announcing itself. - **Nothing comes back.** There is no reply, open or booking data returning to Clay, so the table cannot suppress on engagement and cannot report on what the list produced. Teams that want that loop close it through the CRM both tools write to rather than between these two directly. - **Credits are spent before the push.** The action itself is cheap; the waterfall that filled the row is not. Clay's conditional run setting is the control that matters, because it stops the expensive enrichment running on rows that were never going to qualify. Set the condition before the volume, not after the first bill. **Failures people hit:** - 400 LEAD_ALREADY_IN_CAMPAIGN. Why: The contact already has a lead in that campaign. lemlist documents the add endpoint as one that creates and never updates, so this is the designed response rather than a fault. Fix: Use the Update Lead in Campaign action for anybody already there, gated on a lookup column. Nothing was written by the refused call. - 409 LEAD_ALREADY_IN_OTHER_CAMPAIGN. Why: Deduplication is on and the contact has a lead in a different campaign. Fix: Decide whether somebody in another campaign should be enrolled again. Note that only the deduplicate parameter drives this check: the campaign's own remove duplicates setting does not. - A lead was refused and its details changed anyway. Why: The lead is always new, and the contact and company it matches are updated with whatever fields you sent regardless. Fix: Treat the add action as a write to the contact even when it fails as a lead. If that is not what you want, look up first and branch. - A populated field came back empty after a push. Why: updateStrategy defaults to overwrite, where a sent value replaces the stored one and an empty value clears it. Fix: Send overwriteIgnoreEmpty to keep stored values where your column is blank, or fillEmptyOnly to fill only what is empty. Kept values are reported back as FIELDS_KEPT warnings. - A merge tag is not resolving in the campaign. Why: The custom variable name was rewritten on storage. Only letters, digits, underscore, hyphen, space and hash are kept, and anything else becomes an underscore. Fix: Name the Clay column with characters lemlist keeps, and match the merge tag to the stored name rather than the one you typed. - A company field you wrote shows up on other people's leads. Why: Company-prefixed fields reach the company record the lead is matched to, which is shared by every lead linked to it. Fix: Keep company columns out of a bulk push unless you intend to edit the company. lemlist has a separate Upsert Company endpoint for doing it deliberately. - Requests started failing during a bulk run. Why: lemlist rate-limits all routes at 20 requests per 2 seconds, per API key. Fix: Read Retry-After and X-RateLimit-Remaining, which come back on every response. Note X-RateLimit-Reset is a human-readable date rather than a timestamp, which trips up anything parsing it. - Nobody can find the API key. Why: lemlist shows it once at creation and never again. Fix: Generate a new one in Settings, Integrations, and store it properly this time. Rotating it means re-entering it in Clay, since the connection is the key. **What practitioners say** (14 threads from 2024 to 2026, read 2026-10-11): The pair by name returns nothing, so the search was for the job: enriching in one tool and sending from another. Two things come out of it. The constraint on this arrangement is the sending side rather than the table, measured in mailboxes and daily sends. And the integration gap people actually complain about is the CRM at the other end, not the sequencer, which is worth knowing before anybody decides this pair is the missing piece. - The real ceiling is mailboxes, not the table (r/revops, December 2025, 4 points): https://www.reddit.com/r/revops/comments/1pg7scy/need_help_setting_up_our_growth_engine/ - The complaint is about the CRM end, not the sequencer end (r/CRMSoftware, January 2026, 2 points): https://www.reddit.com/r/CRMSoftware/comments/1qgbhkb/what_made_you_switch_crms_and_what_almost_made/ - The loop back is what people value and what this pair does not give (r/SaaS, February 2026, 2 points): https://www.reddit.com/r/SaaS/comments/1r0e05t/ive_had_an_obsession_with_customer_journeys_and/ - Clay is a complex tool and people say so without being asked (r/salesdevelopment, August 2024, 1 points): https://www.reddit.com/r/salesdevelopment/comments/1d47t87/has_anyone_used_claycom_to_create_prospecting/ - A three-action integration is the cheap part of the setup (r/Emailmarketing, May 2024, 2 points): https://www.reddit.com/r/Emailmarketing/comments/1b8cuy6/how_does_claycom_works_what_are_the_alternatives/ Sources: https://university.clay.com/docs/lemlist-integration-overview | https://www.clay.com/integrations/data-provider/lemlist | https://developer.lemlist.com/api-reference/endpoints/leads/create-lead-in-campaign | https://developer.lemlist.com/api-reference/getting-started/authentication | https://developer.lemlist.com/api-reference/getting-started/rate-limits ### n8n and Reverse Contact The route that handles async resolution, and the one a security team signs off on. - Built as: Built on the API, Zapier, Make or n8n - Syncs: One way, in - Moves: Contacts, Companies - Costs to turn on: Metered by usage. Setup: Hours - Requires: An n8n instance, self-hosted or cloud, and a Reverse Contact API key - Full guide: https://www.reversecontact.com/integrations-hub/n8n-integrations/n8n-reverse-contact-integration **Verdict.** n8n is the only route in this directory that comfortably handles Reverse Contact's live endpoints, because those return a task to poll rather than a record. A HubSpot workflow cannot wait; an n8n workflow can, with a Wait node and a loop. Self-hosting also answers the question that stops several of these builds, which is whether customer records may leave infrastructure you control. **What syncs:** - Trigger (in): A CRM webhook, a schedule, or a queue. n8n does not care which. - The call (out): An HTTP Request node POSTs to /v2/enrich/persons with a Bearer token from credentials. - Async handling (in): For /live, poll GET /v2/webhooks/:webhookId in a loop until status is succeeded. Polling is free and off the rate-limit clock. - Write-back (out): The native HubSpot or Salesforce node updates the record with the mapped fields. **Which editions carry it** (rows n8n, columns Reverse Contact): - n8n, self-hosted with Cached lookup inside one run: Yes - n8n, self-hosted with Live refresh, which returns a task: Yes - n8n, self-hosted with Records never leave infrastructure you control: Yes - n8n, self-hosted with A non-engineer can change it next month: No - n8n Cloud with Cached lookup inside one run: Yes - n8n Cloud with Live refresh, which returns a task: Yes - n8n Cloud with Records never leave infrastructure you control: No - n8n Cloud with A non-engineer can change it next month: No - A HubSpot or Salesforce workflow with Cached lookup inside one run: With a caveat - A HubSpot or Salesforce workflow with Live refresh, which returns a task: No - A HubSpot or Salesforce workflow with Records never leave infrastructure you control: With a caveat - A HubSpot or Salesforce workflow with A non-engineer can change it next month: With a caveat - A Clay column with Cached lookup inside one run: Yes - A Clay column with Live refresh, which returns a task: No - A Clay column with Records never leave infrastructure you control: No - A Clay column with A non-engineer can change it next month: Yes - A Zap or a Make scenario with Cached lookup inside one run: Yes - A Zap or a Make scenario with Live refresh, which returns a task: With a caveat - A Zap or a Make scenario with Records never leave infrastructure you control: No - A Zap or a Make scenario with A non-engineer can change it next month: Yes **How to connect it** (Whoever owns the n8n instance, plus whoever can create a Reverse Contact API key. On self-hosted that is usually the same person, which is half the appeal.. An hour for the cached path. The poll loop for the live endpoints is another hour and only some builds need it.): 1. Decide self-hosted or cloud first, because it is the reason you are here [n8n: deployment]. The usual reason to choose this route over the Clay app or the Zapier app is that customer records may not leave infrastructure you control, and that is a deployment decision rather than a workflow one. The workflow is identical either way, so the question costs nothing to settle now and is awkward to revisit after a security review has started. 2. Decide where the enriched value is written, and what it may overwrite [Your CRM: property names]. The API returns a record and nothing writes it anywhere. That is more work than a marketplace app and it is exactly why this route never flattens a field a rep owns. Prefix the properties it writes, and promote a value into a human-maintained field with a separate rule or not at all. 3. Create a key for this workflow and cap it [Reverse Contact: Workspace, API Keys]. Keys are created in Workspace then API Keys, and a per-key rate limit can hold one integration below the workspace maximum. This matters more here than on any other route: an n8n run goes as fast as the node allows, and the minute limit is shared with every other integration on the workspace. 4. Make a Header auth credential rather than typing a header into the node [n8n: Credentials, Header Auth]. n8n recommends a Predefined Credential Type wherever one exists, and there is none for Reverse Contact, so this is the generic case: Header auth, with the name Authorization and the value Bearer followed by your key. Credentials are stored apart from the workflow JSON, which is what keeps the workflow safe to export, review and commit. 5. Turn on Never Error and Include Response Headers and Status [n8n: the node, Options, Response]. Both are off by default. The node reports success only on a 2xx, so a lookup that matched nobody stops the execution, and without the status code you cannot tell that miss from a rate limit. Together these two turn an empty answer into a branch, and this is the step to take before the first real run rather than after it. 6. Check before you fetch, on the endpoint that costs nothing [POST /v2/fetch/persons/check]. Reverse Contact recommends this sequence itself: the check says whether a profile is cached and when it was last updated, so the workflow picks a 1-credit cached read or a 2-credit live refresh on evidence rather than on a guess. It is free, and the decision it enables is the main lever on this bill. 7. Set Items per Batch and a Batch Interval before the first bulk run [n8n: the node, Options, Batching]. Items per Batch takes a count and Batch Interval takes a wait in milliseconds. Pacing a five-thousand-row run under the workspace minute limit is a two-field change here, and discovering the limit instead is a wall of 429s with a retry storm behind it. 8. Build the poll loop only for the calls that need one [n8n: a Wait node and an IF]. Only the live and contact endpoints answer with a task. Read data.webhookId, then poll GET /v2/webhooks/:webhookId until the status reads succeeded, breaking on errored. Polling is free and off the rate-limit clock, so the loop costs wall clock and nothing else. **How to check it worked:** - Call the free check endpoint on your own profile URL and read the update date. It costs nothing, it proves the credential works, and that date is the number the rest of your cost model rests on. - Point the node at somebody who does not exist and run it with Never Error still off. Watching the execution stop is the clearest demonstration of why it goes on, and the call costs no credits either way. - Start one live job and poll it by hand, timing it. The published aim is under 15 seconds and the documented ceiling is tens of minutes, and your own figure is what decides whether that loop can sit anywhere near a request path. - Run twenty rows with Batch Interval at 0 and read quotas.minuteRateLimit on the last response. If left is already near zero on twenty rows, an unpaced run over five thousand was never going to finish. Agent skill for this pair: https://www.reversecontact.com/integrations-hub/skills/n8n-reverse-contact.md **Field mapping:** - One HTTP Request node, POST maps to https://api.reversecontact.com/v2. Every endpoint is reachable from the same node, which is why the absence of a dedicated node costs nothing. It also means no node update can break this workflow, and there is no predefined credential type to pick. - A Header auth credential maps to Authorization: Bearer rc_your_api_key. n8n's generic credential list carries Header auth alongside Basic, Digest, Query and the two OAuth types. Credentials live outside the workflow JSON, so the workflow stays safe to export and review. - Never Error, in Response options maps to A 404 or a 402, both of which cost nothing. The node reports success only on a 2xx by default, so a confident null stops the execution. Reverse Contact charges 0 credits on every 4xx and 5xx, so the miss was free and only the workflow needed telling about it. - Include Response Headers and Status maps to The status code, beside the body. Off by default, so the node hands back the body alone. With Never Error on you need the status to tell a miss from a rate limit, which makes these two options a pair rather than two independent choices. - Items per Batch and Batch Interval maps to The workspace minute limit. Reverse Contact applies a per-minute limit per workspace, reports it in quotas.minuteRateLimit on every response and answers 429 past it. Batching with an interval in milliseconds is how a bulk run stays underneath it. - A Wait node and a loop maps to POST /v2/fetch/persons/live, then GET /v2/webhooks/:webhookId. The live endpoints answer with a webhookId rather than a record. Poll until the status is succeeded, break on errored and read errorCode. Polling is free and does not count against the rate limit. - Pagination mode maps to POST /v2/search/people. Search answers in pages, and n8n exposes $pageCount and $response.body for the loop. People search is priced per profile delivered, so the free count endpoint should size the query before the pagination starts. - Timeout, in milliseconds maps to A published 500ms P95 on the cached calls. The node aborts a request that takes longer than this to begin responding. A short timeout is safe on the cached endpoints and wrong on the live ones, which are not slow so much as asynchronous. - Does not cross: A dedicated node. Reverse Contact ships none, which is why there is no predefined credential type to pick and also why no node update can break this workflow. - Does not cross: A trigger. Nothing in Reverse Contact starts an n8n workflow, so the trigger is a CRM webhook, a schedule or a queue. The one thing it will send you unasked is the callback POST to a webhookUrl you supply on the live and contact endpoints. - Does not cross: A refund for a failed callback delivery. Reverse Contact documents that an invalid, erroring, timing-out or unreachable webhook URL is not refunded, because the data was fetched: the job reports succeeded with a deliveryStatus and the result is still there to poll for. - Does not cross: Any write back into Reverse Contact. The direction runs one way, and there is nothing in the product to write to. **What breaks:** - **There is no dedicated node.** Reverse Contact ships no n8n node, so this is the HTTP Request node plus credentials. That is five minutes of work and it means no node update can break your workflow. - **You own the uptime.** Self-hosting removes the third-party meter and hands you the pager. For most teams a small managed instance is the right compromise. - **The credit cost is published, the dollar rate is not.** A reverse lookup from an email is 2 credits, a cached lookup 1, a live refresh 2, and a poll is free. No dollar rate per lookup is published, so the money figure depends on the pack or plan the credits came from. **Failures people hit:** - The workflow stops on a contact who is not in the database. Why: The HTTP Request node reports success only on a 2xx by default, and a confident null is not a 2xx. Fix: Turn on Never Error in the node's Response options and branch on the body with an IF node. The call cost 0 credits either way, so nothing was wasted except the execution. - A 429 on a run that worked fine on a shorter list. Why: Reverse Contact applies a minute limit per workspace, shared with every other integration on it, and answers 429 past it. Fix: Set Items per Batch and a Batch Interval rather than adding a retry, and read quotas.minuteRateLimit for limit, used, left and nextReset. A per-key rate limit stops this workflow starving the rest of the workspace. - The poll loop never finishes. Why: A live job ends at succeeded or errored, and Reverse Contact documents the wait as usually seconds and possibly tens of minutes. Fix: Break on errored as well as succeeded, read errorCode, and cap the loop. An uncapped Wait loop on a job that will not finish is an execution running until something external kills it. - A live call returned nothing to map. Why: The live endpoints are asynchronous by design. The response carries a webhookId rather than a record, which is what the documentation means by built to feed async pipelines rather than to block a request. Fix: Read data.webhookId from the first call, poll GET /v2/webhooks/:webhookId until the status is succeeded, then take data.result. The polling is free and off the rate-limit clock. - The result never arrived and the credit was spent anyway. Why: Where a webhookUrl is used instead of polling, Reverse Contact keeps the credit on a delivery failure because the data was fetched, and reports the job as succeeded with a deliveryStatus naming the problem. Fix: Poll the webhook id and collect the result you have already paid for. The four documented delivery failures are webhook-url-invalid, webhook-url-errored, webhook-url-timeout and webhook-url-unreachable. - Everything failed at once, including the calls that were free. Why: Below 2 credits the free Check endpoints are paused as well and answer 402 NO_CREDITS, because the fetch a check precedes can itself cost 2. Fix: Branch on quotas.workspace.credits.left, which rides on every response. GET /v2/usage, GET /v2/flags and webhook polling keep answering whatever the balance, so a balance check never fails for the reason the lookup did. - An endpoint that worked last week returns nothing. Why: Reverse Contact replaced /v2/resolve with /v2/enrich and /v2/search/persons with /v2/search/people, and documented the old pair as live only until 13 October 2026. Fix: Search the workflow JSON for both old paths and change them. A workflow exported before that date and imported after it fails on its first run rather than at deploy time, which is the worst moment to find out. - A search cost far more than the number of requests suggested. Why: People search is priced per profile delivered rather than per request, while company search is priced per page of up to 100 results, so the two are not the same arithmetic. Fix: Call the free count endpoint to size a people search before you run it, and set the pagination limit deliberately. An unbounded pagination mode on a broad query is the expensive mistake on this endpoint. **What practitioners say** (14 threads from 2025 to 2026, read 2026-10-11): Nobody discusses this pair by name, so the search was for the job: building an enrichment workflow in n8n and paying for it. Every thread is somebody doing exactly that, and the recurring conclusion is the same one Reverse Contact's own documentation reaches, which is to make a cheap call first and only escalate what passes. The threads are also candid about the cost of enrichment in a way vendor pages are not. - Check cheaply, then escalate, arrived at independently (r/n8n, May 2026, 2 points): https://www.reddit.com/r/n8n/comments/1truqhw/how_i_use_website_enrichment_as_a_preapollo/ - A confidence score is what makes tiering possible (r/n8n, May 2026, 2 points): https://www.reddit.com/r/n8n/comments/1truqhw/how_i_use_website_enrichment_as_a_preapollo/ - A subscription is the wrong shape for lumpy volume (r/n8n, March 2026, 2 points): https://www.reddit.com/r/n8n/comments/1rfp9ka/automating_crm_data_enrichment_at_scale_with_n8n/ - Only pull the expensive data on the records you actually want (r/n8n, May 2026, 2 points): https://www.reddit.com/r/n8n/comments/1t4pk5e/best_data_enrichment_tools/ - An API is the reliable half and matching is still the hard half (r/n8n, June 2026, 2 points): https://www.reddit.com/r/n8n/comments/1u863pl/how_to_built_a_lead_enrichment_workflow_in_n8n_to/ Sources: https://docs.reversecontact.com/getting-started | https://docs.reversecontact.com/guides/credits | https://docs.reversecontact.com/guides/rate-limits | https://www.reversecontact.com/pricing | https://www.reversecontact.com/integrations | https://docs.n8n.io/integrations/builtin/core-nodes/n8n-nodes-base.httprequest | https://developers.hubspot.com/docs/api-reference/legacy/automation/workflow-actions/custom-code-actions ### Make and Reverse Contact A verified app with three modules and an escape hatch for everything else. - Built as: Native, Zapier, Make or n8n - Syncs: One way, in - Moves: Contacts, Companies - Costs to turn on: Metered by usage. Setup: Minutes - Requires: A Make plan with enough operations, and a Reverse Contact API key - Full guide: https://www.reversecontact.com/integrations-hub/reverse-contact-integrations/make-reverse-contact-integration **Verdict.** The verified Make app is the second of the two no-code routes to Reverse Contact, and the one with the better escape hatch. Three named modules cover the common cases and Make an API Call covers the rest, so a scenario never hits a wall that forces a raw HTTP module and a second copy of the credentials. Against Zapier it trades named operations for generality and a cheaper meter. Against a direct API call it trades money for the fact that a non-engineer can open it and see what happened. **What syncs:** - Trigger (in): Any Make trigger: a watch module on a CRM, a webhook, a schedule, a spreadsheet row. - Reverse Email Lookup (out): Takes an email, returns the person and the company. The common case, and the module most scenarios use. - Make an API Call (out): Any endpoint the named modules do not cover, authorised with the connection you already made. - Write-back (in): Make's own app modules for the CRM or sequencer that owns the record. **Which editions carry it** (rows Reverse Contact, columns Make): - Freshness check, free with A named Make module: Not available - Freshness check, free with Make an API Call: Available - Freshness check, free with A named Zapier action: Available - Person from a profile URL with A named Make module: Available - Person from a profile URL with Make an API Call: Available - Person from a profile URL with A named Zapier action: Available - Company from a profile URL with A named Make module: Available - Company from a profile URL with Make an API Call: Available - Company from a profile URL with A named Zapier action: Available - Person from an email with A named Make module: Available - Person from an email with Make an API Call: Available - Person from an email with A named Zapier action: Available - Company from a domain with A named Make module: Not available - Company from a domain with Make an API Call: Available - Company from a domain with A named Zapier action: Available - People or company search with A named Make module: Not available - People or company search with Make an API Call: Available - People or company search with A named Zapier action: Available - Credit balance and usage with A named Make module: Not available - Credit balance and usage with Make an API Call: Available - Credit balance and usage with A named Zapier action: Available - Live refresh with A named Make module: Not available - Live refresh with Make an API Call: Buildable with a poll loop - Live refresh with A named Zapier action: Not available - A trigger, so it starts the run with A named Make module: Not available - A trigger, so it starts the run with Make an API Call: Not available - A trigger, so it starts the run with A named Zapier action: Not available **How to connect it** (Whoever can edit a scenario, plus whoever can create a Reverse Contact API key. No Make admin, and no approval queue like the HubSpot app has.. Fifteen minutes for the scenario. Deciding whether a named module covers what you need is the part to do first.): 1. Check whether a named module covers your call at all [Make: the app, All Modules]. There are four: Reverse Email Lookup, Get LinkedIn Profile, Get a LinkedIn Company, and Make an API Call. Everything else Reverse Contact publishes, the free freshness check, company lookup from a domain, people and company search, the live endpoints, reaches you only through the generic call. Finding that out after the scenario is drawn is the common way this costs an afternoon. 2. Decide where the enriched value lands, before the mapping screen [The app that owns the record]. Map into properties nothing else writes, prefixed so nobody types into one by hand. Make will faithfully write whatever you map, including an empty value from a lookup that matched nobody, and the field a rep maintains is the expensive one to get wrong. 3. Create a key for this scenario and cap it [Reverse Contact: Workspace, API Keys]. Keys are created in Workspace then API Keys, and a per-key rate limit can hold one integration below the workspace maximum. A scenario with an iterator over a thousand rows is exactly the thing that should not be allowed to exhaust the workspace minute. 4. Make the connection once and reuse it [Make: the module, Connection]. The app is listed as Verified with Reverse Contact as the Official Vendor, which means Make reviewed it and the developer is the vendor rather than a third party. One connection serves every module in the app, including Make an API Call, so the key is entered once rather than per module. 5. Put the filter on the route, not inside the module [Make: the link between two modules]. A Make filter sits on the connection between modules and stops the bundle travelling, so a filter in front of the enrichment is what keeps operations off rows that were never going to resolve. This is the cheapest line in the scenario and it is usually added last. 6. Handle the no-match case explicitly [Make: a router, or a filter after the lookup]. A lookup that matches nobody is a successful module run with nothing in it rather than an error, so the scenario carries on to the update. Route the empty bundles somewhere else, which is also where a second provider would go if you were building a waterfall. 7. Build the poll loop only if you actually need live data [Make: a repeater and a sleep module]. Make can do what a Zap cannot here, because a repeater and a sleep module make a polling loop buildable. Reverse Contact documents polling as free and off the rate-limit clock, so the cost is entirely Make operations: every iteration of the loop is one, and the job can take tens of minutes. 8. Run the scenario once and read the bundle, not the log [Make: Run once, then the module output]. Click into the module after the run and read the actual bundle. The execution log says the module succeeded, which it did, and the bundle is the only place the difference between a matched profile and an empty one is visible. **How to check it worked:** - Run Reverse Email Lookup on an address you know matches nobody, and watch the module succeed. Doing it on purpose once is how you find out what your mapping writes when that happens in production. - Check the credit balance either side of that miss. It should not move, because Reverse Contact charges 0 credits on a 4xx, while the Make operation was spent regardless. - Point Make an API Call at the free freshness check and read the update date it returns. That proves the escape hatch works on your connection and tells you how stale the cached record is before you buy a refresh. - Turn the scenario on, let one real record through, then open the record in the destination app rather than the Make history. The history reports what Make did; the record shows what landed. Agent skill for this pair: https://www.reversecontact.com/integrations-hub/skills/make-reverse-contact.md **Field mapping:** - Reverse Email Lookup maps to Reverse lookup from an email, 2 credits. Takes an email and returns person and company data in one module. The common case and the module most scenarios are built on, and the only one of the three named modules that starts from something a CRM actually holds. - Get LinkedIn Profile maps to Cached lookup from a profile URL, 1 credit. Person data from a profile URL. Cheaper per call than the reverse lookup and unmetered from the $249 plan up, so it is the module to prefer wherever the URL is already on the record. - Get a LinkedIn Company maps to Cached lookup from a profile URL, 1 credit. The company equivalent, also from a profile URL rather than from a domain. A domain is a reverse lookup and needs the generic module. - Make an API Call maps to Any endpoint, on your connection. Performs an arbitrary authorised API call, which is the whole reason this app does not hit a wall. You still supply the path, the body and your own reading of the response, so this module needs somebody who has opened the API reference. - The free freshness check maps to No named module. Reachable only through Make an API Call. It costs nothing, says whether a profile is cached and when it was last updated, and is the call Reverse Contact recommends making before you spend anything. - People or company search maps to No named module. Also only through the generic call. Search is priced per profile delivered, and the count endpoint that sizes a query first is free, so make that call before the one that bills. - The write-back maps to Not Reverse Contact's job. Make's own module for whatever owns the record carries the mapped fields the rest of the way. Nothing travels back to Reverse Contact, because there is nothing in the product to write to. - Any trigger maps to Does not exist in this app. All four modules are actions. Reverse Contact never starts a scenario, so there is always a watch module, a webhook or a schedule in front of it. - Does not cross: A trigger of any kind. All four modules are actions, which Make's own listing states by counting four modules and four actions, so something else always starts the scenario. - Does not cross: A business email or a direct phone number. Those are separate endpoints at 3 and 20 credits, charged only when one is found, and neither has a named module here. - Does not cross: The live endpoints, natively. They answer with a task id rather than a record, so live resolution is a repeater and a sleep module around Make an API Call, with every iteration costing an operation. - Does not cross: Anything travelling back to Reverse Contact. This is a read layer and the direction only runs one way. **What breaks:** - **Operations are charged per module, per bundle.** A scenario that watches, enriches and updates spends three operations on every record, and an iterator over 100 records multiplies that. Make is generally cheaper per unit than Zapier and the arithmetic is the same shape, so do it before you design for volume. - **There are no triggers in the app.** Reverse Contact never starts a scenario. Something else does, which is correct for a data layer and means the scenario always has a watch module or a webhook in front of it. - **Make an API Call is not a free pass.** It authorises the call with your connection, which is the convenience, but you still have to know the endpoint, the body and what the response looks like. For anything beyond the three named modules this route needs somebody who has read the API reference, same as a raw HTTP module would. - **Under 2 credits the free checks stop too.** When the Reverse Contact workspace has fewer than 2 credits left, even the free check endpoints return 402 rather than a result. A scenario built to check first and spend second fails at the check. **Failures people hit:** - The module succeeded and the record got an empty field. Why: A lookup that matches nobody is a successful run with no data rather than an error, because Reverse Contact returns null rather than a best guess. Fix: Put a filter after the lookup testing that the field exists, or a router sending the empty bundles elsewhere. The scenario is otherwise working exactly as drawn. - The operations count is far higher than the number of records. Why: Make charges an operation per module per bundle, so an iterator over a hundred records multiplies every module behind it by a hundred. Fix: Filter on the route before the enrichment rather than after it, and aggregate where a module accepts a batch. The arithmetic is the design on this route, the same as the task count is on Zapier. - The call you need has no module. Why: The app publishes four modules. The freshness check, company lookup from a domain, search and the live endpoints are not among them. Fix: Use Make an API Call on the same connection. It authorises with the credential you already made, so this is a module change rather than a second copy of the key. - Everything stopped, including the calls that cost nothing. Why: Below 2 credits the free Check endpoints are paused too and answer 402 NO_CREDITS, because the fetch a check precedes can itself cost 2. Fix: Route on quotas.workspace.credits.left, which is in every bundle, and stop the scenario before the balance reaches nothing. GET /v2/usage keeps answering when the checks do not. - A 429 from a scenario that worked on a smaller list. Why: Reverse Contact applies a minute limit per workspace, and the limit is shared with every other integration on it. An iterator runs as fast as Make will let it. Fix: Read quotas.minuteRateLimit, which carries limit, used, left and the next reset, and set a per-key rate limit for this scenario so it cannot starve the rest of the workspace. - The poll loop runs forever. Why: A live job finishes when its status reads succeeded or errored, and Reverse Contact documents that this is usually seconds but can be tens of minutes. Fix: Break on errored as well as succeeded, and cap the repeater. An uncapped loop on a job that will not finish is an operations bill rather than a hung scenario. - A webhook result arrived as a delivery failure. Why: Where a callback URL is used instead of polling, Reverse Contact reports an unreachable or erroring URL as a succeeded job carrying a deliveryStatus, and states that delivery failures are not refunded because the data was fetched. Fix: Poll GET /v2/webhooks/:webhookId to collect the result you already paid for. The job is not lost, only the delivery was. - Credits expired before the scenario spent them. Why: Credit packs are valid 3 months. A scenario that runs in bursts around a campaign can reach the end of a quarter holding credits it bought. Fix: Size the pack to a quarter of real volume rather than to a discount, or move to an Unlimited plan, where the cached endpoints the plan names stop being metered. **What practitioners say** (14 threads from 2023 to 2026, read 2026-10-11): Nobody discusses this pair by name, so the search was for the job: getting enriched data into a CRM without an engineer. The most useful thread is somebody trying hard to avoid a middle layer and being told there is not one, which is the argument of this page made by a stranger. The rest are about where the data under the automation comes from, which is the half the no-code tools do not supply. - Somebody asking how to avoid the middle layer, and the answer (r/CRM, July 2024, 1 points): https://www.reddit.com/r/CRM/comments/1e67lf0/need_recommendations_for_a_data_enrichment_tool/ - The no-code tools are the glue, and something else is the data (r/automation, November 2025, 2 points): https://www.reddit.com/r/automation/comments/1oqxqoy/has_anyone_replaced_zapier_or_make_completely/ - The question this whole directory exists to answer, asked plainly (r/GrowthHacking, October 2025, 1 points): https://www.reddit.com/r/GrowthHacking/comments/1o6r4dn/everyone_talks_about_enrichment_but_heres_how/ - A job change is a signal, not just a stale field (r/GrowthHacking, October 2025, 1 points): https://www.reddit.com/r/GrowthHacking/comments/1o6r4dn/everyone_talks_about_enrichment_but_heres_how/ - Fewer handoffs beats better handoffs (r/Emailmarketing, December 2025, 1 points): https://www.reddit.com/r/Emailmarketing/comments/1pc4o43/has_anyone_found_a_clean_way_to_handle_enrichment/ Sources: https://www.make.com/en/integrations/reversecontact | https://zapier.com/apps/reverse-contact/integrations | https://www.reversecontact.com/integrations | https://docs.reversecontact.com/guides/credits | https://docs.reversecontact.com/guides/rate-limits | https://docs.reversecontact.com/getting-started | https://www.reversecontact.com/pricing ### Zapier and Reverse Contact A native app with nine operations, and a miss that costs nothing. - Built as: Native, Zapier, Make or n8n - Syncs: One way, in - Moves: Contacts, Companies - Costs to turn on: Metered by usage. Setup: Minutes - Requires: A Zapier plan with enough tasks, and a Reverse Contact API key - Full guide: https://www.reversecontact.com/integrations-hub/zapier-integrations/zapier-reverse-contact-integration **Verdict.** This is the shortest route between Reverse Contact and a CRM or a sequencer that has no app of its own, and since the native app shipped it is a connection rather than a build. Nine operations cover everything a middle step needs, the enrichment bills nothing on a miss, and the whole thing is a dropdown rather than an HTTP module with a Bearer token typed into it. What decides whether it scales is Zapier's task meter, not anything on Reverse Contact's side: a task per step per record is excellent at hundreds of records a month and poor at hundreds of thousands. **What syncs:** - Trigger (in): Anything Zapier already connects to: a new CRM contact, a form submission, a new row, a schedule. - The enrichment step (out): Enrich a Person or Enrich a Company, taking the email or domain from the trigger step. 2 credits on a match, 0 on a miss. - The free checks (out): Check a Person Profile and Check a Company Profile cost 0 credits, so a Zap can test for cached data before spending anything. - Write-back (in): Whatever app owns the record. Zapier's own CRM actions map the returned fields. **Which editions carry it** (rows Reverse Contact, columns Zapier): - Credits, from $100 with Check a Person or Company Profile: Always free - Credits, from $100 with Get LinkedIn Profile or Company: 1 credit a call - Credits, from $100 with Search Person or Company: 1 credit a call - Credits, from $100 with Enrich a Person or a Company: 2 credits a call - Go, $249 a month with Check a Person or Company Profile: Always free - Go, $249 a month with Get LinkedIn Profile or Company: Unlimited - Go, $249 a month with Search Person or Company: 1 credit a call - Go, $249 a month with Enrich a Person or a Company: 2 credits a call - Plus, $449 a month with Check a Person or Company Profile: Always free - Plus, $449 a month with Get LinkedIn Profile or Company: Unlimited - Plus, $449 a month with Search Person or Company: Unlimited - Plus, $449 a month with Enrich a Person or a Company: 2 credits a call - Max, $699 a month with Check a Person or Company Profile: Always free - Max, $699 a month with Get LinkedIn Profile or Company: Unlimited - Max, $699 a month with Search Person or Company: Unlimited - Max, $699 a month with Enrich a Person or a Company: Unlimited - Platform, quoted with Check a Person or Company Profile: Always free - Platform, quoted with Get LinkedIn Profile or Company: Unlimited - Platform, quoted with Search Person or Company: Unlimited - Platform, quoted with Enrich a Person or a Company: Unlimited **How to connect it** (Anybody who can edit a Zap, plus whoever can create a Reverse Contact API key. No admin on either side.. Fifteen minutes. Working out how many tasks a record will cost takes longer than building it.): 1. Count the tasks per record before you build anything [A pencil, not a screen]. Zapier charges a task for each step that runs, so a Zap that triggers, enriches and updates spends three tasks on every record whether or not the lookup matched. Multiply by records a month and compare it with an hour of engineering. This is the decision that cannot be undone later without rebuilding, and it is the one nobody takes first. 2. Decide where the enriched value is written [The app that owns the record]. Point the update step at properties nothing else writes to, prefixed so a rep never types into one. A Zap that writes a title into the field somebody maintains by hand will keep doing it quietly, and the damage is only visible once somebody notices their own entry has gone. 3. Create a scoped Reverse Contact key for this Zap [Reverse Contact: Workspace, API Keys]. Keys are made in Workspace then API Keys, and a per-key rate limit can cap one integration below the workspace maximum. Give the Zap its own key with its own cap, so a runaway Zap cannot starve everything else on the workspace minute limit. 4. Add the Reverse Contact connection once [Zapier: the action step, Choose account]. The app authenticates against your own workspace, so the credits are yours rather than the platform's. That is the opposite of the Clay app, which runs on Clay credits by default, and it is why this route needs a Reverse Contact account and that one does not. 5. Pick the action that matches the identifier your trigger carries [Zapier: the nine operations]. Enrich a Person takes an email or a name plus company. Get LinkedIn Profile takes a profile URL. Search Person takes criteria. Which one you can use is decided by the trigger, not by preference, and it also decides which Reverse Contact plan makes the Zap unmetered. 6. Put a filter in front of the enrichment, not after it [Zapier: Filter by Zapier]. A filter step costs a task and stops the ones behind it from running at all. On a trigger that fires on every record update rather than on creation, that filter is the difference between enriching new contacts and re-enriching the whole database every time somebody edits a note. 7. Decide whether the free check is worth its task [Zapier: Check a Person Profile]. Check a Person Profile costs 0 credits and tells you whether a profile is cached and how fresh it is. It still costs a Zapier task. So checking first saves credits and spends tasks, and which way that trade goes depends on your match rate rather than on best practice. 8. Test on one record and read what came back [Zapier: Test step]. Run the Zap once on a record you know the answer for, then open the enrichment step output. A miss comes back without a profile rather than as an error, so a Zap that maps the output blindly writes an empty field and reports success. **How to check it worked:** - Run Enrich a Person on an address you know matches nobody. The step should succeed with no profile attached and spend no credits, and the point of doing it on purpose is to see what your mapping does with that. - Check your credit balance before and after that miss. It should not move, because Reverse Contact charges 0 credits on a 4xx, and the Zapier task history will show a task spent anyway. - Add Get Workspace Usage as a temporary last step and read the credits left. It costs nothing, and it is the only way a Zap can see the balance it is spending. - Turn the Zap on, let one real record through, then open the record in the destination app rather than the Zapier history. The history reports what Zapier did and the record shows what actually landed. Agent skill for this pair: https://www.reversecontact.com/integrations-hub/skills/zapier-reverse-contact.md **Field mapping:** - Enrich a Person maps to enrich_person, 2 credits if found. Takes an email, or a name plus company, and returns the matched identity. Zapier's own listing states 2 credits if a profile is found and 0 if there is no match, which makes a miss free on this route and is the single most useful fact about it. - Enrich a Company maps to enrich_company, 2 credits if found. Takes a domain and returns the company profile. Same billing shape: nothing is charged when there is no match. - Get LinkedIn Profile maps to get_linkedin_profile. Takes a profile URL rather than an email, so it is the cheap route when the trigger already carries one. This is the cached lookup Reverse Contact prices at 1 credit and makes unmetered from the $249 plan up. - Get LinkedIn Company maps to get_linkedin_company. The company equivalent, from a company profile URL. Also a cached lookup rather than a reverse one. - Check a Person Profile maps to check_person, 0 credits. Says whether a person profile exists in the database from its URL or ID. Free in credits, and still one Zapier task, which is the trade this page keeps coming back to. - Check a Company Profile maps to check_company, 0 credits. The company equivalent, also stated as 0 credits on the listing. - Search Person and Search Company maps to search_person, search_company. The two Queries rather than Functions, so Zapier treats them as lookups that find an existing thing. Search is priced per profile delivered, and the free count endpoint that would let you size a query first is not one of the nine. - Get Workspace Usage maps to get_workspace_usage, 0 credits. Returns the workspace credit usage and quotas, total, used and left. The only way a Zap can read its own balance, and worth a scheduled Zap of its own rather than a step inside a working one. - Does not cross: Any trigger. The app publishes nine operations and none of them is a trigger, so Reverse Contact never starts a Zap. Something else has to fire it: a CRM record, a form, a schedule, a webhook. That is the right shape for a data layer and it does mean the Zap always has at least two other steps. - Does not cross: The live endpoints. They answer with a task id and complete in the background, and a Zap has no loop to poll with. Reverse Contact documents a live result as usually seconds and possibly tens of minutes, so this is not a Delay step with a longer delay. - Does not cross: A business email or a direct phone number. Those are separate endpoints at 3 and 20 credits, charged only when one is found, and neither is among the nine operations. - Does not cross: The free search count endpoint. Search Person and Search Company are both here and the call that would tell you how many results a query has before you pay for them is not, so size a search outside the Zap. **What breaks:** - **A task is charged per step, not per Zap.** A three-step Zap that triggers, enriches and updates spends three tasks on every record. That arithmetic, rather than the credit cost, is what usually decides whether this route survives contact with volume. Work out tasks per record and multiply before committing to it. - **There are no triggers in this app.** Reverse Contact does not start a Zap. It is an action and a search, so something else has to fire: a CRM record, a form, a schedule, a webhook. That is correct for a data layer and it does mean the Zap always has at least two other steps. - **The live endpoints do not fit a Zap.** Live resolution hands back a task id and completes in the background. A Zap has no loop, so the honest options are the cached actions here, or n8n where polling is natural. Polling is free and off the rate-limit clock wherever you do it. - **Under 2 credits the free checks stop too.** When a Reverse Contact workspace drops below 2 credits the free check endpoints return 402 rather than a result, because the fetch a check precedes can itself cost 2. A Zap built to check first and enrich second therefore fails at the check, not at the step you would expect. - **Credit packs expire after 3 months.** Packs from 5K to 1M credits are valid 3 months, so a Zap that runs in bursts can reach the end of a quarter with credits it paid for and cannot use. Above roughly 15,000 lookups a month Reverse Contact's own pricing page points at an Unlimited plan instead. **Failures people hit:** - The Zap reports success and the field in the CRM is empty. Why: A lookup that matches nobody is not an error. Reverse Contact returns null rather than a best guess, and the Zapier step completes normally with no profile attached. Fix: Put a Filter by Zapier step between the enrichment and the update, testing that the field you are about to write actually exists. One extra task per record buys you a CRM that is never written an empty value. - The task count is far higher than the number of records. Why: Zapier charges a task for every step that runs, not per Zap and not per record, so step count multiplies the bill. Fix: Count steps, then move the filter as early as the trigger allows: a filter that fires first stops every step behind it. Polls themselves consume no tasks, so the trigger is not what is costing you. - The Zap re-enriches people it already enriched. Why: The trigger is firing on any record change rather than on creation, which is a property of the CRM app's trigger rather than of this one. Fix: Switch to a creation trigger where the app has one, or filter on the enrichment field being empty. On a 2-credit action an unconditional re-run is a standing monthly cost rather than a one-off. - Everything stopped, including the steps that were free. Why: When a Reverse Contact workspace drops below 2 credits the free Check endpoints are paused too and answer 402 NO_CREDITS, because the fetch a check precedes can itself cost 2. Fix: Run Get Workspace Usage on a schedule rather than waiting for the failure. It costs nothing, and GET /v2/usage keeps answering when the checks do not. - A 429 on a Zap that was working yesterday. Why: Reverse Contact applies a minute limit per workspace, and a per-key limit if one was set. A second Zap, a Clay table or somebody in the dashboard shares that same workspace minute. Fix: Give each integration its own key with its own cap, which the API key management guide documents, and read quotas.minuteRateLimit on any response to see limit, used, left and the next reset. - A live refresh never returns anything to map. Why: The live endpoints are asynchronous by design: they reply with a webhookId and deliver the result afterwards, usually in seconds and sometimes in tens of minutes. Fix: Use the cached actions in the Zap. Live resolution belongs in a workflow with a loop, which is n8n or a Make scenario with a repeater, and the result can be written back by a second Zap on a webhook if the Zap is where the logic lives. - Credits expired before they were spent. Why: Credit packs are valid 3 months, and the packs run from 5K to 1M. A Zap that fires in bursts can reach the end of a quarter holding credits it paid for. Fix: Match the pack to a quarter of real volume rather than to a discount, or move to an Unlimited plan, where the cached endpoints the plan names stop being metered at all. - A search returns far more results than expected and costs more than expected. Why: Search is priced per profile delivered rather than per request, and the free count endpoint that would size the query first is not one of the nine operations. Fix: Narrow the criteria before the Zap goes live, and test the same query outside Zapier where the count endpoint is reachable. A search is the one operation here whose cost is not knowable from the step configuration. **What practitioners say** (14 threads from 2022 to 2026, read 2026-10-11): Nobody discusses this pair by name, so the search was for the job: moving enriched records between a form, a CRM and a sender without writing code. Almost every thread converges on the same argument, which is that Zapier is the right answer at a volume and the wrong one past it, and that the threshold is arithmetic rather than taste. The cost threads are the useful ones, because they are written by people who found the number the hard way. - The threshold is a volume, and practitioners name it (r/salesforce, August 2024, 18 points): https://www.reddit.com/r/salesforce/comments/1f4ccqg/is_anyone_using_zapier/ - A filter in front of the expensive step is the fix, and it is easy to get wrong (r/zapier, April 2026, 2 points): https://www.reddit.com/r/zapier/comments/1sgi1ta/zapier_bill_went_from_30_to_160month_when_i_added/ - The crossover with n8n is a pricing model rather than a feature (r/zapier, April 2026, 2 points): https://www.reddit.com/r/zapier/comments/1sgi1ta/zapier_bill_went_from_30_to_160month_when_i_added/ - The same complaint from the other side of the meter (r/zapier, April 2026, 3 points): https://www.reddit.com/r/zapier/comments/1sgi1ta/zapier_bill_went_from_30_to_160month_when_i_added/ - Safe and right are separate questions, and this thread separates them (r/salesforce, August 2024, 9 points): https://www.reddit.com/r/salesforce/comments/1f4ccqg/is_anyone_using_zapier/ Sources: https://zapier.com/apps/reverse-contact/integrations | https://www.reversecontact.com/integrations | https://docs.reversecontact.com/guides/credits | https://docs.reversecontact.com/guides/rate-limits | https://www.reversecontact.com/pricing | https://docs.reversecontact.com/getting-started ### Attio and Reverse Contact The one CRM here whose own workflow can call the API and read the answer. - Built as: Built on the API - Syncs: One way, in - Moves: Contacts, Companies, Custom objects - Costs to turn on: Metered by usage. Setup: Hours - Requires: An Attio workspace on a plan with automations, and a Reverse Contact API key - Full guide: https://www.reversecontact.com/integrations-hub/attio-integrations/attio-reverse-contact-integration **Verdict.** Attio is the only CRM in this directory that can run the whole enrichment inside its own automation builder: call the API, read the response, parse it, write the fields. No middle layer, no second meter and no engineer, which is a genuinely different answer from every other CRM here. The constraints are small and real: a 20-second block timeout that rules out live resolution, a Parse JSON step that fails on a type mismatch rather than degrading, and blocks that Attio currently labels legacy while it reworks the builder. **What syncs:** - Trigger (in): A record created or updated in Attio, or an inbound Webhook received block. - The call (out): Send HTTP request: POST to /v2/enrich/persons with an Authorization header and the record's email in the body. 2 credits. - The response (in): Status code and body come back as variables. Parse JSON turns the body into named fields for the next block. - Write-back (in): A record update block writes the parsed fields onto your own objects and attributes, custom ones included. **Which editions carry it** (rows Attio, columns Reverse Contact): - Attio with Call an outside API from its own automation: Yes - Attio with Read the response in a later step: Yes - Attio with Without writing any code: Yes - Attio with Without a particular edition or extra hub: Nearly - HubSpot, with Data Hub with Call an outside API from its own automation: Yes - HubSpot, with Data Hub with Read the response in a later step: Yes - HubSpot, with Data Hub with Without writing any code: No - HubSpot, with Data Hub with Without a particular edition or extra hub: No - HubSpot, without Data Hub with Call an outside API from its own automation: No - HubSpot, without Data Hub with Read the response in a later step: No - HubSpot, without Data Hub with Without writing any code: No - HubSpot, without Data Hub with Without a particular edition or extra hub: No - Salesforce with Call an outside API from its own automation: Yes - Salesforce with Read the response in a later step: Yes - Salesforce with Without writing any code: Nearly - Salesforce with Without a particular edition or extra hub: No - Pipedrive with Call an outside API from its own automation: Yes - Pipedrive with Read the response in a later step: No - Pipedrive with Without writing any code: Yes - Pipedrive with Without a particular edition or extra hub: No - Zoho CRM, Enterprise and above with Call an outside API from its own automation: Yes - Zoho CRM, Enterprise and above with Read the response in a later step: Yes - Zoho CRM, Enterprise and above with Without writing any code: No - Zoho CRM, Enterprise and above with Without a particular edition or extra hub: No - monday CRM with Call an outside API from its own automation: No - monday CRM with Read the response in a later step: No - monday CRM with Without writing any code: No - monday CRM with Without a particular edition or extra hub: No **How to connect it** (Whoever can edit a workflow in Attio, plus whoever can create a Reverse Contact API key. No engineer, which is the point of this route.. An hour. Most of it is deciding the Parse JSON paths and output types, which is the part that fails if rushed.): 1. Confirm the workspace has automations, because the free plan does not [Attio: plan and billing]. Attio has a free plan and puts automations on the paid ones, so this whole route depends on one. The REST API is available either way, which is the fallback if the plan is not there yet, and it is a different build with an engineer in it. 2. Model the attributes before you build the workflow [Attio: the object, Attributes]. This is the reason to be on Attio at all and it is the step people skip. Create attributes that belong to the data provider, beside the ones a rep owns, rather than deciding which of somebody else's fields the enrichment is allowed to overwrite. Doing it first also tells you which Parse JSON output types you need. 3. Check which output type each value needs, from the three on offer [Attio: Parse JSON, Output Type]. There are three: Boolean maps to a Checkbox attribute, Number and Number (Array) map to Number and Rating, and String and String (Array) map to Text, Email Address, Domain, Select, Multi-Select, Currency, Status and Phone. An employee count is a Number and a headline is a String, and getting that pairing wrong fails the block rather than writing nothing. 4. Add the Send HTTP request block and test the Authorization header first [Attio: Send HTTP request]. Method POST, the URL, a Content-Type header because the request has a body, and Authorization set to Bearer plus your key. Attio supports custom headers, states that forbidden header names are not supported, and says it may block others for platform security, so prove this one works before building the rest. 5. Read the status code before you read the body [Attio: the block's response variables]. The block provides the response status code and the body as variable inputs for later blocks. Branch on the status with a Condition block: a 402 means the credit balance is gone, a 429 means the workspace minute limit, and both look like an empty profile if you only ever parse the body. 6. Write the Parse JSON paths in JavaScript traversal syntax [Attio: Parse JSON, Path]. A root key is just the key name, a nested value is every key joined by dots, and an array element uses the index in brackets. Attio documents that a path evaluating to nothing returns an empty value rather than failing, which is exactly the right behaviour for a provider that returns null rather than a guess. 7. Decide what an empty answer does, then wire the write [Attio: a Condition, then a record update]. An unresolved lookup arrives as empty fields, so the record update block will happily write nothing over something. Put the condition before the write rather than after it, and the workflow stops being able to erase a value a rep typed. 8. Keep live resolution out of this workflow [Attio: not here]. The Send HTTP request block has a 20-second timeout, and a live job answers with a task id and is documented as usually seconds and possibly tens of minutes. Attio does have Delay and Loop blocks, so a bounded poll is constructible, and it is still the wrong place for it. **How to check it worked:** - Run the workflow on a record whose answer you know, then on an email that resolves to nobody. The second should leave the attributes empty rather than failing, because a path that evaluates to nothing returns an empty value. - Set one Parse JSON field to the wrong output type on purpose, a headline declared as a Number, and watch the block fail. That is the one failure mode here that is loud, and seeing it once tells you what the error looks like. - Point the Send HTTP request block at the free check endpoint and read the update date it returns. It costs nothing, it proves the Authorization header is not being stripped, and the date is what decides whether you ever want a live refresh. - Run it twice on the same record and confirm the second run overwrites nothing a rep owns. If the enrichment attributes are separate from the rep ones, as step two set them up to be, this is boring, which is the result you want. Agent skill for this pair: https://www.reversecontact.com/integrations-hub/skills/attio-reverse-contact.md **Field mapping:** - Send HTTP request, POST maps to https://api.reversecontact.com/v2/enrich/persons. Supports DELETE, GET, HEAD, PATCH, POST and PUT, with the URL, headers, Content-Type and body all built from hard-coded text or variables from earlier blocks. The block provides the response status code and body as variables for everything downstream, which is the property this whole page rests on. - An Authorization header maps to Bearer rc_your_api_key. Custom headers are supported. Attio states that forbidden header names are not, and that it may block others as needed for platform security, so test this one before assuming it. - Parse JSON, Path maps to data.currentPosition.title. Written in the same syntax you would use to traverse the object in JavaScript: a root key on its own, a nested value as dot-joined keys, an array element by index in brackets. - Parse JSON, Output Type maps to String, Number or Boolean. Three types, and Attio states the type must match what the path evaluates to or the block fails. String and String (Array) map to Text, Email Address, Domain, Select, Multi-Select, Currency, Status and Phone; Number and Number (Array) to Number and Rating; Boolean to Checkbox. - A Condition block on the status code maps to 200, 402 or 429. The three outcomes worth branching on. A 402 means the credit balance reached zero, which pauses even the free check endpoints, and a 429 means the workspace minute limit. Parsing the body alone makes both look like a person who does not exist. - A record update block maps to Your own objects and attributes. Custom objects included, which is the reason to be on Attio. The enriched attributes sit beside the ones a rep maintains instead of competing with them for the same field. - Delay and Loop blocks maps to A bounded poll, if you insist. Delay takes seconds through weeks, and Loop iterates a list with an optional limit rather than repeating until a condition. So a poll is constructible and ugly, and this is not where live resolution belongs. - Anything outbound to Reverse Contact maps to Nothing at all. This is a read layer. No Attio record or attribute is sent anywhere, and there is nothing in the product to send it to. - Does not cross: The live endpoints, sensibly. They answer with a task id, the HTTP block times out at 20 seconds, and a live job is documented as usually seconds and possibly tens of minutes. - Does not cross: A business email or a direct phone number. Both are separate endpoints at 3 and 20 credits, charged only when one is found, and the email finder is asynchronous as well. - Does not cross: A bulk backfill. Workflows are triggered per record, so the back catalogue belongs in Clay or n8n reading and writing through the Attio REST API. - Does not cross: Anything travelling back to Reverse Contact. The direction runs one way, and there is nothing in the product to write to. **What breaks:** - **Twenty seconds on the HTTP block.** Attio documents a 20-second timeout on Send HTTP request. A cached reverse lookup fits comfortably against a published 500ms P95. Anything that answers with a task to poll does not, and while Attio does have Delay and Loop blocks, Loop iterates a list with an optional limit rather than repeating until a condition is met. A bounded poll is therefore constructible and awkward, and live resolution still belongs somewhere else. - **Parse JSON fails on a type mismatch.** Each extracted field declares an output type, and Attio states that a type which does not match what the path evaluates to will fail. A field that is sometimes null and sometimes a string is exactly the shape a data layer returns, so decide what an unresolved lookup does before you add the block. - **Attio labels these blocks legacy.** The block library lists Send HTTP request and Parse JSON as legacy while Attio reworks its workflow builder. They are documented and they work, and it is a fair signal that the configuration may move. Worth knowing before a build rests on the exact field names. - **Some headers are blocked.** Custom headers are supported, and Attio states that certain headers are not and that others may be blocked as needed for platform security. The Authorization header this needs is ordinary, and it is still the first thing to test rather than assume. - **Automations are a paid feature.** Attio has a free plan and automations are on the paid plans, so the route on this page needs one. The REST API is available either way, which is the fallback if the plan is not there yet. **Failures people hit:** - The Parse JSON block failed and the workflow stopped. Why: Attio states that the output type must match what the path evaluates to or it will fail, and gives setting a name path as a Number as the example. Fix: Check the type against the three on offer. Most of a person record is a String; an employee count and a follower count are Numbers, and an is-open-to-work flag is a Boolean. - The attributes came back empty and nothing errored. Why: That is the documented behaviour of both halves. Reverse Contact returns null rather than a best guess, and Attio states that a path evaluating to nothing returns an empty value and will not fail. Fix: Nothing is broken. Put a Condition block before the record update so an empty answer writes nothing, rather than writing nothing over something. - A value a rep typed has been replaced by a blank. Why: The record update block wrote the empty result of an unresolved lookup, because no condition stood between them. Fix: Condition first, write second, and keep the provider's attributes separate from the ones a rep owns. The second half of that is why the attribute modelling is step two of the setup rather than an afterthought. - The request is rejected and the header looks right. Why: Attio supports custom headers, states that forbidden header names are not supported, and says it may block others as needed to maintain platform security. Fix: Test the Authorization header on the free check endpoint, which costs nothing. If it is being stripped you want to know that before the rest of the workflow exists. - Everything stopped at once, including the free checks. Why: Below 2 credits Reverse Contact pauses the free Check endpoints too and answers 402 NO_CREDITS, because the fetch a check precedes can itself cost 2. Fix: Branch on the status code, which the HTTP block hands you alongside the body. GET /v2/usage keeps answering whatever the balance, so a scheduled workflow can watch the balance even when nothing else works. - A 429 on a workflow that was fine yesterday. Why: Reverse Contact applies a minute limit per workspace, shared with every other integration on it, and answers 429 past it. Fix: Read quotas.minuteRateLimit from the body for limit, used, left and nextReset, and give this workflow its own key with a per-key cap so it cannot starve a Clay table running beside it. - The HTTP block timed out. Why: Attio documents a 20-second timeout on Send HTTP request, and the live endpoints answer with a task rather than a record. Fix: Use the cached endpoints here, which publish a 500ms P95. Live resolution belongs in n8n, and the Attio REST API is how the answer comes back when it arrives. - An endpoint that worked last week returns nothing. Why: /v2/resolve was replaced by /v2/enrich and /v2/search/persons by /v2/search/people, with the old pair documented as live only until 13 October 2026. Fix: Open the Send HTTP request block and change the URL. It is a hard-coded string in a workflow rather than a configuration setting, so nothing will warn you that it has stopped resolving. **What practitioners say** (14 threads from 2024 to 2026, read 2026-10-11): Nobody discusses this pair by name, so the search was for the job: keeping a CRM current without reps maintaining it. One comment recommends this exact build to a stranger, naming Attio and the reason, which is as close to a review of this page as the threads get. The rest converge on a single idea, that data quality is a system design problem rather than a discipline problem. - Somebody recommending this build, by name and for the right reason (r/b2bmarketing, March 2026, 2 points): https://www.reddit.com/r/b2bmarketing/comments/1s1eb3j/best_ai_crm_for_data_enrichment_looking_for/ - Reps should not be maintaining the CRM at all (r/CRMSoftware, February 2026, 3 points): https://www.reddit.com/r/CRMSoftware/comments/1qjuhg5/how_do_businesses_keep_crm_data_reliable_as_teams/ - Capture it without the rep's help, and judge it on friction (r/CRMSoftware, January 2026, 1 points): https://www.reddit.com/r/CRMSoftware/comments/1qjuhg5/how_do_businesses_keep_crm_data_reliable_as_teams/ - Given an Attio workspace, the advice is an API and a workflow engine (r/CRM, October 2025, 1 points): https://www.reddit.com/r/CRM/comments/1okbrcu/keeping_our_crm_up_to_date_w_linkedin/ - One primary identifier per record is what makes any of this match (r/CRMSoftware, January 2026, 1 points): https://www.reddit.com/r/CRMSoftware/comments/1qjuhg5/how_do_businesses_keep_crm_data_reliable_as_teams/ Sources: https://attio.com/help/reference/automations/legacy-workflows/legacy-workflows-block-library | https://attio.com/help/academy/workflows-course/http-and-json-blocks | https://docs.reversecontact.com/getting-started | https://docs.reversecontact.com/guides/credits | https://docs.reversecontact.com/guides/rate-limits | https://www.reversecontact.com/pricing | https://support.pipedrive.com/en/article/automations-webhook-requests | https://www.zoho.com/crm/developer/docs/functions/limits-quotas.html | https://developers.hubspot.com/docs/api-reference/legacy/automation/workflow-actions/custom-code-actions ### Pipedrive and Reverse Contact The automation can fire a request and cannot read the answer, which decides the whole build. - Built as: Built on the API, Zapier, Make or n8n - Syncs: One way, in - Moves: Contacts, Companies, Deals - Costs to turn on: Metered by usage. Setup: Hours - Requires: A Reverse Contact API key, a Pipedrive plan with automations, and somewhere outside Pipedrive to receive the webhook - Full guide: https://www.reversecontact.com/integrations-hub/reverse-contact-integrations/pipedrive-reverse-contact-integration **Verdict.** Pipedrive is the clearest case in this directory of a CRM whose automation builder looks like it can do the job and cannot quite. The webhook action exists, it is well documented and it fires on conditions you define, but the response goes nowhere, so an enrichment is always a round trip: webhook out, a worker in the middle, API call back in. Once you accept that, the build is small and the limits are generous. The mistake is designing for a one-step automation that was never possible. **What syncs:** - Trigger (out): An automation on person or organisation created, firing the webhook action to your endpoint. - The enrichment (out): Your worker, a Zap or a Make scenario POSTs to /v2/enrich/persons with the email. 2 credits on a match, free on a check. - Write-back (in): A PATCH to the Pipedrive API sets the custom fields. 10 tokens a record from the daily budget. - Anything back to Reverse Contact (out): Nothing. This is a read layer, and the worker decides which Pipedrive fields may be written. **Which editions carry it** (rows Pipedrive, columns Reverse Contact): - Lite, $14 a seat with An automation with a webhook action: No - Lite, $14 a seat with Reading what that webhook returned: No - Lite, $14 a seat with Enriching from outside, through the API: Yes - Lite, $14 a seat with Burst headroom for a backfill, per token: No - Growth, $39 a seat with An automation with a webhook action: Yes - Growth, $39 a seat with Reading what that webhook returned: No - Growth, $39 a seat with Enriching from outside, through the API: Yes - Growth, $39 a seat with Burst headroom for a backfill, per token: Workable - Premium, $59 a seat with An automation with a webhook action: Yes - Premium, $59 a seat with Reading what that webhook returned: No - Premium, $59 a seat with Enriching from outside, through the API: Yes - Premium, $59 a seat with Burst headroom for a backfill, per token: Yes - Ultimate, $79 a seat with An automation with a webhook action: Yes - Ultimate, $79 a seat with Reading what that webhook returned: No - Ultimate, $79 a seat with Enriching from outside, through the API: Yes - Ultimate, $79 a seat with Burst headroom for a backfill, per token: Yes **How to connect it** (A global admin, because creating an automation webhook is admin-only. Plus whoever runs the worker in the middle and whoever can create a Reverse Contact API key.. Half a day, most of it standing the worker up. The Pipedrive half is twenty minutes once you accept the round trip.): 1. Accept the round trip before you draw anything [A whiteboard, not Pipedrive]. The webhook action sends a body to a path and the documented fields are the webhook, the method and the body. Nothing hands the response to a later step, so the shape is always webhook out, worker in the middle, API call back in. Designing for a one-step automation is the mistake this page exists to prevent, and it is only discoverable after you have built the first half. 2. Decide where the worker lives, because that is the real build [Zapier, Make, n8n or your own host]. The native Zapier app can be the worker with no code and bills nothing when a lookup misses. An n8n instance keeps records on infrastructure you control and handles the live endpoints. Your own service is the cheapest at volume. This is the decision that determines who maintains the pair. 3. Create the fields the enrichment is allowed to own [Pipedrive: Settings, Data fields]. Custom fields, prefixed, separate from the ones a rep fills in. The write comes back through the API from outside the CRM, which means nothing in Pipedrive is standing between a bad mapping and a field somebody maintains by hand. 4. Create a dedicated automation webhook as a global admin [Pipedrive: Settings, Webhooks, + Webhooks, Automation webhook]. This action is global-admin only, and Pipedrive states that existing webhooks cannot be re-used for automations, so it has to be a new one of this specific type. If no automation webhook exists yet, the webhook action will not even appear in the automation builder. 5. End the endpoint URL with the right character [Pipedrive: the webhook, endpoint URL]. Pipedrive requires the endpoint URL to conclude with a slash, an ampersand, a question mark or an equals sign, to stop malformed URLs being assembled from a base domain and a path. It is the most specific and least guessable requirement on this page. 6. Pick a method from the three it offers [Pipedrive: the webhook action, Method]. POST, PUT or DELETE. There is no GET, which is a second reason the automation cannot fetch anything: it is built to send. Use POST and compose the body with the key-value builder or raw JSON, pulling the email straight off the record. 7. Build the write-back with the token budget in mind [Your worker, against the Pipedrive API]. The daily allowance is 30,000 base tokens times the plan multiplier times seats, and reading one record costs 2 tokens while updating one costs 10. So an enrichment round trip is about 12 tokens, and a search is 40 on its own, which is the call to avoid in a loop. 8. Respect the 429 rather than retrying through it [Your worker, reading the response headers]. Pipedrive publishes x-ratelimit-limit, x-ratelimit-remaining, x-ratelimit-reset and x-daily-requests-left on responses. Ignoring a 429 and keeping the volume up earns a 403 from Cloudflare as an HTML error page, which is a much worse failure than the one you were retrying past. **How to check it worked:** - Fire the automation once at a request bin rather than at your worker, and read the execution history. It shows the final body and path, which is the only place to confirm the record fields interpolated the way you expected. - Point the webhook at a URL that returns a 500 on purpose. Pipedrive states that a webhook which is not working or is missing authentication fails the automation execution, so you should see the automation fail rather than carry on quietly. - Run the worker on an email that resolves to nobody and confirm it writes nothing back. The lookup costs no credits on a miss, and the thing being tested is whether your worker knows the difference between an empty answer and an error. - Read x-daily-requests-left after a hundred-record backfill. That number against your seat count is what tells you whether a full-database pass is one night or a week. Agent skill for this pair: https://www.reversecontact.com/integrations-hub/skills/pipedrive-reverse-contact.md **Field mapping:** - The automation trigger maps to Nothing yet. A person or organisation created or updated, with whatever conditions you set. Pipedrive notes that automated webhooks can be triggered by all users regardless of their visibility permissions or admin status, which is worth knowing before a condition relies on ownership. - The webhook action: Webhook, Method, Body maps to POST to your worker. The three mandatory fields, plus a path appended to the webhook's base domain. Methods are POST, PUT or DELETE; there is no GET. The body is built with a key-value builder that offers the record's fields from a dropdown, or raw JSON for full control. - The response to that webhook maps to Discarded. This is the whole reason the pair has the shape it does. The documented action has a webhook, a method, a body and a path, and no output, so whatever Reverse Contact answers cannot reach a later step. - Your worker, holding the email maps to POST /v2/enrich/persons, 2 credits. Identity, the current role, history, education, skills and location on one schema. A miss returns null with a confidence score and costs nothing, because every 4xx and 5xx is free. - Your worker, holding a domain maps to POST /v2/enrich/companies, 2 credits. Firmographics from a domain or a company name. Run it on the organisation rather than once per person attached to it. - The write back in maps to PATCH a person or organisation, 10 tokens. Through the Pipedrive API with your own credential. Updating one entity costs 10 tokens and reading one costs 2, so the round trip is about 12 against a daily budget of 30,000 times the plan multiplier times seats. - A search, if you reach for one maps to 40 tokens, and 10 requests per 2 seconds. The most expensive endpoint on the budget and the only one with its own burst limit, which is identical on every plan and every authentication type. This is the call that turns a backfill into a queue. - Anything outbound to Reverse Contact maps to Only what your worker sends. Reverse Contact stores nothing back. The direction runs one way, and there is nothing in the product to write to. - Does not cross: The response to the webhook action. The documented inputs are a webhook, a method, a body and a path, and there is no output for a later step to read, which is why this build always has a worker in it. - Does not cross: A GET from inside an automation. The method list is POST, PUT and DELETE, so the automation cannot fetch anything even in principle. - Does not cross: The live endpoints. They answer with a task id and are documented as usually seconds and possibly tens of minutes, so they belong in the worker rather than anywhere near the automation. - Does not cross: A business email or a direct phone number. Both are separate endpoints at 3 and 20 credits, charged only when one is found. **What breaks:** - **The webhook action cannot use the response.** Pipedrive's documentation for the automation webhook covers the body, the path and the execution history, and describes no way to read the response into a later step. Treat it as fire and forget: the enriched fields come back through a separate API call, from whatever received the webhook. - **Global admin only, and the webhook must exist first.** The action is available to global admin users, and it will only offer webhooks already created in Settings as Automation webhooks. Existing webhooks cannot be reused. If the action is missing from the builder, that is usually why. - **Automations are a plan feature, under two names.** The support article says Advanced and higher; the pricing page sells Lite, Growth, Premium and Ultimate and lists automations from Growth. Both are Pipedrive's own pages and they use different plan names for the same gate, so check the account. - **The API budget is tokens, not calls.** The daily allowance is 30,000 base tokens times the plan multiplier, 1 on Lite rising to 7 on Ultimate, times seats. Reading one record is 2 tokens, a list is 20, an update is 10 and a search is 40. Exhausting it returns 429 until midnight in the server timezone, which may not be your midnight. - **Bursts are capped per token, every two seconds.** On top of the daily budget there is a rolling two-second window: 20 requests on Lite up to 120 on Ultimate for an API token, and 80 up to 480 for an OAuth app. Search is 10 per two seconds on every plan and every auth type, which is the one that catches a backfill. - **A failing webhook fails the automation.** Pipedrive states that if the webhook stops working or is missing authentication or permissions, the automation execution fails. Webhook executions also count against the normal automation execution limits, and pause when those are reached. **Failures people hit:** - The webhook action is not in the automation builder. Why: Pipedrive states that if webhooks are not pre-built you cannot add the webhook action, and that existing webhooks cannot be re-used for automations. Fix: Create a new webhook of the Automation webhook type in Settings, as a global admin. A regular webhook already in the account will not appear, however well it works elsewhere. - The webhook will not save and the URL looks fine. Why: Pipedrive requires the endpoint URL to conclude with a slash, an ampersand, a question mark or an equals sign, to prevent malformed URLs being assembled from a base domain and a path. Fix: Add the trailing character. It is the least guessable requirement on this page and it produces no useful error message. - The automation fires and nothing is ever enriched. Why: The webhook action sends and does not receive. The documented inputs are a webhook, a method, a body and a path, with nothing handed to a later step. Fix: Put a worker in the middle: the native Zapier app, an n8n workflow or your own service. The automation is the trigger, and the enrichment and the write-back both happen outside the CRM. - The whole automation execution failed. Why: Pipedrive states that if the webhook is not working any more or is missing authentication or permissions, the automation execution will fail. Webhook executions also count against the normal automation execution limits and pause when those are reached. Fix: Check the execution history, which shows the final body and path. A worker returning a 500 fails the automation rather than being retried quietly, which is better behaviour than it feels like at the time. - 429 on the write-back, with the daily budget nowhere near spent. Why: That is a burst limit rather than the daily one. Burst limits are per token, per user, on a rolling 2-second window: 20 requests on Lite up to 120 on Ultimate for an API token, and 80 up to 480 for an OAuth app. Fix: Pace the worker and read x-ratelimit-remaining and x-ratelimit-reset. A search is the one to watch: 10 requests every 2 seconds on every plan and every authentication type. - A 403 and an HTML page from Cloudflare. Why: Pipedrive documents that continuing to send high volume after a 429 earns a 403, returned as a Cloudflare HTML error page rather than as an API response, and that only high-volume api_token traffic is blocked this way. Fix: Stop retrying, fix the pacing, and parse the rate-limit headers instead of the clock. A worker that treats 429 as a reason to try harder turns a recoverable limit into a block. - The budget ran out earlier in the day than expected. Why: The daily token budget is shared across every user and integration on the account, and the endpoints are weighted: a list read is 20 tokens and a search is 40 against 2 for a single read. Fix: Read x-daily-requests-left, replace loops of single reads with filtered list calls, and check whether something else on the account is spending it. Admins are notified automatically as the budget nears its end. - The reset did not happen when the day did. Why: Pipedrive documents that the token budget resets at midnight in the server timezone, which may not be aligned with the timezone you are in. Fix: Schedule a backfill against the server reset rather than local midnight, and confirm the reset time by watching x-daily-requests-left rather than assuming it. **What practitioners say** (14 threads from 2023 to 2026, read 2026-10-11): Nobody discusses this pair by name, so the search was for the job: enriching an inbound Pipedrive lead before a rep calls it. One thread is somebody asking for exactly this build, and the answers in it are products rather than methods. What the threads agree on is that the enrichment and the stale-data tracking both end up outside Pipedrive, which is the conclusion this page reaches from the documentation. - Somebody asking for precisely this build, and why (r/pipedrive, June 2026, 2 points): https://www.reddit.com/r/pipedrive/comments/1uivsr6/best_way_to_enrich_inbound_leads_automatically/ - Teams already run it the way this page describes (r/pipedrive, May 2026, 1 points): https://www.reddit.com/r/pipedrive/comments/1tcvt7u/what_is_going_to_be_my_biggest_pain_using/ - The gap is acknowledged by the people answering, not just the people asking (r/pipedrive, May 2026, 1 points): https://www.reddit.com/r/pipedrive/comments/1tcvt7u/what_is_going_to_be_my_biggest_pain_using/ - What a Pipedrive consultant spends their time on is not licences (r/CRM, November 2025, 3 points): https://www.reddit.com/r/CRM/comments/1oq5hil/are_you_using_or_implementing_pipedrive_what_are/ - Input quality is a permanent battle, which is the case for not relying on inputs (r/salesforce, February 2024, 26 points): https://www.reddit.com/r/salesforce/comments/1b260v6/how_do_you_deal_with_poor_data_quality_in_a_crm/ Sources: https://support.pipedrive.com/en/article/automations-webhook-requests | https://pipedrive.readme.io/docs/core-api-concepts-rate-limiting | https://www.pipedrive.com/en/pricing | https://docs.reversecontact.com/getting-started | https://docs.reversecontact.com/guides/credits | https://docs.reversecontact.com/guides/rate-limits | https://www.reversecontact.com/pricing ### Zoho CRM and Reverse Contact A scripting language inside the CRM, and an edition gate in front of it. - Built as: Built on the API, Zapier, Make or n8n - Syncs: One way, in - Moves: Contacts, Companies - Costs to turn on: Metered by usage. Setup: Hours - Requires: A Reverse Contact API key, and Zoho CRM Enterprise or above for the in-CRM route - Full guide: https://www.reversecontact.com/integrations-hub/reverse-contact-integrations/zoho-reverse-contact-integration **Verdict.** Zoho is the only CRM here that ships a programming language, and with Enterprise it genuinely removes the middle layer: a workflow rule fires a Deluge function, invokeUrl calls Reverse Contact, and the same function writes the fields back. Thirty seconds of execution inside automation is more headroom than HubSpot gives custom code and more than Attio gives an HTTP block. Below Enterprise the honest answer is the same as everywhere else: a workflow webhook out to Zapier, Make or a worker, and the API to write back. **What syncs:** - Trigger (in): A workflow rule on lead or contact creation, calling a Deluge function. - The call (out): invokeUrl POSTs to /v2/enrich/persons with the Authorization header and the record's email. 2 credits. - The response (in): Deluge parses the JSON in the same function and maps the fields you want. - Write-back (in): zoho.crm.updateRecord sets the fields. That integration task spends an API credit as well as the function credit. **Which editions carry it** (rows Zoho CRM, columns Reverse Contact): - Button, related list, validation rule or REST API: 10 seconds with One cached lookup and one write: Fits comfortably - Button, related list, validation rule or REST API: 10 seconds with Check freshness first, refresh only if stale: Fits comfortably - Button, related list, validation rule or REST API: 10 seconds with A live refresh, polled to completion: Terminated - Button, related list, validation rule or REST API: 10 seconds with Fifty records in one run: Terminated - Workflow, blueprint or approval: 30 seconds with One cached lookup and one write: Fits comfortably - Workflow, blueprint or approval: 30 seconds with Check freshness first, refresh only if stale: Fits comfortably - Workflow, blueprint or approval: 30 seconds with A live refresh, polled to completion: Tight - Workflow, blueprint or approval: 30 seconds with Fifty records in one run: Tight - Schedule: 15 minutes with One cached lookup and one write: Fits comfortably - Schedule: 15 minutes with Check freshness first, refresh only if stale: Fits comfortably - Schedule: 15 minutes with A live refresh, polled to completion: Fits comfortably - Schedule: 15 minutes with Fifty records in one run: Fits comfortably **How to connect it** (Somebody with the Manage Extensibility permission on an Enterprise edition or above, plus whoever can create a Reverse Contact API key. Below Enterprise, whoever runs the worker instead.. Half a day for the Deluge route. Confirming the edition and the permission takes five minutes and saves most of it.): 1. Check the edition and the permission together, because they fail identically [Zoho: Setup, then profile Developer Permissions]. Functions have full access on Enterprise, CRM Plus, Ultimate and Zoho One, and Standard and Professional can reach them only through Extensions. Separately, creating one needs the Manage Extensibility permission. An admin without that permission sees exactly what somebody on the wrong edition sees, which is nothing. 2. Decide trigger or schedule, because the ceiling differs by a factor of thirty [Zoho: the function category]. A workflow, blueprint or approval function gets 30 seconds. A scheduled one gets 15 minutes. A button, related list, validation rule or REST API function gets 10. Zoho terminates anything that exceeds its category, so this choice is the design rather than a setting. 3. Create the fields the enrichment is allowed to own [Zoho: Setup, Modules and Fields]. Prefixed, and separate from anything a rep types into. The function writes with zoho.crm.updateRecord and will write exactly what you tell it, including an absent value, so the separation is what makes the pair safe to leave running. 4. Write the invokeUrl call and read the response map [Zoho: the Deluge function]. invokeUrl takes the URL, the type and the parameters, with the Authorization header carrying your key. Worth knowing before you paste it: the key lives in the function source, so anybody with Manage Extensibility can read it, which is a weaker position than a Salesforce Named Credential and stronger than a key in a third-party cloud. 5. Test for the key before you write the field [Zoho: the Deluge function, again]. Reverse Contact returns null rather than a best guess when it is not confident, so the response map simply has no key for an unresolved field. Three lines of Deluge checking for it is the difference between an enrichment that fills gaps and one that creates them. 6. Count both meters before you loop over anything [Zoho: Setup, API Dashboard]. Every function execution is one function credit, and the Deluge integration tasks inside it that touch CRM records cost API credits as well. Zoho says so explicitly, having previously had no way to identify those calls, so an enrichment loop draws down two pools at once. 7. Avoid searching from inside the function [Zoho: the Deluge function]. Search records invoked from a function is one of seven calls under the sub-concurrency limit, which is 10 across every edition. Fetching by id instead keeps you on the ordinary concurrency limit, which is 20 per org per app on Enterprise. 8. Put the bulk pass on a schedule and chunk it [Zoho: Setup, Functions, Schedule]. Fifteen minutes is generous and the 200,000 lines of execution cap is not a line count of your source: Zoho notes that loops, conditional branches and called child functions all contribute. Chunking a backfill is what keeps a scheduled pass inside both ceilings. **How to check it worked:** - Run the function on a record whose answer you know, then on an email that resolves to nobody. The second is the test: the field should be left alone rather than blanked, which is what the key check in step five is for. - Point invokeUrl at the free check endpoint and read the update date. It costs nothing, it proves the header survives, and the date is what tells you whether a live refresh would buy anything. - Run a loop over fifty records from a workflow function on purpose and watch it be terminated at 30 seconds. Seeing the category timeout fire once is cheaper than discovering it during a list import. - Open the API Dashboard and read Credits by Application and Functions after that run. It attributes consumption to the function that caused it, which is the only way to see the second meter at all. Agent skill for this pair: https://www.reversecontact.com/integrations-hub/skills/zoho-reverse-contact.md **Field mapping:** - A workflow rule on Leads or Contacts maps to Nothing yet. The trigger. A workflow, blueprint or approval function gets 30 seconds of execution, which is more headroom than a HubSpot custom code action and the same as an Attio HTTP block. - invokeUrl, inside the function maps to POST /v2/enrich/persons, 2 credits. Identity, the current role, history, education, skills and location on one schema. The call itself costs nothing from either Zoho meter, because an outbound call is not a CRM API call. - invokeUrl, from a domain maps to POST /v2/enrich/companies, 2 credits. Firmographics from a domain or a company name. Run it on the account rather than once per contact attached to it. - The response, as a Deluge map maps to success, data, error, metadata, quotas. Five keys on every endpoint. metadata.updatedAt is the one worth reading before paying for a refresh, and quotas.workspace.credits.left is how the function can see its own balance. - zoho.crm.updateRecord maps to Your own prefixed fields. Costs an API credit at the Update Records rate, because Zoho includes Deluge integration tasks in API credit consumption. Insert, update and upsert take up to 100 records per call, and the maximum credit deduction for those is 10. - A scheduled function maps to A bulk pass, with 15 minutes. Where a backfill belongs, and the only category in Zoho with enough runtime to poll a live job to completion. Zoho recommends designing long-running logic here explicitly. - A workflow webhook, below Enterprise maps to Zapier, Make or your own worker. The fallback when functions are not available. The shape is then identical to the Pipedrive build: out to a worker, enrich, and back in through the API. - Anything outbound to Reverse Contact maps to Nothing at all. This is a read layer. No Zoho record or field is sent anywhere, and there is nothing in the product to send it to. - Does not cross: A marketplace app inside Zoho. Reverse Contact maintains apps on Clay, Zapier and Make and nothing inside any CRM, so the in-CRM route is one you write rather than one you install. - Does not cross: Functions on Standard or Professional, other than through Extensions. Zoho states that full access begins at Enterprise, CRM Plus, Ultimate and Zoho One. - Does not cross: A business email or a direct phone number. Both are separate endpoints at 3 and 20 credits, charged only when one is found, and the email finder is asynchronous as well. - Does not cross: Anything travelling back to Reverse Contact. The direction runs one way and there is nothing in the product to write to. **What breaks:** - **Functions in full are Enterprise and above.** Zoho states that Functions are available on Enterprise, CRM Plus, Ultimate and Zoho One with full access, and that Standard and Professional can only access them through Extensions. The in-CRM route on this page therefore starts at Enterprise, and the fallback below it is a workflow webhook to something else. - **Thirty seconds inside automation, ten elsewhere.** Category timeouts are 30 seconds for workflow, blueprint and approval, 10 seconds for a button, related list, validation rule or REST API call, and 15 minutes on a schedule. A function that exceeds its category is terminated. Put a bulk pass on a schedule rather than hoping a button will carry it. - **Two meters, and the second one is quiet.** A function execution is one function credit; the Deluge integration tasks inside it that read or write CRM records are counted as API credits as well. Zoho says so explicitly, having previously not counted them. An enrichment loop therefore draws down both pools, and the API pool is the smaller one on Standard at 100,000 a day maximum. - **API limits are credits and concurrency, not calls a minute.** The allowance is 50,000 credits plus 250 to 2,000 per user licence in a rolling 24 hours, capped at 100,000 on Standard and 3,000,000 on Professional, with 5,000 on the free edition. There is no per-minute limit; instead concurrency caps simultaneous calls per org per app at 5 on free rising to 20 on Enterprise. - **You need the Manage Extensibility permission.** Creating and managing functions requires that permission under Developer Permissions in profile settings. An admin without it sees no option to create one, which reads like an edition problem and is not. **Failures people hit:** - There is no option to create a function anywhere. Why: Two causes that look identical. Functions have full access on Enterprise, CRM Plus, Ultimate and Zoho One, with Standard and Professional reaching them only through Extensions. Separately, creating and managing them needs the Manage Extensibility permission under Developer Permissions. Fix: Check the permission before the edition, because it is the cheaper of the two to fix and an admin without it sees exactly what somebody on the wrong edition sees. - The function was terminated partway through. Why: Zoho enforces a timeout by category: 10 seconds for a button, related list, validation rule or REST API call, 30 seconds for workflow, blueprint and approval, and 15 minutes on a schedule. Fix: Move the work to the Schedule category, which Zoho recommends for long-running logic. There is no setting to raise a category timeout, so this is a move rather than a tweak. - The function hit the lines of execution limit. Why: A single invocation is capped at 200,000 lines of execution, and Zoho notes this counts lines the runtime actually executes: loops, conditional branches and called child functions all contribute. Fix: Chunk the loop rather than widening it. A scheduled pass over records in batches counts far fewer lines than one that re-reads a collection on every iteration. - The API credit pool emptied and nothing called the API. Why: Deluge integration tasks count as API credit consumption. Zoho changed this deliberately, having had no way to identify calls made through them, so zoho.crm.searchRecords costs the same as the Search Records API. Fix: Open Credits by Application and Functions on the API Dashboard, which attributes consumption to the function that caused it. The X-API-CREDITS-REMAINING header appears on responses once you pass half the daily limit. - TOO_MANY_REQUESTS from a function making very few calls. Why: That is the sub-concurrency limit, which is 10 across every edition and applies to seven expensive calls including search records invoked from a function, the Query API and the Composite API. Fix: Fetch by id rather than searching from inside the function. Zoho notes that sub-concurrency does not apply to integration tasks at all, so the same work routed that way is subject only to the ordinary concurrency limit. - The function wrote an empty value over a real one. Why: Reverse Contact returns null rather than a best guess when it is not confident, so the response map has no key at all for an unresolved field and Deluge writes the absence. Fix: Test for the key before writing it, and keep the enrichment in prefixed fields of its own. Three lines of Deluge separate an enrichment that fills gaps from one that creates them. - A live refresh timed out inside the workflow function. Why: The live endpoints answer with a webhookId rather than a record, and the workflow category allows 30 seconds against a job documented as usually seconds and possibly tens of minutes. Fix: Move the live path to a scheduled function, where the ceiling is 15 minutes and the poll fits. Polling is free and off the rate-limit clock, so the only costs are the function credit and the waiting. - An endpoint that worked last week returns nothing. Why: /v2/resolve was replaced by /v2/enrich and /v2/search/persons by /v2/search/people, with the old pair documented as live only until 13 October 2026. Fix: Search your functions for both old paths and change every invokeUrl that carries one. The strings are in Deluge source, so one text search finds all of them, which is a genuine advantage of keeping this inside the CRM. **What practitioners say** (14 threads from 2024 to 2026, read 2026-10-11): Nobody discusses this pair by name, so the search was for the job: enriching a Zoho lead automatically as it arrives. The best thread is a Zoho user asking twice for a way to do it without Zapier or Make, and getting product recommendations instead of the answer, which is that Zoho can make the call itself from Enterprise up. That gap between what the product does and what its users know it does is this page. - A Zoho user asking for the thing Zoho already does (r/CRM, July 2024, 1 points): https://www.reddit.com/r/CRM/comments/1e67lf0/need_recommendations_for_a_data_enrichment_tool/ - The answer people give instead is a provider plus a connector (r/CRM, August 2025, 2 points): https://www.reddit.com/r/CRM/comments/1e67lf0/need_recommendations_for_a_data_enrichment_tool/ - The problem is stated the same way whichever CRM is in the question (r/CRM, July 2025, 3 points): https://www.reddit.com/r/CRM/comments/1mb49xl/how_do_you_keep_your_crm_data_updated_without/ - Cleaning is not the same job as keeping clean (r/CRM, July 2024, 3 points): https://www.reddit.com/r/CRM/comments/1efuuio/bad_data_in_our_crm/ - The durable part is process rather than tooling (r/CRM, July 2024, 2 points): https://www.reddit.com/r/CRM/comments/1efuuio/bad_data_in_our_crm/ Sources: https://www.zoho.com/crm/developer/docs/functions/limits-quotas.html | https://www.zoho.com/crm/developer/docs/api/v8/api-limits.html | https://www.zoho.com/crm/zohocrm-pricing.html | https://docs.reversecontact.com/getting-started | https://docs.reversecontact.com/guides/credits | https://docs.reversecontact.com/guides/rate-limits | https://www.reversecontact.com/pricing ### monday CRM and Reverse Contact A thousand API calls a day until Pro, which is the whole design constraint. - Built as: Built on the API, Zapier, Make or n8n - Syncs: One way, in - Moves: Contacts, Companies, Custom objects - Costs to turn on: Metered by usage. Setup: Hours - Requires: A Reverse Contact API key, a monday plan with automations, and a receiver for the webhook - Full guide: https://www.reversecontact.com/integrations-hub/reverse-contact-integrations/monday-reverse-contact-integration **Verdict.** monday CRM is the least opinionated CRM in this directory and the most constrained to enrich, for one reason that has nothing to do with features: 1,000 API calls a day until you reach Pro. Everything else works. Webhooks are solid, the GraphQL API is pleasant, columns take whatever you write into them. But a read and a write per record against a four-figure daily ceiling means this is a trickle rather than a sweep until the plan changes, and the right build is one that enriches on creation and never backfills. **What syncs:** - Trigger (out): A webhook on create_item or a column change, verified with monday's challenge handshake. - The enrichment (out): Your receiver, a Zap or a Make scenario calls /v2/enrich/persons with the email from the item. 2 credits. - Write-back (in): A GraphQL change_multiple_column_values mutation sets the columns. One call against the daily count. - Anything back to Reverse Contact (out): Nothing. This is a read layer, and the receiver decides which columns may be written. **Which editions carry it** (rows Reverse Contact, columns monday CRM): - Enrich 100 new items a day with Free, Basic or Standard: Comfortable - Enrich 100 new items a day with Pro: Comfortable - Enrich 100 new items a day with Enterprise: Comfortable - Enrich 500 a day with Free, Basic or Standard: At the limit - Enrich 500 a day with Pro: Comfortable - Enrich 500 a day with Enterprise: Comfortable - Enrich 2,000 a day with Free, Basic or Standard: Over the daily budget - Enrich 2,000 a day with Pro: Comfortable - Enrich 2,000 a day with Enterprise: Comfortable - Backfill 20,000 items in one pass with Free, Basic or Standard: Over the daily budget - Backfill 20,000 items in one pass with Pro: Over the daily budget - Backfill 20,000 items in one pass with Enterprise: At the limit - Run it beside another integration with Free, Basic or Standard: Over the daily budget - Run it beside another integration with Pro: At the limit - Run it beside another integration with Enterprise: Comfortable **How to connect it** (Somebody who can create a monday app and an OAuth token, plus whoever hosts the webhook receiver and whoever can create a Reverse Contact API key.. A day. The challenge handshake is twenty minutes and the volume arithmetic in step one is what decides whether the rest is worth doing.): 1. Do the volume arithmetic before anything else, because it may end the project [A calculator, not monday]. The daily API call limit is 1,000 on Free, Basic and Standard, 10,000 on Pro and 25,000 on Enterprise, resetting at midnight UTC and shared with every other integration on the account. An enrichment round trip is at least one read and one write, so anything below Pro is a few hundred records a day and never a backfill. 2. Decide which columns the enrichment owns, and write down their ids [monday: the board]. A board is columns somebody named rather than a contact object with agreed semantics. Mutations address columns by id, so renaming one in the interface breaks nothing and duplicating a board for another team produces new ids that break everything silently. Write the ids down somewhere outside monday. 3. Build the receiver and answer the challenge first [Your own host, or n8n]. monday posts a randomly generated token in a challenge field to prove you control the URL, and expects the identical value returned in a challenge field of your JSON response. A receiver that does not implement that cannot be registered at all, so this is step one of the build rather than a detail. The URL is also capped at 255 characters. 4. Create the webhook with an integration app token, not a personal one [monday: a monday app with an integration feature]. Two things follow from doing it this way. Requests then carry a JWT in the Authorization header that you can verify against the app Signing Secret, and end users cannot disable the webhook, which monday documents as deliberate so a curious user cannot toggle an integration off. 5. Subscribe to the narrowest event you can [monday: the create_webhook mutation]. The mutation takes a board, a url, an event and a config, so a status-column event can be scoped to one column and one value. Every event that fires is a round trip against a four-figure daily budget, so the filter is the budget. 6. Enrich in the receiver, not in monday [Your worker, or an n8n workflow]. monday has no HTTP step in its automations, so the call to Reverse Contact always happens outside. That also means the live endpoints are available here in a way they are not on most of these pages, because a worker can poll and a CRM automation cannot. 7. Write back with change_multiple_column_values rather than one call per field [Your worker, against the monday API]. One mutation carrying every enriched column is one call against the daily limit; six mutations are six. On a 1,000-call budget that distinction is the difference between 400 records a day and 70. 8. Read the RateLimit headers and throttle before you are throttled [Your worker, on every response]. monday returns RateLimit-Policy and RateLimit headers in the IETF format, reporting minuteRate, concurrency and complexityMinute with a remaining value and a reset. Every rate-limit error also carries retry_in_seconds. Honouring those is cheaper than retrying, because all requests count toward the limits even when they fail. **How to check it worked:** - Register the webhook and confirm it was accepted. monday will not create one against a URL that fails the challenge, so a successful registration is itself the proof that half the build works. - Trigger the event once and verify the JWT in the Authorization header against the app Signing Secret. Doing it on the first event rather than later is what stops the receiver quietly accepting anything that finds the URL. - Run twenty records through and read the RateLimit header on the last response. The remaining value against your tier is what turns the volume arithmetic in step one from an estimate into a measurement. - Write to a column id you have deliberately mistyped. The mutation does not error in a way that looks like a mistake, which is exactly why the column ids belong written down. Agent skill for this pair: https://www.reversecontact.com/integrations-hub/skills/monday-reverse-contact.md **Field mapping:** - A board event maps to Nothing yet. Created through the create_webhook mutation with a board, a url, an event and a config, so an event can be scoped to one column and one value. Custom automations are metered separately from API calls, starting at 250 a month on Standard and rising to 25,000 on Pro. - The webhook payload maps to Your receiver, over POST. Carries a JWT in the Authorization header when the webhook was created with an integration app token, verifiable against the app Signing Secret. Requests retry once a minute for thirty minutes, so a receiver that is briefly down loses nothing. - Your worker, holding an email maps to POST /v2/enrich/persons, 2 credits. Identity, the current role, history, education, skills and location on one schema. Costs nothing on a miss, because every 4xx and 5xx is free, and nothing from monday's budget either because it is not a monday call. - Your worker, holding a domain maps to POST /v2/enrich/companies, 2 credits. Firmographics from a domain or a company name. Worth running once per account board item rather than once per person linked to it, which also halves the monday calls. - A live refresh, if you want one maps to POST /v2/fetch/persons/live, 2 credits. Genuinely available on this route, unlike most of the CRM pages here, because the worker is outside monday and can poll. Polling is free and off the rate-limit clock. - change_multiple_column_values maps to Every enriched column, in one call. The mutation that matters for the budget. One call carrying six values costs one of your daily allowance; six calls cost six, and on 1,000 a day that decides your throughput. - A column id maps to Not a column name. Mutations address columns by id. Renaming a column in the interface is harmless and duplicating a board mints new ids, so a write can land nowhere without anything reporting a failure. - Anything outbound to Reverse Contact maps to Only what your worker sends. This is a read layer. Nothing travels back, and there is nothing in the product to write to. - Does not cross: An HTTP step inside a monday automation. There is none, which is why this build always has a receiver in it and why the enrichment is never a monday feature. - Does not cross: A contact object with agreed fields. A board is columns somebody named, addressed by id, so there is no schema for a mapping to be wrong about and no schema to protect you either. - Does not cross: A business email or a direct phone number. Both are separate Reverse Contact endpoints at 3 and 20 credits, charged only when one is found. - Does not cross: A backfill on anything below Pro. One thousand calls a day shared across every integration on the account is a few hundred records, and the limit resets at midnight UTC rather than at yours. **What breaks:** - **1,000 API calls a day on Basic and Standard.** The daily call limit resets at midnight UTC and is 1,000 on Free, Basic and Standard, 10,000 on Pro and 25,000 on Enterprise, and it is shared across every personal token, private app and public app on the account. Exceeding it returns DAILY_LIMIT_EXCEEDED. An enrich-and-write loop is at least one call per record, so plan the volume against the plan before anything else. - **Complexity is a second, separate budget.** Reads and writes have a complexity budget of 5,000,000 points a minute each on an app token, 10,000,000 combined on a personal token, and 1,000,000 on trial, NGO and free accounts, on a sliding 60-second window. A single query may not exceed 5,000,000 points. Add a complexity field to a query to see the cost before you run it at scale. - **Automations are metered too, and separately.** Custom automations start at Standard with 250 a month and rise to 25,000 on Pro. That is the budget the trigger comes out of, and it is independent of the daily API call count that the write-back spends. - **The webhook endpoint must answer a challenge.** monday posts a randomly generated token in a challenge field when the webhook is created, and expects the identical value back in a challenge field of the response. A receiver that does not implement it cannot be registered. The URL is also capped at 255 characters. - **A board is columns, not a schema.** There is no contact object with agreed semantics, only columns somebody named. That makes the write flexible and makes the mapping fragile: renaming a column in the interface does not break the mutation, which addresses columns by id, but duplicating a board for a new team produces new column ids and silently breaks nothing until the first write lands nowhere. **Failures people hit:** - DAILY_LIMIT_EXCEEDED halfway through the afternoon. Why: The daily call limit is 1,000 on Free, Basic and Standard, 10,000 on Pro and 25,000 on Enterprise, shared across every personal token, private app and public app on the account. Fix: Collapse the write into one change_multiple_column_values call, narrow the webhook event, and find out what else on the account is spending the budget. An increase can be requested through the API analytics dashboard if the account consistently exceeds it. - The webhook will not register at all. Why: monday posts a randomly generated token in a challenge field to verify you control the URL, and expects the identical value back in a challenge field of your JSON response body. The URL is also capped at 255 characters. Fix: Implement the challenge before anything else. It is four lines in most frameworks, and no webhook exists until it passes. - An end user turned the integration off. Why: A webhook created with a personal token can be toggled by end users. monday documents that webhooks created with an integration app token cannot, specifically so an app is not disrupted by a curious user. Fix: Create a monday app with an integration feature, generate an OAuth token for it, and call create_webhook with that. The same change is what puts a verifiable JWT in the Authorization header. - The write reported success and the column is empty. Why: Mutations address columns by id rather than by name, so a wrong id is a well-formed mutation against a column that is not the one you meant. Fix: Keep the column ids written down outside monday, and re-check them after any board is duplicated. Duplicating a board for a new team mints new ids and breaks nothing visibly until the first write. - ComplexityException on a query that looks small. Why: Complexity is a separate budget from the call count: 5,000,000 points for a single query, and a per-minute budget on a sliding window that is 1,000,000 on trial, NGO and free accounts. Fix: Add the complexity field to the query to read the cost before and after, request only the fields you need, reduce nesting, and use the page and limit arguments. monday recommends exactly those three. - Retries made everything worse. Why: All requests count toward the limits even when they fail, and every rate-limit error carries a retry_in_seconds field that a retry loop usually ignores. Fix: Read the RateLimit header, which reports minuteRate, concurrency and complexityMinute with a remaining value and a reset in seconds, and throttle before the remaining value reaches zero. - The lookup came back empty and the column was blanked. Why: Reverse Contact returns null rather than a best guess when it is not confident, and a worker that maps the response straight into a mutation writes the absence. Fix: Branch in the worker on the field being present and omit it from the mutation otherwise. A column left alone costs nothing; a column overwritten with nothing costs a rep's trust in the board. - An endpoint that worked last week returns nothing. Why: /v2/resolve was replaced by /v2/enrich and /v2/search/persons by /v2/search/people, with the old pair documented as live only until 13 October 2026. Fix: Change both paths in the worker. This is the one route where that fix is in ordinary version-controlled code rather than inside a CRM automation nobody can diff. **What practitioners say** (14 threads from 2022 to 2026, read 2026-10-11): Nobody discusses this pair by name, so the search was for the job: filling monday board columns from outside and getting any value from it. The best thread is somebody asking whether enrichment was worth buying at all, because their reps ignored the twenty new fields, and the answers to it are the most useful editorial guidance in the whole harvest. On a pair with a four-figure daily call ceiling, picking fewer fields is also the cheapest thing you can do. - A field that changes nothing is a field not worth a call (r/CRMSoftware, October 2026, 1 points): https://www.reddit.com/r/CRMSoftware/comments/1wy7xg8/whats_the_point_of_data_enrichment_if_the_sales/ - The question that opens the thread is the one to ask before buying anything (r/CRMSoftware, October 2026, 3 points): https://www.reddit.com/r/CRMSoftware/comments/1wy7xg8/whats_the_point_of_data_enrichment_if_the_sales/ - Give the rep one line rather than twenty fields (r/CRMSoftware, October 2026, 1 points): https://www.reddit.com/r/CRMSoftware/comments/1wy7xg8/whats_the_point_of_data_enrichment_if_the_sales/ - The test for whether a field earns its column (r/CRMSoftware, October 2026, 1 points): https://www.reddit.com/r/CRMSoftware/comments/1wy7xg8/whats_the_point_of_data_enrichment_if_the_sales/ - The monday answer, when people ask, is always a middle layer (r/mondaydotcom, January 2025, 2 points): https://www.reddit.com/r/mondaydotcom/comments/1ib1kxy/linkedin_add_on_for_monday_crm/ Sources: https://developer.monday.com/api-reference/docs/rate-limits | https://developer.monday.com/api-reference/reference/webhooks | https://monday.com/crm/pricing | https://docs.reversecontact.com/getting-started | https://docs.reversecontact.com/guides/credits | https://docs.reversecontact.com/guides/rate-limits | https://www.reversecontact.com/pricing ### Outreach and Reverse Contact 10,000 requests an hour per user, and nothing to install inside Outreach. - Built as: Built on the API, Zapier, Make or n8n - Syncs: One way, in - Moves: Contacts, Companies - Costs to turn on: Metered by usage. Setup: Hours - Requires: A Reverse Contact API key and Outreach API access through an OAuth app - Full guide: https://www.reversecontact.com/integrations-hub/outreach-integrations/outreach-reverse-contact-integration **Verdict.** Outreach is the easiest sequencer in this directory to enrich against, and the reason is mundane: the rate limit is 10,000 an hour per user rather than a shared team budget, so a backfill over an existing prospect list is an ordinary thing to do rather than a negotiation. There is nothing to install, which is consistent with how Reverse Contact ships everywhere, and the real work is deciding what happens to a prospect whose lookup returned null before a cadence picks them up. **What syncs:** - Trigger (out): A webhook on prospect created, or a scheduled sweep over prospects missing a title. - The enrichment (out): POST /v2/enrich/persons with the prospect email. 2 credits on a match, free for a prior freshness check. - Write-back (in): PATCH the Outreach prospect with title, company, seniority and whatever else the schema holds. - Cadence entry (in): Gate it on the enrichment having resolved, so an unknown prospect does not get the generic first touch. **Which editions carry it** (rows Outreach, columns Reverse Contact): - Outreach: 10,000 an hour, per user with The budget is yours rather than shared: Yes - Outreach: 10,000 an hour, per user with A full backfill is an ordinary thing to do: Yes - Outreach: 10,000 an hour, per user with No documented surcharge for deep paging: Yes - Outreach: 10,000 an hour, per user with The key travels in a header, not a URL: Yes - Salesloft: 600 cost a minute, per team with The budget is yours rather than shared: No - Salesloft: 600 cost a minute, per team with A full backfill is an ordinary thing to do: Partly - Salesloft: 600 cost a minute, per team with No documented surcharge for deep paging: No - Salesloft: 600 cost a minute, per team with The key travels in a header, not a URL: Yes - Smartlead Standard: 1,000 an hour, per key with The budget is yours rather than shared: Partly - Smartlead Standard: 1,000 an hour, per key with A full backfill is an ordinary thing to do: No - Smartlead Standard: 1,000 an hour, per key with No documented surcharge for deep paging: Yes - Smartlead Standard: 1,000 an hour, per key with The key travels in a header, not a URL: No - lemlist: 20 per 2 seconds, per key with The budget is yours rather than shared: Partly - lemlist: 20 per 2 seconds, per key with A full backfill is an ordinary thing to do: Partly - lemlist: 20 per 2 seconds, per key with No documented surcharge for deep paging: Yes - lemlist: 20 per 2 seconds, per key with The key travels in a header, not a URL: Yes - Instantly: 6,000 a minute, per workspace with The budget is yours rather than shared: No - Instantly: 6,000 a minute, per workspace with A full backfill is an ordinary thing to do: Yes - Instantly: 6,000 a minute, per workspace with No documented surcharge for deep paging: Yes - Instantly: 6,000 a minute, per workspace with The key travels in a header, not a URL: Yes **How to connect it** (Somebody who can register an OAuth app in Outreach, plus whoever hosts the middle layer and whoever can create a Reverse Contact API key.. A day. The OAuth app is the slow part and the enrichment itself is an afternoon.): 1. Decide where enrichment sits relative to cadence entry, because it cannot be undone [Your own process, not a settings screen]. A sequencer renders the first touch from whatever the prospect record holds at send time. Enriching somebody already two steps into a cadence improves the fourth email and cannot repair the first, which is the one that decided the reply. Everything else on this page is reversible and this is not. 2. Decide which prospect fields the enrichment owns [Outreach: custom fields on Prospect]. Use custom fields rather than the ones a rep edits between calls. A sequencer is the one place in a stack where a wrong value is not merely untidy: it is sent to somebody, with your name on it, and no later correction reaches them. 3. Register an OAuth application and ask for the narrowest scopes [Outreach: the developer portal]. There is no app to install and nothing in Outreach that calls an external API, so the only way in is the API itself. Reading and writing prospects needs prospects.read and prospects.write; asking for more is a conversation with whoever approves it. 4. Read X-RateLimit-Limit from a live response rather than hard-coding the number [Any Outreach API response]. The documented limit is 10,000 requests an hour per user, and Outreach states in as many words that it reserves the right to adjust limits at any time. Every response carries X-RateLimit-Limit, X-RateLimit-Remaining and X-RateLimit-Reset, the last aliased as Retry-After. 5. Check before you fetch, on the endpoint that costs nothing [POST /v2/fetch/persons/check]. The free check says whether a profile is cached and when it was last updated, so a sweep over an existing prospect list spends 2 credits only on the records that need it. On a list of any size this is the difference between a budget and a bill. 6. Write the suppression rule before the enrichment rule [Your middle layer]. The response carries more reasons not to send than reasons to send. A current employer that disagrees with the account on the prospect, an isInRemembrance flag, an isOpenToWork flag: each one is a prospect who should leave the cadence rather than receive a better version of it. 7. PATCH the prospect, then let the cadence pick it up [Outreach: PATCH /api/v2/prospects/:id]. Update the record first and add to the cadence second, in that order, every time. The sequence of those two calls is the whole content of this build, and getting it the other way round is the mistake step one is about. 8. Run a hundred prospects before you run the list [Your middle layer, with a limit on it]. At 10,000 an hour per user you have room to be careless, which is its own hazard. A hundred-record pass tells you the real resolved rate on your own list, and that number rather than any published match rate is what decides whether the rest is worth running. **How to check it worked:** - Enrich one prospect, then look at the rendered preview of the first cadence step for that person. The preview is the only place you see what the recipient will see, and it is where a fallback that reads badly becomes obvious. - Run the free check on a prospect you know is current and read the update date. If it is recent, a 2-credit live refresh buys you nothing, and knowing that on one record saves it on thousands. - Enrich somebody whose current employer differs from the account they are filed under, deliberately. Your suppression rule should pull them out of the cadence, and this is the one test that proves the rule exists. - Read X-RateLimit-Remaining after a hundred-record pass. That number against the hour tells you whether a full backfill is one sitting or several, and it is per user, so it is yours rather than the team's. Agent skill for this pair: https://www.reversecontact.com/integrations-hub/skills/outreach-reverse-contact.md **Field mapping:** - Prospect emails maps to POST /v2/enrich/persons, 2 credits. Identity, the current role, history, education, skills and location on one schema. A miss returns null with a confidence score and costs nothing at all, because every 4xx and 5xx is free. - Account domain maps to POST /v2/enrich/companies, 2 credits. Firmographics from a domain or a company name. Run it on the account rather than once per prospect attached to it, which is both cheaper and more consistent. - A profile URL already on the prospect maps to POST /v2/fetch/persons, 1 credit. Half the price, and unmetered from the $249 plan rather than the $699 one. Prospects sourced from a profile rather than from a form often already carry one. - currentPosition.title maps to Prospect title, in a custom field. The field most cadence openers reference, and the one most likely to be out of date on a list built six months ago. - currentPosition.companyName maps to A suppression check, not a field. Compare it with the account the prospect is filed under. A disagreement is the single most useful signal on this page: that person has moved, and the cadence written for their old job is about to reach their new one. - metadata.updatedAt maps to A custom date field. When the record was last updated. Store it, and the next sweep can skip everything refreshed recently instead of paying to re-resolve it. - Prospect update maps to PATCH /api/v2/prospects/:id. One request against a limit of 10,000 an hour per user. Write the custom fields and leave the rep-maintained ones alone. - Anything outbound to Reverse Contact maps to Only what your middle layer sends. This is a read layer. No prospect, cadence or activity is sent anywhere, and there is nothing in the product to send it to. - Does not cross: An app inside Outreach. There is no listing and nothing in the product that calls an external API, which is consistent with Reverse Contact maintaining apps on Clay, Zapier and Make and nothing inside any CRM or sequencer. - Does not cross: A business email or a direct phone number. Both are separate endpoints at 3 and 20 credits, charged only when one is found, and the email finder is asynchronous. - Does not cross: Anything that repairs an email already sent. A sequencer renders at send time, so enrichment after cadence entry improves later steps and nothing before them. - Does not cross: The Kaia endpoints, which are a different product with their own limits: 3 API calls a second and 6,000 a day, applied at org level rather than per user. **What breaks:** - **10,000 requests an hour, per user.** Outreach documents the limit as per-user rather than per-org, which is the opposite of how Salesloft meters the same thing. Bulk endpoints and Kaia have their own rules, and Kaia specifically is 3 calls a second and 6,000 a day at org level. - **Outreach reserves the right to change it.** The documentation says so in as many words, which is worth quoting to anyone designing a backfill around the current figure. Read X-RateLimit-Limit from a live response rather than hard-coding 10,000. - **Nothing is installed inside Outreach.** There is no app, no marketplace listing and no in-product step that calls an external API. Everything on this page is assembled from a webhook, something in the middle, and the Outreach API. Budget for the middle thing existing and being owned by somebody. - **Enrichment after cadence entry is wasted.** A sequencer renders the first touch from whatever the record holds at send time. Enriching a prospect that is already two steps into a cadence improves the fourth email and cannot repair the first, which is the one that decided the reply. - **Under 2 credits the free checks stop too.** When the Reverse Contact workspace has fewer than 2 credits left, even the free check endpoints return 402 rather than a result. A sweep designed to check cheaply first fails at the check rather than at the enrichment. **Failures people hit:** - The first email went out with the old job title in it. Why: A sequencer renders each step from the record as it stands at send time, and the prospect was added to the cadence before the enrichment ran. Fix: Enrich first, add to the cadence second, with no exceptions. Nothing repairs a sent email, which is why this is the one ordering decision on the page that matters. - A beautifully personalised email reached somebody who left the company. Why: The enrichment wrote a title and nobody compared the returned current employer with the account the prospect sits under. Fix: Compare currentPosition.companyName against the account and route disagreements out of the cadence. This is three lines in the middle layer and it is the highest-value check on the page. - A 429 and a rateLimitExceeded error. Why: Outreach rate-limits per user at 10,000 requests an hour, and bulk endpoints and Kaia apply their own rules, with Kaia at 3 calls a second and 6,000 a day at org level. Fix: Read X-RateLimit-Remaining and honour X-RateLimit-Reset, which is aliased as Retry-After. The error body names the limit it thinks you exceeded and the time it resets, which is more than most APIs give you. - The limit changed and the backfill stopped halfway. Why: Outreach states that it reserves the right to adjust API rate limits at any time to safeguard platform performance and ensure fair use. Fix: Read X-RateLimit-Limit from a live response rather than hard-coding 10,000. A worker that discovers its own ceiling survives a change that a worker with a constant in it does not. - The prospect record was updated and the cadence step did not change. Why: Steps already rendered and sent are gone, and a step scheduled for later picks up the current record. There is nothing to re-render. Fix: Check the rendered preview of the next step rather than the record. If the cadence has moved past the step that used the field, the enrichment improved nothing a recipient will see. - Everything stopped, including the calls that were free. Why: Below 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. Fix: Watch quotas.workspace.credits.left, which rides on every response. GET /v2/usage keeps answering whatever the balance, so a scheduled balance check never fails for the reason the lookup did. - The resolved rate is far below the published match rate. Why: A published figure is a global average over a provider's whole corpus and your list is not that corpus. Reverse Contact publishes 70%+ as an identity match rate and says to measure your own. Fix: Run 500 of your own rows and count. That number is the one that decides the economics of this build, and nothing else is a substitute for it. - An endpoint that worked last week returns nothing. Why: /v2/resolve was replaced by /v2/enrich and /v2/search/persons by /v2/search/people, with the old pair documented as live only until 13 October 2026. Fix: Change both paths in the middle layer. On this route that is ordinary version-controlled code, which is one advantage of there being no app to configure. **What practitioners say** (14 threads from 2023 to 2026, read 2026-10-11): Nobody discusses this pair by name, so the search was for the job: enriching a prospect before a cadence touches them. The threads are about where the research happens rather than which tool does it, and they agree on the ordering this page argues for. The most useful contribution is from somebody whose enrichment quality was good enough to pass and not good enough to score on, which is the failure that looks like success. - The question is asked as a workflow question, not a tool question (r/LeadGeneration, July 2025, 2 points): https://www.reddit.com/r/LeadGeneration/comments/1m9t2y1/best_ways_to_enrich_prospect_data_before_outreach/ - The enrichment runs before the record is worth sequencing (r/LeadGeneration, July 2025, 1 points): https://www.reddit.com/r/LeadGeneration/comments/1m9t2y1/best_ways_to_enrich_prospect_data_before_outreach/ - Enrichment good enough to pass and not good enough to score on (r/nocode, April 2026, 1 points): https://www.reddit.com/r/nocode/comments/1s3yg00/i_built_a_full_lead_enrichment_scoring_outreach/ - Keep a human review step until you have measured it (r/openclaw, March 2026, 6 points): https://www.reddit.com/r/openclaw/comments/1qy1o5e/im_evaluating_openclaw_for_b2b_sales_automation/ - Where the list comes from still decides the outcome (r/LeadGeneration, August 2025, 1 points): https://www.reddit.com/r/LeadGeneration/comments/1m9t2y1/best_ways_to_enrich_prospect_data_before_outreach/ Sources: https://developers.outreach.io/api/getting-started | https://developer.salesloft.com/docs/platform/api-basics/rate-limits/ | https://api.smartlead.ai/guides/rate-limits | https://developer.lemlist.com/api-reference/getting-started/rate-limits | https://developer.instantly.ai/getting-started/rate-limit | https://docs.reversecontact.com/getting-started | https://docs.reversecontact.com/guides/credits | https://docs.reversecontact.com/guides/rate-limits | https://www.reversecontact.com/pricing ### Salesloft and Reverse Contact One rate limit for the whole team, so your integration competes with the others. - Built as: Built on the API, Zapier, Make or n8n - Syncs: One way, in - Moves: Contacts, Companies - Costs to turn on: Metered by usage. Setup: Hours - Requires: A Reverse Contact API key, and Salesloft API access through an API key or an OAuth app - Full guide: https://www.reversecontact.com/integrations-hub/reverse-contact-integrations/salesloft-reverse-contact-integration **Verdict.** Salesloft enriches the same way Outreach does and meters it completely differently, and the metering is the page. Six hundred cost a minute for the entire team means an enrichment sweep is not a private decision: it spends the same budget as the CRM sync, the dialler and the conversation intelligence tool. The build itself is ordinary, a webhook on cadence membership, a lookup, a PATCH back. The planning is working out what is already spending the budget before you add to it. **What syncs:** - Trigger (out): A webhook on person_created, or cadence_membership_created to catch someone as they enter a cadence. - The enrichment (out): POST /v2/enrich/persons with the person's email. 2 credits on a match, nothing for a freshness check. - Write-back (in): PATCH the Salesloft person with title, company and seniority. Each call draws from the team cost budget. - Anything back to Reverse Contact (out): Nothing. This is a read layer, and your middle step decides what Salesloft is allowed to receive. **Which editions carry it** (rows Salesloft, columns Reverse Contact): - Pages 1 to 100, at 1 point each with A hundred requests fit inside one minute: Yes - Pages 1 to 100, at 1 point each with Room left for the rest of the team: Yes - Pages 1 to 100, at 1 point each with The route Salesloft recommends: Partly - Pages 101 to 150, at 3 points with A hundred requests fit inside one minute: Yes - Pages 101 to 150, at 3 points with Room left for the rest of the team: Partly - Pages 101 to 150, at 3 points with The route Salesloft recommends: No - Pages 151 to 250, at 8 points with A hundred requests fit inside one minute: No - Pages 151 to 250, at 8 points with Room left for the rest of the team: No - Pages 151 to 250, at 8 points with The route Salesloft recommends: No - Pages 251 to 500, at 10 points with A hundred requests fit inside one minute: No - Pages 251 to 500, at 10 points with Room left for the rest of the team: No - Pages 251 to 500, at 10 points with The route Salesloft recommends: No - Page 501 and beyond, at 30 points with A hundred requests fit inside one minute: No - Page 501 and beyond, at 30 points with Room left for the rest of the team: No - Page 501 and beyond, at 30 points with The route Salesloft recommends: No - A cursor poller on updated_at with A hundred requests fit inside one minute: Yes - A cursor poller on updated_at with Room left for the rest of the team: Yes - A cursor poller on updated_at with The route Salesloft recommends: Yes **How to connect it** (A Salesloft admin if you need the client credentials flow, plus whoever hosts the receiver and whoever can create a Reverse Contact API key.. A day and a half. Finding out what else is already spending the team rate limit is a conversation rather than a task.): 1. Find out what else holds API credentials on the team, before you add anything [Salesloft: your own integrations list, and a conversation]. The rate limit is 600 cost a minute at team level, and Salesloft states plainly that one integration can affect another's limit. So the budget you are designing against is already partly spent by the CRM sync, the dialler and anything else connected. This is the step with no screen and it is the one that decides the design. 2. Decide where enrichment sits relative to cadence entry [Your own process]. Steps render from the record at send time, so enriching somebody already in a cadence improves later emails and cannot touch the one that has gone. Enrich, then add to the cadence. This is irreversible in the only way that matters: the recipient already read it. 3. Choose the auth method on governance grounds, not convenience [Salesloft: API keys or an OAuth app]. API keys are for your own team only; anything distributed has to be an OAuth application. The client credentials flow for a private app has to be enabled by an admin and then runs with that admin's permissions, which is a question about accountability rather than about tokens. 4. Plan the backfill as a cursor poller, not as pagination [Salesloft: the updated_at field]. Page numbers above 100 cost extra and the surcharge rises steeply. Salesloft recommends a cursor poller on updated_at instead and publishes a guide for it. Taking this decision before you write the loop saves rewriting the loop. 5. Make the webhook receiver answer fast and work later [Your receiver]. A failing webhook gets three retries 15 seconds apart and is then marked failed. Fifteen seconds is not long enough to ride out a deploy, so the receiver has to accept the call immediately and do the enrichment asynchronously rather than answering with the result. 6. Check before you fetch, on the free endpoint [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 it has to. On a shared rate limit this matters twice: fewer Reverse Contact credits, and fewer Salesloft calls to re-read records you were never going to refresh. 7. Write the suppression rule before the enrichment rule [Your receiver]. The response carries more reasons not to send than reasons to send: a current employer that disagrees with the account, an isInRemembrance flag, a confident null. Each is a person who should leave the cadence rather than get a better version of the same email. 8. Read the cost headers rather than counting calls [Every Salesloft API response]. x-ratelimit-endpoint-cost reports what the request just cost and x-ratelimit-remaining-minute reports what is left. Each endpoint costs 1 by default and Salesloft can change a cost at any time, on the grounds that a cost change deprecates nothing, so the headers are the only reliable figure. **How to check it worked:** - Read x-ratelimit-remaining-minute at a busy time of day rather than at the start of a sprint. That number is the budget you actually have, and it is lower than 600 whenever anything else is running. - Request page 101 of anything and read x-ratelimit-endpoint-cost. It should come back as 3 rather than 1, which is the cheapest possible demonstration that the pagination surcharge is real. - Take the receiver down for a minute and fire a webhook at it. Three retries 15 seconds apart means you have 45 seconds before the event is marked failed, and knowing that number changes how you deploy. - Enrich one person, then open the rendered preview of their next cadence step. The preview is the only place you see what the recipient sees, and a fallback that reads badly is only obvious there. Agent skill for this pair: https://www.reversecontact.com/integrations-hub/skills/salesloft-reverse-contact.md **Field mapping:** - A cadence membership webhook maps to Your receiver. Three retries 15 seconds apart and then marked failed, so accept quickly and enrich asynchronously. Answering the webhook with the enrichment result is the design that breaks during a deploy. - Person email address maps to POST /v2/enrich/persons, 2 credits. Identity, the current role, history, education, skills and location on one schema. A confident null costs nothing, because Reverse Contact charges 0 credits on every 4xx and 5xx. - Account domain maps to POST /v2/enrich/companies, 2 credits. Firmographics from a domain or a company name. Once per account rather than once per person on it, which also saves the Salesloft reads. - A profile URL already on the person maps to POST /v2/fetch/persons, 1 credit. Half the credits, and unmetered from the $249 plan rather than the $699 one. Worth routing to deliberately wherever the URL is already there. - Reading one person maps to 1 cost, by default. Every endpoint costs 1 unless documented otherwise, and Salesloft reserves the right to change any cost at any time because a cost change does not deprecate anything. - Reading page 101 and beyond maps to 3 to 30 cost, rising by page range. The one documented surcharge: 3 points for pages 101 to 150, 8 for 151 to 250, 10 for 251 to 500 and 30 past 500. This is why a backfill is a cursor poller rather than a loop. - Writing the enriched fields back maps to PATCH a person, 1 cost. Cheap per call and still part of the team budget. Collapse the write into one request per person rather than one per field. - Anything outbound to Reverse Contact maps to Only what your receiver sends. This is a read layer. No person, cadence or call is sent anywhere, and there is nothing in the product to send it to. - Does not cross: An app inside Salesloft. There is no listing and no in-product step that calls an external API, which is consistent with Reverse Contact maintaining apps on Clay, Zapier and Make and nothing inside any CRM or sequencer. - Does not cross: A distributed integration built on an API key. Keys are for customers only, so anything shared with another team has to be an OAuth application. - Does not cross: A business email or a direct phone number. Both are separate endpoints at 3 and 20 credits, charged only when one is found. - Does not cross: Anything that repairs a sent email. Steps render at send time, so enrichment after cadence entry improves what comes next and nothing that has gone. **What breaks:** - **600 cost a minute, shared across the team.** The limit is per team and not per integration, and Salesloft says explicitly that one integration can affect another's limit. Before adding an enrichment loop, find out what else holds API credentials on that team, because the budget is already partly spent. - **Endpoint costs can change without notice.** Each endpoint costs 1 by default and Salesloft reserves the right to change a cost at any time, on the grounds that a cost change does not deprecate anything. Read x-ratelimit-endpoint-cost from live responses rather than assuming a call still costs what it cost last quarter. - **Deep pagination is expensive on purpose.** Page 101 to 150 costs 3 points a request, 151 to 250 costs 8, 251 to 500 costs 10, and past 500 costs 30. A backfill that walks pages is therefore quadratically worse than one that uses a cursor poller on updated_at, which is what Salesloft recommends instead. - **API keys will not get a partner app approved.** Keys are for customers only. Anything distributed has to be an OAuth app, and the client credentials flow for private apps has to be enabled by an admin and runs with that admin's permissions, which is a governance question rather than a technical one. - **A failing webhook gets four attempts and stops.** Three retries, 15 seconds apart, then marked failed. Fifteen seconds is not long enough to ride out a deploy, so the receiver needs to accept quickly and do the enrichment asynchronously rather than answering the webhook with the result. **Failures people hit:** - A 429 on a sweep that worked in a test account. Why: The limit is 600 cost a minute at team level rather than per integration, and Salesloft states that one integration can affect another's limit. A test team has nothing else running on it. Fix: Read x-ratelimit-remaining-minute at a busy hour and design against that figure. A team with many integrations can ask Salesloft to adjust the limit, which is a conversation rather than a setting. - The backfill got slower the further it went. Why: Page numbers above 100 carry an additional cost: 3 points for pages 101 to 150, 8 for 151 to 250, 10 for 251 to 500 and 30 past 500. Fix: Rewrite it as a cursor poller on updated_at, which Salesloft recommends and documents. The cost stays at the default of 1 however far back the history goes. - A call that used to be cheap is now expensive. Why: Each endpoint has a default cost of 1 and Salesloft can change the cost of an existing endpoint at any time, on the stated grounds that the functionality is not deprecated by a cost change. Fix: Read x-ratelimit-endpoint-cost from live responses rather than holding a table of costs. The header is there precisely because the numbers move. - Webhook events are being marked failed during deploys. Why: A failing webhook gets three retries 15 seconds apart and is then marked failed, which gives the receiver about 45 seconds in total. Fix: Accept the webhook immediately, queue the work, and enrich asynchronously. A receiver that answers with the enrichment result cannot survive a restart. - The private app stopped working when somebody left. Why: The client credentials flow has to be enabled by an admin and runs with that admin's permissions, so it inherits their account rather than standing on its own. Fix: Use a service account that will outlast an individual, and document whose permissions the integration is actually running with. This is a governance answer rather than a technical one. - A well-personalised email reached somebody who changed job. Why: The enrichment wrote a new title and nothing compared the returned current employer against the account the person sits under. Fix: Compare currentPosition.companyName with the account and route disagreements out of the cadence. Three lines in the receiver, and the highest-value check on this page. - Everything stopped, including the calls that were free. Why: Below 2 Reverse Contact credits the free Check endpoints are paused too and answer 402 NO_CREDITS, because the fetch a check precedes can itself cost 2. Fix: Branch on quotas.workspace.credits.left, which rides on every response. GET /v2/usage keeps answering whatever the balance, so a balance check never fails for the same reason. - An endpoint that worked last week returns nothing. Why: /v2/resolve was replaced by /v2/enrich and /v2/search/persons by /v2/search/people, with the old pair documented as live only until 13 October 2026. Fix: Change both paths in the receiver. It is ordinary version-controlled code on this route, which is the one consolation of there being no app to install. **What practitioners say** (14 threads from 2020 to 2026, read 2026-10-11): Nobody discusses this pair by name, so the search was for the job: enriching a cadence before it sends, and paying for the credentials that make it possible. Two of the five are about the economics of buying enrichment from the platform you already own, and one is about what happens when a sales tool holding your tokens is breached, which is the question the governance step in the setup exists to answer. - Practitioners name the threshold where a third party beats the native option (r/hubspot, March 2025, 2 points): https://www.reddit.com/r/hubspot/comments/1jex0zv/do_you_pay_for_clearbit_enrichment/ - A bundled data product is usually strong on one half and thin on the other (r/hubspot, March 2025, 6 points): https://www.reddit.com/r/hubspot/comments/1jex0zv/do_you_pay_for_clearbit_enrichment/ - A sales tool holding your tokens is part of your attack surface (r/cybersecurity, September 2025, 32 points): https://www.reddit.com/r/cybersecurity/comments/1n6map7/zscaler_palo_alto_networks_spycloud_among_the/ - The chain this pair sits in, described end to end (r/sales, September 2024, 23 points): https://www.reddit.com/r/sales/comments/1fegpn3/can_you_tldr_what_clay_does_why_is_it_all_the/ - The build is not hard, which is why the budget is the design (r/sales, September 2024, 53 points): https://www.reddit.com/r/sales/comments/1fegpn3/can_you_tldr_what_clay_does_why_is_it_all_the/ Sources: https://developer.salesloft.com/docs/platform/api-basics/rate-limits/ | https://developer.salesloft.com/docs/platform/webhooks/event-types/ | https://developer.salesloft.com/docs/platform/api-basics/ | https://developer.salesloft.com/docs/platform/guides/building-an-efficient-cursor-poller/ | https://docs.reversecontact.com/getting-started | https://docs.reversecontact.com/guides/credits | https://docs.reversecontact.com/guides/rate-limits | https://www.reversecontact.com/pricing ### Smartlead and Reverse Contact The API key rides in the query string, which decides where this runs. - Built as: Built on the API, Zapier, Make or n8n - Syncs: One way, in - Moves: Contacts, Companies - Costs to turn on: Metered by usage. Setup: Hours - Requires: A Reverse Contact API key and a Smartlead API key, used server side - Full guide: https://www.reversecontact.com/integrations-hub/reverse-contact-integrations/smartlead-reverse-contact-integration **Verdict.** Smartlead is the most API-complete sequencer at its price, and the enrichment build is the standard shape: enrich the row, then upload it, rather than uploading and fixing afterwards. Two details set it apart. The key travels in the query string rather than a header, which is a real operational constraint on where the calls can run. And the hourly limit of 1,000 on Standard, rather than the per-minute figure, is what caps a bulk pass. **What syncs:** - The list, before upload (out): Enrich each row with /v2/enrich/persons from its email. 2 credits on a match, nothing on a miss or a check. - Lead upload (in): POST the enriched leads with their custom fields, so personalisation has values to render from. - Reply and event webhooks (out): Smartlead fires events back out, which is how a reply reaches a CRM or a Slack channel. - Anything back to Reverse Contact (out): Nothing. This is a read layer, and your pipeline decides which custom fields get written. **Which editions carry it** (rows Smartlead, columns Reverse Contact): - Standard: 10 a second, 60 a minute, 1,000 an hour with Upload a few hundred enriched leads: Fits - Standard: 10 a second, 60 a minute, 1,000 an hour with Upload two thousand in one sitting: No - Standard: 10 a second, 60 a minute, 1,000 an hour with Loop over the three tight endpoints: No - Standard: 10 a second, 60 a minute, 1,000 an hour with Poll campaign state while uploading: Tight - Pro: 20 a second, 120 a minute, 3,000 an hour with Upload a few hundred enriched leads: Fits - Pro: 20 a second, 120 a minute, 3,000 an hour with Upload two thousand in one sitting: Fits - Pro: 20 a second, 120 a minute, 3,000 an hour with Loop over the three tight endpoints: No - Pro: 20 a second, 120 a minute, 3,000 an hour with Poll campaign state while uploading: Fits - Enterprise: custom on all three with Upload a few hundred enriched leads: Fits - Enterprise: custom on all three with Upload two thousand in one sitting: Fits - Enterprise: custom on all three with Loop over the three tight endpoints: No - Enterprise: custom on all three with Poll campaign state while uploading: Fits **How to connect it** (Whoever can generate a Smartlead API key and whoever runs the server side of this, because the key cannot safely live in a browser. Plus a Reverse Contact key.. An afternoon. Deciding to enrich before the upload rather than after it takes no time and saves all of it.): 1. Decide to enrich before the upload, not after it [Your own pipeline]. Smartlead renders personalisation at send time, so a lead uploaded without the fields a sequence references gets the fallback text and nothing later repairs the email that went. Enriching first is also cheaper, because you can drop the rows that did not resolve instead of sending to them. 2. Put this on a server, because of where the key travels [Not a browser, not a client app]. Smartlead documents authentication as api_key in the query string rather than in a header. Request lines get logged by proxies, error trackers and anything that records a URL, so this route belongs server side and the key belongs on the ordinary rotation schedule rather than treated as a secret that stays secret. 3. Work out the hourly ceiling before the per-minute one [Smartlead: your plan]. Per API key the limits are 60 a minute and 1,000 an hour on Standard with a 10 a second burst, and 120 a minute and 3,000 an hour on Pro with a 20 a second burst. The hourly figure is what caps a bulk pass, and it is plan-wide across every endpoint combined rather than per endpoint. 4. Check before you fetch, on the endpoint that costs nothing [POST /v2/fetch/persons/check]. The free check says whether a profile is cached and when it was last updated, so a pass over a list spends 2 credits only where it needs to. Doing it in this order is what Reverse Contact recommends and it is the main lever on this bill. 5. Write the suppression rule before the enrichment rule [Your pipeline]. The response carries more reasons not to send than reasons to send. A current employer that disagrees with your record, an isInRemembrance flag, a confident null: each one is a row to drop rather than a row to personalise better. 6. Map the enriched values to the exact custom field names the sequence uses [Smartlead: the campaign sequence]. Custom fields are key-value pairs and the key has to match the merge variable in the sequence character for character. A near-miss renders the fallback, which looks like a sending problem and is a naming problem. 7. Upload in batches and leave the tight endpoints alone [Smartlead: the add-leads endpoint]. Three endpoints carry their own limit of 10 requests per 60 seconds per account, independent of the plan-wide figure: leads statistics by campaign, all-leads activities, and domain-wise mailbox health metrics. None of them belongs in a loop. 8. Send one lead to a test campaign and read the rendered email [Smartlead: a campaign with one mailbox]. The rendered first email is the only artefact that tells you whether the mapping worked. The API reporting success means the lead was accepted, which is a different claim entirely. **How to check it worked:** - Enrich one row, upload it to a test campaign with one mailbox, and read the rendered first email. That is the only place a mismatched custom field name is visible, and it is invisible everywhere else. - Upload a row deliberately missing a field the sequence references. The fallback text should appear, and seeing what it looks like once is how you find out whether your fallbacks are good enough to send. - Run 70 requests inside a minute on Standard and watch the limit bite at 60. Knowing the ceiling is real changes how a thousand-row pass gets scheduled. - Grep your logs for api_key after the first run. If the key is in them, that is the finding, and it is better found on day one than during an audit. Agent skill for this pair: https://www.reversecontact.com/integrations-hub/skills/smartlead-reverse-contact.md **Field mapping:** - An email on the row maps to POST /v2/enrich/persons, 2 credits. Identity, the current role, history, education, skills and location on one schema. A confident null costs nothing, because Reverse Contact charges 0 credits on every 4xx and 5xx. - A company domain maps to POST /v2/enrich/companies, 2 credits. Firmographics from a domain or a company name. Once per company rather than once per lead at it, which is both cheaper and more consistent across a campaign. - A profile URL already on the row maps to POST /v2/fetch/persons, 1 credit. Half the credits, and unmetered from the $249 plan rather than the $699 one. Lists sourced from profiles rather than forms often already carry one. - currentPosition.title maps to A custom field, named to match the sequence. The value most openers reference. The key has to match the merge variable exactly, because a near-miss renders the fallback rather than erroring. - company.name and employeeCount maps to Custom fields on the lead. The two values that carry most first-line personalisation. Headcount is a number in the response and a string in a merge field, so decide the formatting before the upload rather than per row. - Add lead to campaign maps to The campaign has to exist first. Smartlead campaigns are built in Smartlead. The sequence, the mailboxes and the schedule are decisions taken before any of this runs, and the campaign id is what the upload is pointed at. - The api_key parameter maps to In the query string, not a header. Documented, and the reason this route is server side. URLs are logged by things you do not control, so treat the key as something that will end up in a log and rotate it accordingly. - Anything outbound to Reverse Contact maps to Only what your pipeline sends. This is a read layer. No lead, campaign or reply is sent anywhere, and there is nothing in the product to send it to. - Does not cross: An app inside Smartlead. There is none, which is consistent with Reverse Contact maintaining apps on Clay, Zapier and Make and nothing inside any CRM or sequencer. - Does not cross: A business email or a direct phone number from Reverse Contact. Both are separate endpoints at 3 and 20 credits, charged only when one is found, and the email finder is asynchronous. - Does not cross: Anything that repairs an email already sent. Personalisation renders at send time, so enrichment after the upload improves later steps and nothing before them. - Does not cross: Campaign creation. Every upload is pointed at a campaign that already exists, built in Smartlead with its own sequence, mailboxes and schedule. **What breaks:** - **The key is a query parameter, not a header.** Smartlead documents authentication as api_key in the query string. URLs get logged, by proxies, by error trackers, by anything that records a request line, so this route should run server side and the key should be rotated on the normal schedule rather than treated as a secret that stays secret. - **1,000 requests an hour on Standard.** Per API key: 60 a minute and 1,000 an hour on Standard with a 10 a second burst, 120 a minute and 3,000 an hour on Pro with a 20 a second burst. The hourly ceiling is the one that bites on a bulk pass, and it is plan-wide across every endpoint rather than per endpoint. - **A few endpoints carry their own limit.** Smartlead notes that some endpoints are expensive enough to have a dedicated limit independent of the plan-wide one. Check the endpoint you intend to hammer before designing a loop around the headline figure. - **Personalisation renders at send time.** A lead uploaded without the fields a sequence references gets the fallback text, and nothing later repairs the email that already went. Enrichment belongs before the upload, which is also where it is cheapest, because you can drop the rows that did not resolve instead of sending to them. - **Credit packs expire after 3 months.** Reverse Contact credit packs run 5K to 1M and are valid 3 months. A sender that runs in campaign bursts can reach the end of a quarter holding credits it paid for and cannot use, which is the case their Unlimited plans are priced for. **Failures people hit:** - The email went out with the fallback text instead of the enriched value. Why: Custom fields are key-value pairs and the key has to match the merge variable in the sequence exactly. A near-miss renders the fallback rather than failing. Fix: Compare the field names character for character, then send one lead to a test campaign and read the rendered email. The rendered email is the only place this is visible. - The upload reported success and the lead is not in the campaign. Why: Add lead to campaign requires a campaign that already exists and is active. Campaigns are built in Smartlead, not through this pipeline. Fix: Confirm the campaign id against the account rather than against your own config. A campaign renamed or archived in Smartlead breaks the upload without the id changing. - 429 after about a thousand requests. Why: The hourly ceiling is 1,000 on Standard and 3,000 on Pro, per API key and plan-wide across every endpoint combined, with per-minute limits of 60 and 120 underneath it. Fix: Pace against the hourly figure rather than the per-minute one, and count every endpoint toward it. The per-minute limit is the one people test and the hourly one is the one that stops a bulk pass. - 429 from one specific endpoint while everything else works. Why: Three endpoints carry their own limit of 10 requests per 60 seconds per account, independent of the plan-wide figure: leads statistics by campaign, all-leads activities, and domain-wise mailbox health metrics. Fix: Take them out of the loop entirely and call them on a schedule instead. No plan raises these three, so there is no upgrade that fixes it. - The API key turned up in a log. Why: Smartlead documents authentication as api_key in the query string, and request lines are logged by proxies, error trackers and anything that records a URL. Fix: Run this server side, keep the key out of any client, and rotate it on a schedule rather than only after an incident. This is a property of the API rather than a mistake you made. - A campaign reached somebody who left the company. Why: The enrichment wrote a title and nothing compared the returned current employer against the company on the row. Fix: Compare currentPosition.companyName with your own value and drop the row rather than uploading it. On a sender this check is worth more than any personalisation it would have enabled. - Everything stopped, including the calls that were free. Why: Below 2 Reverse Contact credits the free Check endpoints are paused too and answer 402 NO_CREDITS, because the fetch a check precedes can itself cost 2. Fix: Branch on quotas.workspace.credits.left, which rides on every response. GET /v2/usage keeps answering whatever the balance, so a balance check never fails for the reason the lookup did. - Credits expired before a campaign used them. Why: Reverse Contact credit packs run from 5K to 1M and are valid 3 months, and a sender that works in campaign bursts does not spend evenly. Fix: Size the pack to a quarter of real volume rather than to a discount, or move to an Unlimited plan, where the cached endpoints the plan names stop being metered at all. **What practitioners say** (14 threads from 2024 to 2026, read 2026-10-11): Nobody discusses this pair by name, so the search was for the job: getting a cold list good enough to send. The threads are unusually blunt because the feedback loop is a bounce rate, and the consensus is stated in one sentence by somebody answering a 60% bounce: the data is the problem and switching the sending tool fixes none of it. The dissenting view, that most teams should fix their targeting rather than their stack, is worth reading too. - The sender is not the variable, and a bounce rate proves it (r/Coldemailing, July 2026, 2 points): https://www.reddit.com/r/Coldemailing/comments/1uzqhev/smartlead_deliverability_lead_quality/ - The sending tools assume you already have the list (r/EmailOutreach, May 2026, 3 points): https://www.reddit.com/r/EmailOutreach/comments/1tnjrbd/lemlist_vs_instantly_vs_smartlead_pricing/ - What the sending tools actually are, said plainly (r/Emailmarketing, June 2024, 5 points): https://www.reddit.com/r/Emailmarketing/comments/1dcuzeb/smartleadai_and_b2b_emails/ - The dissenting view, and it is the right question to ask first (r/agency, February 2026, 2 points): https://www.reddit.com/r/agency/comments/1r428n2/moving_from_solely_apollo_to_clay_smartlead/ - The research that qualifies somebody is the research that writes the email (r/agency, February 2026, 1 points): https://www.reddit.com/r/agency/comments/1r428n2/moving_from_solely_apollo_to_clay_smartlead/ Sources: https://api.smartlead.ai/guides/rate-limits | https://api.smartlead.ai/authentication | https://api.smartlead.ai/guides/webhook-integration | https://docs.reversecontact.com/getting-started | https://docs.reversecontact.com/guides/credits | https://docs.reversecontact.com/guides/rate-limits | https://www.reversecontact.com/pricing ### lemlist and Reverse Contact Basic auth with a leading colon, and a sequencer that sells enrichment of its own. - Built as: Built on the API, Zapier, Make or n8n - Syncs: One way, in - Moves: Contacts, Companies - Costs to turn on: Metered by usage. Setup: Hours - Requires: A Reverse Contact API key and a lemlist API key, sent as HTTP Basic - Full guide: https://www.reversecontact.com/integrations-hub/lemlist-integrations/lemlist-reverse-contact-integration **Verdict.** lemlist is the easiest of the sequencers to connect and the most interesting to reason about, because it sells enrichment itself. The connection is a few lines once you get past the Basic auth with its leading colon, and the limits are comfortable at 20 requests per 2 seconds. The real question is not how to add a second provider but how to order two, which is a waterfall question and the only honest answer involves running both over 500 of your own rows and counting. **What syncs:** - The list, before the campaign (out): Enrich each lead from its email with /v2/enrich/persons. 2 credits on a match. - Lead creation (in): POST the lead to the campaign with the enriched values as custom variables. - Activity webhooks (out): lemlist fires events on opens, replies and other activity, which is how a reply reaches a CRM. - Anything back to Reverse Contact (out): Nothing. This is a read layer, and your pipeline decides which lemlist variables are written. **Which editions carry it** (rows lemlist, columns Reverse Contact): - Both, unconditionally with Resolved by both providers: Two lookups - Both, unconditionally with Resolved only by lemlist: Two lookups - Both, unconditionally with Resolved only by Reverse Contact: Two lookups - Both, unconditionally with Resolved by neither: Two lookups - lemlist first, Reverse Contact on the nulls with Resolved by both providers: One lookup - lemlist first, Reverse Contact on the nulls with Resolved only by lemlist: One lookup - lemlist first, Reverse Contact on the nulls with Resolved only by Reverse Contact: Two lookups - lemlist first, Reverse Contact on the nulls with Resolved by neither: Two lookups - Reverse Contact first, lemlist on the nulls with Resolved by both providers: One lookup - Reverse Contact first, lemlist on the nulls with Resolved only by lemlist: Two lookups - Reverse Contact first, lemlist on the nulls with Resolved only by Reverse Contact: One lookup - Reverse Contact first, lemlist on the nulls with Resolved by neither: Two lookups - Reverse Contact only with Resolved by both providers: One lookup - Reverse Contact only with Resolved only by lemlist: One lookup and an empty row - Reverse Contact only with Resolved only by Reverse Contact: One lookup - Reverse Contact only with Resolved by neither: One lookup **How to connect it** (Whoever can generate a lemlist API key from Settings, plus whoever can create a Reverse Contact key. No admin on either side.. An afternoon to connect. Deciding the order of the two enrichment providers is the part that takes a week of measurement.): 1. Decide the order of the two providers before you connect either [A spreadsheet, not a settings screen]. lemlist sells enrichment itself, so this is not a question of adding a provider but of ordering two. Running both unconditionally means paying twice on every row they can both resolve. The only honest way to settle it is to run both over 500 of your own rows and count, and that measurement is the irreversible-feeling decision on this page. 2. Enrich before the lead enters a campaign [Your own pipeline]. A missing variable renders the fallback text rather than stopping the send, which is the behaviour you want and the reason an unenriched row is easy to miss. Nothing later repairs the email that has gone, so the ordering is the design. 3. Get the Basic auth right, including the leading colon [lemlist: Settings, Integrations, Generate a new API key]. lemlist uses HTTP Basic rather than Bearer. The username is always empty, the password is the key, and the string you encode is a colon followed by the key. Their documentation shouts about this because people get it wrong, and a Bearer header returns an auth error that looks exactly like a bad key. 4. Store the key on the way out of the dialog [lemlist: the key generation screen]. lemlist states that you will not be able to see the key again. That is one sentence and it costs a regeneration and every integration using the old key if you skip it. 5. Parse X-RateLimit-Reset as a date, not a number [Any lemlist API response]. The limit is 20 requests per 2 seconds on all routes, metered per API key. Retry-After is an integer count of seconds, and X-RateLimit-Reset is a human-readable date string, which lemlist calls out specifically. Code that assumes an integer either crashes or parses it to zero and retries immediately. 6. Check before you fetch, on the endpoint that costs nothing [POST /v2/fetch/persons/check]. The free check says whether a profile is cached and how fresh it is, which also happens to be the cheapest way to decide between two providers on a per-row basis rather than a per-list one. 7. Write the suppression rule before the enrichment rule [Your pipeline]. A current employer that disagrees with your record, an isInRemembrance flag, a confident null: each is a row to drop. On a sender that runs multichannel, a wrong row is an email and a connection request rather than just an email. 8. Measure the resolved rate on the list, not the reply rate [Your own data]. Because a fallback renders rather than failing, a campaign with a third of its rows unenriched looks exactly like a campaign that is working. Count how many rows carry the field before you send, and the reply rate stops being the thing that tells you. **How to check it worked:** - Send a request with a Bearer header on purpose and read the error. It looks like a bad key rather than a bad scheme, which is exactly why the colon is worth proving once. - Run both enrichment providers over the same 500 rows and count four numbers: resolved by both, by lemlist only, by Reverse Contact only, by neither. Those four numbers settle the ordering question and nothing else does. - Read X-RateLimit-Reset from a live response and try to parse it with whatever your code uses for timestamps. If it returns zero, you have found the bug before it found you. - Upload a row deliberately missing a variable the campaign references and read the rendered email. The fallback renders silently, so this is the only way to see what an unenriched row actually sends. Agent skill for this pair: https://www.reversecontact.com/integrations-hub/skills/lemlist-reverse-contact.md **Field mapping:** - An email on the lead maps to POST /v2/enrich/persons, 2 credits. Identity, the current role, history, education, skills and location on one schema. A confident null costs nothing, because every 4xx and 5xx is free, which is what makes it safe to put second in a waterfall. - A company domain maps to POST /v2/enrich/companies, 2 credits. Firmographics from a domain or a company name. Once per company rather than once per lead at it. - A profile URL already on the lead maps to POST /v2/fetch/persons, 1 credit. Half the credits, and unmetered from the $249 plan rather than the $699 one. A multichannel sender often already holds one, because the channel needs it. - The free freshness check maps to POST /v2/fetch/persons/check, 0 credits. Whether a profile is cached and when it was last updated. The cheapest possible tiebreak between two providers on a per-row basis. - currentPosition.title and company.name maps to lemlist custom variables. The two values most openers reference. A missing variable renders the fallback text rather than stopping the send, which is why the resolved rate has to be counted rather than inferred. - The lemlist API key maps to HTTP Basic, with a leading colon. Username always empty, password the key, and the encoded string starts with a colon. Not Bearer, and the error for getting it wrong reads like a bad credential. - Its own enrichment, including a bulk endpoint maps to The other provider in the waterfall. This is the fact that shapes the page. Two sources that overlap need an order rather than a toggle: cheapest high-coverage first, the second only on what came back null. - Anything outbound to Reverse Contact maps to Only what your pipeline sends. This is a read layer. No lead, campaign or reply is sent anywhere, and there is nothing in the product to send it to. - Does not cross: An app inside lemlist. There is none, which is consistent with Reverse Contact maintaining apps on Clay, Zapier and Make and nothing inside any CRM or sequencer. - Does not cross: A machine-readable rate limit reset. X-RateLimit-Reset is a human-readable date string by design, and Retry-After is the integer to use instead. - Does not cross: A business email or a direct phone number from Reverse Contact. Both are separate endpoints at 3 and 20 credits, charged only when one is found. - Does not cross: Anything that repairs an email already sent. A fallback renders at send time, so an unenriched row is a sent email with generic text in it rather than an error anywhere. **What breaks:** - **Basic auth, with a colon in front of the key.** lemlist uses HTTP Basic rather than Bearer. The username is empty, the password is the key, and the string to encode is :YourApiKey with the leading colon. Their documentation shouts about it because people get it wrong, and a Bearer header returns an auth error that looks like a bad key. - **20 requests per 2 seconds, per key.** The limit applies to all routes and is metered per API key. At that rate a thousand-row list takes under two minutes, so this is rarely the constraint, but a parallel worker will find it quickly. - **The reset header is a human-readable date.** X-RateLimit-Reset comes back as a formatted date string rather than a Unix timestamp, which lemlist calls out specifically. Code that assumes an integer will either crash or, worse, parse to zero and retry immediately. - **Two enrichment sources need an order, not a toggle.** lemlist ships its own enrichment, including a bulk endpoint. Running two providers without deciding which goes first means paying twice on the rows both can resolve. Cheapest high-coverage source first, the second only on what came back null. - **A fallback is not a blank.** A missing variable renders the fallback text rather than stopping the send, which is the behaviour you want and the reason an unenriched row is easy to miss. Check the resolved rate on the list rather than waiting for a reply rate to tell you. **Failures people hit:** - An authentication error that looks like a bad key. Why: lemlist uses HTTP Basic rather than Bearer. The username is always empty, the password is the key, and the encoded string must start with a colon. Fix: Encode a colon followed by the key. lemlist shouts about this in its own documentation because it is the most common mistake on the API, and the error message does not point at it. - The retry loop fired immediately and made things worse. Why: X-RateLimit-Reset is a human-readable date string rather than a Unix timestamp, so code that parses it as an integer gets zero and retries at once. Fix: Use Retry-After, which is an integer count of seconds. lemlist calls the date format out specifically, which is a fair warning that it has caught people. - 429 from a parallel worker. Why: The limit is 20 requests per 2 seconds, applied to all routes and metered per API key rather than pooled across a team. Fix: Serialise or pace at about ten a second. At that rate a thousand rows takes under two minutes, so there is rarely a reason to parallelise this at all. - The key is gone and nobody wrote it down. Why: lemlist states that you will not be able to see the key again after generating it. Fix: Generate a new one, and expect every integration holding the old key to stop at the same moment. Worth knowing which those are before you click. - A third of the campaign went out with fallback text. Why: A missing variable renders the fallback rather than stopping the send, which is the behaviour you want and makes an unenriched row invisible. Fix: Count the resolved rate on the list before sending rather than waiting for the reply rate to tell you. A campaign with a third of its rows unenriched looks exactly like one that is working. - The enrichment bill is double what the filled fields suggest. Why: Two overlapping providers running unconditionally both charge for every row they can resolve, and most rows resolve on both. Fix: Make the second one conditional on the first returning null. A Reverse Contact miss costs nothing, which makes it the cheaper of the two to put second. - A connection request reached somebody who changed job. Why: Nothing compared the returned current employer against the company on the row, and a multichannel campaign acts on more than one channel per row. Fix: Compare currentPosition.companyName with your own value and drop the row. The cost of a wrong row is higher here than on an email-only sender because it is wrong in two places. - Everything stopped, including the calls that were free. Why: Below 2 Reverse Contact credits the free Check endpoints are paused too and answer 402 NO_CREDITS, because the fetch a check precedes can itself cost 2. Fix: Branch on quotas.workspace.credits.left, which rides on every response. GET /v2/usage keeps answering whatever the balance, so a balance check never fails for the same reason the lookup did. **What practitioners say** (14 threads from 2024 to 2026, read 2026-10-11): Nobody discusses this pair by name, so the search was for the job, and the job here has an unusual shape: lemlist sells enrichment itself, so the question is which of two overlapping providers runs first. Two people who have actually used lemlist's own database report it as competent and commodity, which is the most useful possible input to that decision. The other thread worth reading is somebody drowning in a six-tool stack, which is the cost of getting the ordering wrong. - Somebody who tried the bundled database reports it as commodity (r/EmailProspecting, March 2026, 1 points): https://www.reddit.com/r/EmailProspecting/comments/1ret448/is_lemlists_email_database_worth_the_price_of/ - The sceptical view of every bundled database, including this one (r/EmailProspecting, April 2026, 1 points): https://www.reddit.com/r/EmailProspecting/comments/1ret448/is_lemlists_email_database_worth_the_price_of/ - The data changes faster than any database refreshes (r/EmailProspecting, February 2026, 1 points): https://www.reddit.com/r/EmailProspecting/comments/1ret448/is_lemlists_email_database_worth_the_price_of/ - Six tools that each need attention is six jobs (r/Coldemailing, April 2026, 1 points): https://www.reddit.com/r/Coldemailing/comments/1sxuv1h/our_email_outreach_stack_is_6_tools_glued/ - The stack is three jobs, not one workflow (r/Coldemailing, April 2026, 1 points): https://www.reddit.com/r/Coldemailing/comments/1sxuv1h/our_email_outreach_stack_is_6_tools_glued/ Sources: https://developer.lemlist.com/api-reference/getting-started/authentication | https://developer.lemlist.com/api-reference/getting-started/rate-limits | https://docs.reversecontact.com/getting-started | https://docs.reversecontact.com/guides/credits | https://docs.reversecontact.com/guides/rate-limits | https://www.reversecontact.com/pricing ### Instantly and Reverse Contact 6,000 requests a minute, and a provider registry that may or may not take your key. - Built as: Built on the API, Zapier, Make or n8n - Syncs: One way, in - Moves: Contacts, Companies - Costs to turn on: Metered by usage. Setup: Hours - Requires: A Reverse Contact API key and an Instantly API v2 key with the right scopes - Full guide: https://www.reversecontact.com/integrations-hub/reverse-contact-integrations/instantly-reverse-contact-integration **Verdict.** Instantly is where a bulk enrichment pass stops being a planning exercise. Six thousand requests a minute across the workspace is ten times what Salesloft allows a whole team and a hundred times what Smartlead allows on Standard, so the shape of the build is simply enrich everything and upload. The interesting unknown is the provider registry, which documents a bring-your-own-key model with a cost of zero on the workspace key, and which names no providers publicly. Worth one email to Instantly before building the pipeline the long way. **What syncs:** - The list, before upload (out): Enrich each row from its email with /v2/enrich/persons. 2 credits on a match, free on a check. - Lead upload (in): POST the enriched leads into the campaign with their custom variables. - Webhook events (out): Typed events fire back out on campaign activity, which is how a reply reaches a CRM. - Anything back to Reverse Contact (out): Nothing. This is a read layer, and your pipeline decides which variables get written. **Which editions carry it** (rows Instantly, columns Reverse Contact): - Adding leads to a campaign with The 6,000 a minute workspace budget: Yes - Adding leads to a campaign with Safe to call in a tight loop: Yes - Adding leads to a campaign with Safe to run beside another bulk job: Partly - Reading or updating a lead with The 6,000 a minute workspace budget: Yes - Reading or updating a lead with Safe to call in a tight loop: Yes - Reading or updating a lead with Safe to run beside another bulk job: Partly - Listing emails with The 6,000 a minute workspace budget: No - Listing emails with Safe to call in a tight loop: No - Listing emails with Safe to run beside another bulk job: No - A test send with The 6,000 a minute workspace budget: No - A test send with Safe to call in a tight loop: No - A test send with Safe to run beside another bulk job: No - The AI reply label test with The 6,000 a minute workspace budget: No - The AI reply label test with Safe to call in a tight loop: No - The AI reply label test with Safe to run beside another bulk job: No **How to connect it** (Whoever can create an API v2 key with the right scopes, plus whoever can create a Reverse Contact key. No admin elsewhere.. An afternoon. This is the least constrained of the five sender pairs and the shortest build on the hub.): 1. Ask Instantly about the provider registry before you build the long way [An email to Instantly]. Instantly documents an integration provider registry with credentialSource values of workspace_key, instantly_key and unavailable, and an effectiveCostPerAction of 0 on a workspace key. It does not publish which providers are in it. One email could replace this entire pipeline with a key paste, so it is worth sending before an afternoon is spent. 2. Decide to enrich before the upload, not after it [Your own pipeline]. Personalisation renders at send time, so a lead uploaded without the fields a sequence references gets the fallback and nothing later repairs the email that went. Enriching first also lets you drop the rows that did not resolve rather than sending to them. 3. Create the key with the narrowest scopes that work [Instantly: API v2 keys]. API v2 keys carry scopes per resource, and an endpoint refuses a key that lacks the right one. A pipeline built and tested with an all:all key can fail on a narrower production key, which is correct behaviour and an easy afternoon to lose. Test on the key you will ship. 4. Check before you fetch, on the endpoint that costs nothing [POST /v2/fetch/persons/check]. The free check says whether a profile is cached and when it was last updated, so a bulk pass spends 2 credits only where it has to. With 6,000 requests a minute available on the Instantly side, Reverse Contact credits are the only budget this build has to respect. 5. Write the suppression rule before the enrichment rule [Your pipeline]. A current employer that disagrees with your record, an isInRemembrance flag, a confident null: each is a row to drop rather than a row to personalise better. This matters more here than anywhere else in the set, because nothing in the limits will slow you down enough to notice. 6. Batch in hundreds anyway, with a pause between them [Your pipeline]. Instantly recommends batches of 100 with a 2-second wait between them, and running automations several times a day rather than once. Worth following under a generous ceiling, because the ceiling is shared across every key in the workspace and with API v1 as well. 7. Keep the tight endpoints out of the loop [Instantly: the per-endpoint limits]. Listing emails is 20 requests a minute, a test send is 10 a minute, and the AI reply label test is 500 per 30 days per workspace. The headline figure does not apply to every route, so check the one you intend to call repeatedly. 8. Send one lead and read the rendered email [Instantly: a campaign with one mailbox]. The rendered first email is the only artefact that proves the mapping worked. The API reporting success means the lead was accepted, which is a different claim, and the two are easy to confuse at six thousand requests a minute. **How to check it worked:** - Run the pipeline on the production key rather than the one you developed with. A scope that was never needed in testing is the most likely reason this breaks on the first real run. - Enrich one row, upload it to a campaign with one mailbox, and read the rendered first email. The rendered email is the only place a mismatched field name is visible. - Run two bulk jobs at once on purpose and read what happens. The 6,000 a minute is a workspace budget shared with API v1, so two jobs halve each other rather than each getting the headline figure. - Run a row with a deliberately mismatched current employer through the suppression rule. At this volume an unchecked rule is the one thing that will reach thousands of people before anybody notices. Agent skill for this pair: https://www.reversecontact.com/integrations-hub/skills/instantly-reverse-contact.md **Field mapping:** - An email on the row maps to POST /v2/enrich/persons, 2 credits. Identity, the current role, history, education, skills and location on one schema. A confident null costs nothing, because Reverse Contact charges 0 credits on every 4xx and 5xx. - A company domain maps to POST /v2/enrich/companies, 2 credits. Firmographics from a domain or a company name. Once per company rather than once per lead at it. - A profile URL already on the row maps to POST /v2/fetch/persons, 1 credit. Half the credits, and unmetered from the $249 plan rather than the $699 one. The cheapest route into this pair if your list was sourced from profiles. - currentPosition.title and company.name maps to Custom fields on the lead. The two values most openers reference. The names have to match the sequence variables, and a near-miss renders the fallback rather than erroring. - An API v2 key maps to Scoped per resource. An endpoint refuses a key lacking the relevant scope, which is the right behaviour and means an all:all key in development hides a production failure. - The provider registry maps to credentialSource and effectiveCostPerAction. Documented as a shape rather than a list: workspace_key, instantly_key or unavailable, with a cost of 0 on a workspace key. Which providers it holds is not published, so treat a bring-your-own-key route as a question rather than a capability. - Add leads to a campaign maps to Batches of 100, two seconds apart. Instantly's own recommendation, and worth following under a generous ceiling because the ceiling is shared across every key in the workspace and with API v1. - Anything outbound to Reverse Contact maps to Only what your pipeline sends. This is a read layer. No lead, campaign or reply is sent anywhere, and there is nothing in the product to send it to. - Does not cross: An app inside Instantly. There is none, which is consistent with Reverse Contact maintaining apps on Clay, Zapier and Make and nothing inside any CRM or sequencer. - Does not cross: A published list of registry providers. Instantly documents the registry's shape, including the three credentialSource values and the zero cost per action on a workspace key, and names no providers. - Does not cross: A business email or a direct phone number from Reverse Contact. Both are separate endpoints at 3 and 20 credits, charged only when one is found. - Does not cross: Anything that repairs an email already sent. Personalisation renders at send time, so enrichment after the upload improves later steps and nothing before them. **What breaks:** - **6,000 a minute, and it is a workspace budget.** A hundred requests a second and 6,000 a minute, shared between API v1 and v2 and across every key in the workspace. Generous, and still shared, so two bulk jobs running at once halve each other rather than each getting the headline figure. - **A few endpoints are much tighter.** Listing emails is 20 requests a minute, a test send is 10 a minute, and the AI reply label test is 500 per 30 days per workspace. The headline limit does not apply to every route, so check the one you intend to loop over. - **The provider registry names no providers publicly.** Instantly documents the shape of the registry, including credentialSource values of workspace_key, instantly_key and unavailable, and an effectiveCostPerAction of 0 on a workspace key. It does not publish which providers are in it. Treat a bring-your-own-key route as a question for Instantly rather than a documented capability. - **Scopes are granular, so a key can be silently insufficient.** API v2 keys carry scopes per resource, and an endpoint refuses a key that lacks the right one. A pipeline that worked in testing with an all:all key can fail on a narrower production key, which is the correct behaviour and an easy afternoon to lose. - **The documented bulk advice is batches of 100.** Instantly recommends batching in hundreds with a 2-second wait between batches, and running automations several times a day rather than once. Worth following even under a generous ceiling, because the ceiling is shared with everything else in the workspace. **Failures people hit:** - The pipeline worked in development and fails in production. Why: API v2 keys carry scopes per resource and an endpoint refuses a key that lacks the right one. A development key with broad scopes hides the problem entirely. Fix: Test on the key you intend to ship. The refusal is correct behaviour rather than a fault, which is why nothing in the logs will suggest a permissions problem until you look for one. - Two bulk jobs each got half the speed they expected. Why: The limit applies to the entire workspace and is shared between API v1 and v2 even across multiple API keys, so it is not per job and not per key. Fix: Serialise the jobs or accept the halving. Instantly recommends batches of 100 with a 2-second wait and running automations several times a day rather than once. - 429 from one endpoint while everything else runs fine. Why: Several routes carry their own limit regardless of the headline figure: listing emails is 20 a minute, a test send is 10 a minute, and the AI reply label test is 500 per 30 days per workspace. Fix: Take those out of any loop. No upgrade or pacing on the main budget affects them, because they are not governed by it. - The email went out with fallback text instead of the enriched value. Why: Personalisation renders at send time from whatever the lead record holds, and a field name that does not match the sequence variable renders the fallback rather than failing. Fix: Send one lead to a campaign with one mailbox and read the rendered email. It is the only place this is visible and it costs one request. - Thousands of people got an email they should not have. Why: At 6,000 requests a minute a missing suppression rule has no natural brake. Nothing in the limits slows a bad rule down enough for anybody to notice it first. Fix: Compare currentPosition.companyName against your own value and check isInRemembrance before upload, not after. On this pair that rule is worth more than any personalisation it prevents. - Nobody can tell you which providers the registry holds. Why: Instantly documents the registry as a shape rather than a list: credentialSource of workspace_key, instantly_key or unavailable, and an effectiveCostPerAction of 0 on a workspace key. The providers themselves are not published. Fix: Ask Instantly directly before building the pipeline the long way. A bring-your-own-key route would replace most of this page, and it is one email rather than an investigation. - Everything stopped, including the calls that were free. Why: Below 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. Fix: Branch on quotas.workspace.credits.left, which rides on every response. GET /v2/usage keeps answering whatever the balance, so a balance check never fails for the reason the lookup did. - A quarter of the credits went in an afternoon. Why: This is the one pair in the set with no external brake. A reverse lookup is 2 credits, the Instantly side allows 6,000 requests a minute, and nothing in between enforces a pace. Fix: Call the free check first and refresh only what is stale, set a per-key rate limit on the Reverse Contact side, and read quotas.workspace.credits.left on every response rather than at the end of the run. **What practitioners say** (14 threads from 2024 to 2026, read 2026-10-11): Nobody discusses this pair by name, so the search was for the job: resolving a cold list before a sender touches it. The best comment in the set is somebody who lost three months of enriched contacts when they changed sequencer and now keeps the data layer separate on purpose, which is this page's argument made by somebody who learned it expensively. The accuracy thread is the other one worth reading, because it lands on the same figure the vendor publishes. - Somebody who learned to keep the data layer separate, expensively (r/SaaS, April 2026, 6 points): https://www.reddit.com/r/SaaS/comments/1sabv66/i_analyzed_1000_negative_reviews_of_instantly/ - Practitioners put automated enrichment at 70 to 80 per cent, unprompted (r/b2b_sales, October 2025, 1 points): https://www.reddit.com/r/b2b_sales/comments/1oao70k/sales_folks_how_accurate_is_automated_lead/ - A lead source can die silently for a week (r/microsaas, April 2026, 1 points): https://www.reddit.com/r/microsaas/comments/1sthi1r/i_replaced_apollo_clay_instantly_hubspot_with_one/ - Reply rate is a slow and expensive way to discover a bad list (r/agency, October 2025, 4 points): https://www.reddit.com/r/agency/comments/1oeu8qt/4_months_with_instantly_for_cold_email_08_to_51/ - Which tool matters depends on which bottleneck you have (r/AiAutomations, July 2026, 2 points): https://www.reddit.com/r/AiAutomations/comments/1upqeh3/instantly_vs_acquisity_vs_clay_vs_apollo_what_are/ Sources: https://developer.instantly.ai/getting-started/rate-limit | https://developer.instantly.ai/getting-started/authorization | https://developer.instantly.ai/api-reference/supersearchenrichment/returns-the-full-integration-provider-registry | https://docs.reversecontact.com/getting-started | https://docs.reversecontact.com/guides/credits | https://docs.reversecontact.com/guides/rate-limits | https://www.reversecontact.com/pricing ### ZoomInfo and Reverse Contact ZoomInfo meters records and holds them for a year. Reverse Contact meters calls. That difference decides which is cheaper for you. - Built as: Built on the API, Zapier, Make or n8n - Syncs: One way, out - Moves: Contacts, Companies - Costs to turn on: Needs a higher plan. Setup: Hours - Requires: A ZoomInfo contract with API access, a Reverse Contact API key, and an orchestrator to run the waterfall - Full guide: https://www.reversecontact.com/integrations-hub/zoominfo-integrations/zoominfo-reverse-contact-integration **Verdict.** The interesting difference between these two is not coverage, it is the meter. ZoomInfo charges one credit the first time it enriches a record in a rolling twelve months and then places that record under management, so re-enriching it is free for a year. Reverse Contact charges per call and stops metering whole endpoint families at a plan price. Those models reward opposite behaviours, and the question that decides which suits you is how often you intend to refresh, which almost nobody asks before signing either contract. **What syncs:** - Nothing (out): No sync between two data providers, no app on either side, nothing to configure between them. - The first call (out): Whichever provider the identifier and the budget favour, run from Clay, n8n or your own code. - The fallback (out): The other provider, on the rows that came back empty. The only sense in which these two are connected. - The verification (out): A separate step before anything is sent, which every practitioner account of this build describes adding. **Which editions carry it** (rows ZoomInfo, columns Reverse Contact): - Enrich a record for the first time with On ZoomInfo's record meter: One credit - Enrich a record for the first time with On Reverse Contact's call meter: One credit - Enrich a record for the first time with Counts against a separate limit: The record limit too - Enrich a record for the first time with Can stop being metered: Unmetered from $699 - Re-enrich the same record a month later with On ZoomInfo's record meter: Nothing - Re-enrich the same record a month later with On Reverse Contact's call meter: One credit - Re-enrich the same record a month later with Counts against a separate limit: The record limit too - Re-enrich the same record a month later with Can stop being metered: Unmetered from $699 - Search for people you do not hold with On ZoomInfo's record meter: Nothing - Search for people you do not hold with On Reverse Contact's call meter: One per profile - Search for people you do not hold with Counts against a separate limit: No - Search for people you do not hold with Can stop being metered: Unmetered from $449 - Resolve a profile URL you already hold with On ZoomInfo's record meter: Not what it is for - Resolve a profile URL you already hold with On Reverse Contact's call meter: One cached credit - Resolve a profile URL you already hold with Counts against a separate limit: No - Resolve a profile URL you already hold with Can stop being metered: Unmetered from $249 - Find a missing phone number with On ZoomInfo's record meter: One credit - Find a missing phone number with On Reverse Contact's call meter: Only on a result - Find a missing phone number with Counts against a separate limit: The record limit too - Find a missing phone number with Can stop being metered: Always on credits **How to connect it** (Somebody who can get API access on the ZoomInfo contract, somebody who can create a Reverse Contact key, and whoever owns the orchestrator.. An afternoon to build. Longer to get ZoomInfo API access through procurement.): 1. Work out how often you intend to re-enrich, because the meters reward opposite answers [Your own process, before either contract]. ZoomInfo charges one credit per record per rolling twelve months and then lets you re-enrich free; Reverse Contact charges per call. A list you refresh monthly is cheap on the first model and expensive on the second, and a long tail of one-off lookups is the reverse. Nothing later in this checklist matters as much. 2. Find out what your record limit is, separately from your credits [Your ZoomInfo contract]. ZoomInfo says every enrichment counts against the customer's record limit even when a record under management consumes no further credit. So free re-enrichment is free of credits and not free of the limit, and those are two different budgets to plan against. 3. Audit which identifier your rows carry [Your CRM or your list]. A profile URL is 1 credit on Reverse Contact and unmetered from $249. An email, a name or a domain is 2 and unmetered only from $699. On the ZoomInfo side the free operations are the searches and the lookup, while enrichment is what costs, so the audit changes the cost on both sides in different directions. 4. Create both credentials, and read the rate limits off a live response [ZoomInfo and Reverse Contact]. ZoomInfo returns per-second, per-hour and per-day limit and remaining headers on every response according to its rate-limits page, while its credit page says headers are not currently returned. Read them, and have a fallback that works if they are absent. 5. Put the provider whose misses are free first [Your orchestrator]. On Reverse Contact every 4xx and 5xx is 0 credits and the finders are charged only on a result, with a live fetch as the sole exception. On ZoomInfo the searches and the lookup are free and enrichment costs per new record, so discovering what you cannot resolve is cheap on both sides if you order it deliberately. 6. Check before you fetch, on the endpoints that cost nothing [POST /v2/fetch/persons/check, and ZoomInfo Lookup]. Reverse Contact's free check says whether a profile is cached and when it was last updated. On a comparison this is also the fairest tiebreak available, because a disagreement between two providers is usually a difference in refresh date rather than in accuracy. 7. Add the verification step before anything is sent [A verifier, at the end of the chain]. ZoomInfo's objection to waterfalls is that they take the first answer, and the honest response is to verify the answer rather than to deny the objection. Every practitioner account of this build ends with a verifier and neither vendor's quickstart includes one. 8. Count resolved, correct and deliverable as three different numbers [Your bake-off sheet]. A provider can resolve the wrong person, resolve the right person with a dead address, or decline to answer. A single accuracy figure hides all three, and the whole value of a provider that returns null with a confidence score disappears if your count treats a refusal as a failure. 9. Decide what a null does, and write it down [Your orchestrator]. Fall through to the other provider, queue for review, or write nothing. The option that is never right is writing a low-confidence guess into a field a rep will read as a fact, which is the failure the comparison on this page exists to help you avoid. **How to check it worked:** - Enrich the same record twice on ZoomInfo inside the same year and confirm the second one consumes no credit. Then check whether it counted against your record limit, because those are two separate budgets. - Run the same 500 rows through both providers in both orders. If the order changes the outcome by more than the overlap, the ordering is doing more work than either corpus. - Deliberately exhaust one ZoomInfo window and watch which bucket is named. The 429 carries X-RateLimit-Rejected-Bucket, so you learn whether the second, the hour or the day is your real ceiling. - Compare the update dates rather than the values when the two providers disagree. A difference in refresh date explains most disagreements and tells you something a coverage table cannot. Agent skill for this pair: https://www.reversecontact.com/integrations-hub/skills/zoominfo-reverse-contact.md **Field mapping:** - A record enriched for the first time this year maps to ZoomInfo: 1 bulk data credit, then free for a year. The record is placed under management for a rolling 12 months and can be re-enriched without another credit, though each enrichment still counts against the record limit. - A search, or a lookup maps to ZoomInfo: free. Lookup, Search Companies, Search Contacts, Find Similar Companies, Find Similar Contacts and Find Recommended Contacts consume no credits. - An email, a name or a domain maps to Reverse Contact: 2 credits, unmetered from $699. Identity, current role, history and the company on one schema. A miss returns null with a confidence score and costs nothing. - A profile URL maps to Reverse Contact: 1 credit, unmetered from $249. Half the price, same schema. On a list sourced from profiles this is the single largest lever on the bill. - A freshness check maps to Reverse Contact: free, and the fairest tiebreak. Says whether a profile is cached and when it was last updated. Use it when two providers disagree, because the answer is usually a refresh date. - A missing email or phone number maps to Reverse Contact: 3 and 20 credits, on a result only. Both asynchronous, returning a task id to poll, and both stay on credits on every plan including Platform. - Either provider's answer maps to A verifier, before a sequence. This is ZoomInfo's stated objection to waterfalls and the right answer to it. Resolved is not deliverable on any provider. - Anything between the two maps to Nothing at all. No sync, no app, no shared object. The orchestrator is the only thing that knows both exist. - Does not cross: An integration between the two. No app, no sync, no shared object, and a waterfall is something your orchestrator does rather than something either vendor provides. - Does not cross: A ZoomInfo price. It is quoted rather than listed, so no figure appears on this page and no per-record rate is derived from one. - Does not cross: A dollar cost per enriched record on either side. ZoomInfo sells credits in bulk annually and Reverse Contact sells packs and plans, and dividing either by a record count would be our arithmetic wearing their authority. - Does not cross: Intent data and org charts. ZoomInfo sells both and Reverse Contact does not, which is the clearest reason on this page to keep a ZoomInfo contract rather than replace it. **What breaks:** - **ZoomInfo meters records, not calls.** Each time a record is enriched for the first time within a rolling 12-month period, one credit is consumed and the record is placed under management for a year, during which it can be enriched again without consuming another credit. Each enrichment still counts against the customer's record limit, and credits are purchased in bulk annually. - **Three rate-limit windows, all checked at once.** Standard is 25 a second, 54,000 an hour and 648,000 a day; Builder is 5, 10,800 and 129,600; Scaling is 35, 75,600 and 907,200. The hour and day windows are rolling rather than fixed, a request succeeds only if all three have capacity, and rejected requests do not consume quota. - **Some ZoomInfo operations are free.** Lookup, Search Companies, Search Contacts, Find Similar Companies, Find Similar Contacts and Find Recommended Contacts consume no credits; Enrich Companies and Enrich Contacts cost one bulk data credit per new record. That is the same shape as Reverse Contact's free check and free search count, arrived at independently. - **Two ZoomInfo pages disagree about rate-limit headers.** The rate-limits page lists six headers returned on every response, with the older pair deprecated and due for removal on 2027-01-01. The credit usage page says rate-limit headers are not currently returned. Both are current and this is their inconsistency rather than ours, so read the headers and have a fallback. - **The documentation changed host.** docs.zoominfo.com now returns a permanent redirect to docs.gtm.ai, so a citation or a bookmark from before the move points at a 301. Every ZoomInfo figure on this page was read from the new host on 2026-10-28. - **ZoomInfo pricing is quoted rather than listed.** There is no published price, no published per-record rate and no way to derive one honestly, so this page states none. The rate-limit package names are published and the money is not, which means the throughput you get is knowable in advance and the cost is not. - **Reverse Contact's Unlimited plans stop at 100,000 profiles a day.** Covered calls cost nothing up to 100,000 profiles per workspace per UTC day, then return 429 DAILY_EXTRACTION_LIMIT_EXCEEDED until midnight UTC. ZoomInfo Standard allows 648,000 requests a day and charges per new record, so the two ceilings are in different currencies as well as different sizes. - **Neither coverage figure predicts your list.** Reverse Contact publishes 70%+ as a global identity match rate and says to measure your own on 500 rows. ZoomInfo publishes corpus sizes and no match rate. Both are descriptions of a database rather than forecasts about your rows. **Failures people hit:** - The ZoomInfo credits lasted and the record limit did not. Why: Re-enriching a record under management consumes no credit and still counts against the record limit, which are two separate budgets. Fix: Track both. A refresh schedule designed around the credit model will quietly spend the limit instead, and the limit is the one that is not replenished by not spending credits. - A 429 from ZoomInfo while well under the per-second limit. Why: Three windows are evaluated simultaneously, and the hour and day windows are rolling rather than fixed, so a burst an hour ago still counts. Fix: Read X-RateLimit-Rejected-Bucket from the 429, which names whether it was the second, the hour or the day. Rejected requests do not consume quota, so a backoff costs nothing but time. - The rate-limit headers are not there. Why: ZoomInfo's two documentation pages disagree: the rate-limits page lists six headers on every response, the credit usage page says headers are not currently returned. Fix: Read them when present and fall back to exponential backoff with jitter when they are not. Note also that the older X-RateLimit-Limit and X-RateLimit-Remaining are deprecated and due for removal on 2027-01-01. - A bookmarked ZoomInfo doc now redirects. Why: docs.zoominfo.com returns a permanent redirect to docs.gtm.ai. Fix: Update the citation rather than following the redirect each time. Every ZoomInfo figure on this page was read from the new host on 2026-10-28. - The waterfall produced a worse list than the single provider did. Why: A waterfall takes the first answer it receives, so a badly ordered one promotes a weak source above a strong one. This is ZoomInfo's published objection to the architecture. Fix: Order by accuracy rather than by price, and add verification at the end. The objection is sound and the answer to it is a step rather than a different provider. - The two providers disagree about where somebody works. Why: Two corpora refreshed on different schedules will differ, and the difference is usually recency rather than accuracy. Fix: Compare update dates instead of values. Reverse Contact's free check returns when the profile was last updated, which settles most disagreements for nothing. - 429 DAILY_EXTRACTION_LIMIT_EXCEEDED on an Unlimited plan. Why: Reverse Contact's covered calls are unmetered up to 100,000 profiles per workspace per UTC day and refused until midnight UTC after that. Fix: Spread the job across UTC days. ZoomInfo Standard allows 648,000 requests a day by comparison, and charges per new record, so the comparison is a trade rather than a win either way. - A comparison chart does not match either vendor's own site. Why: Vendors publish figures about competitors. ZoomInfo's own site gives Apollo 270M contacts and 70M companies while Apollo publishes 240M and 30M. Fix: Quote a vendor only about itself and measure the rest. A figure nobody will stand behind in their own documentation is not a figure to buy on. **What practitioners say** (14 threads from 2025 to 2026, read 2026-10-28): Nobody discusses this pair by name, because it is not a pair, so the search was for the job: whether to keep a ZoomInfo contract and what to put in its place. The harvest is unusually practical, including a bake-off methodology with a decision rule in it, and the most useful contributions are the ones that say what ZoomInfo is genuinely better at. Nobody in it argues from coverage figures, which is the opposite of how the category markets itself. - Run a bake-off with a decision rule, and name what you would keep it for (r/gtmengineering, December 2025, 3 points): https://www.reddit.com/r/gtmengineering/comments/1pd3odj/can_clay_be_my_main_enrichment_tool_instead_of/ - Accuracy beats corpus size, according to the people buying it (r/SalesOperations, April 2026, 2 points): https://www.reddit.com/r/SalesOperations/comments/1si8jz0/zoominfo_alternatives_for_revops_teams_what/ - A cached database is as current as its last refresh (r/SalesOperations, April 2026, 1 points): https://www.reddit.com/r/SalesOperations/comments/1si8jz0/zoominfo_alternatives_for_revops_teams_what/ - Keeping both and adding a layer is a real option (r/SalesOperations, April 2026, 1 points): https://www.reddit.com/r/SalesOperations/comments/1si8jz0/zoominfo_alternatives_for_revops_teams_what/ - One team replaced the contract with a lookup in a chat window (r/gtmengineering, December 2025, 3 points): https://www.reddit.com/r/gtmengineering/comments/1pd3odj/can_clay_be_my_main_enrichment_tool_instead_of/ Sources: https://docs.gtm.ai/docs/rate-limits | https://docs.gtm.ai/docs/credit-usage-and-limits | https://www.zoominfo.com/about | https://www.apollo.io/pricing | https://docs.reversecontact.com/getting-started | https://docs.reversecontact.com/guides/credits | https://docs.reversecontact.com/guides/rate-limits | https://www.reversecontact.com/pricing ### Apollo and Reverse Contact Two providers, no integration. Apollo cannot tell you what a waterfall call will cost, and says so. - Built as: Built on the API, Zapier, Make or n8n - Syncs: One way, out - Moves: Contacts, Companies - Costs to turn on: Needs a higher plan. Setup: Hours - Requires: An Apollo paid plan for API enrichment, a Reverse Contact API key, and an orchestrator to run the waterfall - Full guide: https://www.reversecontact.com/integrations-hub/apollo-integrations/apollo-reverse-contact-integration **Verdict.** These are competitors, so the honest page is a waterfall rather than an integration, and the useful finding is not about coverage. It is that Apollo is itself a waterfall over data partners your admin configures, which means Apollo cannot tell you in advance what a call will cost or whether a miss is billed, and its documentation says exactly that. Reverse Contact publishes a credit cost per endpoint and a flat rule that errors are free. Those are two different products wearing the same category name, and knowing which one you are buying matters more than either coverage figure. **What syncs:** - Nothing (out): There is no sync between two data providers, no app on either side and nothing to configure between them. - The first call (out): Whichever provider suits the identifier you hold, in Clay, n8n or your own code. - The fallback (out): The other provider, on the rows that came back null. This is the only sense in which the two are connected. - The verification (out): A separate step at the end, which almost every practitioner who has built this says they added. **Which editions carry it** (rows Apollo, columns Reverse Contact): - Apollo search over its database with The per-call cost is published: Not published - Apollo search over its database with A miss is free: Not published - Apollo search over its database with The answer is in the response: Synchronous - Apollo search over its database with Some plan stops metering it: Always on credits - Apollo waterfall for email or phone with The per-call cost is published: Depends on your config - Apollo waterfall for email or phone with A miss is free: Depends on your config - Apollo waterfall for email or phone with The answer is in the response: Webhook only - Apollo waterfall for email or phone with Some plan stops metering it: Always on credits - Reverse Contact from an email or domain with The per-call cost is published: Published - Reverse Contact from an email or domain with A miss is free: Free - Reverse Contact from an email or domain with The answer is in the response: Synchronous - Reverse Contact from an email or domain with Some plan stops metering it: Unmetered from $699 - Reverse Contact from a profile URL with The per-call cost is published: Published - Reverse Contact from a profile URL with A miss is free: Free - Reverse Contact from a profile URL with The answer is in the response: Synchronous - Reverse Contact from a profile URL with Some plan stops metering it: Unmetered from $249 - Reverse Contact Find Email or Find Phone with The per-call cost is published: Published - Reverse Contact Find Email or Find Phone with A miss is free: Free - Reverse Contact Find Email or Find Phone with The answer is in the response: A task id to poll - Reverse Contact Find Email or Find Phone with Some plan stops metering it: Always on credits **How to connect it** (Somebody who can create an Apollo API key on a paid plan, somebody who can create a Reverse Contact key, and whoever owns the orchestrator.. An afternoon to build. A week to get a result you believe.): 1. Write down the question before choosing a provider, because this decides everything else [Your own notes, not a tool]. Finding people you did not know about is a search problem and resolving somebody you already hold is a lookup problem. They have different costs, different failure modes and different providers, and a waterfall that mixes them pays search prices for rows that only needed resolving. 2. Audit which identifier your rows already carry [Your CRM, your list or your warehouse]. A profile URL is a 1-credit cached lookup on Reverse Contact and unmetered from the $249 plan. An email, a name or a domain is 2 credits and unmetered only from $699. Apollo separately advises a name, a LinkedIn URL or an email for better match rates, so the audit pays off on both sides. 3. Create both keys, and spend the trials rather than a budget [Apollo and Reverse Contact]. Reverse Contact gives a trial with no card and 500 credits on a new account, which is 500 profile-URL lookups or 250 reverse ones, and it runs until those credits are spent rather than for a number of days. Apollo grants 30,000 credits per seat per year upfront on Basic, so a pilot there is a draw against a budget you have already committed. 4. Decide the order by cost of a miss, not by coverage [Your orchestrator]. The provider whose misses are free belongs first, because the rows it cannot resolve cost nothing to discover. On Reverse Contact that is every endpoint except a live fetch; on Apollo's waterfall it depends on which sources your admin configured, so find that out before fixing the order. 5. Check before you fetch, on the endpoint that costs nothing [POST /v2/fetch/persons/check]. The free check says whether a profile is cached and when it was last updated, so a second pass over a list pays only for what has moved. On a bake-off this also tells you how much of one provider's apparent advantage is simply a fresher copy of the same record. 6. Give the webhook somewhere to land before calling the waterfall [Apollo: webhook_url on the request]. Apollo requires a valid webhook_url on every waterfall request and does not return phone numbers in the synchronous response. A build that reads only the immediate reply will report that phones are never found, which is a configuration error that looks exactly like a coverage result. 7. Add the verification step, because everybody who has done this says to [A verifier, at the end]. Every practitioner account of this build ends with a verification step, and several describe paying for verified addresses that bounced anyway. A resolved identity and a deliverable address are two different claims and only one of them is what a sequence needs. 8. Count the resolved rate and the bounce rate separately [Your bake-off sheet]. A provider can identify the right person and give you a dead address, or give you a live address for the wrong person, and a single accuracy number hides both. Reverse Contact returning null with a confidence score rather than a guess is only worth something if your count distinguishes a refusal from a mistake. 9. Decide what a null does before the first production run [Your orchestrator]. Fall through to the other provider, queue for review, or write nothing. All three are defensible and the one that is not is writing a low-confidence guess into a field that a rep will read as a fact. **How to check it worked:** - Run the same 500 rows through both, in both orders, and compare the totals. If the order changes the result by more than the overlap, one of the two is being asked the wrong question. - Count what each provider does when it does not know. A null with a confidence score and a plausible wrong answer cost the same and are not the same, and only your count can tell them apart. - Deliberately send a waterfall request to Apollo with no webhook and read what comes back. Knowing that phones arrive only at the webhook is better learned in a test than from a coverage report. - Verify a sample of addresses from both and record bounces separately from misses. Several practitioners describe paying extra for verified emails that bounced, and the only defence is your own count. Agent skill for this pair: https://www.reversecontact.com/integrations-hub/skills/apollo-reverse-contact.md **Field mapping:** - An email, a name or a domain maps to Reverse Contact: 2 credits, unmetered from $699. Identity, the current role, history and the company on one schema. A miss returns null with a confidence score and costs nothing. - A profile URL maps to Reverse Contact: 1 credit, unmetered from $249. Half the price, same schema. The identifier you hold decides the bill more than the plan does. - A set of filters, looking for new people maps to Apollo search, or Reverse Contact people search. Apollo's paid plans allow 200 search requests a minute, 6,000 an hour and 50,000 a day. Reverse Contact charges 1 credit per profile delivered and nothing for the count endpoint that sizes the result first. - A record missing an email or a phone maps to Apollo waterfall, with run_waterfall_email or run_waterfall_phone. Needs a webhook_url, and phone results come back only at the webhook. The sources queried, and what a miss costs, are whatever your admin configured. - The same gap maps to Reverse Contact Find Email at 3, Find Phone at 20. Charged only when one is found, asynchronous, returning a task id to poll with check_task. These stay on credits on every plan. - A record you think is stale maps to The free check, then a 2-credit live refresh. The check costs nothing and says when the profile was last updated. The live refresh is the one call here billed even when it finds nothing. - Either provider's answer maps to A verifier, before a sequence. Resolved is not deliverable. This step is in every practitioner account of this build and in neither vendor's quickstart. - Anything between the two maps to Nothing at all. No sync, no app, no shared record. The orchestrator is the only thing that knows both exist. - Does not cross: An integration between the two. There is no app, no sync and no shared object, and a waterfall is something your orchestrator does rather than something either vendor provides for the other. - Does not cross: A dollar cost per enriched record for either side. Apollo grants credits per seat per year and Reverse Contact sells packs and plans, and dividing either by a record count would be our arithmetic wearing their authority. - Does not cross: A single answer to what an Apollo waterfall miss costs. Apollo states that it depends on the data requested, your plan, your team's configuration, the sources attempted and each source's pricing rules. - Does not cross: A recommendation based on coverage alone. Both figures are statements about a corpus, and the only figure that decides anything is the one you measure on your own rows. **What breaks:** - **Apollo lists API enrichment as a paid feature.** Apollo's pricing page puts API Enrichment, Waterfall Enrichment, Automated CRM Enrichment and CRM Integrations in the Basic plan at $49 per seat per month on annual billing, with 30,000 credits per seat per year granted upfront. Professional is $79 per seat per month with 48,000, so the entry point for anything on this page is a paid seat. - **Apollo rate limits move with the plan.** General endpoints are 50 a minute, 200 an hour and 600 a day on Free, rising to 200, 400 and 2,000 on Basic and Professional and 200, 600 and 6,000 on Organization. Search is 200 a minute, 6,000 an hour and 50,000 a day on the paid plans, and a 429 carries a retry-after header. - **Apollo's waterfall requires a webhook.** Every waterfall request takes a valid webhook_url, and the synchronous response does not include phone numbers, so phone results arrive only at the webhook. Apollo also advises supplying at least a first and last name, a LinkedIn URL or an email for better match rates, which is the same dependence on an identifier the rest of this page is about. - **What a waterfall miss costs is not a single number.** Apollo states that some data sources charge only when they return data and that others may consume credits for a lookup even when they find nothing, and that usage depends on the data requested, your plan, your team's configuration, the sources attempted and each source's pricing rules. That is honest and it means the cost of a miss is a property of your configuration rather than of the product. - **Reverse Contact publishes one rule, with one exception.** Every 4xx and 5xx is 0 credits, a 404 depends on the endpoint, and Find Email and Find Phone are charged only when something is found. The exception is a live fetch, whose 2 credits are charged when the job is created and kept even when no profile is found, on every plan including Platform. - **Unlimited has a daily ceiling of 100,000 profiles.** The covered calls cost nothing up to 100,000 profiles per workspace per UTC day, then return 429 DAILY_EXTRACTION_LIMIT_EXCEEDED until midnight UTC. The minute limit is 100 on Go, Plus and Max alike, so the plans buy unmetered endpoint families rather than throughput. - **Neither coverage figure predicts your list.** Reverse Contact publishes 70%+ as a global identity match rate and says to measure your own on 500 rows. Apollo's documentation offers no match rate and instead tells you which identifiers improve one. Treat both as statements about a corpus rather than about your rows. **Failures people hit:** - The waterfall never returns a phone number. Why: Apollo requires a webhook_url on every waterfall request and phone results are not in the synchronous response. Fix: Stand the webhook up first and confirm it receives a test payload. This failure is indistinguishable from a coverage problem and has been mistaken for one. - The credit burn is far higher than the pilot suggested. Why: A waterfall was ordered by coverage rather than by what a miss costs, so the rows nobody could resolve were discovered expensively. Fix: Put the provider whose misses are free first. Find out which of your configured Apollo sources charge on a lookup rather than on a result, since Apollo states that both kinds exist. - A search was run on rows that already had an email. Why: Find somebody new and resolve somebody you hold were treated as the same operation, which is the mistake step one of the checklist exists to prevent. Fix: Split the list by the identifier it carries. Rows with an email or a profile URL go to a lookup, and only the rows with neither need a search. - The verified emails bounced. Why: Resolution and deliverability are two different claims, and neither provider's match is a delivery guarantee. Fix: Add a verification step before anything reaches a sequence, and count bounces separately from misses. Every practitioner account of this build includes this step and neither vendor's quickstart does. - A 429 from Apollo on a backfill. Why: General endpoints allow 200 a minute, 400 an hour and 2,000 a day on Basic and Professional, with Organization at 200, 600 and 6,000. Fix: Honour the retry-after header and check which plan the key belongs to, because the hourly and daily figures differ between Basic and Organization while the per-minute one does not. - 429 DAILY_EXTRACTION_LIMIT_EXCEEDED on an Unlimited plan. Why: Reverse Contact's covered calls are unmetered up to 100,000 profiles per workspace per UTC day and refused after that until midnight UTC. Fix: Spread the job across UTC days. The minute limit is 100 on Go, Plus and Max alike, so a bigger plan buys unmetered families rather than a faster backfill. - The two providers disagree about where somebody works. Why: A cached database is as current as its last refresh, and the two corpora are refreshed on different schedules. Fix: Treat the disagreement as the signal rather than as an error, and check the update date. Reverse Contact's free check returns when the profile was last updated, which is the cheapest tiebreak available. - The comparison chart somebody sent does not match either vendor's site. Why: Vendors publish figures for their competitors. ZoomInfo's own site gives Apollo 270M contacts and 70M companies while Apollo publishes 240M and 30M. Fix: Quote a vendor only about itself, and run your own 500 rows. A number nobody will stand behind in their own documentation is not a number to buy on. **What practitioners say** (14 threads from 2025 to 2026, read 2026-10-28): Nobody discusses this pair by name, because it is not a pair, so the search was for the job: deciding between enrichment providers and stacking them when one is not enough. This is the most opinionated harvest of the seven and the most useful, because people who pay for Apollo say what they get. One comment names the exact failure mode this directory's honesty rules exist to prevent, without knowing it was doing so. - A wrong answer instead of no answer is the expensive failure (r/gtmengineering, September 2026, 1 points): https://www.reddit.com/r/gtmengineering/comments/1wjqc2o/apolloio_review_has_it_actually_gotten_better_or/ - The corpora overlap more than the marketing suggests (r/gtmengineering, September 2026, 3 points): https://www.reddit.com/r/gtmengineering/comments/1wjqc2o/apolloio_review_has_it_actually_gotten_better_or/ - Staleness shows up as people who left, not as empty fields (r/gtmengineering, September 2026, 1 points): https://www.reddit.com/r/gtmengineering/comments/1wjqc2o/apolloio_review_has_it_actually_gotten_better_or/ - Changing provider does not fix decay, because they all decay (r/SalesOperations, December 2025, 1 points): https://www.reddit.com/r/SalesOperations/comments/1pph89g/crm_data_enrichment_was_60_garbage_after_3_months/ - The meter matters as much as the match, and they differ by provider (r/SalesOperations, December 2025, 1 points): https://www.reddit.com/r/SalesOperations/comments/1pph89g/crm_data_enrichment_was_60_garbage_after_3_months/ Sources: https://docs.apollo.io/reference/rate-limits | https://docs.apollo.io/docs/enrich-phone-and-email-using-data-waterfall | https://docs.apollo.io/reference/people-enrichment | https://docs.apollo.io/docs/api-pricing | https://www.apollo.io/pricing | https://www.zoominfo.com/about | https://docs.reversecontact.com/getting-started | https://docs.reversecontact.com/guides/credits | https://docs.reversecontact.com/guides/rate-limits | https://www.reversecontact.com/pricing ### LinkedIn Sales Navigator and Reverse Contact The only route on this hub that needs no Sales Navigator edition, and the one the User Agreement addresses by name. - Built as: Built on the API, Zapier, Make or n8n - Syncs: One way, out - Moves: Contacts, Companies - Costs to turn on: Metered by usage. Setup: Minutes - Requires: A Reverse Contact API key. No LinkedIn edition, no LinkedIn API access and no browser extension - Full guide: https://www.reversecontact.com/integrations-hub/linkedin-integrations/linkedin-reverse-contact-integration **Verdict.** Every other page on this hub answers what you are allowed to connect. This one does not connect to LinkedIn at all, which is both its appeal and the thing to be clear-eyed about. A profile URL resolves to a record for 1 credit without any Sales Navigator edition, any API approval or anything running in a rep's browser, and section 8.2 of the User Agreement still addresses information obtained from the Services through third parties such as data aggregators. The mechanical risk and the contractual question come apart here, and a reader deserves both rather than whichever one suits the publisher. **What syncs:** - A profile URL (out): Copied, exported or already on the record. Nothing reads it from LinkedIn on your behalf. - The lookup (out): POST /v2/fetch/persons for a profile URL at 1 credit, or /v2/enrich/persons from an email at 2. - The record (out): Identity, current role, history and the company, on the same schema whichever identifier went in. - Nothing at all (out): No data is written to LinkedIn, no connection is made and no message is sent. There is no inbound direction on this page. **Which editions carry it** (rows LinkedIn Sales Navigator, columns Reverse Contact): - CRM Sync, through an approved partner with A Sales Navigator edition: An Advanced Plus upgrade - CRM Sync, through an approved partner with Risk to a rep's own account: No rep in the path - CRM Sync, through an approved partner with Addressed by section 8.2 as written: An authorised route - CRM Sync, through an approved partner with Somebody to escalate to: Both vendors - An embedded tile in a partner product with A Sales Navigator edition: An Advanced Plus upgrade - An embedded tile in a partner product with Risk to a rep's own account: No rep in the path - An embedded tile in a partner product with Addressed by section 8.2 as written: An authorised route - An embedded tile in a partner product with Somebody to escalate to: Both vendors - A browser extension over linkedin.com with A Sales Navigator edition: No edition at all - A browser extension over linkedin.com with Risk to a rep's own account: Risk to a rep - A browser extension over linkedin.com with Addressed by section 8.2 as written: Reached by the clause - A browser extension over linkedin.com with Somebody to escalate to: Nobody - A third-party database, from a profile URL with A Sales Navigator edition: No edition at all - A third-party database, from a profile URL with Risk to a rep's own account: No rep in the path - A third-party database, from a profile URL with Addressed by section 8.2 as written: Reached by the clause - A third-party database, from a profile URL with Somebody to escalate to: One vendor only **How to connect it** (Whoever can create a Reverse Contact API key. There is no LinkedIn administrator in this build, which is the point.. Minutes through the Clay, Zapier or Make app. An hour against the API directly.): 1. Read section 8.2 with whoever owns that decision, before building anything [LinkedIn: the User Agreement, and your own counsel]. The clause covers information obtained from the Services directly or through third parties such as data aggregators or brokers, without the content owner's consent. This page states the clause and does not interpret it for you, and this is the step that cannot be undone after a list has been built on it. 2. Find out which identifier your records already carry [Your CRM or your list]. A profile URL is a 1-credit cached lookup and unmetered from the $249 plan. An email, a name or a domain is a 2-credit reverse lookup and unmetered only from $699. This single question changes the cost of a backfill by more than any other decision on the page. 3. Create the key and spend the trial credits on your own rows [Reverse Contact: Workspace > API Keys]. The trial takes no card and a new account starts with 500 credits, which is 500 profile-URL lookups or 250 reverse ones, and it runs until those credits are spent rather than for a number of days. The published 70%+ identity match rate is a global figure and Reverse Contact says to measure your own, so spend the trial on that rather than on a demo list. 4. Decide the precision threshold before you look at any results [The request, as a parameter]. Reverse Contact returns null with a confidence score rather than a guess, and the threshold can be raised on the request. Setting it after seeing the results is how a team talks itself into accepting thin matches, which on a list sourced from profiles is the main way this goes wrong. 5. Check before you fetch, on the endpoint that costs nothing [POST /v2/fetch/persons/check]. The free check says whether a profile is cached and when it was last updated. On a list you have enriched before, this is the difference between re-resolving everything and paying only for what has actually moved. 6. Compare the returned employer against what you already hold [Your middle layer or your Clay table]. A list built from profiles six months ago is a list of people some of whom have moved, and a disagreement between the returned current position and the account on your record is the most valuable thing in the response. It is also the only thing on this page that no LinkedIn integration will tell you, because CRM Sync moves data forward rather than auditing what is there. 7. Write to your own system, because there is nowhere else to write [Your CRM, your sequencer or your warehouse]. Nothing in this build writes to LinkedIn, makes a connection or sends a message, and there is no product surface in LinkedIn that would accept it. Treat the output as a record for your own systems and the page's shape follows from that. 8. Run 500 rows and count before anybody plans a campaign on it [Clay, a sheet, or a script]. On [the Clay route](pair:clay+reverse-contact) this costs Clay credits and no Reverse Contact account at all, which makes it the cheapest measurement available. Your own match rate on your own list is the number that decides everything downstream, and it is never the published one. **How to check it worked:** - Take a profile URL for somebody whose job you know changed recently and run it. The returned current position is the test of whether the database is as fresh as the marketing says, measured on a case you can check. - Run the same person from their email and from their profile URL. Compare the records and the cost, because one of those calls is half the price of the other and on most lists you have a choice. - Set the precision threshold high and run fifty rows, then set it low and run the same fifty. The difference is the number of matches you would have accepted without a threshold, and it is usually larger than anybody expects. - Confirm nothing in your build authenticates to LinkedIn. If a step asks a rep to log in, you have assembled a browser extension by accident and the risks on this page have changed. Agent skill for this pair: https://www.reversecontact.com/integrations-hub/skills/linkedin-reverse-contact.md **Field mapping:** - A LinkedIn profile URL maps to POST /v2/fetch/persons, 1 credit. The cheap direction, and unmetered from the $249 plan. A list exported from a profile source usually already carries this column. - An email address maps to POST /v2/enrich/persons, 2 credits. The reverse direction, and unmetered only from the $699 plan. This is the route for an old CRM record that has an address and no profile. - A first name, last name and company maps to POST /v2/enrich/persons, 2 credits. Same price as an email and a thinner identifier, so the confidence score matters more. Raise the precision threshold rather than accepting what comes back. - A company domain maps to POST /v2/enrich/companies, 2 credits. Firmographics from a domain, on the same schema. The enrich_company MCP tool takes a domain as well since November 2026, so an agent no longer has to search first. - currentPosition.title and companyName maps to Your CRM, on fields it owns. The two values a list sourced from profiles is most likely to have wrong, because a profile export is a snapshot and people move. - The position history maps to Context, not a field. Useful for a human writing a first line and poor as a filter. Store it if you will read it and skip it if you will not. - The confidence score maps to A branch, decided in advance. Returning null rather than a guess only helps if something downstream acts on it: another provider, a review queue, or writing nothing. - Anything at all maps to Not LinkedIn. No write, no connection request, no message, no activity. There is no inbound direction in this integration and no product surface that would take one. - Does not cross: Anything written to LinkedIn. No connection, no message, no InMail and no activity, and nothing in the product that would accept one. - Does not cross: The LinkedIn API. Sales permissions require approval as a Sales Navigator Application Platform partner and LinkedIn says it is not currently accepting new partners, so this route does not involve it at all. - Does not cross: A browser extension. Nothing is installed, no rep authenticates and no request reaches linkedin.com, which is the mechanical difference from the category most of this hub is about. - Does not cross: Connections, followers or engagement data. The response carries a verification badge and a follower count, and neither is a seniority signal however convenient it would be. **What breaks:** - **No LinkedIn edition is required, and that is the finding.** The embedded profile card runs on Advanced, and CRM Sync, activity writeback, record matching and the partner tiles all need Advanced Plus, which is quoted rather than listed. This route needs none of them, because nothing in it authenticates against LinkedIn. - **Section 8.2 names third parties explicitly.** LinkedIn's own help centre quotes the clause as prohibiting members from copying, using, displaying or distributing information obtained from the Services "whether directly or through third parties (such as search tools or data aggregators or brokers), without the consent of the content owner". A separate sub-clause covers developing or using crawlers, browser plugins and add-ons to scrape or copy the Services. Read both and decide knowingly. - **A rep's account is not in the path.** LinkedIn says members using prohibited tools risk having their accounts restricted or shut down, and that such tools may stop working without notice. Neither applies mechanically here, because no rep authenticates, nothing is installed in a browser and no request reaches linkedin.com. That is a real difference from the overlay category and it is not an answer to the clause above. - **A profile URL is half the price of an email.** A cached lookup from a profile URL is 1 credit and unmetered from the $249 plan; a reverse lookup from an email, a name or a domain is 2 credits and unmetered only from $699. The identifier you already hold decides the bill, and on a list sourced from profiles that is a large difference. - **The daily ceiling is 100,000 profiles.** On the Unlimited plans the covered calls cost nothing up to 100,000 profiles per workspace per UTC day, then return 429 DAILY_EXTRACTION_LIMIT_EXCEEDED until midnight UTC. The minute limit is 100 on all three tiers, so a million-row backfill is a seven-day job whatever you pay. - **Nothing here backfills LinkedIn, because nothing writes to it.** The hub's warning that CRM Sync moves data only from the moment it is switched on does not apply to this route, and nor does its opposite: there is no history to import and no switch-on date. What you have is a lookup you can run on any record, at any time, including one from five years ago. - **Under 2 credits the free checks stop too.** Below 2 Reverse Contact credits even the free check endpoints answer 402 NO_CREDITS, while GET /v2/usage and webhook polling keep answering. A sweep designed to check cheaply before spending fails at the check. **Failures people hit:** - A list exported six months ago is full of wrong job titles. Why: A profile export is a snapshot, and LinkedIn data ages faster than most because the field that matters most is the one people change. Fix: Re-resolve from the profile URL rather than re-exporting, which costs 1 credit a row and is unmetered from the $249 plan. Run the free check first so you only pay for the rows that have actually moved. - The backfill cost nearly three times the estimate. Why: The estimate assumed a cached lookup from a profile URL at 1 credit and the list actually held email addresses, which is a reverse lookup at 2 and unmetered only from the $699 plan. Fix: Audit which identifier the list carries before pricing anything. Where both are present, send the profile URL, because the record that comes back is the same either way. - 429 DAILY_EXTRACTION_LIMIT_EXCEEDED on an Unlimited plan. Why: The covered calls are unmetered up to 100,000 profiles per workspace per UTC day, after which they are refused until midnight UTC. Fix: Spread the job across days and watch the clock, which is UTC rather than local. The minute limit is 100 on all three Unlimited tiers, so paying more buys unmetered families rather than throughput. - The matches look plausible and the campaign underperformed. Why: A thin identifier such as a name and a company was accepted without a precision threshold, so low-confidence matches were written as facts. Fix: Raise the threshold on the request and decide in advance what a null should do. Reverse Contact returns null with a confidence score rather than a guess, which is only useful if something branches on it. - Legal asked which agreement covers this and nobody had an answer. Why: The build was treated as a technical choice. Section 8.2 addresses information obtained from the Services through third parties such as data aggregators or brokers, and that is a question for counsel rather than for an engineer. Fix: Have the conversation first, which is step one of the checklist for this reason. A list already built on an unanswered question is the expensive version of this problem. - A rep's LinkedIn account was restricted. Why: Not this build. LinkedIn restricts accounts over tools that scrape, modify the appearance of, or automate activity on its website in a member's own session. Fix: Find the extension. If a step in your process asks a rep to log in to LinkedIn, that part is in a different category from the rest of this page and carries a different risk. - Everything stopped, including the calls that were free. Why: Below 2 Reverse Contact credits the free Check endpoints are paused as well and answer 402 NO_CREDITS. Fix: Watch quotas.workspace.credits.left on every response, and check GET /v2/usage on a schedule because it keeps answering whatever the balance. **What practitioners say** (14 threads from 2025 to 2026, read 2026-10-28): Nobody discusses this pair by name, so the search was for the job: turning a LinkedIn list into records with contact details on them. This is the most candid harvest of the seven, because the question is asked constantly and the honest answer is uncomfortable. One commenter who sells a CRM describes the standard workflow and then calls the category what it is, which is more use than any vendor page on the subject. - The standard workflow is scraping, and practitioners say so (r/CRMSoftware, August 2026, 1 points): https://www.reddit.com/r/CRMSoftware/comments/1w0054d/how_to_export_leads_from_linkedin_sales_navigator/ - A LinkedIn list is stale faster than the rest of your data (r/LeadGeneration, July 2025, 2 points): https://www.reddit.com/r/LeadGeneration/comments/1lvobf2/what_is_the_best_tool_to_enrich_linkedin_with/ - A waterfall is what people assemble when one provider is not enough (r/LeadGeneration, July 2025, 3 points): https://www.reddit.com/r/LeadGeneration/comments/1lvobf2/what_is_the_best_tool_to_enrich_linkedin_with/ - The lead looking right is not the contact details being right (r/CRMSoftware, August 2026, 1 points): https://www.reddit.com/r/CRMSoftware/comments/1w0054d/how_to_export_leads_from_linkedin_sales_navigator/ - A job change is detectable and the review queue is the hard part (r/SalesforceDeveloper, June 2026, 1 points): https://www.reddit.com/r/SalesforceDeveloper/comments/1tutsgq/sales_navigator_salesforce_can_contact_updates_be/ Sources: https://www.linkedin.com/legal/user-agreement | https://www.linkedin.com/help/linkedin/answer/a1341387 | https://learn.microsoft.com/en-us/linkedin/shared/api-guide/concepts/rate-limits | https://learn.microsoft.com/en-us/linkedin/shared/authentication/getting-access | https://www.linkedin.com/help/sales-navigator/answer/a8037044 | https://docs.reversecontact.com/getting-started | https://docs.reversecontact.com/guides/credits | https://docs.reversecontact.com/guides/rate-limits | https://www.reversecontact.com/pricing ### Gong and Reverse Contact Gong Enrich names six data partners. Reverse Contact is not one of them, and bring your own key does not change that. - Built as: Built on the API - Syncs: One way, out - Moves: Activities, Contacts, Companies - Costs to turn on: Metered by usage. Setup: Days - Requires: A Gong technical administrator to create API credentials, a Reverse Contact API key, and somewhere to run the lookup - Full guide: https://www.reversecontact.com/integrations-hub/gong-integrations/gong-reverse-contact-integration **Verdict.** Gong knows exactly who was on the call and surprisingly little about them. Its own Enrich feature closes part of that gap with a waterfall over six named data partners, and Reverse Contact is not one of them, so this is an API build rather than a configuration. The fact worth the whole page is what Gong Enrich does when somebody has changed job: it checks, finds they have left, stops before querying anybody, and charges nothing. You learn that the record is wrong and not what it should say instead. **What syncs:** - The calls (out): GET the calls for a date range, then read the internal and external participants on each. - The external participants (out): Email addresses that may belong to nobody in your CRM, which is the gap this build exists to close. - The lookup (out): POST /v2/enrich/persons on each external address. 2 credits on a match, nothing on an error. - The write (in): To the CRM Gong already reads, or through Gong's own CRM upload endpoint if there is no CRM. **Which editions carry it** (rows Gong, columns Reverse Contact): - Gong Enrich, a partner on Gong credits with Reverse Contact can be the provider: No - Gong Enrich, a partner on Gong credits with A job change says where they went: No - Gong Enrich, a partner on Gong credits with A miss costs nothing: Partly - Gong Enrich, a partner on Gong credits with The answer reaches the Gong record: Yes - Gong Enrich, a partner on your own key with Reverse Contact can be the provider: No - Gong Enrich, a partner on your own key with A job change says where they went: No - Gong Enrich, a partner on your own key with A miss costs nothing: Partly - Gong Enrich, a partner on your own key with The answer reaches the Gong record: Yes - Reverse Contact through the Gong API with Reverse Contact can be the provider: Yes - Reverse Contact through the Gong API with A job change says where they went: Yes - Reverse Contact through the Gong API with A miss costs nothing: Yes - Reverse Contact through the Gong API with The answer reaches the Gong record: Partly - The CRM enriched, Gong reading it with Reverse Contact can be the provider: Yes - The CRM enriched, Gong reading it with A job change says where they went: Yes - The CRM enriched, Gong reading it with A miss costs nothing: Yes - The CRM enriched, Gong reading it with The answer reaches the Gong record: Yes **How to connect it** (A Gong technical administrator for the API credentials, an admin if Enrich is in scope, plus whoever hosts the middle layer and whoever can create a Reverse Contact API key.. A day or two. The credentials and the participant extraction are the slow parts.): 1. Decide whether you are turning Gong Enrich on, because that cannot be undone [Gong: Admin center > Data enrichment]. Gong states that once Enrich is enabled it cannot be disabled, though manual and flow permissions can be withdrawn afterwards. It is a separate question from this build and a cheaper answer to a narrower problem, so decide it deliberately rather than while looking for something else. 2. Work out what your Gong call budget already is [Gong: whatever is already connected]. The limit is 3 calls a second and 10,000 a day for the company, not for your integration. Before designing a sweep, find out what the CRM sync, the BI export and anything else are already spending, because this is the one number on the page that somebody else can exhaust for you. 3. Create API credentials as a technical administrator [Gong: the API page, app.gong.io/company/api]. You get an Access Key and an Access Key Secret, combined with a colon and base64 encoded for a Basic Authorization header, or a bearer token through the OAuth flow. The base URL is per company and is shown on the API authentication page rather than being a constant you can hard-code. 4. Pull the calls for a date range and read the participants [Gong: the calls endpoints, with the cursor]. A list response carries a records field with the page size, the page number and the total, plus a cursor when there is more. Repeat the call with that cursor and change nothing else, and remember that Gong may add JSON fields without warning so ignore what you do not use. 5. Separate the external participants from the internal ones [Your middle layer]. The internal ones are your colleagues and enriching them is a waste of credits and slightly rude. The external ones are the point, and the subset worth paying for is narrower still: the addresses that match nothing you already hold. 6. Check before you fetch, on the endpoint that costs nothing [POST /v2/fetch/persons/check]. The free check says whether a profile is cached and when it was last updated, so a sweep over a quarter of calls spends 2 credits only where the answer is genuinely new. Errors cost nothing either, which is the opposite of how the Gong side of this works. 7. Compare the returned employer against the account the call was filed under [Your middle layer]. This is the whole reason to do this rather than use Enrich. When Gong decides a contact has left the account it stops and tells you nothing further; a reverse lookup on the same address returns the current position, which is where they went. One comparison, and it is the most valuable line of code in the build. 8. Write the answer to the CRM, not to Gong [Your CRM, through its own API]. Gong already reads the CRM, so writing there gives one copy of the answer, costs none of the daily Gong allowance and survives a change of recorder. Gong's API can take CRM data if there is genuinely no CRM, and that is the only case where pushing into Gong is the right move. 9. Run one quarter of calls before running the archive [Your middle layer, with a limit on it]. A quarter tells you how many external participants a call actually has, how many of them are unknown, and therefore what the archive would cost in both credits and Gong calls. At 10,000 calls a day for the company, that arithmetic decides whether a backfill is a weekend or a month. **How to check it worked:** - Take a call with an external participant you know is not in the CRM, and follow it all the way through. If the account ends up on the record, the build works; if it ends up only in a log, it does not. - Enrich somebody who has changed employer since the call, deliberately. The returned current position should name the new company, which is precisely the answer Gong Enrich declines to go and get. - Read the records field and the cursor on a list response rather than assuming one page. A build that reads the first page of a quarter and reports success is the quiet failure here. - Count your Gong calls for a day against 10,000 and remember whose budget it is. If the CRM sync is already using most of it, your sweep has to run when it is not. Agent skill for this pair: https://www.reversecontact.com/integrations-hub/skills/gong-reverse-contact.md **Field mapping:** - A call, by date range maps to The Gong calls endpoint, cursor paged. One of 10,000 company-wide calls a day at 3 a second. The records field carries the page and the total, and a cursor arrives when there is more. - External participants on that call maps to Email addresses, and little else. Gong returns internal and external participants along with topics, trackers, public comments, scorecards and transcripts. An external participant who matches nothing in the CRM is the subject of this page. - That email address maps to POST /v2/enrich/persons, 2 credits. Identity, the current role, the history and the company behind it on one schema. A miss returns null with a confidence score and costs nothing. - The domain of that address maps to POST /v2/enrich/companies, 2 credits. Firmographics from a domain. A meeting booked from a personal address has no useful domain, which is the case where the person lookup is the only route to the account. - currentPosition.companyName maps to A comparison against the filed account. The one row on this table that justifies the build. Gong tells you the contact has left; this tells you where they went. - currentPosition.title and seniority maps to The CRM contact record. Who was actually in the room, in the terms a pipeline review uses. Gong has the attendance and not the seniority. - The resolved contact maps to Your CRM, which Gong already reads. One copy of the answer, no Gong calls spent, and it survives replacing the recorder. Gong's CRM upload endpoint is for the case where there is no CRM at all. - Anything outbound to Reverse Contact maps to Only the identifier you send. This is a read layer. No call, transcript or recording is sent anywhere, and there is nothing in the product to send it to. - Does not cross: Reverse Contact inside Gong Enrich. The supported partners are LeadIQ, Wiza, RocketReach, Lusha, ZoomInfo and Findymail, and bring your own key applies to a partner on that list rather than adding to it. - Does not cross: A published Gong credit rate. Gong says consumption varies by data type, provider and other factors, that the applicable rate is shown in the Admin Center, and that it may be updated prospectively, so no figure belongs on this page. - Does not cross: The transcript. Nothing in this build reads what was said, and a transcript is the one thing on a call record that should not leave the company for an enrichment. - Does not cross: A business email or a direct phone number from Reverse Contact. Both are separate endpoints at 3 and 20 credits, charged only when one is found, and both are asynchronous, which is the same job Gong Enrich already does inside the product. **What breaks:** - **10,000 API calls a day, for the whole company.** Three a second and 10,000 a day, applied at company level rather than per integration, so the budget is shared with every other tool connected to Gong. A 429 carries Retry-After, and Gong states that support can change the limits if required. - **Gong Enrich supports six providers and no others.** LeadIQ, Wiza, RocketReach, Lusha, ZoomInfo and Findymail, with email and phone kept in separate waterfalls that you order independently. Bring your own key applies per supported partner, so it changes the billing rather than the list. - **Enrich stops at a job change rather than resolving it.** Before querying any partner, Gong checks whether the contact still works at the company on their record, and if they do not, or if it cannot match them to a company at all, enrichment stops and no credits are used. That is a sensible way to avoid paying for a dead record and it means the most valuable fact in the response is the one you never get. - **A Gong credit is spent on an email you are not allowed to use.** Returned addresses are validated and a failing one is discarded, and Gong says the credit is still charged because the partner did return data. Reverse Contact's own Find Email refunds when nothing is found, so the two products disagree about what a miss is. - **Enrich cannot be switched off once it is on.** Gong says that once you enable Enrich it cannot be disabled, although permissions for manual and automatic enrichment can be removed afterwards. It is also the one step here that an admin takes rather than a developer. - **A partner already queried is skipped for 90 days.** Within 90 days Enrich skips data partners it has already asked about that contact, and after 90 days the full waterfall can run again. So a second attempt on a stale record is not the same operation as the first, which matters when somebody reports that Enrich again did nothing. - **EU and California contacts can be excluded wholesale.** The enrichment controls carry settings to exclude people located in the European Union and people in California. Useful, blunt, and worth checking before anybody concludes that a region has no data. - **A low balance on either side stops a different thing.** With no Gong credits, contact enrichment stops while account enrichment carries on, manual enrichment becomes unavailable and flows continue without enriching. With no Reverse Contact credits even the free check endpoints answer 402 NO_CREDITS, and GET /v2/usage keeps answering. **Failures people hit:** - Reverse Contact is not in the data partner dropdown. Why: Gong Enrich supports LeadIQ, Wiza, RocketReach, Lusha, ZoomInfo and Findymail, and the list is not extensible by the customer. Fix: Stop looking for it and build on the API instead, or enrich the CRM and let Gong read it. Bring your own key will not help, because it attaches a credential to a partner that is already on the list. - Enrich reported that the contact has left and did nothing else. Why: Gong checks whether the contact still works at the company on their record before querying any partner, and stops if they do not, using no credits. Fix: That is the designed behaviour and it is also your signal. Take the same address to a reverse lookup, which returns the current position, and treat the Gong result as a trigger rather than as a dead end. - A Gong credit was charged for an email we could not use. Why: Returned addresses are validated and a failing one is discarded, and Gong charges the credit anyway because the partner returned data. Fix: Order the waterfall with the most accurate provider first rather than the cheapest, since a wrong answer costs the same as a right one. Nothing on the Gong side refunds it. - Enrich again did nothing on a record we know is stale. Why: Within 90 days Enrich skips data partners it has already queried for that contact, so a second attempt may have nobody left to ask. Fix: Wait for the 90 days, add a partner that has not been tried, or go round it with a lookup of your own. The second attempt is not a retry of the first. - A 429 from Gong halfway through a backfill nobody else was running. Why: The limit is 3 calls a second and 10,000 a day at company level, shared with every other integration connected to Gong. Fix: Honour Retry-After, and find out what the CRM sync and any BI export are spending before scheduling a sweep. Gong says support can raise the limits if required, which is a conversation rather than a setting. - The sweep read one page of calls and reported success. Why: List endpoints page with a cursor, and a response carries a records field with the page size, page number and total. Fix: Repeat the request with the cursor from the previous response and change nothing else. Compare the rows you processed against the total in the records field before believing any run. - A region came back with no data at all. Why: Gong's enrichment controls carry settings to exclude people located in the European Union and people in California. Fix: Check the exclusion settings before concluding anything about coverage. This is a configured policy rather than a gap in anybody's database. - The integration broke after an endpoint rename. Why: Reverse Contact replaced /v2/resolve with /v2/enrich and /v2/search/persons with /v2/search/people, with the old pair documented as live only until 13 October 2026. Fix: Change both paths in the middle layer. Gong separately warns that it may add JSON fields without notice, so a reader that ignores unknown fields survives both kinds of change. **What practitioners say** (14 threads from 2023 to 2026, read 2026-10-28): Nobody discusses this pair by name, so the search was for the job: getting usable facts about the people on a recorded call. The threads are mostly about choosing a conversation intelligence tool, and the useful ones are about what happens to the data afterwards. The best contribution is a warning about automating a field update from an enrichment, which is advice this page needed and does not give itself. - Use a title as a signal rather than as an update (r/Dynamics365, September 2026, 5 points): https://www.reddit.com/r/Dynamics365/comments/1w6czhf/using_claude_as_an_orchestration_layer_across/ - A transcript is data, not an instruction (r/Dynamics365, September 2026, 1 points): https://www.reddit.com/r/Dynamics365/comments/1w6czhf/using_claude_as_an_orchestration_layer_across/ - The data is only worth what something downstream does with it (r/SalesOperations, August 2023, 1 points): https://www.reddit.com/r/SalesOperations/comments/14yys5p/conversational_intelligence_tool/ - What a rep wants at call time is a record, not a transcript (r/salesdevelopment, April 2025, 2 points): https://www.reddit.com/r/salesdevelopment/comments/1k9nc32/nooks_vs_gong_engage_vs/ - The recorder records, and something else has to move the data (r/sales, September 2025, 5 points): https://www.reddit.com/r/sales/comments/1nnoo71/gong_for_startup/ Sources: https://help.gong.io/docs/what-the-gong-api-provides | https://help.gong.io/apidocs/introduction-2 | https://help.gong.io/docs/about-gong-enrich | https://help.gong.io/docs/about-enrich-configuration | https://help.gong.io/docs/configure-enrich-1 | https://help.gong.io/docs/how-enrich-consumes-credits | https://help.gong.io/docs/enrich-a-contact | https://help.gong.io/docs/enrich-contacts-from-a-flow | https://docs.reversecontact.com/getting-started | https://docs.reversecontact.com/guides/credits | https://docs.reversecontact.com/guides/rate-limits | https://www.reversecontact.com/pricing ### Google Workspace and Reverse Contact A custom function gets 30 seconds. A script gets six minutes. A live job can take tens of them. - Built as: Built on the API, Zapier, Make or n8n - Syncs: One way, in - Moves: Contacts, Companies, Custom objects - Costs to turn on: Metered by usage. Setup: Hours - Requires: A Google account, a Reverse Contact API key, and Apps Script or an orchestrator that can read the sheet - Full guide: https://www.reversecontact.com/integrations-hub/google-integrations/google-reverse-contact-integration **Verdict.** A spreadsheet is the only tool in this directory that can call an API, read the answer and do it without paying anybody more, which is why so many enrichment pipelines live in one and why so many of them quietly break. The limits that matter are not rate limits but clocks: 30 seconds inside a cell, 6 minutes inside a script, and a live job that may take longer than both. Build it as a trigger that checkpoints, keep the sheet as the thing people look at, and do not let a formula be the thing that spends credits. **What syncs:** - The queue (out): Rows with an email or a domain and an empty answer column, read by Apps Script or by an orchestrator. - The lookup (out): UrlFetchApp to POST /v2/enrich/persons. 2 credits on a match, nothing on an error. - The answer (in): Written back to the row, keyed on a stable id rather than on a row number. - The state (in): A status column and a timestamp, so a run that dies halfway can be resumed rather than repeated. **Which editions carry it** (rows Google Workspace, columns Reverse Contact): - A custom function in a cell with A 500ms cached lookup: Yes - A custom function in a cell with A 1,000-row pass: No - A custom function in a cell with A live job that takes minutes: No - A custom function in a cell with Running with nobody watching: No - A script run by hand with A 500ms cached lookup: Yes - A script run by hand with A 1,000-row pass: Partly - A script run by hand with A live job that takes minutes: No - A script run by hand with Running with nobody watching: No - A time-driven trigger with A 500ms cached lookup: Yes - A time-driven trigger with A 1,000-row pass: Yes - A time-driven trigger with A live job that takes minutes: Partly - A time-driven trigger with Running with nobody watching: Yes - An orchestrator reading the sheet with A 500ms cached lookup: Yes - An orchestrator reading the sheet with A 1,000-row pass: Yes - An orchestrator reading the sheet with A live job that takes minutes: Partly - An orchestrator reading the sheet with Running with nobody watching: Yes - Your own code on the Sheets API with A 500ms cached lookup: Yes - Your own code on the Sheets API with A 1,000-row pass: Yes - Your own code on the Sheets API with A live job that takes minutes: Yes - Your own code on the Sheets API with Running with nobody watching: Yes **How to connect it** (Anybody with a Google account and the Reverse Contact key. No administrator is involved, which is the appeal and the risk.. An hour for a working script. An afternoon for one that can be left alone.): 1. Give every row a stable id before anything else, because this cannot be retrofitted [Column A of the sheet]. An answer has to come back to an identity rather than to a position, and the moment somebody sorts or filters the sheet a row number stops meaning anything. Write an id once, never reuse one, and key every write on it. This is the only step on the page that is painful to add later. 2. Decide which column is the status, and what its values are [The sheet, as a real column]. Three values are enough: not tried, resolved, and tried and unresolved. An empty answer cell cannot distinguish between a row nobody has reached and a row where the lookup honestly found nothing, and that distinction is what stops you paying twice for the same miss. 3. Put the API key in Script Properties, not in a cell [Apps Script: Project Settings > Script Properties]. A key in a cell travels with every copy of the sheet, every export and every share, and there is no way to take it back out of somebody's downloaded copy. Script Properties stay with the script, and the key goes on the Authorization header rather than in the URL. 4. Check before you fetch, on the endpoint that costs nothing [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 missing. Errors cost nothing either, so a thin list is cheap to discover on the Reverse Contact side even though it still spends your UrlFetch quota. 5. Write the answer before moving on to the next row [Your script loop]. Resist batching the writes to the end of the run, because a six-minute timeout then loses every answer you have paid for. Write each row as it resolves and accept the extra Sheets calls, which are limited at 60 a minute per user and are the cheaper thing to spend. 6. Make the script resumable, then put it on a trigger [Apps Script: Triggers]. A script gets 6 minutes per execution whatever you pay, so a list of any size has to be processed in passes that start where the last one stopped. Reading the status column is what makes that work, and it is why the status column is step two rather than an afterthought. 7. Decide what happens to a live job before you call one [Your own design]. A live fetch returns a task id rather than a record, charges its 2 credits when the job is created and keeps them whatever comes back. Store the task id on the row immediately, and let the next trigger run check it, because nothing in Apps Script can wait that long. 8. Run 500 rows and count, which is the whole point of doing this here [The sheet itself]. The published 70%+ identity match rate is a global average and Reverse Contact says to measure your own. Five hundred of your own rows and a formula give you the number that decides whether any of the rest of this directory is worth building, and a spreadsheet is the cheapest place there is to get it. **How to check it worked:** - Sort the sheet while a run is in progress, deliberately. If an answer lands on the wrong person, the write is keyed on a row number and that is the bug to fix before anything else happens. - Kill the script mid-run and start it again. It should skip what resolved and retry only what did not, and if it starts from the top you are paying for the same rows twice. - Put a formula version of the lookup in one cell and then edit an unrelated cell. If the lookup runs again, you have found out why a custom function is the wrong shape, at a cost of 2 credits. - Run the free check on somebody you know is current and read the update date. If it is recent, a live refresh buys nothing and you have avoided the one endpoint here that bills on a miss. Agent skill for this pair: https://www.reversecontact.com/integrations-hub/skills/google-reverse-contact.md **Field mapping:** - A stable id, written once maps to Column A, never reused. The thing every write is keyed on. A row number is a position rather than an identity and changes the moment anybody sorts or filters. - An email in the row maps to POST /v2/enrich/persons, 2 credits. Identity, the current role and the company on one schema. A miss returns null with a confidence score and costs nothing. - A domain in the row maps to POST /v2/enrich/companies, 2 credits. Firmographics from a domain. Deduplicate the domains first, because a list of people at twenty companies needs twenty company calls rather than a hundred. - A profile URL in the row maps to POST /v2/fetch/persons, 1 credit. Half the price, and unmetered from the $249 plan rather than the $699 one. A list exported from a profile source usually already has this column. - currentPosition.title and companyName maps to Two columns the script owns. Keep them separate from anything a person types in, because a script that overwrites a hand-corrected cell is the fastest way to lose the team's trust in the sheet. - The confidence score maps to A number column, not a hidden rule. In a sheet the threshold can be a formula somebody can see and argue with, which is better than a constant buried in the script. - A live job's task id maps to Its own column, written before the wait. The 2 credits are charged at job creation and kept whatever comes back, so the id is the only record that you have already paid. - The status and the timestamp maps to Two columns, both required. What makes the run resumable and what stops a second pass paying again for a miss. Without them an empty answer cell means two different things. - Does not cross: A Google Workspace Marketplace app. Reverse Contact publishes none, which is consistent with apps on Clay, Zapier and Make and nothing inside any CRM, sequencer or productivity suite. - Does not cross: A supported way to wait for a live job in one execution. The runtime caps are 30 seconds in a custom function and 6 minutes in a script, on every account type. - Does not cross: A business email or a direct phone number in a formula. Both are separate endpoints at 3 and 20 credits, charged only when one is found, and both are asynchronous. - Does not cross: Anything that makes a sheet transactional. The status column is a convention you maintain, not a guarantee the store provides. **What breaks:** - **A custom function gets 30 seconds, a script gets six minutes.** Both figures are the same on a consumer account and on Workspace, so there is no upgrade that buys more time. A lookup documented at 500ms at the 95th percentile fits either; a live job documented as possibly taking tens of minutes fits neither, and that is the one constraint on this page that no amount of care works around. - **UrlFetch is 20,000 a day, or 100,000 on Workspace.** Per user, resetting 24 hours after the first request rather than at midnight. A response is capped at 50 MB with 100 headers and 8 KB of header data per call, none of which an enrichment response comes near. - **Triggers get 90 minutes a day, or six hours on Workspace.** That is total runtime across all time-driven triggers on the account, which is the real budget for an unattended sweep. On a consumer account 90 minutes a day is fifteen six-minute executions, so the checkpoint has to be efficient rather than merely present. - **The Sheets API is 60 writes a minute per user.** 300 requests a minute per project and 60 a minute per user per project, counted separately for reads and writes, with no daily limit at all. Exceeding it returns 429 and the documented remedy is truncated exponential backoff, so a writer that retries immediately makes it worse. - **A sheet has no row locking.** Two runs writing the same row produce one surviving value and no error, and a run that dies halfway leaves rows that look pending and are not. Nothing in Apps Script or the Sheets API fixes this; it is a property of the store, and the fix is a status column with an owner and a timestamp. - **A row number is not an identity.** Sorting a sheet, inserting a row or filtering it moves every row below the change. An answer that comes back addressed to row 412 lands on whoever is in row 412 now, which is a silent, plausible, wrong result of exactly the kind this directory refuses to publish. - **A live fetch is billed even when it finds nothing.** Its 2 credits are charged when the job is created and kept whatever comes back, which is the one Reverse Contact endpoint where a miss costs money. In a sheet that matters more than elsewhere, because a failed write leaves the row looking unprocessed and the next run pays again. **Failures people hit:** - The enrichment landed on the wrong person. Why: The write was keyed on a row number and somebody sorted, filtered or inserted a row while the run was going. Fix: Key every write on an id in column A that is written once and never reused. This is the one failure here that produces a confident wrong answer rather than a missing one, which makes it the worst. - Exceeded maximum execution time. Why: Apps Script allows 6 minutes per script execution and 30 seconds per custom function, on every account type. Fix: Process in passes driven by the status column and put the script on a time-driven trigger. There is no plan that raises the per-execution ceiling, so a resumable loop is the only shape that works. - Credits were spent and the rows still look untried. Why: The call and the write are two operations, so a run that is charged and then fails to write leaves the row in its original state. Fix: Write a status and a timestamp as soon as the call returns, and store a live job's task id before waiting on it. A live fetch keeps its 2 credits whatever comes back, which is the one endpoint where this gap costs real money. - Two people ran it and one set of answers vanished. Why: A spreadsheet has no row locking, so concurrent writes resolve to whichever one landed last with no error raised. Fix: Make one writer responsible, or move the job state to a store that can claim a row and keep the sheet as the review screen. Nothing in Apps Script makes a sheet transactional. - A formula in a cell is spending credits on its own. Why: A custom function re-runs whenever the sheet recalculates, and each run is another billed API call. Fix: Use a script or a trigger that writes a value, so the cell ends up holding an answer rather than an instruction to go and buy one again. - Service invoked too many times for one day: urlfetch. Why: UrlFetch is capped at 20,000 calls a day on a consumer gmail.com account and 100,000 on Workspace, per user, resetting 24 hours after the first request. Fix: Deduplicate domains before enriching companies and run the free check first, which is the cheapest way to cut the call count. Note that the Workspace figure matches Reverse Contact's own 100,000 profile daily ceiling, so at that scale both sides stop together. - A 429 from the Sheets API during a write-heavy run. Why: Writes are limited to 60 a minute per user per project and 300 a minute per project, counted separately from reads. Fix: Back off with truncated exponential backoff as the documentation says rather than retrying straight away. There is no daily limit, so slowing down costs nothing but time. - The whole thing broke and the only person who understood it has left. Why: A script in one person's account with the logic in their head, which is the normal end state of a spreadsheet pipeline. Fix: Keep the credential in Script Properties, the status model in the sheet where it is visible, and a comment at the top saying what the columns mean. None of that is technical work and it is the difference between a prototype and something a team owns. **What practitioners say** (14 threads from 2022 to 2026, read 2026-10-28): Nobody discusses this pair by name, so the search was for the job: enriching a list of leads that lives in a spreadsheet. One thread is about precisely this and reads like a post-mortem, which is the most useful material in any of the seven harvests. The agreement across four years is striking: nobody argues that a sheet cannot do it, and everybody who has done it warns about the same three things, none of which are rate limits. - The thing that forces the move is locking, not volume (r/automation, October 2026, 1 points): https://www.reddit.com/r/automation/comments/1x1d243/using_google_sheets_as_the_queue_for_a/ - A row number is not a name, and sorting proves it (r/automation, October 2026, 1 points): https://www.reddit.com/r/automation/comments/1x1d243/using_google_sheets_as_the_queue_for_a/ - Paid for and not written is a state your sheet cannot see (r/automation, October 2026, 1 points): https://www.reddit.com/r/automation/comments/1x1d243/using_google_sheets_as_the_queue_for_a/ - The real bill is maintenance, and it arrives at 2am (r/gtmengineering, April 2026, 2 points): https://www.reddit.com/r/gtmengineering/comments/1s9ylfe/supabase_google_sheets_claude_code_replaced_clay/ - The architecture was obvious four years before the tools were (r/zapier, February 2022, 2 points): https://www.reddit.com/r/zapier/comments/sufa4z/data_enrichment_in_google_sheets/ Sources: https://developers.google.com/apps-script/guides/services/quotas | https://developers.google.com/workspace/sheets/api/limits | https://docs.reversecontact.com/getting-started | https://docs.reversecontact.com/guides/credits | https://docs.reversecontact.com/guides/rate-limits | https://www.reversecontact.com/pricing ### ClickUp and Reverse Contact The Business plan buys the webhook. It does not buy the throughput. - Built as: Built on the API, Zapier, Make or n8n - Syncs: One way, in - Moves: Tasks, Contacts, Companies - Costs to turn on: Needs a higher plan. Setup: Hours - Requires: ClickUp Business or above for task webhooks, a ClickUp API token, and a Reverse Contact API key - Full guide: https://www.reversecontact.com/integrations-hub/clickup-integrations/clickup-reverse-contact-integration **Verdict.** ClickUp can start this and cannot finish it. A Call webhook automation sends a task out at exactly the right moment, which is the hard half of most builds, and then there is no documented way to read the reply back into a custom field, so the answer returns through the API as a separate write. Two plan gates decide whether it is worth doing, and they do not line up: Business turns the webhook on and leaves you on the slowest rate limit ClickUp publishes. **What syncs:** - The trigger (out): A Call webhook automation on a task change, sending the payload to your endpoint with headers you set. - The lookup (out): POST /v2/enrich/persons from your middle layer. 2 credits on a match, nothing on an error. - The write-back (in): The ClickUp API sets the custom fields on the task, against 100 requests a minute on most plans. - The status change (in): Move the task when the lookup resolves, so an unenriched task is visible rather than merely unchanged. **Which editions carry it** (rows ClickUp, columns Reverse Contact): - Free Forever with The Call webhook action exists: No - Free Forever with Actions enough for a 1,000-row pass: No - Free Forever with API fast enough for a backfill: No - Free Forever with Conditions to gate the trigger: No - Unlimited and Core with The Call webhook action exists: No - Unlimited and Core with Actions enough for a 1,000-row pass: Just - Unlimited and Core with API fast enough for a backfill: No - Unlimited and Core with Conditions to gate the trigger: No - Business with The Call webhook action exists: Yes - Business with Actions enough for a 1,000-row pass: Yes - Business with API fast enough for a backfill: No - Business with Conditions to gate the trigger: Yes - Business Plus with The Call webhook action exists: Yes - Business Plus with Actions enough for a 1,000-row pass: Yes - Business Plus with API fast enough for a backfill: Yes - Business Plus with Conditions to gate the trigger: Yes - Enterprise with The Call webhook action exists: Yes - Enterprise with Actions enough for a 1,000-row pass: Yes - Enterprise with API fast enough for a backfill: Yes - Enterprise with Conditions to gate the trigger: Yes **How to connect it** (A ClickUp Workspace admin or owner to activate the Automations ClickApp, plus whoever hosts the middle layer and whoever can create a Reverse Contact API key.. An afternoon on Business or above. Longer if the plan has to be upgraded first.): 1. Check the plan before designing anything, because this one gate decides everything [ClickUp: Settings > Plan]. Task webhooks are unavailable on Free Forever and on Unlimited and Core. There is no configuration, no workaround inside the product and no partial version: either the Call webhook action is there or this build has to happen before the task is created instead. 2. Activate the Automations ClickApp [ClickUp: ClickApps, as an admin or owner]. Automations have to be switched on at Workspace level by an admin or an owner before anybody can create one. Guests cannot create Automations at all, and limited members can only do so where they already have edit permissions on the location. 3. Decide which custom fields the enrichment owns [ClickUp: Custom Fields on the List]. Use fields the enrichment owns outright rather than ones a person edits between calls. Remember that a custom field has to be added to each List or Space you want to combine it in, so decide the scope now rather than after the first dashboard comes back half empty. 4. Create the webhook and put the key in a header [ClickUp: Manage Automations > Webhooks]. Custom headers take an Authorization value, which is where the credential belongs, because a URL parameter ends up in a log. Note before you save that ClickUp will not show you the header value again, so record which key went in somewhere you trust. 5. Test the webhook with the button, on a List that holds nothing real [ClickUp: Test webhook]. The Test webhook button sends an example payload, which is enough to confirm the endpoint, the headers and the shape. Point the first one at a request bin rather than at the enrichment, so that a mistake costs nothing and tells you more. 6. Check before you fetch, on the endpoint that costs nothing [POST /v2/fetch/persons/check]. The free check says whether a profile is cached and when it was last updated, so a backfill spends 2 credits only where the answer is genuinely missing. Every 4xx and 5xx costs nothing either, which means a miss on a thin list is free on the Reverse Contact side even though it still spends a ClickUp Action. 7. Write back through the API, and pace it for 100 a minute [ClickUp: the public API, with a personal or OAuth token]. The write is a separate call rather than a return value, and on Business the ceiling is 100 requests a minute per token. Read X-RateLimit-Remaining rather than assuming the number, because the limit depends on the plan of the Workspace hosting the token rather than on your own. 8. Move the task when the lookup resolves [ClickUp: a status, not just a field]. A task whose enrichment silently failed looks exactly like one that was never triggered, because an empty custom field is the default state. A status change makes the difference visible to a human, which is the only monitoring this build gets on a plan with one day of Automations history. 9. Run a hundred tasks and then read your Action usage [ClickUp: Automations usage]. Actions are the meter that will actually bite, because exceeding them pauses every Automation in the Workspace rather than just this one. A hundred-task pass tells you the real cost per enriched record in Actions, and that number against the monthly allowance is the answer to whether a backfill is possible at all. **How to check it worked:** - Trigger the automation on one task and watch the request arrive at your endpoint. Confirm the header is there, because this is the last moment you can read it. - Let one lookup fail on purpose, by sending an address that cannot resolve. The task should end up in a status that says so rather than sitting with an empty field, which is indistinguishable from never having run. - Write 150 fields in a minute through the API, deliberately. The 429 and its X-RateLimit-Reset tell you what your real backfill rate is, and on Business that figure is 100 a minute whatever the plan above it offers. - Check the Automations usage page after the test pass and multiply. If a hundred tasks cost a hundred Actions, a Business workspace has 10,000 a month for everything it does, not just for this. Agent skill for this pair: https://www.reversecontact.com/integrations-hub/skills/clickup-reverse-contact.md **Field mapping:** - An email on the task, in a custom field maps to The Call webhook payload. ClickUp sends information about the task that triggered the automation. Dynamic variables such as the task ID can go in the URL, which is how your endpoint knows what to write back to. - That email maps to 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. - A company domain maps to POST /v2/enrich/companies, 2 credits. Firmographics from a domain. Run it against the account task rather than once per person attached to it. - A profile URL already on the task maps to POST /v2/fetch/persons, 1 credit. Half the price, and unmetered from the $249 plan rather than the $699 one. Worth checking for before paying for a reverse lookup. - currentPosition.title maps to A text or dropdown custom field. A dropdown if you intend to filter or group on it, because a free-text title is unfilterable in practice once a few hundred variants arrive. - currentPosition.companyName maps to A comparison, then a field. Compare it against the account the task is filed under before writing it. A disagreement means the person has moved, which is the most useful thing this response carries. - metadata.updatedAt maps to A date custom field. Store it and the next sweep can skip everything refreshed recently instead of paying to resolve it again. - The resolved values maps to The ClickUp API, as a separate call. Not a return value from the automation. The webhook is outbound only, so the write is a new request against 100 a minute on most plans. - Does not cross: An app inside ClickUp. ClickUp lists no Reverse Contact integration and Reverse Contact publishes apps on Clay, Zapier and Make and nothing inside any CRM, sequencer or work management tool. - Does not cross: A reply the automation can read. The Call webhook action sends a payload; nothing documented brings the response back into the automation or into a field. - Does not cross: A business email or a direct phone number. Both are separate endpoints at 3 and 20 credits, charged only when one is found, and both are asynchronous, which an automation cannot wait for. - Does not cross: The live endpoints. A live job is documented as aiming for under 15 seconds and possibly taking tens of minutes, and nothing in a ClickUp automation waits for that. **What breaks:** - **Task webhooks start at Business.** ClickUp lists task webhooks, Automations integrations and Chat webhooks as unavailable on Free Forever and on Unlimited and Core, and available from Business. Every plan can use Automations; what the lower plans cannot do is send anything to a URL you choose. - **The API is 100 requests a minute until Business Plus.** Limits are per token and depend on the plan of the Workspace hosting the token: 100 a minute on Free, Unlimited and Business, 1,000 on Business Plus, 10,000 on Enterprise and Enterprise Plus. A 429 carries X-RateLimit-Limit, X-RateLimit-Remaining and X-RateLimit-Reset as a Unix timestamp. - **Exceed the Action allowance and Automations stop for the month.** Actions are 100 a month on Free, 1,000 on Unlimited and Core, 10,000 on Business, and 25,000 or 100,000 on Business Plus depending on whether the plan is an old one or a new one. They reset on the first of the month, PST, and when the limit is passed ClickUp pauses the Workspace's Automations until it resets. - **One trigger, fifteen conditions, six actions.** That is the shape of a single automation, and conditions are themselves a Business feature. It is enough for this build and it is worth knowing before designing something that branches, because the branch has to live in your middle layer instead. - **A saved header cannot be read back.** ClickUp says URL headers are sensitive and that once they are saved you cannot view the values to edit them. That is good security and poor operations: there is no way to confirm which key is in there, so rotating one means replacing the header rather than checking it. - **Usage history is one day on Business.** ClickUp stores one day of Automations activity on Free, Unlimited, Core and Business, 30 days on Business Plus and six months on Enterprise. An enrichment that failed on Friday is not diagnosable on Monday at the plan this build needs. - **Under 2 credits the free checks stop too.** Below 2 Reverse Contact credits even the free check endpoints answer 402 NO_CREDITS. The automation still fires and still spends an Action, so the cost lands on the ClickUp side while nothing is enriched. **Failures people hit:** - The Call webhook action is not in the list. Why: Task webhooks are listed as unavailable on Free Forever and on Unlimited and Core. Fix: Check the plan rather than the permissions. There is no setting that adds it, so the options are Business or enriching before the task is created, which a Zap or a Make scenario on the inbound form does without any ClickUp gate. - Every Automation in the Workspace stopped at once. Why: The monthly Action allowance was exceeded, and ClickUp pauses the Workspace's Automations for the rest of the month rather than throttling the one that ran hot. Fix: Route the 90% email that goes to owners and admins somewhere people read, and count Actions per enriched record before a backfill. Actions reset on the first of the month, PST. - The enrichment ran and the custom field is still empty. Why: The automation sent the payload and nothing wrote the answer back. The Call webhook action has no documented way to read the HTTP response. Fix: Add the write as a separate ClickUp API call keyed on the task ID, which is why the task ID belongs in the webhook URL as a dynamic variable. There is no version of this where the automation returns the value. - A 429 from ClickUp halfway through a backfill. Why: The API allows 100 requests a minute per token on Free, Unlimited and Business, and the limit follows the plan of the Workspace hosting the token. Fix: Honour X-RateLimit-Reset, which is a Unix timestamp, and read X-RateLimit-Limit rather than hard-coding a number that changes with somebody else's plan. - Nobody can tell which API key the webhook is using. Why: ClickUp states that URL headers are sensitive and that once saved the values cannot be viewed to edit them. Fix: Keep the record outside ClickUp, and rotate by replacing the header rather than inspecting it. Treat the saved header as write-only from the moment you click save. - The dashboard shows the enriched field for one List only. Why: A custom field has to be added to the other Spaces and Lists before data from them can be combined in a single card. Fix: Decide the field scope when you create it, not when the first report is due. This is a modelling decision in ClickUp rather than a reporting one. - A task that failed on Friday cannot be diagnosed on Monday. Why: Automations usage history is one day on Free, Unlimited, Core and Business, and 30 days only from Business Plus. Fix: Make the task carry its own evidence: a status for enriched, a status for tried and unresolved, and a date field for when. The record outlives the log on every plan this build runs on. - Everything stopped, including the calls that were free. Why: Below 2 Reverse Contact credits the free Check endpoints are paused as well and answer 402 NO_CREDITS. Fix: Watch quotas.workspace.credits.left on every response and check GET /v2/usage on a schedule, because it keeps answering when the lookups do not. Note that the automation still spends a ClickUp Action either way. **What practitioners say** (14 threads from 2022 to 2026, read 2026-10-28): Nobody discusses this pair by name, so the search was for the job: holding people and company records in ClickUp and getting external data onto them. Almost every thread came back from r/clickup itself, which is thinner material than the other pages here get and unusually consistent in what it says. The recurring complaint is the exact shape of this page: the automations look capable until you want one to fetch something. - Everything in ClickUp is a task, including a person (r/clickup, September 2023, 1 points): https://www.reddit.com/r/clickup/comments/16mzf9u/not_a_database/ - Getting external data into a custom field means the API (r/clickup, February 2023, 1 points): https://www.reddit.com/r/clickup/comments/xohvbb/is_clickup_really_that_good/ - The automations look more capable than they are (r/clickup, December 2024, 2 points): https://www.reddit.com/r/clickup/comments/1hlck6d/thinking_about_switching_from_monday/ - A field is scoped to where you put it, which is a modelling decision (r/clickup, December 2024, 1 points): https://www.reddit.com/r/clickup/comments/1hlck6d/thinking_about_switching_from_monday/ - Prove it on the free plan, then find out what the upgrade is for (r/clickup, December 2024, 1 points): https://www.reddit.com/r/clickup/comments/1hlck6d/thinking_about_switching_from_monday/ Sources: https://developer.clickup.com/docs/rate-limits | https://help.clickup.com/hc/en-us/articles/31126817112343-Create-a-task-webhook-Automation | https://help.clickup.com/hc/en-us/articles/35313844961943-Integrate-ClickUp-using-Automation-webhooks | https://help.clickup.com/hc/en-us/articles/23477062949911-Automations-feature-availability-and-limits | https://docs.reversecontact.com/getting-started | https://docs.reversecontact.com/guides/credits | https://docs.reversecontact.com/guides/rate-limits | https://www.reversecontact.com/pricing ### Slack and Reverse Contact Workflow webhook triggers are 10 a minute, which is the real ceiling on enrich on demand. - Built as: Built on the API, Zapier, Make or n8n - Syncs: One way, in - Moves: Messages, Contacts, Companies - Costs to turn on: Metered by usage. Setup: Hours - Requires: A Reverse Contact API key, somewhere to run the lookup, and a Slack app or an incoming webhook - Full guide: https://www.reversecontact.com/integrations-hub/slack-integrations/slack-reverse-contact-integration **Verdict.** 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. **What syncs:** - The ask (out): A workflow link, a slash command or a webhook trigger carries an email or a domain out of Slack. - The lookup (out): POST /v2/enrich/persons in the orchestrator or the custom step. 2 credits on a match, nothing on an error. - The answer (in): chat.postMessage or an incoming webhook, one message per second per channel. - The routing (in): Which channel it lands in, decided by what came back rather than by who asked. **Which editions carry it** (rows Slack, columns Reverse Contact): - Slack: built-in Workflow Builder steps with Send an identifier out: No - Slack: built-in Workflow Builder steps with Read the answer back in: No - Slack: built-in Workflow Builder steps with Works without a plan upgrade: No - Slack: built-in Workflow Builder steps with Can wait for an async job: No - Slack: a custom step you build and host with Send an identifier out: Yes - Slack: a custom step you build and host with Read the answer back in: Yes - Slack: a custom step you build and host with Works without a plan upgrade: No - Slack: a custom step you build and host with Can wait for an async job: Partly - ClickUp: the Call webhook automation with Send an identifier out: Yes - ClickUp: the Call webhook automation with Read the answer back in: No - ClickUp: the Call webhook automation with Works without a plan upgrade: No - ClickUp: the Call webhook automation with Can wait for an async job: No - Google Sheets: Apps Script with Send an identifier out: Yes - Google Sheets: Apps Script with Read the answer back in: Yes - Google Sheets: Apps Script with Works without a plan upgrade: Yes - Google Sheets: Apps Script with Can wait for an async job: Partly - Gong: nothing in product, the API only with Send an identifier out: No - Gong: nothing in product, the API only with Read the answer back in: No - Gong: nothing in product, the API only with Works without a plan upgrade: No - Gong: nothing in product, the API only with Can wait for an async job: No **How to connect it** (Somebody who can add an app or an incoming webhook to the workspace, plus whoever owns the orchestrator and whoever can create a Reverse Contact API key.. An afternoon for the orchestrator route. A week for a custom step, most of it review.): 1. Decide which channel, and who is accountable for it [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. 2. Decide whether the lookup runs outside Slack or inside 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. 3. Create the Reverse Contact API key and check a balance call first [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. 4. Add the incoming webhook or the app, and keep the key out of the URL [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. 5. Check before you fetch, on the endpoint that costs nothing [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. 6. Write the message so the first line is the decision [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. 7. Decide what an unresolved lookup posts [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. 8. Count the messages for a week before adding a second trigger [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. **How to check it worked:** - Post a real lookup into the channel and then ask the person who owns it what they would do next. If the answer is not obvious from the first line of the message, the message is wrong rather than the data. - Fire the webhook trigger eleven times inside a minute, deliberately. The eleventh should be refused, and knowing what your workflow does when it is refused is better learned now than during a launch. - Run the free check on somebody you know is current and read the update date. If it is recent, a live refresh buys nothing, and that is the cheapest thing to learn on one record. - Turn the orchestrator off and watch the channel. Nothing should appear, and if something still does, there is a second path posting to that channel that nobody remembered. Agent skill for this pair: https://www.reversecontact.com/integrations-hub/skills/slack-reverse-contact.md **Field mapping:** - An email typed into a workflow or slash command maps to 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 maps to 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 maps to 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 maps to 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 maps to 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 maps to 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 maps to 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 maps to 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. - Does not cross: An app inside Slack. There is no Reverse Contact listing on the Slack Marketplace, which is consistent with apps on Clay, Zapier and Make and nothing inside any CRM, sequencer or collaboration tool. - Does not cross: A built-in Workflow Builder step that calls an arbitrary URL. Slack documents connector steps for supported third parties and custom steps you build yourself, and nothing in between. - Does not cross: A business email or a direct phone number. Both are separate endpoints at 3 and 20 credits, charged only when one is found, and both are asynchronous, which a Slack message is a poor shape for. - Does not cross: Anything stored. A channel is not a datastore, and an enrichment that lives only in a message has to be paid for again the next time somebody asks. **What breaks:** - **Workflow webhook triggers are 10 a minute.** This is the ceiling on enrich on demand and it is low. Event triggers get 10,000 an hour and the Events API gets 30,000 deliveries per workspace per app per 60 minutes, so a sweep is fine and a team typing lookups all morning is not. Design the busy case as a scheduled pass rather than as a queue of trigger calls. - **Posting is one message a second, per channel.** The same figure whether you use chat.postMessage, an incoming webhook or anything else, with short bursts tolerated. Slack says that if an app keeps exceeding its allowance, users see an error telling them some messages are not being displayed, which is a failure the sender never sees. - **Every Slack plan gets the same rate limits.** The four web API tiers are 1+, 20+, 50+ and 100+ requests a minute per method per workspace, and nothing in the documentation makes them depend on what you pay. The plan decides whether you can build inside Slack at all; it does not buy throughput. - **Reading channel history is now a question about your app, not your plan.** Since 29 May 2025, conversations.history and conversations.replies drop to one request a minute and 15 objects for commercially distributed apps that are not Marketplace approved. Internal customer-built apps are explicitly unaffected and keep 50+ a minute and 1,000 objects, so a Slack app your own team builds for your own workspace is the exempt case. - **Under 2 credits the free checks stop too.** When the Reverse Contact workspace has fewer than 2 credits left, even the free check endpoints answer 402 NO_CREDITS. A bot that checks cheaply before spending fails at the check, and in a channel that reads as the bot being broken rather than as a billing problem. **Failures people hit:** - The channel went quiet and nobody noticed for a fortnight. Why: A silent integration and a working integration look identical in Slack, because the absence of a message is not an event. Fix: 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. - Everybody muted the channel. Why: The 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. Fix: 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. - The eleventh lookup in a minute did nothing. Why: Workflow webhook triggers are limited to 10 per minute, and the eleventh is refused rather than queued. Fix: 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. - Messages stopped appearing in one busy channel but not the others. Why: Posting is limited to one message a second per channel, by chat.postMessage and incoming webhooks alike, and sustained excess is throttled. Fix: 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. - The app could suddenly only read fifteen messages at a time. Why: conversations.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. Fix: 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. - A custom step will not install. Why: Apps carrying workflow steps have to be org-ready, and custom steps cannot be developed on a Free plan. Fix: 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. - A beautifully formatted message about somebody who left the company. Why: The enrichment returned a current employer and nothing compared it with the account the alert was about. Fix: 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. - Everything stopped, including the calls that were free. Why: Below 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. Fix: 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. **What practitioners say** (14 threads from 2023 to 2026, read 2026-10-28): 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. - Slack is already where people find out, just by hand (r/dataengineering, November 2023, 212 points): https://www.reddit.com/r/dataengineering/comments/17tqj7b/fellow_des_how_do_you_manage_data_quality/ - Enrich before the message, and route by what came back (r/SIEM, January 2023, 2 points): https://www.reddit.com/r/SIEM/comments/107si31/anyone_using_slack_or_teams_for_their_security/ - The orchestrator does the lookup and Slack does the interaction (r/SIEM, January 2023, 1 points): https://www.reddit.com/r/SIEM/comments/107si31/anyone_using_slack_or_teams_for_their_security/ - Treat Slack as the front door and keep the logic underneath it (r/CustomerSuccess, March 2026, 2 points): https://www.reddit.com/r/CustomerSuccess/comments/1rltfs2/use_slack_as_csp/ - A job change is what people actually want the alert for (r/GrowthHacking, October 2025, 1 points): https://www.reddit.com/r/GrowthHacking/comments/1o6r4dn/everyone_talks_about_enrichment_but_heres_how/ Sources: https://docs.slack.dev/apis/web-api/rate-limits/ | https://docs.slack.dev/changelog/2025/05/29/rate-limit-changes-for-non-marketplace-apps/ | https://docs.slack.dev/workflows/ | https://docs.slack.dev/workflows/workflow-steps/ | https://slack.com/help/articles/360035692513-Guide-to-Slack-Workflow-Builder | https://docs.slack.dev/messaging/sending-messages-using-incoming-webhooks/ | https://help.clickup.com/hc/en-us/articles/31126817112343-Create-a-task-webhook-Automation | https://developers.google.com/apps-script/guides/services/quotas | https://help.gong.io/docs/what-the-gong-api-provides | https://docs.reversecontact.com/getting-started | https://docs.reversecontact.com/guides/credits | https://docs.reversecontact.com/guides/rate-limits | https://www.reversecontact.com/pricing ### Slack and Gong Channel alerts come from streams, and a stream has to be the standard kind. - Built as: Native, Marketplace app - Syncs: Events only - Moves: Messages, Activities - Costs to turn on: Paid add-on or licence. Setup: Minutes - Requires: A Gong contract, a Slack admin to install the app, and a Gong admin to connect it - Full guide: https://www.reversecontact.com/integrations-hub/slack-integrations/slack-gong-integration **Verdict.** The cheapest useful thing you can do with a Gong contract, and the one most likely to be configured into noise. Personal alerts about comments and mentions need no thought and work well. Channel alerts are the part worth designing, because they come from streams rather than from a notification rule, which means the question is not "what should we be alerted about" but "which calls belong in a collection somebody is accountable for". A stream per team with a strict filter is the version that is still on in six months. **What syncs:** - Comment and mention alerts (in): To a user's own Gong app in Slack when somebody comments on a followed call, replies to their comment, or mentions them. - New calls in a stream (in): A stream collects calls as they happen and notifies a chosen channel. The stream has to be the Standard type for the channel selector to appear. - A shared call (in): Posted to a channel by hand, which is how a specific moment reaches people who do not follow the stream. - Replies to comments (out): Answer a Gong comment from inside Slack and it reaches Gong, which is the only thing that travels in this direction. - CRM records or call data (event): Nothing. This is a notification surface, not a sync. The records live in Gong and in whichever CRM Gong is connected to. **Which editions carry it** (rows Slack, columns Gong): - Public, Gong is a member with Show it in the channel picker: Works - Public, Gong is a member with Post a stream notification to it: Works - Public, Gong is not a member with Show it in the channel picker: Works - Public, Gong is not a member with Post a stream notification to it: Works - Private, Gong has been added with Show it in the channel picker: Works - Private, Gong has been added with Post a stream notification to it: Works - Private, Gong has not been added with Show it in the channel picker: Invisible to Gong - Private, Gong has not been added with Post a stream notification to it: Invisible to Gong **How to connect it** (A Slack admin to install the app, then a Gong tech or business admin to connect it. Gong names both roles, and they are rarely the same person.. Ten minutes for the connection. The streams are the real work and they are never finished.): 1. Have a Slack admin install the Gong app first [Slack]. Gong states the order plainly: a Slack admin must install the Gong app in Slack, and then both business and tech admins can connect Slack to a Gong workspace. A Gong admin alone cannot complete this. 2. Connect from Gong, not from Slack [Gong: Admin center, Settings, Ecosystem, Slack]. Click CONNECT, choose the Slack workspace, sign in, then Allow to give Gong access to Slack. You are returned to the Slack integration settings page, which is where the connection lives afterwards. 3. Decide the company-wide notification question at the prompt [Gong: the Turn on Slack notifications message]. Immediately after connecting, Gong offers to turn notifications on for all recorded users. Saying yes is a decision about everybody's Slack, so it is worth knowing it is coming rather than clicking through it. 4. Understand what the personal notifications cover [Gong: Notifications settings]. Three events reach a user's personal Gong app in Slack: somebody comments on a call they follow, somebody replies to a comment they made, and somebody mentions them in a comment. None of those can go to a channel. 5. Build a stream for anything a channel should hear [Gong: Conversations, Your library or Company library]. Channel notifications are a stream feature. Click + New, then Stream, name it, and choose whether it lives in Your library, private to you, or Company library, visible to everyone. At least one filter is required. 6. Add Gong to the channel if it is private [Slack: the private channel]. Gong's scopes explain why: chat:write.public lets it post to public channels it is not a member of, while groups:read only shows private channels Gong has been added to. A private channel without the app is invisible in the picker. 7. Set the stream type to Standard [Gong: the stream form, step 5]. Gong notes that Slack notifications require the company to be connected to Slack and the stream type to be Standard. A stream of any other type will not offer the Slack channel. 8. Check the tracker behind the filter is alive [Gong: the stream filters]. If you filter on an AI tracker that is inactive, or your company has insufficient credits, Gong documents that matching calls will not be collected. The stream looks configured and quietly gathers nothing. **How to check it worked:** - Comment on a call somebody else follows and confirm it reaches their personal Gong app in Slack. That is the half that needs no configuration. - Create a stream with one broad filter, point it at a test channel, and watch what arrives for a day. Volume is the failure mode on this pair and a day of real traffic is the only honest measurement of it. - Point a stream at a private channel before adding Gong to it. The channel should not appear in the picker, which tells you the scope model is working rather than the integration failing. - If a stream filters on an AI tracker, confirm the tracker is active and the credits are there. A stream collecting nothing looks identical to a stream nobody is posting to. Agent skill for this pair: https://www.reversecontact.com/integrations-hub/skills/slack-gong.md **Field mapping:** - channels:read maps to Display Slack channels. Basic name and ID of public channels, which is how the channel picker is populated. - chat:write maps to Post to channels Gong is a member of. The ordinary posting permission, and the one that covers private channels once Gong has been invited. - chat:write.public maps to Post to public channels Gong is not in. The asymmetry that explains the whole setup: a public channel needs no invitation and a private one does. - groups:read maps to Display private channels Gong has been added to. Only the ones it has been added to, which is why a private channel is missing from the picker until somebody invites the app. - groups:write maps to Nothing, at the moment. Gong says so outright: not used at the moment, reserved for a future where people name a private channel for Gong to post to. - im:history maps to Read direct messages. Used to carry comments made in Slack back into Gong on the call they belong to. The one piece of this integration that travels in the other direction. - users:read, users:read.email maps to View people. The pair of scopes behind matching a Slack person to a Gong user, which is what makes a mention resolve. - Call sharing maps to The Share call tab on the call page. Calls and call snippets go to public or private channels from Gong's own interface rather than from a notification rule. - Does not cross: A channel version of the three personal notifications. Following a call, replying to a comment and being mentioned are all personal events, and no setting routes them to a channel. - Does not cross: A private channel Gong has not been added to. It will not appear in the picker, because groups:read only covers channels the app is in. - Does not cross: Calls matching an inactive AI tracker, or any tracker at all when the company is short of credits. Gong documents those as not collected. **What breaks:** - **Channel alerts are a stream feature, not a notification setting.** Slack notifications on a channel are configured inside a stream, at the step where you set up notifications, and the stream must be set to Standard or the Slack channel selector does not appear at all. Teams looking for a notifications screen that routes call events to channels do not find one, because the routing is the stream. - **A private channel needs Gong invited first.** Gong has to be added to a private channel before anything arrives. Anyone in the channel can do it, and until somebody does the channel can be selected and stays silent. That combination, a valid configuration with no output, is the hardest failure to attribute on this pair. - **Two admins, on two different teams.** A Slack admin installs the Gong app and a Gong business or tech admin connects the workspace. In most companies those are different people, so the setup is a scheduling problem rather than a technical one, and it is worth starting the conversation before anybody promises a date. - **Volume is the only real failure mode.** Everything here works. The integration fails when a stream is defined loosely enough that the channel fires dozens of times a day, the team mutes it, and the alerting looks healthy in every admin screen while nobody reads it. A muted channel is worse than no integration, because everyone still believes it works. **Failures people hit:** - A channel is missing from the Slack channel picker. Why: It is a private channel and Gong has not been added to it. groups:read only shows private channels the app is in. Fix: Invite the Gong app to that channel in Slack. Public channels never need this, which is why the problem only ever appears on private ones. - The Slack channel option is not offered on a stream. Why: Either the company is not connected to Slack, or the stream type is not Standard. Gong requires both. Fix: Check the connection in Admin center, Settings, Ecosystem, Slack, then set the stream type to Standard in step 5 of the stream form. - Notifications arrive as direct messages and never in a channel. Why: Those three notification types are personal by design: a comment on a followed call, a reply to your comment, and a mention. Channel alerting is a stream feature. Fix: Build a stream with filters and point it at the channel. There is no setting that redirects a personal notification. - A stream is collecting nothing. Why: If the filter uses an AI tracker that is inactive, or the company has insufficient credits, Gong documents that matching calls are not collected. Fix: Check the tracker is active and the credits are available. A filter on participants or account name is a useful control test because it depends on neither. - The channel is unusable because of the volume. Why: A stream needs at least one filter and a broad one matches most calls. This is the failure mode on this pair and it is a configuration decision rather than a defect. Fix: Narrow the filters and choose the brief type deliberately. Highlights is the default and works for most teams; a noisier brief in a busy channel is what gets the integration muted. - A stream nobody else can see. Why: It was saved to Your library, which is private, rather than Company library. Fix: Choose the library location when creating the stream. It is a field on the same form and easy to leave at its default. - The connection stopped working after an app update. Why: Gong updates the Gong for Slack app from time to time and the new version needs re-authorising. Fix: Click Authorize when prompted. Gong notes this on the connection article, and it is a permissions prompt rather than a reinstall. - A Gong admin cannot complete the setup. Why: The Slack half has to come first. A Slack admin installs the Gong app, and only then can business and tech admins connect it from Gong. Fix: Get the Slack install done as a separate task. Two admins on two teams is the real cost of this ten-minute integration. **What practitioners say** (14 threads from 2024 to 2026, read 2026-10-11): Almost nobody discusses this integration directly, so the search was for the job: getting what happens on a call in front of people who were not on it. The threads are about Gong's price and about turning transcripts into actions, and the most useful ones are from people who solved the second problem with something other than a notification. Read as a group they suggest the channel alert is the easy half and the hard half is deciding what deserves one. - What people want is the action, not the alert (r/CustomerSuccess, March 2024, 12 points): https://www.reddit.com/r/CustomerSuccess/comments/1biph2e/can_you_turn_gong_transcripts_into_actions/ - The ask behind the thread is a summary somebody can act on (r/CustomerSuccess, March 2024, 5 points): https://www.reddit.com/r/CustomerSuccess/comments/1biph2e/can_you_turn_gong_transcripts_into_actions/ - Cost is the reason this pair gets re-evaluated (r/SalesOperations, September 2025, 5 points): https://www.reddit.com/r/SalesOperations/comments/1iruhko/gong_replacement/ - The platform is working against channel notifications (r/Slack, May 2025, 5 points): https://www.reddit.com/r/Slack/comments/1kd04ln/whats_your_biggest_frustration_with_slack/ - Even inside Gong, people reach for the manual route (r/CustomerSuccess, March 2024, 5 points): https://www.reddit.com/r/CustomerSuccess/comments/1biph2e/can_you_turn_gong_transcripts_into_actions/ Sources: https://help.gong.io/docs/about-the-slack-integration | https://help.gong.io/docs/connect-to-slack | https://help.gong.io/docs/slack-scopes-used-by-gong | https://help.gong.io/docs/create-a-stream ### Slack and ClickUp Free on every plan, and only the person who set it up can extend it. - Built as: Native, Marketplace app - Syncs: Two-way sync - Moves: Tasks, Messages - Costs to turn on: Included on both sides. Setup: Minutes - Requires: Nothing beyond both accounts. Guests and limited members cannot use it. - Full guide: https://www.reversecontact.com/integrations-hub/slack-integrations/slack-clickup-integration **Verdict.** One of the five integrations in this directory that costs nothing extra on either side, and the only one whose main failure mode is an org chart problem. It does what you want: task, Doc and comment links unfurl with real detail, a message becomes a task or a comment without leaving Slack, and ClickUp activity syncs into the channels you choose. Two things decide whether it survives contact with a real team. Guests and limited members are excluded entirely, and only the person who created the Workspace connection can add new activity locations, so the integration quietly depends on one named individual still working here. **What syncs:** - Task, Doc and comment links (out): Unfurl in Slack with the title, a description preview, status, assignees, priority and location. Needs a personal connection to appear. - A Slack message to a task (in): Added as a ClickUp comment, styled as a quote, with a link back to the original Slack message. - New tasks (in): Created with the /clickup new command or the Create Task action. Tasks can also be edited straight from a task preview. - ClickUp activity (out): Task creation, status changes, comments, attachments and assignee changes, per Space, Folder, Subfolder or List. Public and private channels on a personal connection, public only on a Workspace connection. - Slack messages into search (in): Connected Search indexes selected public channels back one year, and the indexing pass can take up to 24 hours. - Messages to a Super Agent (in): Sent from the message menu. Attachments are not included. **Which editions carry it** (rows ClickUp, columns Slack): - Personal connection with Public channel: Activity sync works - Personal connection with Private channel: Activity sync works - Workspace connection with Public channel: Activity sync works - Workspace connection with Private channel: Not available - Guest or limited member with Public channel: Not available - Guest or limited member with Private channel: Not available **How to connect it** (A ClickUp Workspace owner or admin for a Workspace connection. Anyone else can make a personal one, and that choice decides more than it looks like it does.. Ten minutes, then up to a day before Connected Search has finished indexing.): 1. Choose the connection type first, because it decides which channels you can use [ClickUp: App Center, Slack]. A personal connection can sync ClickUp activity to public and private Slack channels. A Workspace connection can only sync to public ones. Teams that run deal or project work in private channels pick the Workspace connection for the governance and then find the channels they care about are unavailable. 2. Know who will be able to add locations afterwards [The same decision]. Only the creator of a Workspace connection can set up new locations for ClickUp activity messages. Admins and owners cannot add new ones; they can only map existing messages to more Spaces, Folders, Subfolders or Lists. Connect as somebody who will still be here next year. 3. Connect, and pick what Connected Search may index [App Center: Slack, Connect an app]. You can select specific public channels or choose All public channels. This is a scope decision rather than a convenience one, and the OAuth scopes are published in ClickUp's own table if security needs to read them before you click. 4. Map ClickUp locations to channels [ClickUp: Slack notification settings]. Sync Spaces, Folders, Subfolders and Lists to the channels that should hear about them, then choose which task and Doc actions actually notify. Mapping everything is the mistake: a channel that reports every status change gets muted in a week. 5. Let the index finish before you judge the search [ClickUp: AI Command Bar]. Initial indexing can take up to 24 hours and you can watch the progress. After that, a new Slack message takes up to ten minutes to become searchable, so neither number is a fault to report. 6. Tell the team who is excluded [ClickUp: user roles]. Guests and limited members cannot use the integration at all. On a workspace that runs with contractors or clients as guests, that is a meaningful share of the people in the channel. **How to check it worked:** - Sync one List to a private channel. If it is not offered, you are on a Workspace connection and that is the documented behaviour rather than a bug. - Have somebody who is not the connection creator try to add a new location. Finding out now is better than finding out when that person has left. - Search for a Slack message posted ten minutes ago. If it is missing, wait rather than reconnect. - Ask a guest to use a Slack action and confirm it fails, so nobody spends an afternoon on a permission that does not exist. Agent skill for this pair: https://www.reversecontact.com/integrations-hub/skills/slack-clickup.md **Field mapping:** - A ClickUp task, Doc or comment link maps to An unfurled Slack preview. Title, a description preview and status, shown to everybody in the channel regardless of their ClickUp permissions. - A Slack message maps to A ClickUp comment on a task. Styled as a quote with a link back, from the message action menu. - A Slack message maps to A new ClickUp task. Through the slash command or the Create Task action, so the thread that spotted the work becomes the work. - ClickUp activity maps to A mapped channel. Creation, status changes, comments, attachments and assignments, chosen per action rather than all at once. - Selected public Slack channels maps to ClickUp Connected Search. Indexed, and searchable only by people who are members of both sides. - Does not cross: Private channels, on a Workspace connection. Only a personal connection reaches them. - Does not cross: Anything for a guest or a limited member. They are excluded from the integration entirely. - Does not cross: Attachments on a message sent to a Super Agent. ClickUp documents that they are not included. **What breaks:** - **Only the connection creator can add locations.** For a Workspace connection, new locations for ClickUp activity messages can only be set up by the person who created the connection. Admins and owners can map existing messages to additional Spaces, Folders, Subfolders and Lists, and cannot add a new location at all. When that person changes team or leaves, extending the integration becomes a re-install, and nothing in the interface tells you why the option is missing. - **Guests and limited members are excluded.** ClickUp states that guests and limited members cannot use the integration with Slack, cannot enable Slack activity messages and cannot use the Slack actions. In an agency workspace or any setup where clients and contractors are guests, that is a large share of the channel for whom the integration simply does not exist, and they will see other people creating tasks from messages they cannot act on. - **Private task previews are public in the channel.** Links to private ClickUp tasks or Docs will be seen by everyone in a channel, with the task title, description snippet, status, assignees and priority on display. The permission model that protects the task in ClickUp does not travel with the link. Decide whether that is acceptable before installing rather than after somebody pastes a link into a channel with clients in it. - **A task in several Lists reports from one.** Tasks in multiple Lists only generate Slack activity messages if their home List is inside the selected location, so a task surfaced into a second List stays silent. There is no limit on how many activity messages you configure and duplicates are suppressed if several people set up the same one, which is the pleasant surprise on this page, but a private channel has to be given access with /invite @ClickUp before it can receive anything. **Failures people hit:** - A channel is missing from the list when setting up. Why: ClickUp names three reasons: the channel was deleted, you have not joined it, or it is new. Fix: Join the channel, then wait. A newly created or joined channel can take five minutes to appear, and no logout is needed. - Private channels cannot be selected at all. Why: A Workspace connection syncs to public channels only. A personal connection reaches both. Fix: Decide which you want. Changing it means reconnecting, so it is worth settling before the mapping work. - An admin cannot add a new ClickUp location to a channel. Why: Only the creator of the Workspace connection can add locations. Admins and owners can map existing messages to more locations and nothing else. Fix: Go back to the connection creator, or recreate the connection under an account the team will keep. - Search does not find a message that is definitely there. Why: Indexing. A new message takes up to ten minutes to become searchable, and the initial index can take 24 hours. Fix: Check the progress in the AI Command Bar before reconnecting anything. - Somebody saw a task they should not have. Why: A link unfurl shows the title and description preview to the channel, whatever that person's ClickUp permissions are. Fix: Treat pasting a task link as publishing its title. There is no permission check on the preview, so the control is which channel you paste into. - A contractor cannot use any of it. Why: Guests and limited members are excluded from the integration. Fix: A full member seat is the only route. Plan around it rather than troubleshooting it. **What practitioners say** (14 threads from 2024 to 2026, read 2026-10-11): Almost nobody posts about configuring this integration, so the search was for the decision behind it: whether to run both tools or let one absorb the other. ClickUp has been shipping chat features aimed squarely at that question, and the threads are a running verdict on how it is going. The consistent answer from people who have tried both is that the integration is the realistic arrangement and the replacement is not, which makes the setup choices above the ones that matter. - The blunt answer to replacing Slack, from somebody who had tried (r/clickup, September 2024, 6 points): https://www.reddit.com/r/clickup/comments/1foncqc/can_clickup_chat_replace_slack/ - Somebody is running the experiment in public (r/clickup, June 2026, 26 points): https://www.reddit.com/r/clickup/comments/1u3w892/for_those_interested_im_migrating_my_team_from/ - Great in principle, unusable in practice is the recurring phrase (r/clickup, March 2025, 14 points): https://www.reddit.com/r/clickup/comments/1jglymk/clickup_chat_is_it_ready_to_replace_slack/ - A small team that did switch found the gap in the small things (r/clickup, March 2025, 7 points): https://www.reddit.com/r/clickup/comments/1jglymk/clickup_chat_is_it_ready_to_replace_slack/ - The advice that generalises is to pick one source of truth (r/clickup, January 2026, 4 points): https://www.reddit.com/r/clickup/comments/1q69pv3/clickup_vs_slack_whats_actually_working_for_teams/ Sources: https://help.clickup.com/hc/en-us/articles/6304922742295-Intro-to-the-integration-with-Slack | https://help.clickup.com/hc/en-us/articles/6304985978903-Sync-ClickUp-activity-with-Slack-channels | https://help.clickup.com/hc/en-us/articles/6305046290583-Preview-tasks-Docs-and-comments-in-Slack | https://help.clickup.com/hc/en-us/articles/6304968094615-Use-Slack-actions ### Slack and Outreach Connected once for the whole instance, then every notification is personal. - Built as: Native, Marketplace app - Syncs: Events only - Moves: Messages, Activities - Costs to turn on: Paid add-on or licence. Setup: Minutes - Requires: An Outreach contract, an Outreach admin, and permission to add apps to Slack - Full guide: https://www.reversecontact.com/integrations-hub/slack-integrations/slack-outreach-integration **Verdict.** Lighter than the other Slack pairs here, and personal rather than broadcast. One admin connects the instance over Slack OAuth, Outreach maps users to their Slack accounts automatically, and from then on each person chooses which alerts reach Slack instead of the in-app feed, email or the browser. The channel story is thin on purpose: only the Kaia meeting summary is documented at account level, one channel per account, and turning that on makes account notifications visible to everyone in the channel. Read it as a better inbox for reps, not as a team alerting system. **What syncs:** - Personal notifications (in): Email-reply mismatches, meeting updates, new voicemails, bounce limits, CRM plug-in errors, mentions and overdue tasks, to the user who owns them. - Kaia meeting summaries (in): Sent automatically when ready, and the one notification documented at account level, with a single Slack channel per account. - Deal Agent suggestions (in): AI-detected opportunity updates from a call recording, which a user can accept, reject or edit from Slack. - Accepting a suggestion (out): The decision travels back to Outreach and updates the opportunity field, which is the only thing moving in this direction. - Prospects, sequences and activity (event): Nothing. This is a notification surface. The records stay in Outreach and in whichever CRM it syncs with. **Which editions carry it** (rows Outreach, columns Slack): - A reply from an unexpected address with Slack: Delivered - A reply from an unexpected address with A browser notification: Not available - Meeting updates and voicemails with Slack: Delivered - Meeting updates and voicemails with A browser notification: Not available - Bounce limit warnings with Slack: Delivered - Bounce limit warnings with A browser notification: Not available - A prospect opening, clicking or replying with Slack: Not available - A prospect opening, clicking or replying with A browser notification: Delivered - An incoming call with Slack: Not available - An incoming call with A browser notification: Delivered **How to connect it** (An Outreach admin to connect the instance, then every user for their own notifications, and whoever owns an account for its channel.. Ten minutes for the admin. Then it is never finished, because the useful part is per person and per account.): 1. Check you can add apps to the Slack workspace [Slack: app management]. Outreach lists it as a prerequisite before anything else. The connection is made from Outreach, but it installs an app in Slack, and a locked-down workspace will stop the admin halfway through. 2. Connect at the instance level [Outreach: Administration, Organization, Org info, General]. Scroll to Slack notifications and follow the prompts. This is Slack OAuth once for the whole org rather than per user, and once it is done Outreach tries to map Outreach users to their Slack users automatically. 3. Decide the account-channel question before you enable it [Outreach: the same screen]. Allow users to connect Slack channels to Outreach accounts is a separate switch, and Outreach warns what it means: account-related notifications sent to those channels may be visible to all channel members. That is a disclosure decision rather than a feature toggle. 4. Tell people their notifications are personal [Outreach: Personal Settings, General, Notifications]. The admin connection enables nothing by itself. Each user toggles their own Slack notifications, and a user who does not see Slack as an option has not been mapped yet rather than hit a bug. 5. Set the browser notifications separately, and expect to [The browser, after clicking Enable browser notifications]. Three of the most-wanted events are browser-only: a prospect opening an email, clicking a link or replying. Outreach notes these need OS-level permission, so a blocked popup setting silently disables them. 6. Attach a channel to an account only where it earns one [Outreach: the account details page]. The notifications for Slack panel sits under the account name in the top right. Pick a public channel from the autocomplete, and note that the Outreach app does not need to be invited to it, unlike most Slack integrations. 7. Know what the account channel can actually deliver [The same panel]. One notification type is supported today: the Kaia meeting summary, triggered after a call associated with that account once Kaia has processed the recording. Outreach says more may be added; today that is the list. 8. Accept one channel per account [The same panel]. Each account links to a single Slack channel, changed by returning to the account page. Outreach recommends this for teams running dedicated deal channels, which is exactly the shape it fits. **How to check it worked:** - Have one non-admin check Personal Settings for a Slack option. Its absence means the user mapping has not happened, which is the documented answer and not a permissions problem. - Trigger a prospect open or click and watch where it arrives. It will be a browser notification rather than a Slack message, and that surprises people who assumed everything routes everywhere. - Attach a test account to a channel and run a Kaia call against it. The summary arrives after the call ends and after Kaia has processed the recording, so a short delay is expected rather than a failure. - Before enabling account channels for everybody, post one account notification to a channel and look at who is in it. Outreach warns the content may be visible to all channel members, and seeing it once makes the point. Agent skill for this pair: https://www.reversecontact.com/integrations-hub/skills/slack-outreach.md **Field mapping:** - Somebody other than the recipient replying maps to Personal, available in Slack. A prospect replies from a different address, belonging either to another prospect or to somebody Outreach does not know. The notification exists because the reply would otherwise be invisible. - Meeting updates maps to Personal, available in Slack. Booked via your public calendar link, reassigned to another prospect, rescheduled, or scheduled on your behalf by another Outreach user. - New voicemails maps to Personal, available in Slack. One trigger, one notification. The simplest thing on the list. - Bounce limits maps to Personal, available in Slack. Three thresholds: 50% of the bounce rate, 80%, and a final warning when you cannot send for the next 24 hours. The one notification on this page that stops work if ignored. - Plug-in and sync errors maps to Personal, available in Slack. Issues with the connected CRM, and a disconnected mailbox or calendar that has stopped synchronising. Worth routing somewhere a person actually reads. - Mentions and urgent tasks maps to Personal, available in Slack. Being mentioned in the Kaia chat, and an urgent task going past its due date. - Kaia meeting summary maps to Personal and account-level. The only event that exists in both systems, and the only one an account channel can deliver. - An account to a channel maps to One channel per account, public only. Selected from an autocomplete on the account details page. The Outreach app does not need to be invited to the channel, which is unusual and worth knowing. - Does not cross: Email engagement into Slack. Opens, clicks and replies are browser notifications, and Outreach states plainly that not all notifications support all channels. - Does not cross: More than one Slack channel per account, or a private one. The autocomplete offers public channels and each account links to a single one. - Does not cross: Any account notification other than the Kaia meeting summary. Outreach says more types may be added in future releases; that is the entire list today. **What breaks:** - **Channel alerting is barely supported.** Outreach documents only the Kaia meeting summary at account level, with one Slack channel per account. Teams expecting reply alerts routed to a deal channel will not find that here, and the documentation is itself inconsistent, with release notes describing Slack features the core setup article does not list. Check what your instance actually offers before designing around it. - **Account channels expose account notifications.** The admin setting that lets users connect Slack channels to Outreach accounts carries an explicit warning that account-related notifications sent to those channels may be visible to all channel members. In a shared or client-facing channel that is a disclosure decision rather than a configuration one, and it belongs with whoever owns the account relationship. - **Not every notification supports every channel.** Outreach states it plainly: not all notifications support all channels. So a notification a rep expects in Slack may only exist in the in-app feed or by email, and the toggle for it simply will not be there. The only reliable way to know is the notifications screen in a real account. - **User mapping has to work first.** The integration maps Outreach users to Slack users automatically after connection, and personal notifications depend on that mapping succeeding. Where it fails, the user sees no option to enable Slack at all, which looks like a missing feature rather than an unmapped account and is the first thing to check. **Failures people hit:** - A user cannot see Slack in their notification settings. Why: Outreach answers this one directly: Slack must be enabled by an Outreach admin and mapped to the user's account. Fix: Confirm the instance-level connection exists, then check the user mapping. Outreach maps users automatically after connecting, so an unmapped person usually joined afterwards. - Nothing happened after the admin connected it. Why: Correct behaviour. The admin connection enables the channel and switches nothing on; each user toggles their own notifications. Fix: Send people to Personal Settings, General, Notifications. This is the single most common reason the integration is reported as broken on day one. - Opens and clicks never arrive in Slack. Why: They are browser notifications rather than Slack ones. Outreach states that not all notifications support all channels. Fix: Enable browser notifications and grant the OS-level permission. There is no configuration that routes engagement events into Slack. - Browser notifications are enabled and still nothing appears. Why: Popups are blocked, or the OS permission was never granted. Outreach says the browser asks after you press Enable browser notifications. Fix: Check both the browser and the operating system settings. Outreach answers this in its own FAQ, which is a sign of how often it happens. - The channel selector is missing on an account. Why: Either Slack is not connected to the Outreach org, or the account-channel feature has not been enabled by an admin. Fix: An admin connects the integration and enables the feature in Org info. You also need edit permission on the account you are configuring. - An account channel receives nothing but meeting summaries. Why: That is the full list. Outreach supports only the Kaia meeting summary at account level today. Fix: Use personal notifications for everything else. Outreach notes additional types may come in future releases, which is not something to plan around. - The meeting summary arrived late. Why: It is triggered post-call and sent after Kaia has processed the recording. Outreach documents a short delay. Fix: Wait rather than reconfiguring. If it never arrives, check the call was actually associated with that account. - Account notifications are visible to people who should not see them. Why: Outreach warns about this when the feature is enabled: account-related notifications sent to a channel may be visible to all channel members, and only public channels can be selected. Fix: Treat channel membership as the access control, because it is. This is a decision to take before enabling the feature across the org. **What practitioners say** (14 threads from 2023 to 2026, read 2026-10-11): Nobody discusses this pair by name, so the search was for the job: putting sales activity into the channel where a team already works. What comes back is almost entirely about structure and restraint, from people running client and deal channels at scale. The advice is consistent and it maps onto the one account-level feature Outreach supports: one channel per thing, organised around the account rather than the tool. - One channel per account is what works, and it is what Outreach supports (r/agency, July 2025, 1 points): https://www.reddit.com/r/agency/comments/1mbrrcx/how_are_you_structuring_your_slack_to_your_clients/ - The channel is the access control, whether you meant it to be (r/CustomerSuccess, August 2025, 10 points): https://www.reddit.com/r/CustomerSuccess/comments/1mrdvr9/do_yall_support_your_customers_in_slack_b2b_saas/ - Integration count has a ceiling (r/Slack, April 2026, 1 points): https://www.reddit.com/r/Slack/comments/1slry58/how_do_you_actually_manage_a_high_volume_of/ - A notification is a prompt, and the system of record is elsewhere (r/Netsuite, June 2026, 1 points): https://www.reddit.com/r/Netsuite/comments/1u9ai4y/netsuite_slack_integration_for_sales_orders/ - Threads hide the thing you wanted people to see (r/Slack, May 2025, 5 points): https://www.reddit.com/r/Slack/comments/1kd04ln/whats_your_biggest_frustration_with_slack/ Sources: https://support.outreach.io/support/solutions/articles/159000425170-admin-configuration-of-outreach-app-for-slack | https://support.outreach.io/support/solutions/articles/159000425264-configure-in-app-notifications-and-notifications-for-slack-in-outreach | https://support.outreach.io/support/solutions/articles/159000430400-account-level-notifications-in-outreach-for-slack ### Slack and Zapier One message a second per channel, and a bot message cannot start a Zap. - Built as: Zapier, Make or n8n, Marketplace app - Syncs: Events only - Moves: Messages - Costs to turn on: Metered by usage. Setup: Minutes - Requires: A Zapier plan sized to your task volume, and a free app slot on a free Slack plan - Full guide: https://www.reversecontact.com/integrations-hub/slack-integrations/slack-zapier-integration **Verdict.** 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. **What syncs:** - Messages into a channel (out): Public, private and direct, with editing, deleting and scheduling. Roughly one message per second per channel. - New messages as triggers (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 (in): A new reaction or a mention can start a Zap, which is the lightest way to let a human approve something. - Channel administration (out): Create public and private channels, set a topic, invite and remove users. More than most teams realise is available. - Files and users (in): New file and new user triggers, useful for onboarding automation rather than for sales alerting. - Message history in bulk (event): 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 editions carry it** (rows Zapier, columns Slack): - Free with Free, under 10 apps: Triggers and actions, default polling - Free with Free, at 10 apps: No slot to install it - Free with Any paid plan: Triggers and actions, default polling - Professional with Free, under 10 apps: Plus polling control - Professional with Free, at 10 apps: No slot to install it - Professional with Any paid plan: Plus polling control - Team or Enterprise with Free, under 10 apps: Plus polling control - Team or Enterprise with Free, at 10 apps: No slot to install it - Team or Enterprise with Any paid plan: Plus polling control **How to connect it** (Anybody with a Slack account, unless the workspace restricts apps, in which case a workspace owner or admin.. Three minutes, and then a decision about which trigger to use.): 1. Count your app slots if you are on free Slack [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 [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 [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 [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 [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 [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. **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. Agent skill for this pair: https://www.reversecontact.com/integrations-hub/skills/slack-zapier.md **Field mapping:** - A human message in a channel maps to An instant trigger. Public, private or saved, with separate triggers for each, plus new file and new channel. - A message matching a search maps to A polling trigger. New Message From Query is the one that polls, so it is the one with latency. - A thread reply maps to 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 maps to 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. - 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. - Does not cross: A slash command, as an action. It posts as text. - Does not cross: An eleventh app on a free Slack workspace. The slot limit is ten in total. **What breaks:** - **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. **Failures people hit:** - A Zap never fires on messages posted by another tool. Why: Messages preceded by indentation, which is how bots, slash commands and integrations post, cannot trigger a workflow. Fix: 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. Why: Thread replies trigger the same way top-level messages do. Fix: 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. Why: A plain mention in an action is text. Slack needs Zapier's special formatting for mentions and notifications to work. Fix: Use the documented formatting. There is no error to find, because the post succeeded. - A slash command in an action did nothing. Why: It posts as text rather than running. Fix: Call the underlying thing directly from the Zap instead, or trigger the automation another way. - Messages are dropping during a burst. Why: Slack allows about one message per second per channel, tolerating short bursts and rate-limiting sustained ones. Fix: 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. Why: A free Slack workspace at its ten-app limit, or a workspace that restricts app installs. Fix: Free a slot, or get a workspace owner or admin to approve it. Neither is a Zapier setting. **What practitioners say** (14 threads from 2023 to 2026, read 2026-10-11): 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. - The most upvoted advice is to stop asking about the tools (r/productivity, November 2023, 6 points): https://www.reddit.com/r/productivity/comments/17sy9tp/professionals_who_automate_slack_zapier_etc/ - Even practitioners call this hard, and name the reason (r/productivity, November 2023, 5 points): https://www.reddit.com/r/productivity/comments/17sy9tp/professionals_who_automate_slack_zapier_etc/ - Newer Slack surfaces are not always reachable (r/Slack, July 2025, 3 points): https://www.reddit.com/r/Slack/comments/1lvzjyd/slack_lists_api_zapier_automations/ - The thing people most want to build is a bot that answers in a channel (r/zapier, January 2023, 3 points): https://www.reddit.com/r/zapier/comments/10eimim/openai_slack_zapier/ - Consultants describe the work as process rather than integration (r/productivity, November 2023, 3 points): https://www.reddit.com/r/productivity/comments/17sy9tp/professionals_who_automate_slack_zapier_etc/ Sources: https://help.zapier.com/hc/en-us/articles/8495993391629-How-to-get-started-with-Slack-on-Zapier | https://docs.slack.dev/apis/web-api/rate-limits/ | https://docs.slack.dev/changelog/2025/05/29/rate-limit-changes-for-non-marketplace-apps/ ### Slack and n8n The trigger needs a bot token and the node wants OAuth, so you build both. - Built as: Zapier, Make or n8n, Built on the API - Syncs: Two-way sync - Moves: Messages - Costs to turn on: Metered by usage. Setup: Hours - Requires: An n8n instance you host or rent, and a Slack app with the right token type - Full guide: https://www.reversecontact.com/integrations-hub/slack-integrations/slack-n8n-integration **Verdict.** This is the most capable Slack integration in the directory and the one with the most ways to misconfigure the credential. The node reaches almost the whole Slack surface and the HTTP Request node covers the rest, so the question is never whether you can do something, it is which token you did it with. n8n recommends OAuth2 for the node, the Slack Trigger requires an access token and refuses OAuth2, message search needs a user token rather than a bot token, and several scopes are not available to bots at all. Get the token model right on day one and this pair is the cheapest Slack automation you can run. **What syncs:** - Messages into Slack (in): Send, update, delete, get permalink, and send-and-wait-for-response, which pauses the workflow until a human answers. - Messages out to n8n (out): Through the Slack Trigger node, which requires an access token and does not support OAuth2. - Channels (two-way): Archive, close, create, invite, join, kick, leave, rename, set purpose, set topic, unarchive, and read history and replies. - Files, reactions and stars (two-way): Upload and read files, add and remove reactions, manage stars. More than the native connectors in this directory offer. - Users and user groups (two-way): Read users, update profiles and statuses, create and manage user groups. - Anything the node misses (two-way): The HTTP Request node, using the same Slack credential, so an unsupported endpoint is a configuration rather than a blocker. **Which editions carry it** (rows n8n, columns Slack): - OAuth2 only with Actions on the Slack node: Works - OAuth2 only with A Slack trigger: Does not work - OAuth2 only with Custom bot identity: Does not work - Access token only with Actions on the Slack node: Works - Access token only with A Slack trigger: Works - Access token only with Custom bot identity: Works - Both configured with Actions on the Slack node: Works - Both configured with A Slack trigger: Works - Both configured with Custom bot identity: Works **How to connect it** (Whoever administers the n8n instance, plus a Slack workspace member who can create an app. The Slack app is the integration; n8n is the thing calling it.. An hour, most of it spent on scopes.): 1. Create the Slack app from a manifest, not from scratch [Slack: Your Apps, Create New App, From a manifest]. n8n publishes a manifest. Pasting it sets the scopes and the event subscriptions in one step, which is considerably less error-prone than ticking scopes by hand and discovering the missing one at run time. 2. Expect to create two credentials, not one [n8n: credentials]. n8n recommends OAuth2 for the Slack node and requires an API access token for the trigger. Those are two separate credentials against the same Slack app, and assuming one will serve both is the most common first-hour mistake on this pair. 3. Check the scopes you need are available to a bot token [Slack: OAuth and Permissions]. n8n lists scopes that do not exist as bot token scopes, including channels:write and stars:read. If your workflow needs one of those, the design changes rather than the configuration. 4. Subscribe to events, including ones not on the list [Slack: Event Subscriptions]. After Slack verifies the Request URL you can manage subscriptions in the app manifest under settings.event_subscriptions. For an event n8n does not list, add it as a bot event in Slack and select Any Event in the node. 5. Know which auth your version needs for a custom bot identity [The Slack node, Message, Send]. From node version 2.6, Custom Bot Profile Photo works only with Access Token authentication. It relies on chat:write.customize, a bot-token-only scope the OAuth2 user-token path cannot use. On 2.5 and below the option still appears with OAuth2 and Slack ignores it, which is worse than it being hidden. 6. Design the posting rate before you build the loop [Your workflow]. Slack allows roughly one message per second per channel with a workspace ceiling above it, and gives no guarantee beyond short bursts. Batch into one message rather than iterating. **How to check it worked:** - Fire the trigger and confirm it uses the access token credential rather than failing on OAuth. - Send a message with a custom bot icon. If it posts with the default icon and no error, you are on OAuth2 with a node version that ignores the option. - Run a search and count the results. From node version 2.7 you get 20 per request, which is a cap rather than an empty result. - Post twice in quick succession to the same channel and watch for throttling before you build anything that loops. Agent skill for this pair: https://www.reversecontact.com/integrations-hub/skills/slack-n8n.md **Field mapping:** - The Slack node maps to OAuth2 credential. n8n's recommended method for the node itself. - The Slack Trigger node maps to API access token credential. Required. The trigger does not take OAuth, which is why this pair needs two credentials. - A custom bot icon or emoji maps to Access Token authentication only, from node 2.6. It needs chat:write.customize, which is a bot-token scope that the OAuth2 user-token path cannot use. - A Slack event n8n does not list maps to Any Event in the node. Add it as a bot event in Slack first, then select Any Event. - A search request maps to 20 results, about 10 requests a minute. From node version 2.7, with Channel Types, date filters and a Keyword Search Only option that disables semantic search. - Does not cross: Scopes that are not available to bot tokens, including channels:write and stars:read. - Does not cross: A custom bot profile photo over OAuth2 from node 2.6 onwards, and on 2.5 and below the option appears and is ignored. - Does not cross: Sustained posting above roughly one message per second per channel. **What breaks:** - **Two credentials, because the trigger will not take OAuth.** n8n documents OAuth2 as the recommended method for the Slack node and an API access token as required for the Slack Trigger, which does not support OAuth2. Any workflow that both listens to Slack and writes back therefore holds two Slack credentials. The failure is quiet: the trigger simply never fires, and nothing in the workflow says why. - **Bot tokens cannot do several things.** n8n lists scopes that are not available as bot token scopes, including channels:write, stars:read, stars:write, users.profile:write and the private search scopes, and notes that some Slack endpoints only work with user tokens. If the operation you need is in that set, the token type is the design decision rather than a setting you flip later. - **Search is rate limited and capped.** From node version 2.7 search returns 20 results a request and is limited to roughly 10 requests a minute per user, Return All was removed in favour of a Limit capped at 50, and output field names changed, so `text` became `content`. n8n says plainly that search is not built for exhaustive retrieval. Semantic ranking on question-style queries needs a paid Slack AI plan. - **Slack's own posting limits still apply.** Roughly one message per second per channel, with a workspace ceiling above it, and Slack gives no guarantee that messages are stored or displayed when a burst goes too far. A workflow that posts per record rather than per digest fails selectively and silently, which is harder to notice than failing outright. **Failures people hit:** - The trigger will not authenticate. Why: It is configured with OAuth2. n8n requires an API access token for the Slack Trigger node. Fix: Create a second credential of the access token type against the same Slack app. - A custom bot icon is ignored. Why: From node version 2.6 the option needs Access Token authentication, because chat:write.customize is a bot-token-only scope. On 2.5 and below the option is shown with OAuth2 and Slack ignores it. Fix: Switch that workflow to the access token credential. There is no error to find, which is why this one survives upgrades. - A scope cannot be granted. Why: Some scopes do not exist for bot tokens at all, including channels:write and stars:read. Fix: Check n8n's list before designing around the operation. This is a redesign rather than a permission request. - An event n8n does not list is needed. Why: The node exposes a set of events, and yours is not in it. Fix: Add the event as a bot event in Slack, then select Any Event in the node and branch on the payload. - Search returns only twenty results. Why: From node version 2.7 search returns 20 per request and is limited to roughly 10 requests a minute. Fix: Paginate deliberately and narrow with the Channel Types and date filters rather than fetching everything. - Messages drop during a loop. Why: Slack's posting limit of roughly one message per second per channel, with no guarantee beyond short bursts. Fix: Batch the output into a single message. This is the same constraint every Slack integration in this directory hits. **What practitioners say** (14 threads from 2025 to 2026, read 2026-10-11): Unusually for this directory, the threads are people building rather than people complaining. The recurring subject is connecting Slack to a self-hosted n8n, which is the configuration this page spends most of its length on, and the recurring artefact is somebody publishing their workflow for others to copy. - Self-hosted is the common case, and the connection is the hard part (r/n8n, June 2025, 5 points): https://www.reddit.com/r/n8n/comments/1lm49l9/finally_figured_out_how_to_connect_slack_to_a/ - People publish their workflows, which is the fastest way in (r/n8n, June 2026, 9 points): https://www.reddit.com/r/n8n/comments/1u9easr/i_built_a_n8n_automated_workflow_to_track_daily/ - Multi-turn conversation is where people get stuck (r/n8n, April 2025, 3 points): https://www.reddit.com/r/n8n/comments/1jqvkp1/slack_chat_with_n8n_ai_help/ - The pair shows up inside bigger builds rather than on its own (r/n8n, June 2025, 13 points): https://www.reddit.com/r/n8n/comments/1l8g8dy/inquiry_for_endtoend_n8n_ghl_and_slack/ - The same setup guide gets posted in both communities (r/Slack, June 2025, 3 points): https://www.reddit.com/r/Slack/comments/1lm46wa/quick_slack_automation_guide_with_selfhosted_n8n/ Sources: https://docs.n8n.io/integrations/builtin/app-nodes/n8n-nodes-base.slack | https://docs.n8n.io/integrations/builtin/credentials/slack | https://docs.slack.dev/apis/web-api/rate-limits/ ### Slack and Google Workspace An admin installs it once, then every person has to connect their own account. - Built as: Native, Marketplace app - Syncs: Two-way sync - Moves: Messages, Activities - Costs to turn on: Included on both sides. Setup: Minutes - Requires: Nothing to buy. An admin installs each app, then every member connects their own account. - Full guide: https://www.reversecontact.com/integrations-hub/slack-integrations/slack-google-integration **Verdict.** The Slack Google Workspace integration is one of the five here that costs nothing extra on either side, and the one most likely to be declared finished before it works. An admin installs the Drive and Calendar apps once, and then nothing happens for anybody until each person connects their own Google account. The fix for that at scale is domain-wide authentication, which needs a Slack admin and a Google Workspace super admin in the same conversation. Get those two steps right and this is fifteen minutes; skip the second and you have a workspace where the integration is installed, invisible and quietly blamed. **What syncs:** - Drive files into Slack (in): Create, share and open Drive files from Slack, and search shared files there. The files stay in Drive and are not stored in your workspace. - Drive notifications (in): Comment and access-request updates arrive in Slack, which is the half that actually changes how quickly people respond. - New Docs, Sheets and Slides (out): Created from inside Slack, which is the lightest version of starting a document where the conversation happened. - Calendar invites (two-way): Respond to invites and create events from Slack, with reminders before a meeting starts. - Meeting status (in): Slack status updates automatically during a meeting, and syncs only with the primary calendar of the connected Google account. **Which editions carry it** (rows Slack, columns Google Workspace): - Free with Members connect their own accounts: Available - Free with Domain-wide authentication: Available - Free with A daily or weekly schedule in a channel: Not available - Free with Installing across workspaces from one place: Not available - Pro or Business+ with Members connect their own accounts: Available - Pro or Business+ with Domain-wide authentication: Available - Pro or Business+ with A daily or weekly schedule in a channel: Available - Pro or Business+ with Installing across workspaces from one place: Not available - Enterprise Grid with Members connect their own accounts: Available - Enterprise Grid with Domain-wide authentication: Available - Enterprise Grid with A daily or weekly schedule in a channel: Available - Enterprise Grid with Installing across workspaces from one place: Available **How to connect it** (A Slack Workspace or Org Owner or Admin to install, and a Google Workspace Super Admin if you want the domain-wide route. Otherwise every member, one at a time.. Twenty minutes to install. Weeks, in practice, waiting for people to connect their own accounts.): 1. Install each app from the Slack Marketplace [Slack Marketplace: Google Drive, Google Calendar]. Add to Slack, Add the app, Allow. These are two separate apps with two separate installs, and installing one does nothing for the other. On Enterprise organizations an Org Owner or Admin can install at the org level and push the app to the workspaces that need it. 2. Decide now whether members connect themselves or you do it for them [Slack: the app Home tab, Settings]. The default is per person, and it is where these projects stall. Domain-wide authentication connects every member with an email on your domain automatically, and Slack documents it as available on all plans rather than as an enterprise feature. 3. Get a Google Workspace Super Admin for the domain route [Slack: Domain-wide Authentication, Add domain]. Any Slack owner or admin can start the process, and authorising access on the Google side needs a Super Admin. The two apps each have their own Add domain button, so a domain verified for Calendar is not verified for Drive. 4. Understand what the domain route takes away [The same screen]. Once a domain is verified, members cannot disconnect their Google accounts, and connected members are automatically subscribed to event reminder notifications. They can turn the notifications off in the app's Settings; they cannot turn the connection off. 5. Invite the Calendar app into any channel that should get notices [Slack: the channel]. Type /invite @google calendar in the channel. A channel the app has not been invited to receives nothing, and this is a per-channel step rather than a setting on the app. 6. Configure the channel schedule if you are on a paid plan [Slack: Google Calendar Home, Channel Notifications]. Slack documents the daily or weekly schedule from a shared calendar as a paid-plan feature, both for channels and for your own daily schedule. On Free the app still works; the recurring digest is what is missing. 7. Turn Status Sync on deliberately [Slack: Google Calendar Home, Settings]. It writes your Slack status from your calendar. Worth a conversation before switching it on for a team, because a meeting title is not always something you want posted beside your name. 8. Know the reset before you need it [Slack Marketplace: Google Calendar, Configuration]. Slack's own fix for missing or out-of-date events is to click Revoke under Your Authorization and then Add to Slack again. That is the documented repair rather than a support ticket. **How to check it worked:** - Check a colleague's account rather than your own. Installing the app and connecting your account are different jobs, and the admin who installed it is always the first person connected. - Invite the app to one channel and confirm something arrives. A channel without the invite is silent and looks identical to a broken integration. - Share a Drive file with a channel where somebody lacks access. Slack prompts you to adjust the file permissions, which is the behaviour to show people once rather than explain twice. - If you enabled domain-wide authentication, confirm with one member that they cannot disconnect. That is documented behaviour and it is better discovered in a test than in a complaint. Agent skill for this pair: https://www.reversecontact.com/integrations-hub/skills/slack-google.md **Field mapping:** - Create a Drive file from Slack maps to Slash command, document, presentation or spreadsheet. Takes a title and an optional message, and offers to share it with a person or channel as it is created. Unchecking that box creates the file without sharing it. - Share an existing Drive file maps to Add from Google Drive. Slack prompts to adjust file permissions when members of the channel cannot view, comment or edit. The prompt is the governance, and it is per share. - Drive comments maps to Replies from inside Slack. Notification scope is managed in Google Drive rather than in Slack: open the file, the comments icon, then Notifications. - Your own calendar maps to The Google Calendar app Home tab. Today, Tomorrow or a chosen date, with event details, guest list and location behind the three-dots menu. Multiple calendars can be connected from the Accounts dropdown. - Event responses maps to The app's Messages tab. Where you accept or change a response. Worth telling people, because the Home tab shows the schedule and does not take the answer. - Channel notifications maps to Only after /invite @google calendar. A per-channel invite rather than an app setting, and the most common reason a correctly configured channel receives nothing. - A daily or weekly schedule in a channel maps to Paid Slack plans. Slack states the recurring schedule notification from a shared calendar is a paid-plan feature, and the same applies to your personal daily schedule. - Slack status maps to Status Sync, off until you turn it on. Written from the calendar you connected. One calendar drives it, which is why a team calendar and a personal one do not combine into one status. - Does not cross: A shared team view of everybody's calendar. The integration is built around the individual, which is the gap practitioners most often describe when they expect a glanceable team schedule in a channel. - Does not cross: Governance of Drive file access from inside Slack. Permissions stay Google's, and Slack only prompts at the moment of sharing. - Does not cross: Anything at all in a channel the Calendar app has not been invited to. **What breaks:** - **Install and connect are different jobs.** An admin installs the app for the workspace; every member who wants it then connects their own Google account. Nothing about the admin screen suggests the rollout is incomplete, so the usual failure is a workspace where the apps are installed, a handful of people connected in the first week, and everybody else concluded the integration does not work. - **Domain-wide authentication needs two admins.** It is available to workspace owners and admins on Free, Pro and Business Plus and to org owners and admins on Enterprise, and authorising it requires a Google Workspace super admin. In most companies those are two different people on two different teams, which makes this a scheduling problem rather than a configuration one. It is also the only route that scales past a few dozen people. - **Status syncing reads one calendar.** Slack syncs status with the primary calendar of the connected Google account and no other. A person who keeps client meetings on a second calendar shows as available through all of them, and there is no setting that adds one. The same shape of limit as HubSpot's calendar sync, for the same reason. - **Drive files are not yours to govern in Slack.** Files shared from Drive stay in Drive and are not stored in the workspace. Slack retention does not apply to them, an export will not contain them, and revoking access happens in Google rather than in Slack. That is the correct design and it matters to anyone who assumed a Slack export was a complete record of what was shared. **Failures people hit:** - A channel receives no calendar notifications at all. Why: The Google Calendar app has not been invited to that channel. It is a per-channel step, not an app-wide setting. Fix: Type /invite @google calendar in the channel. Then configure the notifications from the app's Home tab under Channel Notifications. - Events are missing or out of date in the app. Why: The authorisation has gone stale. Slack documents this as its own fix rather than a support path. Fix: Open the Google Calendar page in the Slack Marketplace, Configuration tab, click Revoke under Your Authorization, then Add to Slack to reconnect. - There is no daily or weekly schedule option. Why: The workspace is on the Free plan. Slack marks the recurring schedule notification as a paid-plan feature in two places. Fix: Nothing to configure. The rest of the app works on Free, and a human posting the schedule is the honest substitute until the plan changes. - The integration works for the admin and nobody else. Why: Installing the app and connecting an account are different jobs. The admin who installed it connected themselves in the process. Fix: Either chase every member through the Home tab, or enable domain-wide authentication and connect everybody at once. - A member wants to disconnect their Google account and cannot. Why: Domain-wide authentication is enabled, and Slack documents that members cannot disconnect while it is. Fix: There is no per-member exemption. They can turn off the event reminder notifications they were automatically subscribed to, which is usually the real complaint. - Drive is connected and Calendar is not, or the reverse. Why: They are two separate apps with separate installs, separate authorisations and separate Add domain steps. Fix: Repeat every step for the second app. A domain verified for one is not verified for the other. - Somebody shared a Drive file nobody in the channel can open. Why: Slack prompts to adjust file permissions when members lack access, and the prompt can be dismissed. Fix: Fix the sharing in Google Drive. Slack never owns these permissions, which is worth saying out loud to a team that assumes posting a file grants access to it. - The Agents and tools tab is not in the sidebar. Why: Slack renamed it, and older workspaces still show the previous label. Fix: Look for a Tools tab instead, and click More if neither is visible. Slack notes this on both app articles. **What practitioners say** (14 threads from 2024 to 2026, read 2026-10-11): The threads are about the gap between what people expect from these two apps and what they do. The recurring disappointment is specific and correct: the official Google Calendar integration is built around the individual, so nobody gets the glanceable team schedule they imagined. The other theme is provisioning, where practitioners describe Slack's own plan tiers as the obstacle rather than Google. - The integration is personal, and people expect it to be shared (r/Slack, February 2026, 1 points): https://www.reddit.com/r/Slack/comments/1rehxqa/using_google_calendar_and_slack_what_am_i_missing/ - The documented workaround is a shared calendar in a channel (r/Slack, February 2026, 1 points): https://www.reddit.com/r/Slack/comments/1rehxqa/using_google_calendar_and_slack_what_am_i_missing/ - Provisioning is where Slack's plan tiers bite (r/Slack, January 2026, 1 points): https://www.reddit.com/r/Slack/comments/1prnykm/google_workspace_integration_with_slack/ - Guest seats are the cheap route people forget (r/gsuite, September 2024, 1 points): https://www.reddit.com/r/gsuite/comments/1ffe327/bridge_between_google_chat_and_slack/ - Threads are where channel notifications go to be missed (r/Slack, May 2025, 5 points): https://www.reddit.com/r/Slack/comments/1kd04ln/whats_your_biggest_frustration_with_slack/ Sources: https://slack.com/help/articles/205875058-Google-Drive-for-Slack | https://slack.com/help/articles/206329808-Google-Calendar-for-Slack | https://slack.com/help/articles/360047862573-Enable-domain-wide-authentication-for-calendar-and-file-apps-in-Slack ### Apollo and Slack Not an alert feed any more: you prospect, enrich and sequence by typing in Slack. - Built as: Native, Marketplace app, Built on the API - Syncs: Two-way sync - Moves: Messages, Activities, Contacts - Costs to turn on: Included on both sides. Setup: Minutes - Requires: An Apollo plan and a Slack workspace. An Apollo admin to connect it, and professional or organization for agents. - Full guide: https://www.reversecontact.com/integrations-hub/apollo-integrations/apollo-slack-integration **Verdict.** This stopped being a notification integration and nobody updated the mental model. An Apollo admin connects it once for the whole workspace, and from then on anybody can prospect, enrich, sequence and report by typing in a Slack thread, under the permissions and credit limits they already have in Apollo. Notifications still exist and are configured in two separate places, which is the one genuinely confusing thing about it: system activity and tasks live in Apollo's notification settings, and anything from the AI assistant or a scheduled agent lives under AI Assistant, Channels. Email engagement alerts are in neither, and come from the Chrome extension or a workflow. **What syncs:** - Natural language requests (in): Search, research, enrich, add to a list or sequence, export, ask about sequence performance, pause a sequence. The conversation is saved into Apollo's AI assistant. - Agent recommendations (out): On professional and organization plans. They run on a schedule, arrive in Slack for review, and Apollo continues the work once you approve one. - System activity notifications (out): Data request activity, either per completion or as a daily digest, enabled in Apollo's notification settings and ticked through to Slack. - Task notifications (out): Configured in the same place, and aimed at reps with busy workloads rather than at admins. - Email opens and clicks (event): Not in either notification screen. They come from the Chrome extension's desktop alerts, or from a workflow with an email opened or email clicked trigger. - Credits (event): Spent from Slack exactly as they are in the app. Enriching ten contacts in a thread costs what enriching ten contacts costs. **Which editions carry it** (rows Apollo, columns Slack): - Free or basic with The app, and everything you type: Included - Free or basic with System activity and task notifications: Included - Free or basic with Agents that recommend unprompted: Not included - Professional with The app, and everything you type: Included - Professional with System activity and task notifications: Included - Professional with Agents that recommend unprompted: Included - Organization with The app, and everything you type: Included - Organization with System activity and task notifications: Included - Organization with Agents that recommend unprompted: Included **How to connect it** (An Apollo admin, once, for the whole workspace. Nobody else has to do anything.. Five minutes to connect. The thinking is about credits and about which notifications go where.): 1. Check the plan against what you expect it to do [Apollo: Settings, Plans]. Apollo states the Slack app is available on all plans and that agents are available on professional and organization. If the reason you want this is unprompted recommendations rather than a surface to type into, that is a plan question before it is a setup one. 2. Decide who is allowed to spend credits before connecting [Apollo: Settings, Users and teams]. Apollo applies the same plan, permission and credit guardrails in Slack as in the product, so this is not a new permission model. It is a large reduction in friction against an existing one, which is the part worth discussing first. 3. Connect as an Apollo admin [Apollo: Settings, Integrations, or AI Assistant, Channels]. Click Connect beside Slack and sign in to the workspace. The integration is team-wide and only an admin can do it, so a non-admin seeing no Slack option is looking at the correct screen. 4. Set system activity and task notifications [Apollo: Settings, Notifications]. Tick what you want for system activity or tasks, then tick the option to receive them in Slack, then Save. System activity covers data request completions, either one by one or as a daily digest, which is the admin visibility half. 5. Set the AI assistant notifications separately [Apollo: AI Assistant, Channels]. Confirm Slack shows as connected, then choose which alerts you want: scheduled threads and long-running tasks. Apollo documents these as configured separately from the settings above, and that is the single most confusing thing about this pair. 6. Set up an agent if your plan carries them [Slack: Agents and apps, Apollo.io, Manage]. Agents run on a schedule and surface a recommendation in Slack for you to approve or decline. Approving one lets Apollo continue the work. They also run in the AI assistant, so Slack is where you see them rather than where they live. 7. Start a thread and chain the requests [Slack: Apollo.io, Messages]. Apollo's own advice is to be specific and chain: find prospects on criteria, then refine the search, then enrich with emails and phone numbers, then add to a list or sequence, then export. Each step continues in the same thread. 8. Decide where engagement alerts come from [Apollo: the Chrome extension or workflows]. Email opens and clicks are not in either notification screen. Apollo points at the Chrome extension for real-time desktop alerts, or a workflow with an email opened or email clicked trigger, which can send notifications to Slack users or channels. **How to check it worked:** - Have a non-admin run a request in a thread. They should be able to do exactly what they can do in Apollo and nothing more, which is the guardrail working rather than a permissions problem. - Enrich two contacts from Slack and then check the credit balance. Seeing the meter move for a one-sentence request is the point worth making to a team once. - Set a system activity notification and an AI assistant notification, then confirm both arrive. They are configured in different places and it is easy to believe you have done both when you have done one. - Ask the thread about a sequence you know the numbers for. Reporting questions are the cheapest way to test the connection without spending anything. Agent skill for this pair: https://www.reversecontact.com/integrations-hub/skills/apollo-slack.md **Field mapping:** - Find people and companies maps to A search in the thread, on your criteria. Apollo's own example is five VPs of sales in San Francisco at software companies with 100 to 500 employees. Refining and expanding happen in the same thread rather than as a new request. - Research people and companies maps to Returned into the thread. The research half of the AI assistant, reachable from Slack. Nothing is written anywhere until you ask for it to be. - Enrich contacts maps to Verified emails and phone numbers. The action that spends credits, and the one a one-sentence request makes easiest. Costs exactly what it costs in the product. - Add contacts to a list or sequence maps to An existing Apollo list or sequence. Apollo's example is adding the first ten contacts to a named sequence. The sequence has to exist already, as it does everywhere else in Apollo. - Ask about performance maps to An answer in the thread. Reply rates and sequence performance questions, which is the cheapest thing on this list because it reads rather than writes. - Take a sequence action maps to Simple actions, such as pausing. Documented as simple actions rather than full sequence management, so treat the reporting and the pausing as the realistic scope. - Export maps to A CSV. The end of the documented chain: find, enrich, add to a list or sequence, or export. Worth knowing a rep can take a prospect list out of Apollo from Slack. - The conversation itself maps to Saved into Apollo's AI assistant. So the thread is not the only record of what was asked, which matters both for continuity and for anybody auditing what was spent. - Does not cross: Anything reaching a CRM. Work done here lands in Apollo, and the CRM timeline is a separate integration with its own page. - Does not cross: A permission this integration grants on its own. Apollo states that each user can only take actions in Slack that they already have permission to perform, under the same plan, permission and credit limits. - Does not cross: Creating a sequence or a list from scratch in a thread. The documented chain adds contacts to ones that exist; agents are the feature that proposes creating new ones. **What breaks:** - **Notifications are configured in two unrelated places.** Settings, Notifications covers system activity and tasks, and Apollo states that AI assistant notifications, including scheduled agents and long-running tasks, are configured separately under AI Assistant, Channels. Somebody who sets one and expects the other gets silence from the half they did not touch. - **Agents need professional or organization.** The Slack app is on all Apollo plans and agents are not. Agents are the part that produces unprompted recommendations, so on a lower plan this is a surface you use rather than one that comes to you. - **Only an admin can connect it, and it is workspace-wide.** A team-wide integration with no per-user authentication. The upside is nobody has to connect anything; the consequence is that the decision is made once for everybody by one person. - **Convenience and the credit meter are the same thing.** Apollo applies the same plan, permission and credit guardrails in Slack as in the app. Enriching from a thread is not cheaper than enriching from the product, and it is considerably easier to do without thinking about it. - **It does not update the CRM.** This pair moves work and attention, not records. The CRM timeline comes from Apollo's CRM integration, which is a separate thing to configure. **Failures people hit:** - There is no Connect option beside Slack. Why: The Slack integration is team-wide and only an Apollo admin can connect it. Fix: Ask an Apollo admin. There is no per-user alternative, and once they have connected it everybody in the workspace can use it without connecting anything themselves. - Notifications were configured and half of them never arrive. Why: There are two separate screens. Settings, Notifications covers system activity and tasks; AI assistant notifications, including scheduled agents and long-running tasks, are configured under AI Assistant, Channels. Fix: Set both. Apollo documents the separation explicitly, and it is the most common misconfiguration on this pair. - No recommendations ever arrive unprompted. Why: Agents need a professional or organization plan. On a lower plan this is a surface you use rather than one that contacts you. Fix: Check the plan before debugging the channel. Agents also run in the AI assistant, so if they exist at all you will see them there too. - Email opens and clicks are not reaching Slack. Why: They are in neither notification screen. Apollo routes engagement alerts through the Chrome extension or through workflows. Fix: Use the Chrome extension for real-time desktop alerts, or build a workflow with an email opened or email clicked trigger and a send notifications action pointed at a Slack user or channel. - A rep cannot do something in Slack that a colleague can. Why: Working as intended. Each user can only take actions in Slack that they already have permission to perform in Apollo, under the same plan, permission and credit limits. Fix: Fix the permission profile in Apollo rather than looking for a Slack setting. There is no Slack-side permission model to adjust. - Credits went down faster than anybody expected. Why: Enrichment from a thread costs exactly what enrichment costs, and a one-sentence request is much easier to make than the same action in the product. Fix: This is a policy problem rather than a configuration one. Decide who is allowed to enrich at volume, and use the system activity notifications, which exist precisely to make data requests visible. - A request returned nothing useful. Why: Apollo's own guidance is to be specific and to chain requests rather than asking for everything at once. Fix: Start with the criteria, then refine in the same thread, then enrich, then add to a list or sequence. Backing out and messaging Apollo again starts a new chat and loses the context. - A sequence could not be added to. Why: The documented chain adds contacts to lists and sequences that already exist. Creating them is not part of it. Fix: Build the sequence in Apollo first. This is the same prerequisite every sequencer pair in this directory has. **What practitioners say** (14 threads from 2024 to 2026, read 2026-10-11): Searching this pair by name is a trap worth recording: Apollo is also the name of a well-known discontinued Reddit client, and the first search returned a subreddit full of iOS push-notification threads about it. Searched properly, almost nobody discusses Apollo and Slack together, so this is a job search about getting sales work and alerts into the channel where the team already is. The recurring theme is restraint, from people who have watched a channel become unreadable. - There is a ceiling on how many integrations a workspace can carry (r/Slack, April 2026, 1 points): https://www.reddit.com/r/Slack/comments/1slry58/how_do_you_actually_manage_a_high_volume_of/ - The safeguard people reach for is an approval step, not a permission (r/Slack, April 2026, 1 points): https://www.reddit.com/r/Slack/comments/1slry58/how_do_you_actually_manage_a_high_volume_of/ - One channel per subject beats one channel per tool (r/agency, July 2025, 1 points): https://www.reddit.com/r/agency/comments/1mbrrcx/how_are_you_structuring_your_slack_to_your_clients/ - A notification is a prompt to look, not a record (r/Netsuite, June 2026, 1 points): https://www.reddit.com/r/Netsuite/comments/1u9ai4y/netsuite_slack_integration_for_sales_orders/ - The tool-count problem is what people actually complain about (r/microsaas, April 2026, 1 points): https://www.reddit.com/r/microsaas/comments/1sthi1r/i_replaced_apollo_clay_instantly_hubspot_with_one/ Sources: https://knowledge.apollo.io/hc/en-us/articles/22464817775117-Integrate-Slack-with-Apollo | https://knowledge.apollo.io/hc/en-us/articles/34009920880781-Configure-Notifications-on-Apollo ### Apollo and LinkedIn Sales Navigator Not an integration. A browser extension, against a user agreement that forbids one. - Built as: Native - Syncs: One way, in - Moves: Contacts, Companies - Costs to turn on: Metered by usage. Setup: Minutes - Requires: A paid Apollo plan for the CRM hop, credits for each save, and a reading of LinkedIn's terms - Full guide: https://www.reversecontact.com/integrations-hub/apollo-integrations/apollo-linkedin-integration **Verdict.** Every other page in this directory describes an integration; this one describes a browser extension and a user agreement that prohibits the category it belongs to, and pretending otherwise would be the most useful thing we could get wrong. The capability is real: open a LinkedIn profile, see Apollo's data over it, save the person as a contact and put them in a sequence, all in a few seconds. The risks are also real and they are borne by the person with the LinkedIn account rather than by the vendor. Read LinkedIn's section 8.2 before you roll this out to a team, decide knowingly, and do not let anybody describe it internally as an integration with LinkedIn, because LinkedIn has not agreed to one. **What syncs:** - A LinkedIn profile to an Apollo contact (in): Save contact or access email, or access email and phone. Both consume Apollo credits. - Apollo data over the page (in): Rendered in your browser by the extension. Nothing is written to LinkedIn and nothing is stored there. - Saved contacts into sequences and lists (in): Inside Apollo, from the extension. The sequencing happens in Apollo, not on LinkedIn. - Colleagues at the same company (in): The extension surfaces similar profiles and colleagues, which is the part that makes it a list-building tool rather than a lookup. - Anything back to LinkedIn (out): Nothing. There is no write path, no app and no API between the two companies. **How to connect it** (Whoever is doing the prospecting. There is no admin step, which is most of why this pair spreads through a team without anybody deciding to adopt it.. Two minutes. Read the second step before you spend them.): 1. Read LinkedIn's User Agreement before the extension, not after [LinkedIn: User Agreement, section 8.2]. LinkedIn forbids using software, scripts, browser plugins or other means to access its services, and says prohibited tools may stop working without notice. Nothing on this page changes that, and every step below sits underneath it. 2. Decide who in the team is allowed to use it [A policy, not a settings page]. Because there is no admin install, the decision gets made by whoever installs the extension first. If your company has a view on scraping, this is the moment it needs to be written down rather than discovered. 3. Install the Apollo Chrome extension [Chrome Web Store]. A per-user browser install with no connection between the two platforms behind it. Apollo renders its own data over the LinkedIn page in your browser; nothing is written back to LinkedIn and no API sits between them. 4. Open a profile and choose how much you are revealing [A LinkedIn profile, with the extension open]. Save contact or access email saves the person and reveals an address. Access email and phone does both. Apollo prices these separately in credits, so this click is the spend. 5. Decide the EU and UK question yourself [Your own filtering, before the sequence]. Apollo states that it does not remove EU-based or UK-based contacts for you. Whoever owns your lawful basis has to apply that filter somewhere downstream, and the extension is not the place it happens. 6. Send from Apollo, not from LinkedIn [Apollo: sequences and lists]. Saved contacts flow into Apollo sequences and lists. Keeping the sending inside Apollo is also the arrangement least likely to involve automating actions on LinkedIn itself, which is the part practitioners report getting shut down. **How to check it worked:** - Check your credit balance before and after revealing one phone number. Apollo publishes the cost, and seeing it move is how a team learns the meter is real. - Confirm a saved contact arrived in the Apollo list you expected rather than in a default one. - Spot-check one revealed email against a reply, not against a verification badge. The number that matters is whether you got answered. - If you operate in the EU or UK, pick ten saved contacts and check whether any of them should not have been saved. Apollo will not have done that for you. Agent skill for this pair: https://www.reversecontact.com/integrations-hub/skills/apollo-linkedin.md **Field mapping:** - A LinkedIn profile you are viewing maps to An Apollo contact. Saved from the extension. Apollo prices a verified email at 1 credit. - The same profile, with a phone number maps to An Apollo contact with a direct dial. Apollo prices a verified phone number at 8 credits, which is eight times the email and the reason a team burns an allowance faster than it planned. - Contact and company enrichment maps to Filled fields on the Apollo record. Published at 1 to 8 credits depending on what comes back. - An AI research run maps to Insight on the Apollo record. 1 credit per run, so a workflow that researches every saved contact doubles the cost of saving them. - Anything at all maps to Back to LinkedIn. Nothing. No write path, no app, no API. The extension is a reader and LinkedIn is unaware of it. - Does not cross: EU and UK contacts, filtered out. Apollo says plainly that it does not do this for you. - Does not cross: Any LinkedIn field, as a field. You are getting Apollo's record for a person you found on LinkedIn, which is a different thing from LinkedIn's data about them. - Does not cross: Automated actions on LinkedIn. Practitioners report that Apollo's automated LinkedIn outreach stopped, and the steps above deliberately keep sending inside Apollo. **What breaks:** - **LinkedIn's terms prohibit the category.** Section 8.2 of the User Agreement forbids using software, scripts, browser plugins or add-ons to scrape or copy the Services including profiles, and a separate clause forbids bots or other unauthorised automated methods to access the Services, add or download contacts or send messages. LinkedIn's help centre states that members using prohibited tools risk having their accounts restricted or shut down. The exposure sits with the rep whose account it is, which is a management decision rather than a procurement one. - **It can stop working without notice.** LinkedIn says prohibited tools may become non-operational without notice, and the mechanism is simply that the page changes. Any workflow built on an overlay of somebody else's website inherits that fragility, so a list build that has to complete this quarter should not have this as its only path. The data itself is available through Apollo's own search and API, which is the route that does not depend on a page layout. - **No EU or UK filtering is applied for you.** Apollo states plainly that it does not remove EU-based or UK-based contacts from the Chrome extension, and recommends checking a prospect's location on LinkedIn before saving them so that you stay GDPR compliant. That makes compliance a per-save human judgement in the middle of a fast repetitive task, which is a poor place to put it. If your market includes Europe, build the check into the process rather than relying on the rep noticing. - **Credits are the meter, and they expire.** Saving a contact or revealing an email or phone number consumes credits. Apollo pools credits across the team and grants them upfront each billing cycle, and unused credits expire rather than carrying over. A team that does its list building in one week a month therefore pays for a monthly allowance it uses unevenly, and the free plan does not include the CRM integrations that would get the saved contact anywhere useful. **Failures people hit:** - The extension stopped returning anything on LinkedIn pages. Why: LinkedIn states that tools in this category may become non-operational without notice, and practitioners report exactly that happening. Fix: There is no configuration fix. Treat continuity as a risk you carry rather than a service level, and keep the contacts you have already saved exported. - Credits are gone and nobody did a bulk job. Why: Phone reveals. Apollo publishes a verified phone number at 8 credits against 1 for an email, and the cost is per click rather than per campaign. Fix: Agree as a team when a phone number is worth revealing. The habit, not the volume, is what empties the allowance. - Legal asked who approved this and nobody had. Why: There is no admin install. One rep adds a browser extension and the company has adopted a tool. Fix: Decide the policy explicitly. This is the only integration in the directory where the governance gap is the default state rather than a misconfiguration. - EU contacts are in a sequence that should not have them. Why: Apollo does not remove EU-based or UK-based contacts, and says so. Fix: Filter before the sequence, in Apollo or in whatever sits downstream. Nothing upstream will do it. - An email bounced that Apollo showed as verified. Why: Verification is a claim about the address at some point in time, not a guarantee of deliverability today. Fix: Measure your own bounce rate over a few hundred sends rather than trusting a per-record badge, and treat the rate as the number worth quoting internally. **What practitioners say** (14 threads from 2024 to 2026, read 2026-10-11): This is the only pair in the directory where the threads are about whether the integration is allowed to exist. In March 2025 practitioners reported LinkedIn removing company pages belonging to tools in this category, and the conversation since has been about which vendors are exposed and which are not. Nobody is arguing the extension does not work. They are arguing about how long it will keep working and what it costs to be wrong. - The category got a visible enforcement moment (r/sales, March 2025, 17 points): https://www.reddit.com/r/sales/comments/1j6tuj8/with_the_linkedin_crackdown_on_apollo_seamless/ - How a vendor sources data predicts whether it is exposed (r/sales, March 2025, 8 points): https://www.reddit.com/r/sales/comments/1j6tuj8/with_the_linkedin_crackdown_on_apollo_seamless/ - The automated half appears to be gone (r/GrowthHacking, February 2026, 4 points): https://www.reddit.com/r/GrowthHacking/comments/1qzykwk/is_apollos_automated_linkedin_outreach_dead_now/ - Teams are choosing between this and the licensed route (r/b2bmarketing, October 2026, 4 points): https://www.reddit.com/r/b2bmarketing/comments/1wxzl6u/sales_navigator_or_apollo/ - The licensed route has its own weakness (r/b2bmarketing, October 2026, 5 points): https://www.reddit.com/r/b2bmarketing/comments/1wxzl6u/sales_navigator_or_apollo/ Sources: https://knowledge.apollo.io/hc/en-us/articles/4409229262093-Prospect-on-LinkedIn-with-the-Apollo-Chrome-Extension | https://www.linkedin.com/legal/user-agreement | https://www.linkedin.com/help/linkedin/answer/a1341387 | https://www.apollo.io/pricing ### Apollo and Salesforce Six hours to configure it, then it turns itself on whether or not you finished. - Built as: Native, Marketplace app - Syncs: Two-way sync - Moves: Contacts, Companies, Deals, Activities - Costs to turn on: Needs a higher plan. Setup: Hours - Requires: Apollo Basic or above, a Salesforce edition with API access, and a Salesforce admin - Full guide: https://www.reversecontact.com/integrations-hub/apollo-integrations/apollo-salesforce-integration **Verdict.** The deepest engagement-to-CRM sync in the directory, and the one with the most self-starting behaviour. Apollo pushes contacts, accounts, deals and activity into Salesforce in real time once enabled, with per-object settings and field mapping you control. Three documented behaviours decide whether the first month is calm: the configuration window is six hours and then syncing enables itself, push settings govern only net new contacts because updates to existing ones push regardless, and pushing any contact creates its account whether or not you asked, because Salesforce requires one. **What syncs:** - Contacts and leads (out): Net new contacts push on save, with field mapping you configure. Updates to existing contacts push automatically whatever the push settings say. - Accounts (out): Created or updated whenever a contact is pushed, even with Push accounts off, because Salesforce requires every contact to link to an account. - Deals (two-way): Full bidirectional, or pull-only, or push-only. With bidirectional on, Salesforce is the source of truth for deals that have already synced. - Activities (out): Emails, tasks, notes, meeting summaries and phone calls, each configured separately so you choose what reaches the CRM. - Salesforce records into Apollo (in): Pull settings bring records back, and can infer accounts where your org works in leads. - Custom objects (in): Read only. Organization plans can configure up to ten, and the data cannot trigger Apollo workflows. **Which editions carry it** (rows Apollo, columns Salesforce): - Already pushed as a lead with Leads: updated as a lead - Already pushed as a lead with Contacts: updated as a lead - Already pushed as a contact with Leads: updated as a contact - Already pushed as a contact with Contacts: updated as a contact - Never pushed with Leads: updated as a lead - Never pushed with Contacts: updated as a contact **How to connect it** (A Salesforce admin to install the managed package, and an Apollo user with permission to edit CRM integrations. The two are rarely the same person.. An hour of clicks, and the six hours after it are not optional free time.): 1. Clear the configuration afternoon before you connect anything [Your calendar]. On a paid Apollo plan the clock starts at the connection: six hours to set the field mapping and the inbound and outbound settings, after which syncing enables itself. You cannot manually pull records during the window, so there is no way to use the time for anything but configuration. 2. Decide production or sandbox, because you get one [Apollo: Settings, Integrations, Salesforce]. Connect for production, or Connect to Sandbox, and never both at once. A team that rehearses in a sandbox has to disconnect it before going live, which means doing the configuration twice unless the rehearsal was the point. 3. Install the Apollo managed package for the right users [Salesforce AppExchange, via Apollo]. Click Install Managed Package in Apollo, which redirects you to the AppExchange. Apollo strongly recommends installing for all users, or for the specific profiles that contain your Apollo users. Installation takes a few minutes and needs Salesforce admin access. 4. Create the integration user in the Apollo Setup app [Salesforce: App Launcher, Apollo Setup]. Open the Apollo Setup app, click Get Started, and create a new integration user or select an existing one. Apollo strongly recommends keeping every default permission selected to prevent sync issues, and warns that mapping custom Salesforce fields later requires giving this user access to those fields now. 5. Authenticate from Apollo as that user [Apollo: Connect, Yes Continue]. Whoever connects using the dedicated integration user becomes the team sync user, and that one connection does the account-wide syncing. Individual Apollo users do not need to connect their own Salesforce accounts for standard data sync. 6. Set the push type knowing it is close to permanent [Apollo: Salesforce, Contacts, Sync]. Leads or contacts, and the choice only governs records that have never been pushed. Existing leads stay leads and keep being updated as leads; existing contacts stay contacts. Salesforce can convert a lead to a contact and cannot convert one back. 7. Configure each activity type separately [Apollo: Activities, Sync]. Emails, tasks, notes, meeting summaries and phone calls are five settings rather than one switch. If something else in the org already logs emails or calls, this is where you keep Apollo out of that lane. 8. Run a manual Push all after any mapping change [Apollo: people or company search]. Apollo documents that a manual push overrides the sync settings entirely, ignoring stage restrictions and other limits, and that a Push all is how you apply a new field or stage mapping to records already in Salesforce. Manual push also does not work during the initial data pull. **How to check it worked:** - Check the clock the moment you connect. If the six hours expire mid-configuration, syncing starts against whatever the mapping looked like at that minute, and the first sync is the one that touches every matched record. - Push one net new contact whose account does not exist in Salesforce, with Push accounts switched off. The account will be created anyway, and seeing it happen once is cheaper than explaining it later. - Switch push off and then change a contact that already exists in Apollo. It will still reach Salesforce, because push settings only govern net new and CSV-imported records. - Check the Owner field on a record Apollo created. Records created through the team sync connection normally carry the integration user, so a team that routes on Owner needs to decide what to do about that before go-live. Agent skill for this pair: https://www.reversecontact.com/integrations-hub/skills/apollo-salesforce.md **Field mapping:** - Contacts maps to Salesforce contacts or leads, your choice. Push based on certain stages is available here and only here. A contact with no stage is not pushed unless you explicitly include No stage in the selection. - Leads maps to Salesforce leads. If your org works in leads, contacts associate with leads rather than accounts. Apollo can infer accounts for you in the pull settings instead. - Accounts maps to Salesforce accounts, whether or not you asked. Pushing a net new contact creates or updates its account even with Push accounts off, because Salesforce will not accept a contact without one. - Deals maps to Salesforce opportunities. Bidirectional, pull-only or push-only. With bidirectional on, Salesforce is the source of truth for deals that have already synced. - Activities maps to Five separate settings. Emails, tasks, notes, meeting summaries and phone calls, configured one at a time. This is the object where a duplicate-logging problem is prevented rather than fixed. - The source field maps to Defaults to Apollo. Set on new contacts synced from Apollo, and if the field you pick is a picklist you choose the value too. Worth setting deliberately, because it is the only attribution this integration writes. - Unverified emails maps to Off unless you tick it. Push unverified emails for contacts and leads governs the email address only, not whether the contact is pushed. A contact with an unverified email still arrives; the address does not. - Custom objects maps to Read only, up to ten on Organization plans. They come into Apollo and cannot trigger Apollo workflows, so they are context for a rep rather than something to automate on. - Does not cross: Filtering beyond stage. Apollo states that Salesforce push settings do not support filtering on anything else, so there is no way to push only contacts whose custom field has a particular value. - Does not cross: A lead-to-contact conversion. Changing the push type affects new records only, and converting existing leads is Salesforce's own lead conversion process rather than an Apollo setting. - Does not cross: The Owner field, in the usual case. Records created through the team sync connection normally carry the integration user, and Apollo's documented alternative is mapping its created_by field to Salesforce CreatedById instead. **What breaks:** - **The configuration window closes by itself.** Six hours after you first connect on a paid plan, syncing enables automatically whether or not the field mapping is finished, and you cannot manually pull records until it does. Book the configuration session for immediately after the connection rather than for the following morning, because the integration does not wait and the first sync is the one that writes to every matched record. - **Push settings do not govern updates.** They apply to net new contacts saved in Apollo or imported by CSV. Every update to a contact that already exists pushes automatically regardless. Teams who switch push off expecting Apollo to go quiet find it still writing, and the only real control over a given field is the mapping. - **Accounts are created whether you asked or not.** Pushing a net new contact creates or updates its linked account even with Push accounts off, because Salesforce will not accept a contact without one. In an org where account creation is governed, that is a process conversation to have before go-live rather than a surprise for whoever owns data quality. - **One org at a time, and not the free plan.** You can connect a production org or a sandbox, never both, so rehearsing in a sandbox means disconnecting it before you go live. Apollo's free plan excludes CRM integrations entirely, which makes Basic the real floor for anything on this page. - **Existing connections have a deadline.** Apollo states that all existing Salesforce connections must upgrade to the managed package by 31 December 2026, and recommends doing it early. The upgrade keeps your field mappings and push and pull settings, and the migrate option is being rolled out gradually, so a team that cannot see it yet is waiting for an email from Apollo rather than looking in the wrong place. **Failures people hit:** - Insufficient access on cross reference ID. Why: The integration user cannot see a record that the one being written relates to through a lookup or master-detail field. It is a record sharing problem rather than an object or field permission. Fix: Check the sharing model and the lookup fields for the integration user, not for yourself. Practitioners in r/salesforce point out that being an admin does not guarantee read and edit access to every field, which is why the error survives an admin credential. - Syncing started before the mapping was finished. Why: The six hour configuration window expired. On a paid plan Apollo enables syncing automatically at that point, whether or not anybody was ready. Fix: Fix the mapping and run a manual Push all, which Apollo documents as the way to apply a new field or stage mapping to records already in Salesforce. The first sync cannot be unwound. - Apollo is still writing after push was switched off. Why: Push settings govern net new contacts saved in Apollo and ones imported from a CSV. Updates to contacts that already exist push automatically regardless. Fix: Control the field mapping rather than the push toggle. A field Apollo must never write is a field Apollo must not be mapped to. - A contact landed on the wrong account. Why: The contact matched more than one existing Salesforce account, and Apollo documents assigning one at random in that case. Fix: Use consistent account naming, or push only contacts whose accounts already exist. There is no tie-break setting to configure. - Accounts are appearing that nobody pushed. Why: Pushing a net new contact creates or updates its linked account even with Push accounts off, because Salesforce requires every contact to have one. Fix: Treat it as a governance conversation rather than a setting. In an org where account creation is controlled, have it before go-live rather than with whoever owns data quality afterwards. - Contacts with no stage are not reaching Salesforce. Why: Push based on certain stages excludes contacts with no stage unless No stage is explicitly selected in the list. Fix: Add No stage to the selection, or push everything. Remember that stage is the only filter available: Apollo states push settings do not support filtering on custom field values. - A sync error survived upgrading the Salesforce edition. Why: An edition with API access is necessary and not sufficient. The same error is produced by the connected user's permissions and by an Apollo field mapping, and one r/salesforce commenter reports legacy Group Edition blocking API integrations whatever you pay. Fix: Confirm which of the three it is before buying the upgrade. Practitioners in that thread say exactly this, and a field mapping or a sharing rule will keep failing after the plan changes. - The migrate option for the managed package is not there. Why: Apollo is rolling the upgrade path out over time. Existing connections have until 31 December 2026 and the option appears when Apollo says it is ready. Fix: Wait for the email rather than reconnecting from scratch. The upgrade preserves existing field mappings and push and pull settings, and a fresh connection would restart the six hour window. **What practitioners say** (14 threads from 2023 to 2026, read 2026-10-11): Two useful things come out of these threads. The first is that the errors people report are Salesforce errors rather than Apollo ones: sharing rules, lookup access and edition limits, with admins surprised that holding the admin profile does not settle it. The second is more interesting, because it is Apollo arguing against its own widest setting: a post in Apollo's own subreddit says not to sync top-of-funnel prospecting data to the CRM at all, which is the opposite of what a connector this thorough implies you should do. - The errors are Salesforce sharing problems, not integration problems (r/salesforce, January 2026, 3 points): https://www.reddit.com/r/salesforce/comments/1qcx3sg/apolloio_integration_help/ - Being a Salesforce admin does not mean you can see every field (r/salesforce, January 2026, 1 points): https://www.reddit.com/r/salesforce/comments/1qcx3sg/apolloio_integration_help/ - Apollo itself says not to sync top-of-funnel data (r/UseApolloIo, December 2025, 2 points): https://www.reddit.com/r/UseApolloIo/comments/1u3u58x/when_to_sync_apollo_to_your_crm_and_when_you/ - Duplicates in the CRM are paid for twice (r/UseApolloIo, June 2026, 1 points): https://www.reddit.com/r/UseApolloIo/comments/1u3u58x/when_to_sync_apollo_to_your_crm_and_when_you/ - An edition upgrade is not a guaranteed fix for a sync error (r/salesforce, July 2026, 1 points): https://www.reddit.com/r/salesforce/comments/1v3llqe/apolloio_integration_with_salesforce/ Sources: https://knowledge.apollo.io/hc/en-us/articles/4414356051725-Integrate-Salesforce-with-Apollo | https://knowledge.apollo.io/hc/en-us/articles/4414469523981-Configure-Salesforce-Push-Settings | https://resources.docs.salesforce.com/latest/latest/en-us/sfdc/pdf/salesforce_app_limits_cheatsheet.pdf ### Apollo and Outreach One Outreach account per Apollo workspace, so connect an admin or nobody sees the sequences. - Built as: Native - Syncs: One way, out - Moves: Contacts, Lists - Costs to turn on: Paid add-on or licence. Setup: Minutes - Requires: An Outreach contract, a paid Apollo plan, and an admin Outreach account to connect - Full guide: https://www.reversecontact.com/integrations-hub/apollo-integrations/apollo-outreach-integration **Verdict.** A deliberately narrow integration that does one thing cleanly: it turns an Apollo search result into an Outreach prospect in a sequence, without a CSV. There is no record sync, no activity writeback and nothing coming the other way, which is the right scope when Apollo is the data layer and Outreach is the sending layer. Two things to get right on day one: connect an admin Outreach account, because only one account can be connected at a time and a non-admin one hides sequences from everybody else; and check the field list, because thirteen fields travel and your personalisation may need a fourteenth. **What syncs:** - Net new people (out): Pushed from Apollo's people search after saving, with Add to Outreach. Creates the prospect in Outreach. - Saved contacts (out): Pushed from the contact's own profile, after which Apollo keeps a shortcut between the two records. - Sequence enrolment (out): Optional at push time, with the sending mailbox chosen in the same step. Click Refresh if a new sequence does not appear. - Thirteen contact fields (out): Name, LinkedIn and website URLs, title, city, state, country, email, phone, street, postal code and time zone, where Apollo holds them. - Outreach activity back to Apollo (in): Nothing. Replies, opens and sequence progress stay in Outreach, so Outreach is where you read performance. **Which editions carry it** (rows Apollo, columns Outreach): - All users with Their own: visible - All users with Their Apollo teammates': visible - All users with Everybody's: visible - Other users on the same team with Their own: visible - Other users on the same team with Their Apollo teammates': visible - Other users on the same team with Everybody's: hidden - Self only with Their own: visible - Self only with Their Apollo teammates': hidden - Self only with Everybody's: hidden **How to connect it** (An Apollo admin, and an Outreach admin account to authenticate with. The second one is the step that is hard to change later.. Ten minutes to connect. The rest is checking what travels before you move a campaign.): 1. Get the Outreach permission before you start [Outreach: governance profile settings]. The connecting user needs permission to create prospects in Outreach. Apollo points at Outreach's own governance profile documentation for it, and without it the authentication completes and the pushes do not. 2. Authenticate with an admin Outreach account [Apollo: Settings, Integrations, Outreach]. Click New Authentication, log into Outreach, then Finish. Apollo allows one Outreach account connected at a time and recommends an admin one specifically so the whole team can reach every Outreach sequence from Apollo. 3. Narrow which mailboxes reps can send from [Apollo: Settings, Users and teams, Permission profiles]. By default, send emails from shows every mailbox in Outreach. Under email permissions, Can send emails from takes All users, Self only, or Other users on the same team. The grid below is this setting, and the default is the widest one. 4. Check the thirteen fields against your sequence templates [Your Outreach templates]. First and last name, LinkedIn URL, website URL, title, city, state, country, email, phone, street, postal code and time zone. A merge field outside that list renders empty rather than failing, which degrades a campaign quietly. 5. Save the people before you push them [Apollo: People search, Net New]. Use search filters, click Net New, tick the prospects and click Save. Add to Outreach, then Push new contacts to Outreach, appears after that. An unsaved person pushed from a profile has to be saved first and Apollo redirects you there. 6. Pick the sequence and the sending mailbox in the same step [Apollo: Add to Outreach]. Enrolling in a sequence is optional at push time and the sending address is chosen alongside it. If a sequence you just built is not in the list, Apollo documents a Refresh that resyncs Outreach sequences and mailboxes rather than a wait. 7. Expect warnings and read them rather than clicking through [Apollo: the enrolment dialog]. Apollo warns before enrolment where it could create duplicate outreach, hurt deliverability or conflict with permissions: contacts already in another sequence, unverified or missing emails, outdated information. Contacts blocked by a workspace sending policy are not enrolled at all. 8. Use the shortcut to confirm the join worked [Apollo: the contact record]. A successful push creates a shortcut between the two platforms, and clicking Outreach on the Apollo contact opens the same person there. No Outreach option on a contact means the push did not land, and the fix is the Push to Outreach item in its menu. **How to check it worked:** - Push one contact and open it in Outreach through the shortcut Apollo creates. If the shortcut is absent, the push failed rather than being slow. - Run one sequence email to yourself through a template that uses every merge field you rely on. Any blank is a field outside the documented thirteen, and it is better to see it in your own inbox. - Push a batch of twenty deliberately containing somebody already in that sequence. The skip and the warning are what you want to see once, because in production they look like a broken push. - Check what mailboxes a non-admin rep can see in the send-from list. If it is all of them, the permission profile is still on the default. Agent skill for this pair: https://www.reversecontact.com/integrations-hub/skills/apollo-outreach.md **Field mapping:** - First name, last name maps to The Outreach prospect's name. Pushed as long as Apollo holds them. A contact Apollo only knows by email arrives without a name and personalises as a blank. - Email maps to The prospect email. Apollo warns at enrolment on unverified or missing emails rather than refusing, so an unverified address can be sequenced if you click through the warning. - Phone maps to The prospect phone. One phone field. Apollo's distinction between a mobile and a direct dial does not survive the push. - Title maps to The prospect title. The field most sequences personalise on after the name, and the one most likely to be stale on an older Apollo contact. - LinkedIn URL, website URL maps to The matching prospect fields. Both travel, which is more than most handoffs manage, and the LinkedIn URL is what makes a manual LinkedIn step in Outreach usable. - City, state, country, street, postal code maps to The prospect address fields. Five of the thirteen are address. Worth knowing if you assumed the budget was spent on richer firmographics. - Time zone maps to The prospect time zone. The one field that changes sending behaviour rather than copy, since Outreach schedules against it. - Everything else in Apollo maps to Nothing. Employee count, industry, funding, technologies, intent signals, Apollo lists and stages all stay in Apollo. A template that needs one of them needs a different source. - Does not cross: Anything from Outreach. Replies, opens, meetings and sequence progress stay there, so performance is read in Outreach and the list is built in Apollo. - Does not cross: Companies. Sequences enrol contacts rather than companies, so a companies list has to be turned into people first. - Does not cross: Mailbox rotation on a CSV push. Apollo documents that rotation is unavailable when adding contacts by CSV, and the route around it is importing to a list first and adding the list. **What breaks:** - **One Outreach account, and it should be an admin.** Apollo connects a single Outreach account at a time. Connect a non-admin one and the team sees only the sequences that account can reach, which looks like missing data and is a permissions choice made once at setup. The connecting user also needs permission to create prospects in Outreach. - **Thirteen fields, and no more.** The documented list is first and last name, LinkedIn URL, website URL, title, city, state, country, email, phone, street, postal code and time zone. Anything your sequences personalise on beyond that has to arrive another way. This is the limit that quietly degrades a campaign rather than breaking it, because the merge field is simply empty. - **Nothing comes back.** There is no writeback of replies, opens, meetings or sequence state into Apollo. Apollo is where the list is built and Outreach is where performance lives, and any report that needs both has to join them somewhere else, usually in the CRM both of them already write to. - **Silent skips during enrolment.** Contacts that are unsubscribed, bounced, marked Do Not Contact, already in the sequence, or limited by ownership and permission settings are skipped rather than failed. That is correct behaviour and it means a push of 200 can enrol 170 with no error. The Activities tab on each contact records what happened. **Failures people hit:** - The team cannot see most of the Outreach sequences. Why: A non-admin Outreach account was connected. Apollo allows one at a time and recommends an admin account precisely so the whole team can reach every sequence. Fix: Reconnect with an admin account. Confirm first that the connecting user has permission to create prospects in Outreach, which is a separate Outreach governance setting. - A sequence you just created is not in the list. Why: Apollo's cached copy of Outreach sequences and mailboxes is stale, or the sequence is inactive. Fix: Click Refresh in the push dialog, which Apollo documents as the resync. If it still does not appear, activate the sequence in Outreach and check you have edit access to it. - A push of 200 enrolled 170. Why: Apollo skips contacts it considers ineligible: unsubscribed, bounced, marked Do Not Contact, already in that sequence, or limited by ownership and permissions. Anything blocked by a workspace sending policy is never enrolled. Fix: Read the warnings on the enrolment screen and the Activities tab on each contact. The number is normal and the explanation is per contact rather than per batch. - A merge field is rendering empty in Outreach. Why: The field is outside the documented thirteen, or Apollo does not hold it for that contact. Neither case produces an error. Fix: Check your templates against the list before moving a campaign. Anything beyond those thirteen has to reach Outreach from the CRM or from an import rather than from this integration. - Insufficient credits when the workspace clearly has credits. Why: Apollo may check credits for the whole batch before enrolment starts rather than per contact, so a large push can fail against a balance that would cover most of it. Fix: Try a smaller batch, and review the waterfall enrichment settings, which is what Apollo's own documentation suggests for this error. - Mailbox rotation is not available on a CSV push. Why: Documented: rotation cannot be selected when contacts are added by CSV. Fix: Import the contacts into an Apollo list first, then add the list to the sequence and select two or more mailboxes. Same contacts, rotation available. - A contact in Apollo has no Outreach shortcut. Why: The push did not complete. Apollo creates the shortcut between the two records as part of a successful push. Fix: Use the Push to Outreach item in the contact's menu to retry. The shortcut is also the quickest way to audit whether a batch actually landed. - Contacts added by a workflow are not in the sequence yet. Why: A workflow or the outbound copilot enrols on its own trigger and schedule, such as hourly or daily, rather than immediately. Fix: Check the workflow's trigger conditions before debugging the integration. This is the one route where a delay is expected rather than a symptom. **What practitioners say** (14 threads from 2024 to 2026, read 2026-10-11): Hardly anybody discusses running these two together. The conversation is about replacing one with the other, and Apollo is running that conversation from its own subreddit with a post arguing it can fully replace Outreach. The most useful thread for anybody on this pair is a different one: Apollo's automated LinkedIn actions stopped working in early 2026, which matters because a team carrying both tools is often doing it for a multichannel sequence. Read the set as a decision aid rather than a troubleshooting guide, which is what this pair actually needs. - Apollo argues in its own subreddit that you should not run both (r/UseApolloIo, December 2025, 13 points): https://www.reddit.com/r/UseApolloIo/comments/1pps307/why_teams_are_switching_from_outreach_to_apollo/ - A team that switched reports keeping nothing (r/UseApolloIo, December 2025, 6 points): https://www.reddit.com/r/UseApolloIo/comments/1pps307/why_teams_are_switching_from_outreach_to_apollo/ - Apollo's automated LinkedIn actions stopped working in early 2026 (r/GrowthHacking, February 2026, 1 points): https://www.reddit.com/r/GrowthHacking/comments/1qzykwk/is_apollos_automated_linkedin_outreach_dead_now/ - The reason people keep Apollo is price, stated plainly (r/LeadGeneration, October 2024, 3 points): https://www.reddit.com/r/LeadGeneration/comments/1g8wjra/why_do_people_still_use_apolloio/ - Coverage outside tech is where the handoff gets thin (r/UseApolloIo, March 2026, 1 points): https://www.reddit.com/r/UseApolloIo/comments/1pps307/why_teams_are_switching_from_outreach_to_apollo/ Sources: https://knowledge.apollo.io/hc/en-us/articles/4414469672077-Integrate-Outreach-with-Apollo | https://knowledge.apollo.io/hc/en-us/articles/4409396985741-Add-Contacts-to-a-Sequence | https://knowledge.apollo.io/hc/en-us/articles/5694087661325-Use-Apollo-with-LinkedIn-to-Send-Personalized-Messages ### Outreach and Zapier Five instant triggers, and the one you want most is the one that polls. - Built as: Zapier, Make or n8n, Marketplace app - Syncs: Two-way sync - Moves: Contacts, Companies, Deals, Tasks, Activities - Costs to turn on: Metered by usage. Setup: Minutes - Requires: An Outreach contract, an Outreach account that can authorise the app, and a Zapier plan sized to your task volume - Full guide: https://www.reversecontact.com/integrations-hub/outreach-integrations/outreach-zapier-integration **Verdict.** The best-equipped app on the Zapier hub, and the only one here that can start a Zap on more than one kind of event. Five of its six triggers are instant, the actions cover the whole prospect lifecycle from create to sequence enrolment, and there is a beta raw API Request for anything the four named actions do not reach. The two things to design around are that the one trigger you want for closed-loop reporting is the only one that polls, and that enrolment has no idempotency: nothing stops a Zap adding the same person to the same sequence twice. **What syncs:** - New prospects (out): New Prospect fires instantly when a prospect is created, which makes Outreach a usable starting point for a chain rather than only a destination. - Calls and task updates (out): New Call and Updated Task both fire instantly. These are the activity events, and they are what a CRM or a warehouse wants if it is keeping its own record of what the team did. - Account and opportunity changes (out): Updated Account and Updated Opportunity fire instantly. Note the asymmetry: there is no trigger for a new account or a new opportunity, only for updates to one. - Completed sequence tasks (out): The one polling trigger, checked every 15 minutes on the free plan, and the only one that requires a Sequence ID up front. It watches the sequence you name rather than all of them. - New prospects, written back (in): Create Prospect takes first and last name, email addresses, and the account, opportunity, stage, persona and owner ids. The ids are the hard part: they are Outreach ids rather than names. - Sequence enrolment (in): Add Prospect to Sequence, usually preceded by Find Sequence to resolve the sequence by name. This is the action the pair exists for and the one with no duplicate protection. - Anything else (in): API Request is a beta action making a raw HTTP call that carries the integration's authentication, so the whole Outreach API is reachable without building an OAuth app of your own. **Which editions carry it** (rows Outreach, columns Zapier): - New Prospect with Starts a Zap instantly: Yes - New Prospect with Polls for changes: No - New Prospect with Needs a Sequence ID first: No - New Call with Starts a Zap instantly: Yes - New Call with Polls for changes: No - New Call with Needs a Sequence ID first: No - Updated Account with Starts a Zap instantly: Yes - Updated Account with Polls for changes: No - Updated Account with Needs a Sequence ID first: No - Updated Opportunity with Starts a Zap instantly: Yes - Updated Opportunity with Polls for changes: No - Updated Opportunity with Needs a Sequence ID first: No - Updated Task with Starts a Zap instantly: Yes - Updated Task with Polls for changes: No - Updated Task with Needs a Sequence ID first: No - Completed Sequence Task with Starts a Zap instantly: No - Completed Sequence Task with Polls for changes: Yes - Completed Sequence Task with Needs a Sequence ID first: Yes **How to connect it** (Somebody with an Outreach account that can authorise the app, plus whoever owns the Zapier workspace. Ideally create a dedicated Outreach user for it first.. Twenty minutes for the first Zap, most of it finding the ids the write actions want.): 1. Decide which Outreach user this connects as [Outreach: users]. The rate limit is 10,000 requests an hour metered per user, so the account you authenticate with determines whose budget a bulk run spends. A dedicated service user is the right answer and it is much easier to do now than to change once Zaps depend on it. 2. Connect Outreach in Zapier [Zapier: the Outreach app]. Add the Outreach app and authenticate as that user. Outreach uses OAuth 2.0, so this is a browser consent rather than a key you paste, and the person completing it needs an Outreach account with the rights to authorise an application. 3. Pick the trigger, knowing which one polls [Zapier: trigger]. New Prospect, New Call, Updated Account, Updated Opportunity and Updated Task are all instant. Completed Sequence Task polls, every 15 minutes on the free plan, and asks for a Sequence ID. Choose deliberately: the polling one is often the one people want and it behaves differently from the rest. 4. Resolve the sequence by name rather than by id [Zapier: Find Sequence]. Find Sequence takes a sequence name or an id and returns the sequence. Put it in front of the enrolment step so the Zap keeps working when somebody rebuilds a sequence, which changes the id and does not change the name. 5. Add your own duplicate check [Zapier: a filter]. Add Prospect to Sequence has no idempotency of its own. Put a filter or a lookup before it so a prospect already in the sequence is not added again. This is the step the integration cannot do for you and the one that stops somebody getting two first emails. 6. Reach for API Request only when the named actions do not fit [Zapier: API Request (Beta)]. The beta API Request action makes a raw HTTP call carrying the integration's authentication, so the rest of the Outreach API is available without building your own OAuth app. It is beta, so treat it as the escape hatch rather than the foundation. **How to check it worked:** - Create one prospect in Outreach and confirm the instant trigger fires in seconds rather than minutes. If it takes a quarter of an hour you have picked the polling trigger by mistake. - Run the enrolment Zap twice on the same prospect and watch what happens. It should be stopped by your filter; if the person is enrolled twice, the guard is not working and it will not announce itself later. - Check which Outreach user the connection authenticated as, in Outreach rather than in Zapier, because that is whose hourly allowance a backfill will spend. - Count the tasks one prospect costs end to end. Two steps is the floor for enrolment, and the number only goes up once filters and lookups are added. Agent skill for this pair: https://www.reversecontact.com/integrations-hub/skills/outreach-zapier.md **Field mapping:** - Create Prospect maps to A new Outreach prospect. First Name, Last Name and Email Addresses, plus Account ID, Opportunity IDs, Stage ID, Persona ID and Owner ID. Every one of those ids has to come from somewhere else in the Zap. - Find Sequence maps to A sequence, by name or id. The only search action, and the only place a human-readable name is resolved for you. Put it before any enrolment step. - Add Prospect to Sequence maps to An enrolment. Takes the prospect and the sequence. No duplicate check, so running it twice enrols twice. - API Request (Beta) maps to Any Outreach endpoint. A raw HTTP request carrying the integration's authentication. Beta, and the escape hatch when the four named actions do not cover the job. - New Prospect, New Call, Updated Task maps to A Zap, instantly. The instant triggers, carrying the Outreach record that changed. These are what let Outreach begin a chain rather than only receive one. - Completed Sequence Task maps to A Zap, within 15 minutes. Polling rather than instant, and scoped to one Sequence ID. The free plan checks every 15 minutes. - Does not cross: A new account or a new opportunity. Only the updated versions have triggers, so a first appearance has to be inferred. - Does not cross: Any duplicate protection on enrolment. Nothing in the integration knows whether a prospect is already in the sequence. - Does not cross: Sequence creation. Find Sequence reads sequences and nothing here writes one, so the sequence is always built in Outreach first. - Does not cross: The reply or the outcome. These triggers carry records and task completion rather than what a prospect said back, which stays in Outreach. **What breaks:** - **Only one trigger polls, and it is the one you want.** Five of the six triggers are instant. Completed Sequence Task is not: Zapier documents checking for new data every 15 minutes on the Free plan, and the trigger requires a Sequence ID, so it watches a single named sequence. That is the event most teams want for closed-loop reporting, which makes this the asymmetry to design around rather than discover. - **Enrolment is not idempotent.** Nothing in Add Prospect to Sequence checks whether the prospect is already enrolled. Run the same Zap twice, or let two Zaps overlap, and the same person is added again. Outreach's other integrations warn about the same thing in different words, which is why the directory's Clay page says to check before you push: the guard is always yours to build. - **The write actions want ids, not names.** Create Prospect takes Account ID, Opportunity IDs, Stage ID, Persona ID and Owner ID. None of those is a name you can type from memory, so a Zap that creates a prospect properly usually needs a lookup step first, and Find Sequence only resolves sequences. - **The rate limit is per user, which is good news.** Outreach allows 10,000 requests an hour and meters them per user rather than per organisation, so a Zap authenticated as its own service user does not spend the reps' allowance. Outreach reserves the right to change it. Connect this as a dedicated user rather than as whoever happened to set it up. - **The meter is per step.** Zapier charges a task per step rather than per Zap, so the Find Sequence plus Add Prospect to Sequence pattern costs two tasks per prospect before anything else in the chain. Over a list of a thousand that is two thousand tasks, which is the arithmetic that decides whether this belongs in Zapier or in something billed differently. - **No trigger for a new account or opportunity.** Updated Account and Updated Opportunity exist; their created counterparts do not. If a Zap needs to fire when an account first appears, it has to infer it from an update or watch the other side of the relationship, which is a workaround rather than a configuration. **Failures people hit:** - The same prospect got two first-touch emails. Why: Add Prospect to Sequence was run twice. The action has no duplicate protection and reports success both times. Fix: Put a filter or a lookup in front of the enrolment step and make the Zap stop when the prospect is already enrolled. Nothing in the integration will do this, so it is a design step rather than a setting. - A Zap that enrols people stopped working after somebody edited the sequence. Why: The Sequence ID was hard-coded and rebuilding a sequence changes it. Fix: Use Find Sequence to resolve the sequence by name and feed its output into the enrolment step. The name survives a rebuild and the id does not. - The trigger takes a quarter of an hour to fire. Why: It is Completed Sequence Task, the only polling trigger, which Zapier checks every 15 minutes on the Free plan. Fix: Accept the delay or redesign around an instant trigger. The other five are instant, so if the latency matters more than the specific event, one of them is usually close enough. - Create Prospect fails on a missing or invalid id. Why: The action takes Account ID, Opportunity IDs, Stage ID, Persona ID and Owner ID, and none of those accepts a name. Fix: Resolve the ids earlier in the Zap, from the record that triggered it or from a lookup. Find Sequence only resolves sequences, so everything else has to arrive already as an id. - A bulk run exhausted somebody's Outreach allowance. Why: Outreach meters 10,000 requests an hour per user, and the connection authenticated as a person rather than as a service account. Fix: Reconnect as a dedicated Outreach user so the Zaps have their own budget. This is much easier before Zaps depend on the connection than after. - The Zapier bill is far higher than the number of Zaps suggests. Why: The meter is per step. An enrolment is at least two steps, and a filter and a lookup make it four. Fix: Count rows multiplied by steps rather than Zaps, and consider batching or an orchestrator billed differently if the arithmetic does not work. The Zapier hub page has the same warning for every pair on it. **What practitioners say** (14 threads from January 2020 to July 2026, read 2026-10-28): Almost nobody writes about wiring these two together, so the search was the job instead: whether to glue a sequencer to the rest of the stack at all, and what the glue costs. Finding even this much needed a fix to the tooling, because "Outreach" is an ordinary English word and searching it returned threads about cold outreach as an activity rather than about the product. - The cost of glue is the maintenance, not the subscription (r/GrowthHacking, July 2026, 1 points): https://www.reddit.com/r/GrowthHacking/comments/1uouiov/the_hidden_cost_of_linkedin_outreach_nobody_talks/ - The spend is never the line item you budgeted (r/GrowthHacking, July 2026, 1 points): https://www.reddit.com/r/GrowthHacking/comments/1uouiov/the_hidden_cost_of_linkedin_outreach_nobody_talks/ - The first question is whether to stitch anything at all (r/gtmengineering, February 2026, 2 points): https://www.reddit.com/r/gtmengineering/comments/1qu621n/crm_recommendations_for_cold_outreach_pipeline/ - The same advice from the other direction (r/gtmengineering, March 2026, 2 points): https://www.reddit.com/r/gtmengineering/comments/1qu621n/crm_recommendations_for_cold_outreach_pipeline/ - Where a sequencer sits when the stack is assembled properly (r/sales, January 2020, 3 points): https://www.reddit.com/r/sales/comments/es84mq/whats_your_cold_email_outreach_stack/ Sources: https://zapier.com/apps/outreach/integrations | https://developers.outreach.io/api/getting-started | https://zapier.com/pricing ### LinkedIn Sales Navigator and Outreach Two tiles on Advanced Plus, and the LinkedIn steps are tasks a human does. - Built as: Native - Syncs: One way, out - Moves: Contacts, Companies, Tasks - Costs to turn on: Paid add-on or licence. Setup: Minutes - Requires: An Outreach contract and a Sales Navigator Advanced Plus licence for every user - Full guide: https://www.reversecontact.com/integrations-hub/linkedin-integrations/linkedin-outreach-integration **Verdict.** The most official LinkedIn integration an engagement tool has, and the narrowest. You get two embedded tiles that put Sales Navigator context next to the prospect in Outreach, and LinkedIn step types in sequences that create tasks for a rep to do by hand. What you do not get is automation: Outreach never sends a connection request or a message on your behalf, because LinkedIn does not permit that, and a tool that claims otherwise is operating outside the partner programme. The gate is Advanced Plus on every seat, which is the quoted edition, and that is the whole evaluation. **What syncs:** - Sales Navigator lead data (out): Into the Outreach prospect view as a tile: current position, time in role, location, Icebreakers, Get Introduced and Related Leads. - Sales Navigator account data (out): Industry, headcount and headquarters on the account tile, with Recommended Leads alongside. - Recommended leads (out): Added to Outreach straight from the account tile, which is the one place the integration creates an Outreach record. - LinkedIn sequence steps (in): View a profile, interact with a post, send a message, send a connection request, or other. Each is a task a human completes in LinkedIn. - Messages, InMails and connection requests (event): Never sent by Outreach. InMail opens LinkedIn in a separate tab from the tile's menu. - Saving a lead from the tile (in): Saves to Sales Navigator, not to Outreach. Outreach documents this because everybody assumes the opposite. **Which editions carry it** (rows LinkedIn Sales Navigator, columns Outreach): - Core with Any Outreach seat: No tiles - Advanced with Any Outreach seat: No tiles - Advanced Plus with Any Outreach seat: Both tiles and the task flow **How to connect it** (An Outreach admin to build the sequences, and whoever controls the Sales Navigator contract to supply Advanced Plus seats.. Short. The licence conversation is the project; the configuration is an afternoon.): 1. Confirm Advanced Plus on every seat that will use it [The Sales Navigator contract]. Outreach states it plainly and points at LinkedIn's own answer: a Sales Navigator Advanced Plus licence is required. This is per user, not per org, so a team on mixed licences gets a tile for some reps and nothing for others. 2. Add the two tiles to the prospect and account views [Outreach: the intelligence tile menu]. There are two, one for Sales Navigator Lead and one for Sales Navigator Account. They are the whole of the read side, and they are embedded LinkedIn rather than Outreach data. 3. Update the Salesforce plugin before you build sequences [Outreach: Salesforce plugin settings]. Outreach notes that the plugin needs updating for LinkedIn tasks to sync to Salesforce. Doing this after a month of sequences means a month of activity that never reached the CRM. 4. Add LinkedIn steps to a sequence [Outreach: a sequence, Add Step, Step Type]. The LinkedIn step types cover sending a connection request, viewing a profile, interacting with posted content and sending an InMail. They appear as tasks in the rep's queue. 5. Set the expectation that these are manual tasks [A conversation with the team]. Every LinkedIn step is a task a human performs. Nothing is automated on LinkedIn, which is a deliberate design rather than a missing feature, and a sequence planned as though it were automated will not be worked. **How to check it worked:** - Open a prospect and confirm both tiles render. If one is missing, check that seat's licence rather than the Outreach configuration. - Complete one LinkedIn task and check it reached Salesforce. That tests the plugin version, which nothing else will. - Click through from the tile to a profile deliberately once, so the team understands that is the action that notifies the prospect rather than opening the tile. - Try the save-as-lead button and look for the result in Outreach. It will not be there, and that is documented behaviour worth knowing before a rep reports it. Agent skill for this pair: https://www.reversecontact.com/integrations-hub/skills/linkedin-outreach.md **Field mapping:** - Sales Navigator lead data maps to The Lead tile in Outreach. Icebreakers, Get Introduced and Related Leads, rendered by LinkedIn inside an iframe rather than fetched by Outreach. - Sales Navigator account data maps to The Account tile. Recommended Leads, Connections and News, including recent posts from the company and its employees. - A LinkedIn action maps to An Outreach sequence step. Connection request, profile view, content interaction or InMail, each as a task in the rep queue. - A completed LinkedIn task maps to Salesforce activity. Only once the Outreach Salesforce plugin is current. Outreach calls this out as a note rather than a step, which is how it gets missed. - Save as a lead, from the tile maps to A Sales Navigator lead. Not an Outreach prospect. The button does what it says on LinkedIn's side and nothing on Outreach's. - Does not cross: Any automated action on LinkedIn. Every step is a task for a person. - Does not cross: A profile view from inside the tile. Outreach documents that reading the tile does not notify the prospect; clicking through to the profile does. - Does not cross: Attachments, context or anything else back into Sales Navigator. The flow is one way, into Outreach. **What breaks:** - **Advanced Plus on every seat, and the docs disagree.** Outreach's current minimum requirements and its FAQ both say Sales Navigator Advanced Plus, attributed to LinkedIn. An older launch page and a task-management article say Team or Enterprise. Price Advanced Plus, confirm with your LinkedIn representative, and note that this is per user: a tile that works for the person who set it up proves nothing about the rest of the team. - **The tile is LinkedIn's code in an iframe.** Outreach documents that the integration is an embedded iframe, so errors inside it, such as a CRM-not-connected message, are LinkedIn errors rather than Outreach ones and reproduce on Sales Navigator directly. Support tickets routinely go to the wrong vendor because of this. Check whether the same action fails in Sales Navigator before raising it with Outreach. - **Nothing on LinkedIn is automated.** Every LinkedIn step type creates a task. Outreach sends no connection requests, no messages and no InMails, and the InMail option in the tile opens LinkedIn in a new tab for you to send it yourself. Teams that model a sequence's capacity on email throughput and then add LinkedIn steps discover the real constraint is how many profiles a rep can work through in an afternoon. - **Saving a lead does not create a prospect.** The save-as-lead control inside the tile saves to Sales Navigator rather than creating an Outreach prospect, which Outreach documents explicitly. Only Recommended Leads on the account tile add to Outreach. If LinkedIn tasks are to reach your CRM at all, the Salesforce plugin has to be updated first, which is a separate step nobody expects. **Failures people hit:** - The tile shows an error such as CRM not connected. Why: The tile is an embedded LinkedIn iframe. Outreach states that these errors are usually LinkedIn's rather than theirs, and you would see the same thing in Sales Navigator directly. Fix: Reproduce it in Sales Navigator itself. If it happens there too, it is a LinkedIn support conversation and no Outreach setting will touch it. - The tile found the wrong person or company. Why: Matching picked an incorrect record. Fix: Expand the window and select Not the right person to unlink, then search for the correct match. - The tile found nobody at all. Why: No match, which is a normal outcome rather than a failure. Fix: Use the back button beside the not-found message to search for the individual or the company by hand. - A rep saved a lead and it never appeared in Outreach. Why: Save as a lead creates a lead in Sales Navigator, not a prospect in Outreach. Fix: Nothing to fix. Tell the team what the button does, because the label invites exactly this mistake. - LinkedIn activity is missing from Salesforce. Why: The Outreach Salesforce plugin is out of date, which is what syncs LinkedIn tasks across. Fix: Update the plugin. The tasks already completed will not retroactively appear, so do this before the first sequence rather than after the first report. - You cannot scroll inside the tile. Why: There are no scrollbars in the embedded view. Fix: Use the arrow keys on each tab and line item to move horizontally. This is documented, and it is the kind of thing a rep reports as broken for months. **What practitioners say** (14 threads from 2022 to 2026, read 2026-10-11): Nobody writes about configuring this pair, so the search was for the job: how teams actually use Sales Navigator alongside a sequencer. The recurring theme is that the licence arrives before the method does. People are given the tool, get one training session, and then ask strangers how to use it, while the answers that get upvoted are all workflow rather than feature. - The licence usually lands before anybody knows what to do with it (r/sales, July 2023, 17 points): https://www.reddit.com/r/sales/comments/153339q/how_do_you_all_use_linkedin_sales_navigator/ - The upvoted answers are all method, not features (r/sales, July 2023, 18 points): https://www.reddit.com/r/sales/comments/153339q/how_do_you_all_use_linkedin_sales_navigator/ - The stack people describe is exactly this pair plus a data source (r/sales, May 2023, 6 points): https://www.reddit.com/r/sales/comments/139b800/its_my_first_sales_job_i_have_zoominfo_salesforce/ - Sales Navigator is a finder, and people expect more (r/sales, July 2023, 6 points): https://www.reddit.com/r/sales/comments/153339q/how_do_you_all_use_linkedin_sales_navigator/ - The fastest route to a method is the person down the corridor (r/sales, May 2023, 16 points): https://www.reddit.com/r/sales/comments/139b800/its_my_first_sales_job_i_have_zoominfo_salesforce/ Sources: https://support.outreach.io/support/solutions/articles/159000425576-linkedin-sales-navigator-tiles-task-flow-overview | https://support.outreach.io/support/solutions/articles/159000426111-linkedin-sales-navigator-outreach-faq | https://support.outreach.io/support/solutions/articles/159000425747 | https://business.linkedin.com/sales-solutions/partners/find-a-partner/outreach ### LinkedIn Sales Navigator and Zapier No triggers at all, so nothing on LinkedIn can ever start a Zap. - Built as: Zapier, Make or n8n, Marketplace app - Syncs: One way, in - Moves: Messages - Costs to turn on: Metered by usage. Setup: Minutes - Requires: A Zapier plan, a LinkedIn account, and page admin rights for company posts - Full guide: https://www.reversecontact.com/integrations-hub/linkedin-integrations/linkedin-zapier-integration **Verdict.** Worth reading before you plan anything, because the headline is a negative. The LinkedIn app on Zapier has no triggers at all: Zapier documents it, and it means no LinkedIn event can ever start an automation. What you get is three actions that publish, two of them posting to a personal profile or a company page you administer and one raw API request for anything else. As a publishing integration it is fine and cheap; as the prospecting integration almost everybody is looking for, it does not exist, and the reason is LinkedIn's partner programme rather than Zapier's roadmap. **What syncs:** - A post on your profile (in): Create Share Update, with text, links, images and visibility settings, fired by a trigger in some other app. - A post on a company page (in): Create Company Update, including mentions and link previews. Only on pages where you are an administrator. - Any other API call (in): API Request, in beta, sends a raw authenticated HTTP request. Bounded by whatever permissions your LinkedIn app actually holds. - Anything out of LinkedIn (out): Nothing. There are no triggers and no search actions, so a Zap can write to LinkedIn and can never read from it. **Which editions carry it** (rows LinkedIn Sales Navigator, columns Zapier): - Any LinkedIn account with Post to your profile: Available - Any LinkedIn account with Post to a company page: Needs the admin role - Any LinkedIn account with React to a LinkedIn event: Does not exist - Company page administrator with Post to your profile: Available - Company page administrator with Post to a company page: Available - Company page administrator with React to a LinkedIn event: Does not exist **How to connect it** (Whoever owns the LinkedIn account. For company posts, somebody with an administrator role on the page.. Two minutes, and the useful work is deciding whether to bother.): 1. Check what you are expecting it to do [Zapier: the LinkedIn app page]. Zapier lists no triggers and no search actions for LinkedIn. That is not a plan limitation or a step you have missed. Nothing on LinkedIn can start a Zap and nothing can be looked up, so any workflow that begins with a LinkedIn event has to begin somewhere else. 2. Confirm your page role if you want company posts [LinkedIn: company page admin settings]. The Create Company Update action requires you to be an administrator of that page. A personal share update does not. 3. Add the connection [Zapier: Apps, Add connection]. Search for LinkedIn, authenticate, grant access. There is no org-level approval and no app review, because the surface being used is small. 4. Build the Zap with LinkedIn at the end [The Zap editor]. LinkedIn can only be an action step. The trigger will be a schedule, a form, a spreadsheet row or an RSS feed, and LinkedIn is where the Zap finishes. 5. Set visibility on each share deliberately [The Create Share Update action]. The action takes text, URLs and images and carries visibility settings. A scheduled post is the one place a wrong visibility setting runs for months without anybody noticing. **How to check it worked:** - Look for a LinkedIn trigger in the Zap editor. Confirming the absence yourself is worth more than reading it here. - Post one share update and check it appears with the visibility you set. - If you are posting to a company page, have somebody without the admin role try it and watch it fail, so the dependency is known before a handover. Agent skill for this pair: https://www.reversecontact.com/integrations-hub/skills/linkedin-zapier.md **Field mapping:** - A Zap step maps to A share update on your profile. Text, URLs and images, with visibility settings on the action. - A Zap step maps to An update on a company page. Requires an administrator role on that page. - Does not cross: Any trigger. Zapier documents that no triggers are available for LinkedIn, so nothing happening on LinkedIn can start a workflow. - Does not cross: Any search action. There is no lookup, so a Zap cannot find a person, a company or a post. - Does not cross: Anything inbound at all. Profile data, connections, messages and engagement are outside this integration entirely. **What breaks:** - **No triggers, which rules out most of the use cases.** Zapier's own documentation says no triggers are available for LinkedIn. New connections, messages, comments and profile views cannot start a Zap. Any design that begins "when someone connects with me on LinkedIn" is impossible here, and the workaround people reach for, scraping their own inbox with an extension, is the category LinkedIn's user agreement prohibits. - **Company posts need a page admin role.** Create Company Update works only where you are an administrator of the page. That is a LinkedIn permission rather than a Zapier one, so the person building the automation often cannot test it, and the fix lives with whoever owns the company page. - **LinkedIn's rate limits apply and are not published.** Zapier notes that LinkedIn's rate limits may affect high-volume workflows and that its pagination limits apply to API requests. LinkedIn sets those limits per endpoint, resets them at midnight UTC and does not publish the standard figures, so the only way to know yours is the Developer Portal or a 429. A posting cadence worth automating is rarely near them; a bulk job would be. - **A premium-sounding app on a metered plan.** Zapier charges per successful action, so the cost is the posting volume rather than the connection. Nothing on the LinkedIn side costs money. The thing to watch is that a Zap which cannot be triggered by LinkedIn will be triggered by something chattier, and the task count follows that trigger rather than your posting schedule. **Failures people hit:** - There is no LinkedIn trigger in the dropdown. Why: There are none. Zapier documents that no triggers are available for LinkedIn. Fix: Trigger the Zap from somewhere else. If the LinkedIn event itself is what you need, this integration cannot provide it. - You cannot look up a person or a company. Why: No search actions are available either. Fix: Use a data provider with an API for the lookup and keep Zapier for the posting step. - The company update action fails. Why: You are not an administrator of the page. Fix: Get the role, or post from the profile instead. This is a LinkedIn permission rather than a Zapier one. - Posts stop going out for no visible reason. Why: LinkedIn applies rate limits to its APIs and does not publish numbers for this surface. Fix: Space the posts out and treat the schedule as a budget. There is no figure to design against, which is itself the answer. **What practitioners say** (14 threads from 2021 to 2026, read 2026-10-11): Nobody discusses this pair, because there is little to discuss. What people discuss is the job they hoped it would do, which is getting LinkedIn data into another system automatically. The answers have been consistent for years: LinkedIn closed those routes, and the alternative is a data provider with an API or the licensed CRM integration. - The access people are looking for was closed years ago (r/salesforce, May 2025, 7 points): https://www.reddit.com/r/salesforce/comments/1ktbscr/api_linkedinsalesforce/ - The volume that sends people looking is real (r/salesforce, May 2025, 7 points): https://www.reddit.com/r/salesforce/comments/1ktbscr/api_linkedinsalesforce/ - The licensed route is what people end up buying (r/salesforce, May 2021, 4 points): https://www.reddit.com/r/salesforce/comments/n91l6w/sales_navigator_integration_with_salesforce_is_it/ - Scraping gets suggested, and it is worth naming as such (r/salesforce, May 2025, 5 points): https://www.reddit.com/r/salesforce/comments/1ktbscr/api_linkedinsalesforce/ - Five years of the same question in different words (r/salesforce, May 2021, 14 points): https://www.reddit.com/r/salesforce/comments/n91l6w/sales_navigator_integration_with_salesforce_is_it/ Sources: https://help.zapier.com/hc/en-us/articles/8495987891853-How-to-get-started-with-LinkedIn-on-Zapier | https://learn.microsoft.com/en-us/linkedin/shared/api-guide/concepts/rate-limits | https://learn.microsoft.com/en-us/linkedin/shared/authentication/getting-access ### LinkedIn Sales Navigator and n8n One resource, one operation: create a post. That is the whole node. - Built as: Zapier, Make or n8n, Built on the API - Syncs: One way, in - Moves: Messages - Costs to turn on: Metered by usage. Setup: Minutes - Requires: An n8n instance and a LinkedIn app. Company posts need the organisation URN. - Full guide: https://www.reversecontact.com/integrations-hub/linkedin-integrations/linkedin-n8n-integration **Verdict.** The smallest node in this directory and the one whose size is the most informative. One resource, one operation, create a post, as a person or as an organisation. That is not n8n being lazy: LinkedIn restricts everything interesting to approved Sales Navigator partners and is not taking new ones, so publishing is all that is available through self-serve permissions. Read this page as a map of what LinkedIn allows rather than as a feature list, and if the job is getting LinkedIn data into a system, the answer is a different provider and no LinkedIn dependency at all. **What syncs:** - A post as a person (in): Create, with the person name or id, the post text, and a media category when the post carries an image or an article URL. - A post as an organisation (in): Same operation with an organisation URN, entered as the bare number rather than the full urn:li:company: form. - Anything else LinkedIn exposes (in): The HTTP Request node on the same credential, bounded by the permissions your LinkedIn app holds, which for most accounts is publishing only. - Anything out of LinkedIn (out): Nothing. There is no read operation and no trigger node, so a workflow can publish and can never listen. **Which editions carry it** (rows n8n, columns LinkedIn Sales Navigator): - OAuth2 with Yourself, as a member: self-service - OAuth2 with Your company page, as the organisation: not available - Community Management OAuth2 with Yourself, as a member: self-service - Community Management OAuth2 with Your company page, as the organisation: only after App Review **How to connect it** (Whoever runs n8n, plus an admin on the LinkedIn Company Page you want to post as. The page is a prerequisite rather than an option.. Half an hour to post as yourself. Weeks if you need to post as the organisation, because that waits on a LinkedIn review.): 1. Decide whether you are posting as a person or as a page [Design, before the developer portal]. Posting as yourself uses an open permission and is live the same afternoon. Posting as an organisation requests w_organization_social, and n8n states plainly that it requires LinkedIn's Community Management App Review. That is the whole difficulty of this pair in one decision. 2. Create the developer app against a Company Page [LinkedIn Developer Portal: create app]. A LinkedIn account is not enough: the app has to be associated with a Company Page, and you can create one during this step if you do not have it. Add a logo, accept the legal agreement, and create the app. 3. Request the products rather than hunting for scopes [LinkedIn: the app's Products tab]. Share on LinkedIn and Sign In with LinkedIn using OpenID Connect are the two self-service products, and they carry w_member_social, profile and email. Add the Advertising API only if you are acting as an organisation. These are the permissions LinkedIn calls open, and they are the only ones available without approval. 4. Pick the credential type that matches your app's age [n8n: LinkedIn credential]. n8n offers Community Management OAuth2 for new accounts and new apps, and plain OAuth2 for older ones. The Legacy option exists to request r_liteprofile and r_emailaddress instead of profile and email, which is for apps created before LinkedIn moved to OpenID Connect. 5. Copy the Client ID and the Primary Client Secret [LinkedIn: the app's Auth tab]. Both go straight into the n8n credential. On n8n Cloud you can use Connect my account and authenticate in the browser instead; self-hosted has to create the developer app either way. 6. Enter the organisation URN as a bare number [n8n: the LinkedIn node, Organization URN]. n8n documents this with an example: 03262013 rather than urn:li:company:03262013. The full form is what LinkedIn shows you everywhere else, which is why this is the most common failure on a node with one operation. 7. Look up your own rate limits, because they are not published [LinkedIn Developer Portal: the app's Analytics tab]. LinkedIn states that standard rate limits are not in the documentation and that the Analytics page shows only endpoints you have called today in UTC. To see a limit for an endpoint that is not listed, make one test call and refresh the page. 8. Accept that nothing can start from LinkedIn [Design, again]. There is no LinkedIn trigger node and no read operation, so a schedule, a webhook from somewhere else, or an approval step has to be what starts the workflow. Any architecture that begins with a LinkedIn event has to be redesigned rather than debugged. **How to check it worked:** - Post once as a person before requesting anything else. If that works, the credential is correct and every remaining problem is a permission rather than a configuration. - Post once as the organisation with the bare number in the URN field. The failure mode for the full urn:li:company: form does not mention the format, so prove this before building on it. - Make one call to each endpoint you plan to use, then open the app's Analytics tab. That is the only documented way to see your own limits, and it has to be done inside the same UTC day. - Check who receives the Developer Admin email alerts. They fire at 75% of quota, only on application-level breaches, and one to two hours late, so the person who gets them needs to be somebody who will act. Agent skill for this pair: https://www.reversecontact.com/integrations-hub/skills/linkedin-n8n.md **Field mapping:** - Post As maps to Person or Organization. The only genuine fork in the node. Organization is the half that needs App Review, and the parameter will happily be set before the review is granted. - Person Name or ID maps to An identifier for the member. Covered by w_member_social, which LinkedIn lists as an open permission: post, comment and like on behalf of an authenticated member. - Organization URN maps to The organisation number, bare. 03262013 rather than urn:li:company:03262013, in n8n's own example. The full form is what the rest of LinkedIn shows you. - Text maps to The post contents. The whole payload. There is no scheduling parameter, so a posting time is a Schedule Trigger in the workflow rather than a field here. - Media Category maps to For images or article URLs. Used when the post carries media rather than being a parameter you always set. Plain text posts leave it alone. - Anything else LinkedIn exposes maps to HTTP Request node, same credential. The documented escape hatch, and the narrowest one in this directory: it reaches only what your app is approved for, which for a self-service app is publishing. - Sales Navigator data maps to Not available without partnership. r_sales_nav_profiles, r_sales_nav_display, r_sales_nav_validation and r_sales_nav_analytics all require approval as a Sales Navigator Application Platform partner. - Lead Gen Form submissions maps to r_marketing_leadgen_automation, applied for separately. n8n names the scope for its Lead Sync setup and states it needs separate Lead Sync API access. It is not part of the two self-service products. - Does not cross: Any read of another member. The three open permissions describe the authenticated member only, which is why no self-service app can turn a profile URL into a person. - Does not cross: Any event. There is no trigger node and LinkedIn exposes no webhook through these permissions, so nothing on LinkedIn can start a workflow. - Does not cross: Comments and likes at scale, even though w_member_social permits them. The node has no operation for either, so they go through raw HTTP and into the rate limits you cannot see. **What breaks:** - **One operation, and no trigger.** The node creates posts and does nothing else, and there is no LinkedIn trigger node, so no LinkedIn event can start a workflow. Every design that begins with something happening on LinkedIn has to start somewhere else. That is a hard boundary rather than a gap to work around, and it is worth establishing before anybody sketches an architecture. - **The organisation URN must be a bare number.** n8n documents entering 03262013 rather than urn:li:company:03262013 for organisation posts. Supplying the full URN is the usual first attempt because it is what LinkedIn shows you elsewhere, and the resulting error does not point at the format. - **The permissions ceiling is LinkedIn's, not n8n's.** The HTTP Request escape hatch only reaches what your LinkedIn application is approved for. Sales permissions, covering profiles, display, validation and analytics, need Sales Navigator Application Platform approval, and LinkedIn states it is not currently accepting new partners. So the escape hatch is narrower here than on any other node in this directory. - **Rate limits exist and are not published.** LinkedIn applies limits per endpoint with both application-level and per-member ceilings, resets them at midnight UTC, and does not publish the standard figures. You find yours in the Developer Portal's analytics or by receiving a 429, and the warning email at 75% of quota arrives one to two hours late by LinkedIn's own documentation. **Failures people hit:** - The organisation post fails and the error says nothing about the URN. Why: The full urn:li:company:03262013 form was entered where n8n documents the bare number 03262013. Fix: Strip it to the number. Test this on its own rather than inside a workflow, because it is the single most likely cause of a failing organisation post. - Posting as the organisation is refused although the scope is ticked. Why: w_organization_social needs LinkedIn's Community Management App Review completed. Requesting the scope and passing the review are two different things. Fix: Submit the review, and post as a member in the meantime. There is no configuration that substitutes for it. - The app cannot be created at all. Why: A LinkedIn Company Page is a prerequisite for a developer app, not an optional association. Fix: Create the page during app creation, which LinkedIn allows. A personal account with no page cannot complete the step. - The credential authorises but the profile call returns nothing. Why: An older app may be issuing r_liteprofile and r_emailaddress where the newer products issue profile and email. The two sets are not interchangeable. Fix: Turn on the Legacy option in the n8n credential for an older app, or recreate the app with Sign In with LinkedIn using OpenID Connect for a new one. - 429 responses with no idea what the limit was. Why: LinkedIn does not publish standard rate limits. There are two ceilings, one for the application and one per member per application, and both reset at midnight UTC. Fix: Open the app's Analytics tab in the Developer Portal, which lists limits only for endpoints you have called today in UTC. For an endpoint that is not listed, make one test call and refresh. - A 429 arrived although usage looked fine. Why: LinkedIn documents returning 429 in rare cases as infrastructure protection rather than as a quota breach, and says service returns to normal automatically. Fix: Retry with a backoff rather than redesigning. If it persists across a day, it is a quota rather than protection. - The quota warning email arrived after the workflow had already failed. Why: Alerts fire at 75% of quota with an expected delay of one to two hours, and only on application-level breaches rather than member-level ones. Fix: Do not use the email as a control. Instrument the workflow's own error branch, because a member-level breach never generates an alert at all. - A workflow was supposed to start when something happened on LinkedIn. Why: There is no LinkedIn trigger node and no read operation. Nothing on LinkedIn can start an n8n workflow through the sanctioned route. Fix: Start the workflow from a schedule, a CRM event or a form, and treat LinkedIn as a destination. A design that needs the other direction needs a different data source rather than a different tool. **What practitioners say** (14 threads from 2023 to 2026, read 2026-10-11): Almost nobody in these threads is using the LinkedIn node. They are using n8n to scrape LinkedIn, and the threads are an argument about whether that works and whether it is allowed. Two answers recur and they are worth reading together: the terms of service prohibit it and accounts get flagged, and the Google-search workaround people reach for instead returns only what Google indexes, which is a headline rather than a profile. The one architectural question in the set is about something else entirely, and it is the best comment of the fourteen. - The thing people actually want is against the terms, and they get flagged for it (r/automation, November 2025, 2 points): https://www.reddit.com/r/automation/comments/1ozd9ph/looking_for_help_automating_linkedin_sales/ - The Google-search workaround is the one people reach for (r/n8n, June 2025, 2 points): https://www.reddit.com/r/n8n/comments/1lgd566/automated_linkedin_lead_scraping_with_n8n_google/ - And it returns a headline rather than a profile (r/n8n, June 2025, 2 points): https://www.reddit.com/r/n8n/comments/1lgd566/automated_linkedin_lead_scraping_with_n8n_google/ - Pacing a workflow to dodge limits moves the problem into n8n (r/n8n, January 2026, 6 points): https://www.reddit.com/r/n8n/comments/1qq7wf4/my_competitors_viral_post_just_became_my_lead/ - Practitioners describe LinkedIn as actively hostile to the whole idea (r/hubspot, January 2026, 3 points): https://www.reddit.com/r/hubspot/comments/1qdrkh5/does_a_good_linkedin_hubspot_integration_exist/ Sources: https://docs.n8n.io/integrations/builtin/app-nodes/n8n-nodes-base.linkedin | https://docs.n8n.io/integrations/builtin/credentials/linkedin | https://learn.microsoft.com/en-us/linkedin/shared/authentication/getting-access | https://learn.microsoft.com/en-us/linkedin/shared/api-guide/concepts/rate-limits ## Workflows ### Inbound speed to lead A form submission enriched, scored, routed and announced in Slack before the visitor closes the tab. - Uses: HubSpot, Reverse Contact, Slack - Build effort: Hours - Page: https://www.reversecontact.com/integrations-hub/workflows/inbound-speed-to-lead - Agent skill: https://www.reversecontact.com/integrations-hub/skills/inbound-speed-to-lead.md **Steps:** 1. **A form submission creates or updates a contact** HubSpot forms on any tier, including free. This is the trigger, and the only part that has to be HubSpot. 2. **The email goes to Reverse Contact** A single POST to the enrich endpoint. Use the cached endpoint here, not the live one: live resolution returns a task to poll, and neither a CRM workflow nor a speed-to-lead path should wait for it. 3. **The record comes back, or it does not** Title, current company, headcount, location, profile URL and a confidence score. A miss returns null rather than a guess, which is what lets the next step branch honestly instead of scoring a fabricated title. 4. **Write to rc_ properties, never to the rep fields** Every value lands in its own property. A second workflow promotes a value to the field people trust only where that field is empty. This is the step teams skip and the reason pipelines get switched off in month three. 5. **Score and route from the enriched fields** Owner assignment from headcount and title rather than from what the visitor typed into a company-size dropdown. This is the actual payoff: routing that does not depend on prospect honesty. 6. **Slack tells the owner, by name** One channel, one trigger, the owner mentioned by name, the enriched context in the message and a link to the record. Not every submission: only the ones above the score threshold. **What will bite:** - **The Slack message cannot follow the record.** HubSpot's Slack workflow action sends to a channel chosen at design time. There is no built-in option to send to the channel associated with the record that triggered it. For this workflow that is fine, because one channel with one owner is the correct design anyway. It becomes a problem the moment somebody asks for per-segment routing, and at that point it is an hour of work in n8n rather than a setting. - **Enrichment on creation writes to your CRM.** This is the whole point and it is also the risk. Anything pointed at a property a human maintains will eventually overwrite something correct with something plausible. The prefix convention and a promote-only-if-empty workflow cost an afternoon and remove the entire class of problem. - **A miss is a real outcome, so handle it.** Reverse Contact returns null with a confidence score rather than a best guess, which is the behaviour you want and only useful if the next step branches on it. Decide in advance what an unresolved lead does: route to a general queue, flag for review, or fall through to a second provider. Doing nothing means those leads silently score zero. - **The alert degrades faster than the pipeline.** Enrichment will keep working for years. The Slack channel will get noisy within a month if the threshold is set generously, and a muted channel looks exactly like a working one from the admin screen. Set the threshold high, review it once a quarter, and send everything below it to a digest. ### The CRM data layer Stop maintaining records by hand. A scheduled loop that fills gaps, respects what reps own and never overwrites a human. - Uses: HubSpot, Clay, Reverse Contact, n8n - Build effort: Days - Page: https://www.reversecontact.com/integrations-hub/workflows/crm-data-layer - Agent skill: https://www.reversecontact.com/integrations-hub/skills/crm-data-layer.md **Steps:** 1. **Read a filtered slice, never the whole portal** A Clay Lookup action pulls only the records missing something: contacts with no title, companies with no employee count, anything not touched in 12 months. Read-only, so nothing in the CRM changes yet. 2. **Reverse Contact fills the gaps** An HTTP API column posts each row's email or domain to the enrich endpoint. Ten minutes to configure, and it works identically for any provider with an API, which is the point of doing it here. 3. **A miss falls through, it does not guess** Null with a confidence score rather than a plausible-looking answer. A conditional run sends only the still-empty rows to a second provider, so the expensive source only ever touches the residue. 4. **Write back to prefixed properties, blanks ignored** Clay's Update action with "ignore blank values" on and an explicit exclusion list for the fields reps maintain. Test on ten rows and open them in the CRM before this ever runs at volume. 5. **Promote, then schedule** A CRM workflow copies the enriched title into the field people trust only where that field is empty. Then auto-update on a weekly cadence, and the backfill becomes a data layer. **What will bite:** - **Clay bills the attempt, not the result.** An action is consumed whether or not anything comes back, so your effective cost per filled field is the action rate divided by your match rate. On a hard segment that multiplier is three or four. This is the single biggest driver of the bill and it is entirely controlled by how tightly you filter the slice you import. - **A write is immediately live to everyone.** There is no staging environment between a Clay Update and your reps. Ten rows, opened by hand in the CRM, before anything is scheduled. Every unpleasant version of this story starts with somebody skipping that step because the columns looked right. - **Importing the whole portal is the classic mistake.** It spends actions on rows that needed nothing, makes the write step far more dangerous, and produces a bill that bears no relation to the value delivered. Filter to the gap, always. - **Nobody publishes a match rate you can hold them to.** Including Reverse Contact, whose 70%+ identity match rate is a global figure rather than a promise about your list. Run 500 of your own rows and count. That number, not anyone's marketing, is what predicts both your coverage and your bill. - **The refresh cadence is a decision, not a default.** Weekly is right for an active pipeline and wasteful for a dormant database. Pick the cadence from how fast the field actually goes stale: job titles move quarterly, headcount annually, and email addresses somewhere in between. ### Signal to sequenced contact A Sales Navigator search becomes an enriched, deduplicated, CRM-checked list in a live campaign. - Uses: LinkedIn Sales Navigator, Clay, Reverse Contact, HubSpot, Smartlead - Build effort: Days - Page: https://www.reversecontact.com/integrations-hub/workflows/outbound-list-build - Agent skill: https://www.reversecontact.com/integrations-hub/skills/outbound-list-build.md **Steps:** 1. **A saved search defines the segment** Sales Navigator filters are the most precise targeting most teams have access to. Save the search rather than exporting it, so the definition lives somewhere reviewable instead of in a filename. 2. **Rows land in a Clay table** The table is the workbench for everything that follows: enrichment, the CRM check, the conditional branches and the push to the sender. Nothing leaves it as a file. 3. **Reverse Contact resolves each row** Profile URL or email in, a structured record out: current role, company, headcount, location, confidence. This is what turns a list of names into a list you can write a first line for. 4. **The CRM check, which is the whole point** A Lookup against every row. Already a customer, already an open deal, already contacted in 90 days, already owned by another rep: each one is a suppression rule, cheap to write and expensive to omit. 5. **Survivors go to the CRM and to the sender** Create the contact so the CRM knows this person is in a sequence, then push to the campaign. Smartlead's webhooks fire on every reply and bounce, so the timeline stays honest without a second sync. **What will bite:** - **Sales Navigator's terms are the real constraint.** Not the tooling. What your contract permits regarding extraction from search results is a question to answer before the build rather than after, and it is not one a directory can answer for you. - **Every enrichment column multiplies the bill.** Clay bills per action on the attempt. Four enrichment columns across a 5,000-row list is 20,000 actions before anything resolves. Order them cheapest-first with conditional runs, so the expensive source only sees the residue. - **The CRM check needs complete activity data.** "Contacted in the last 90 days" is only true if every channel logs to the CRM. If your reps' InMails live in Sales Navigator and never reach the CRM, this rule is quietly lying to you, which is an argument for CRM Sync or against the rule. - **Creating CRM records from a prospecting list is a decision.** Push every sequenced contact into the CRM and the database fills with people who never replied. Push none and your suppression rules have nothing to read next quarter. Most teams create the record and mark it clearly, which is the right trade as long as the marking is consistent. - **Smartlead's entry price comes off a slider.** The $39 figure is the bottom of it. Confirm the tier against your own mailbox count and send volume rather than budgeting from the headline. ### Agent-written account briefs Two MCP servers, no pipeline. An agent researches the account and writes the brief onto the record. - Uses: Reverse Contact, HubSpot, Slack - Build effort: Hours - Page: https://www.reversecontact.com/integrations-hub/workflows/agent-account-briefs - Agent skill: https://www.reversecontact.com/integrations-hub/skills/agent-account-briefs.md **Steps:** 1. **Add the Reverse Contact MCP server** Point the client at the MCP endpoint. OAuth 2.1 where the client supports it, otherwise an Authorization header with your API key. Thirty-seven tools arrive by their own count, 36 of them in its tables: enrich and search for people and companies, the live variants, the search filter catalogues, asynchronous email and phone lookups that return a task id to poll, Lists, Bulk, tasks and goals, and free checks on a profile, your usage and a running task. A company domain now goes straight in through enrich_company, which it did not before November 2026. 2. **Add the CRM's own connector** HubSpot publishes a connector for Claude that sits at 184,000 installs on its marketplace, which makes it one of the most-installed apps HubSpot lists. It reads and writes CRM records under your own permissions. 3. **Write the prompt once, reuse it** Name the account, say which fields to pull, say what the brief should contain, and say explicitly what to do when the data is missing. The last instruction is the one that decides whether this is useful or dangerous. 4. **The agent writes the brief onto the record** A note on the company record, so it is where the rep already looks rather than in a chat log. Optionally a Slack message to the owner, which is the same restraint rule as everywhere else: one channel, one trigger, one owner. **What will bite:** - **An agent will fill a gap unless told not to.** This is the whole risk and it is entirely addressable in the prompt. Tools that return null are doing the right thing; a model that treats a null as an invitation to estimate is not. Test it by asking for a brief on a company you know is thinly covered and checking what it says about headcount. - **It writes to your CRM under your permissions.** Which is convenient and means the blast radius is whatever you can do. Start it on notes rather than on properties. A note is additive and reviewable; a property write is a change to a field somebody else depends on. - **Credits are consumed per call, invisibly.** An agent exploring an account may make several enrichment calls where a pipeline would make one. The usage-check tool exists for exactly this, and it is worth asking for a figure after the first week rather than at the end of the month. - **The live tools are asynchronous here too.** The live variants return a task that the task-check tool polls. That works fine in an agent loop and it is slower than the cached variants. Use live only when freshness is the reason you are doing this at all. - **It does not scale to a list.** One account at a time is the shape. If the job is 5,000 accounts on a schedule, that is a pipeline and it belongs in the CRM data layer. Using an agent for that is slower, less predictable and more expensive. ### Closed won to delivery The deal closes and the work starts itself, with the terms attached and nobody retyping a thing. - Uses: HubSpot, ClickUp, Slack - Build effort: Hours - Page: https://www.reversecontact.com/integrations-hub/workflows/closed-won-handover - Agent skill: https://www.reversecontact.com/integrations-hub/skills/closed-won-handover.md **Steps:** 1. **A deal reaches closed won** The trigger. A deal-based HubSpot workflow, which means Professional for a fully customisable one; Starter covers this with one of its 50 simple workflows if the logic stays simple. 2. **ClickUp creates the delivery work** A ClickUp action inside the HubSpot workflow. Create a list from a template, or a task per line item, with the deal context attached rather than summarised. 3. **The line items travel with it** What was sold goes across, not just the deal name. This is the whole point of doing it properly: the delivery team should not have to open the CRM to find out what the customer bought. 4. **Slack tells the delivery team once** One message, to the channel that owns onboarding, naming the account and linking both records. Not a message per task, which is how this becomes noise inside a fortnight. 5. **Work status reports back to the deal** A ClickUp automation updates the HubSpot record when delivery moves. This is the direction teams forget to build, and it is what stops the CRM going stale the moment the deal closes. **What will bite:** - **Custom fields are the ceiling.** The native integration covers common objects well. Workflows that depend on custom fields are where teams move to Make, which has fuller custom-field support on the ClickUp side. Check your specific fields before you design around the native path. - **The automated half needs Professional.** Manual linking works lower down, but "when a deal closes, do this" is a workflow, and fully customisable workflows start at HubSpot Professional. On Starter you get up to 50 simple workflows and should check yours fits inside one. - **Two automation engines, two places to debug.** Half the logic lives in HubSpot workflows and half in ClickUp automations. That is the price of both directions being native. Write down which side owns which rule before you build the second one. - **Writing to the same field from both sides is a loop.** One rule per direction. HubSpot owns "a deal changed, create or update work"; ClickUp owns "work changed, update the deal". The moment both write to the same field on the same event you have built a loop, and loops between two automation engines are unpleasant to unpick. ### Champion job-change alerts Your best customer contact starts somewhere new. That is a warm pipeline nobody is watching. - Uses: HubSpot, Reverse Contact, Slack - Build effort: Hours - Page: https://www.reversecontact.com/integrations-hub/workflows/champion-job-change - Agent skill: https://www.reversecontact.com/integrations-hub/skills/champion-job-change.md **Steps:** 1. **Build the champion list** A CRM list of contacts on closed-won deals, plus lost deals where the contact was an advocate. Keep it to hundreds rather than thousands: this is a precision play, not a coverage one. 2. **Re-resolve each contact monthly** Reverse Contact returns current role and company against the identity you already hold, with a last-updated timestamp on every response so you can tell fresh data from cached. 3. **Compare to what the CRM believes** Company changed, title changed, or both. The comparison is the workflow: the enrichment is only interesting where it disagrees with the record you already have. 4. **Confidence decides whether it is real** A low-confidence answer is not a job change, it is a maybe. Set a threshold, and send anything under it to a review queue rather than to a rep. Reverse Contact lets you raise the precision threshold on the request itself. 5. **Create the new-company record and alert** A new contact at the new company, linked to the old one so the history is visible, and one Slack message to the account owner naming both. This is the part that turns a data point into pipeline. **What will bite:** - **The old record must not be overwritten.** A job change means creating a record at the new company, not editing the old one. Overwrite the original and you lose the deal history that made this person worth watching, which is the only asset the play depends on. - **Detection is not instant, and should not be.** Profile data reflects a move when the move becomes public, which is days to weeks after it happens. A monthly sweep catches it in time to act. A daily sweep costs twelve times as much to catch the same moves a fortnight earlier. - **A low-confidence match is worse than no match.** Alerting a rep that a champion moved, when they did not, burns the credibility of every future alert. Set the threshold high, review the queue monthly, and accept that you will miss a few rather than sending one wrong. - **Somebody has to own the follow-up.** This workflow produces a small number of high-value alerts, which is exactly the kind that gets admired and not actioned. Assign the alert to a named owner with a next step, or it becomes a monthly report nobody reads. ### Deduplication and identity resolution Four records for one person, and every report quietly counting them as four. - Uses: HubSpot, Reverse Contact, n8n - Build effort: Days - Page: https://www.reversecontact.com/integrations-hub/workflows/crm-deduplication - Agent skill: https://www.reversecontact.com/integrations-hub/skills/crm-deduplication.md **Steps:** 1. **Find the candidate clusters** Group records that might be the same person: same email domain and surname, same profile URL, same normalised name at the same company. This is the cheap, local step and it narrows what you pay to resolve. 2. **Resolve each record to an identity** Reverse Contact turns an email, a name and company, or a profile URL into a canonical record. Two CRM rows resolving to the same identity is a much stronger signal than two rows with similar names. 3. **Read the confidence, not just the match** A miss returns null with a confidence score rather than a guess, and the precision threshold can be raised on the request. Below your threshold, nothing merges: the pair goes to a review queue instead. 4. **Dry run, and have a human read it** Report-only mode. Export the proposed merges with both records side by side and the confidence attached. A hundred rows read by somebody who knows the accounts will find the pattern your rules got wrong. 5. **Merge on the rules you wrote down** Which record survives, which fields win, what happens to conflicting owners and to the activity history. Decide all of it before the first merge, because this is the step you cannot walk back. **What will bite:** - **Merging is close to irreversible.** Most CRM merges cannot be cleanly undone, and the damage is silent: a lost activity history looks exactly like a contact who was never engaged. Treat the dry run as part of the build rather than as a nice-to-have, and keep the export as your record of what happened. - **Identity resolution is not a name match.** That is the point, and it is also a limit. Two records for the same person at different companies over time are the same identity, and whether you want them merged is a policy question rather than a data one. Decide before you build which of those cases is a duplicate and which is a history. - **Personal email addresses resolve badly.** A work email is a strong identity signal; a personal one often is not. Expect a lower resolution rate on the exact records most likely to be duplicated, and route those to review rather than pushing the threshold down to catch them. - **Owners and activity are the real fight.** The technical merge is easy. Deciding which rep keeps the relationship, and what happens to the activity attached to the losing record, is a conversation with sales leadership. Have it before the dry run, not after somebody notices. - **One pass is not a solution.** Duplicates re-accumulate through the same doors they came in: forms, imports, and manual creation. Fix the intake as well, or schedule this and accept it as a standing cost. ### The Salesforce data layer The same enrichment loop, against an org with validation rules, triggers and an API allocation. - Uses: Salesforce, Clay, Reverse Contact - Build effort: Days - Page: https://www.reversecontact.com/integrations-hub/workflows/salesforce-data-layer - Agent skill: https://www.reversecontact.com/integrations-hub/skills/salesforce-data-layer.md **Steps:** 1. **Read what the org enforces** Before any table exists. Which fields are required, which validation rules fire on update, which triggers run, and what the duplicate rules do. This is an hour with an admin and it determines everything after it. 2. **Read a filtered slice into Clay** Leads, contacts, accounts or opportunities missing the field you care about. Read-only, so nothing in the org changes and nothing needs approving yet. 3. **Reverse Contact fills the gaps** An HTTP API column against the enrich endpoints. Identical to the HubSpot version, because this step does not care what CRM is upstream of it. 4. **Write ten records to a sandbox** Not a hundred, not the whole slice. Ten, then read every error. This is where you find the required field nobody documented and the validation rule written in 2019 by somebody who has left. 5. **Promote to production, then schedule** Write to dedicated fields, promote into the trusted ones only where empty, and set the cadence from how fast the field goes stale. Then watch the API allocation for a week. **What will bite:** - **API calls are a shared allocation.** Salesforce meters daily API requests by edition and licence count, across every integration in the org. A large table writing row by row competes with your existing connectors for the same budget, and the symptom of running out is other people's integrations failing, which is an unpopular way to find out. - **A completed run is not a successful write.** Rejections from validation rules and triggers are not always loud upstream. Check the error column every run for the first fortnight, and alert on error rate rather than on job completion. - **Clay bills the attempt, not the result.** Same economics as everywhere else: effective cost per filled field is the action rate divided by your match rate. Filter the import tightly, because on Salesforce the temptation to pull a whole object is stronger. - **You will need a sandbox and an admin.** Both are scheduling problems rather than technical ones, and both sit on somebody else's queue. That is why this workflow is days rather than hours, and almost none of it is build time.