When it breaks

Why your integration is doing that

The vendor documents the feature. Nobody documents the failure, which is the thing you are looking for at 6pm on a Thursday. These are the 494 we found and wrote down while checking 68 integrations, with what each one actually means and what to do about it. Every pair is also written up in full on its own guide.

494documented failures
68integrations
22tools
196need a plan upgrade
How to read it

A symptom, the documented reason, and the fix

Every one of these was read off a vendor's own documentation while a pair page was being written, which means none of them is a guess about what might go wrong.

Most of them are not faults. They are a setting somebody skipped, a scope that is optional and on by default, a tier that does not carry the feature, or a documented ceiling nobody read. That is why they survive a support ticket: the vendor's answer is that the product is behaving as designed, which is true and does not help.

196 of the 494 sit on an integration that needs a plan upgrade or a paid licence on one side, so the fix is a purchase rather than a setting. Those are marked, and the matrix shows which pairings are gated before you start building one.

Each failure is listed under the first tool in its pair's name, which is where the directory files the guide too. So a Reverse Contact build on Pipedrive appears under Pipedrive, because that is the tool whose settings you are in when it breaks.

Where they are

22 tools, worst first

Counted off the list below rather than stated, so this table cannot disagree with it. A high count is a measure of how much has been written up, not of how unreliable a tool is.

ToolDocumented failuresIntegrationsLayer
HubSpot 120 17 crm
Salesforce 69 10 crm
Clay 59 8 orchestrate,data
Slack 50 7 collab
Apollo 37 5 data,prospect,engage
LinkedIn 25 4 prospect
Outreach 14 2 engage
Attio 8 1 crm
Pipedrive 8 1 crm
Zoho 8 1 crm
monday 8 1 crm
ZoomInfo 8 1 data,prospect
n8n 8 1 orchestrate
Zapier 8 1 orchestrate
Make 8 1 orchestrate
Smartlead 8 1 engage
lemlist 8 1 engage
Salesloft 8 1 engage
Instantly 8 1 engage
ClickUp 8 1 collab
Gong 8 1 intel
Google 8 1 collab

The two biggest columns are the two tools this directory has written up most, which is HubSpot as the most connected CRM in B2B and Reverse Contact as the publisher. Neither is evidence about the product.

All 494

Every documented failure

Type the message your tool is showing you. The filter reads the symptom, the cause, the fix and the pair name, and every one of the 494 is in this page whether you filter or not.

All 494 showing

HubSpot

120 documented failures across seventeen integrations, all of them on the HubSpot hub.

The Sales Navigator card does not appear on the contact record

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

Check the edition on the seat, then have that user install the LinkedIn Sales Navigator app from the HubSpot App Marketplace themselves.

On HubSpot and LinkedIn, which needs a plan upgrade on one side

InMails and messages are not reaching the timeline

WhyLinkedIn is not selected in the activity filter. The writeback arrives on the record and the timeline hides it.

On the contact record, open Filter activity and tick LinkedIn. Check one rep who has definitely sent an InMail since go-live.

On HubSpot and LinkedIn, which needs a plan upgrade on one side

Writeback works for some reps and not others

WhyActivity writeback and contact creation need each user to authenticate with the CRM individually. Admin authentication does not cover them.

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.

On HubSpot and LinkedIn, which needs a plan upgrade on one side

A rep cannot update a HubSpot contact from Sales Navigator

WhySales Navigator respects HubSpot permissions. Without read and write access to that record in the CRM, the update is refused on the LinkedIn side.

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.

On HubSpot and LinkedIn, which needs a plan upgrade on one side

The pairing will not complete

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

Disconnect Business Manager, complete the Sales Navigator sync, then reconnect it. If a sandbox was paired for testing, release it before pairing production.

On HubSpot and LinkedIn, which needs a plan upgrade on one side

The CRM filled up with duplicate contacts

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

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.

On HubSpot and LinkedIn, which needs a plan upgrade on one side

Two years of LinkedIn history is missing

WhyThere is no backfill. Only new and updated data syncs after go-live.

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.

On HubSpot and LinkedIn, which needs a plan upgrade on one side

Contact fields populate and company fields do not

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

Check the connecting account's permissions on companies specifically, not just on contacts, then re-test with a single company export.

On HubSpot and ZoomInfo, which needs a plan upgrade on one side

Exports reach fewer records than expected

WhyThe connecting account is on the minimum permission of records they own rather than all records.

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.

On HubSpot and ZoomInfo, which needs a plan upgrade on one side

Duplicates are piling up after exports

WhyThe admin left the create-a-duplicate option available, and reps in a hurry take it.

Restrict the duplicate options in the Admin Portal so updating the existing record is the path of least resistance.

On HubSpot and ZoomInfo, which needs a plan upgrade on one side

The integration broke when somebody left the company

WhyIndividual user account connections tie the integration to people.

Move to the service account connection, which ZoomInfo describes as the default and preferred option for exactly this reason.

On HubSpot and ZoomInfo, which needs a plan upgrade on one side

Nobody authorised ZoomInfo to read the CRM

WhyHubSpot Import is enabled by default and allows ZoomInfo to import and analyse information from HubSpot about your team and your prospects and customers.

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.

On HubSpot and ZoomInfo, which needs a plan upgrade on one side

Reps complain the data overwrote their notes

WhyExport behaviour on those field mappings.

Change the behaviour per field. The mapping screen allows it and the default is not always what a rep would choose.

On HubSpot and ZoomInfo, which needs a plan upgrade on one side

There is no webhook action in the workflow editor

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

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.

On HubSpot and Reverse Contact

The custom code action timed out

WhyAn action must finish within 20 seconds and inside 128 MB of memory, and HubSpot returns an error on exceeding either.

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.

On HubSpot and Reverse Contact

One contact was written another contact's job title

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

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.

On HubSpot and Reverse Contact

Some contacts were quietly left un-enriched

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

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.

On HubSpot and Reverse Contact

A property a rep maintained has been overwritten

WhyNothing in this build decides that for you. The API returns a record and the property it lands in is whichever one your action names.

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.

On HubSpot and Reverse Contact

The workflow reports success and the property is empty

WhyReverse Contact returns null with a confidence score rather than a best guess, so a lookup that matched nobody completes normally rather than failing.

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.

On HubSpot and Reverse Contact

Everything stopped at once, including the calls that were free

WhyBelow 2 credits the free Check endpoints are paused too and answer 402 NO_CREDITS, because the fetch a check precedes can itself cost 2.

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.

On HubSpot and Reverse Contact

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.

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.

On HubSpot and Reverse Contact

The workflow created the task but every field is empty

WhyCustom field mapping is not supported in HubSpot workflows. Only Deal tokens in the name and description carry anything across.

Put the values you need into the description as tokens, and build real field mapping as a ClickUp Automation instead.

On HubSpot and ClickUp, which needs a plan upgrade on one side

A field will not map even inside an Automation

WhyMapping is type to type. A HubSpot email field maps only to a ClickUp Email custom field, and there is no conversion.

Create the matching custom field type in ClickUp first, then map. Renaming does not help, the type does.

On HubSpot and ClickUp, which needs a plan upgrade on one side

The second automation in a chain never fires

WhyAn object created by a HubSpot Automation does not trigger another HubSpot Automation.

Collapse the chain into one automation, or trigger the second step from something a person does rather than from something an automation made.

On HubSpot and ClickUp, which needs a plan upgrade on one side

Nobody can authenticate the integration

WhyClickUp requires a Workspace owner or admin to connect HubSpot.

Get the Workspace owner to do the App Center step. It takes a minute and cannot be delegated by permission alone.

On HubSpot and ClickUp, which needs a plan upgrade on one side

ClickUp is full of Spaces nobody meant to create

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

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.

On HubSpot and ClickUp, which needs a plan upgrade on one side

The HubSpot source and the object actions are not there

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

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.

On HubSpot and Clay, which needs a plan upgrade on one side

Connecting fails with an unexpected error during the app authorization process

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

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.

On HubSpot and Clay, which needs a plan upgrade on one side

The List dropdown shows an error asking you to reconnect

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

Reconnect the account and select that scope. It is the same flow and the rest of the permissions are unaffected.

On HubSpot and Clay, which needs a plan upgrade on one side

A row ran, HubSpot accepted it, and the record is not in the list

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

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.

On HubSpot and Clay, which needs a plan upgrade on one side

The write created a second copy of a record that already existed

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

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.

On HubSpot and Clay, which needs a plan upgrade on one side

A populated HubSpot property came back blank after a run

WhyIgnore blank values was turned off on the Update action. With it off, a blank Clay cell is sent through and overwrites what HubSpot had.

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.

On HubSpot and Clay, which needs a plan upgrade on one side

A company domain lost its subdomain on the way in

WhyKeep subdomains in Company domain is off by default, so shop.example.com is reduced to example.com before the write lands.

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.

On HubSpot and Clay, which needs a plan upgrade on one side

Credits went roughly twice as far as the row count suggested

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

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.

On HubSpot and Clay, which needs a plan upgrade on one side

A private channel does not appear when associating a record

WhyThe HubSpot app is not a member of it. Associations only work with public channels and private channels the app has been added to.

Add the app in that Slack channel, then refresh the record. No HubSpot setting substitutes for it.

On HubSpot and Slack, which needs a plan upgrade on one side

The workflow posts to the wrong room

WhyThe Slack workflow action takes a static channel. It cannot resolve the channel associated with the record being processed.

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.

On HubSpot and Slack, which needs a plan upgrade on one side

A deal lost its channel after a merge

WhyThe Slack channel association comes from the primary record in a merge.

Associate the channel with the record you will keep as primary before merging, or choose the record that already has it as the primary.

On HubSpot and Slack, which needs a plan upgrade on one side

Notifications arrive for one person and not the team

WhyPersonal notification settings are per user, under Settings, Notifications, Other apps.

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.

On HubSpot and Slack, which needs a plan upgrade on one side

The channel is noisy and now everybody has muted it

WhyEvery activity type was ticked when the channel was associated.

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.

On HubSpot and Slack, which needs a plan upgrade on one side

Nothing from a shared channel with a customer is in the CRM

WhySlack Connect conversations are not covered.

There is no setting. Either keep deal discussion in an internal associated channel, or accept that the customer-facing thread is outside the record.

On HubSpot and Slack, which needs a plan upgrade on one side

One object syncs and another does not

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

Log in as the connected user and look. Then add Modify All on that object to their profile rather than widening the integration settings.

On HubSpot and Salesforce, which needs a plan upgrade on one side

Everything broke after somebody changed the connected user

WhyThe replacement has narrower permissions, or belongs to a different Salesforce production org.

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.

On HubSpot and Salesforce, which needs a plan upgrade on one side

Records sync once, then stop

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

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.

On HubSpot and Salesforce, which needs a plan upgrade on one side

A record never arrives in HubSpot at all

WhyNo valid email address. HubSpot documents that those do not sync.

Check the email field before suspecting the mapping. If you need the record anyway, it has to arrive by another route.

On HubSpot and Salesforce, which needs a plan upgrade on one side

The sync looks slow or stuck

WhySalesforce to HubSpot runs on a cycle of roughly 10 to 15 minutes. It is not instant and is not supposed to be.

Wait a cycle before investigating. If it is still missing after that, go to the connected user's permissions first.

On HubSpot and Salesforce, which needs a plan upgrade on one side

Salesforce API limits are being eaten

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

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.

On HubSpot and Salesforce, which needs a plan upgrade on one side

Custom objects will not sync

WhyCustom object sync is HubSpot Enterprise only, and the HubSpot object needs at least one required field.

Check the tier first, then the required field. Both are cheaper to check than the mapping screen is to debug.

On HubSpot and Salesforce, which needs a plan upgrade on one side

Field mappings disappeared after a Salesforce migration

WhyMappings survive a move to a new production org only where the Salesforce field keeps the same internal name.

Match internal names before the cutover, or plan to rebuild the mappings and budget for it.

On HubSpot and Salesforce, which needs a plan upgrade on one side

Syncing started before anybody was ready

WhyThe six-hour configuration window expired and Apollo enabled syncing automatically.

Adjust the settings now, in Settings, Integrations, HubSpot. The settings stay editable; what you cannot undo is the first run.

On HubSpot and Apollo, which needs a plan upgrade on one side

Contacts arrived that should have been filtered out

WhySomebody pushed them manually. Apollo documents that a manual push overrides the sync settings, including stage restrictions.

Treat the conditions as a default rather than a control, and train the team on what the push button on a profile actually does.

On HubSpot and Apollo, which needs a plan upgrade on one side

One admin owns every contact Apollo created

WhyThe pushing users have not linked their personal HubSpot credentials in Apollo, so ownership falls to the shared authentication.

Have each rep link their own credentials. Reassigning afterwards is possible and tedious.

On HubSpot and Apollo, which needs a plan upgrade on one side

Every Apollo contact has the same source

WhyThe source field defaults to Apollo and was never changed.

Point it at the field your reporting uses, and pick the picklist value if that field is a picklist.

On HubSpot and Apollo, which needs a plan upgrade on one side

A push silently did nothing

WhyIt failed, and the failure lives in the integration views rather than on the record.

Open Error logs under Contacts or Accounts, then Push, and retry from there. Queue activity shows what is still waiting.

On HubSpot and Apollo, which needs a plan upgrade on one side

The integration is not available at all

WhyApollo's free plan excludes CRM integrations.

That is a plan question. The extension still works for manual research in the meantime.

On HubSpot and Apollo, which needs a plan upgrade on one side

The first trigger stopped firing when a second one was activated

WhyHubSpot allows one webhook. n8n registers it on activation, and activating another trigger takes the registration with it.

Run one trigger node and branch inside the workflow. If two workflows genuinely need the same event, have the first one call the second.

On HubSpot and n8n

Authentication credentials not found. This API supports OAuth 2.0 authentication

WhyA developer API key was used against a test account. HubSpot documents that developer API keys do not work for test accounts.

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.

On HubSpot and n8n

A self-hosted instance never receives the webhook

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

Put it behind a real certificate. Practitioners on r/n8n report a Cloudflare tunnel fixing exactly this after every guide had been followed.

On HubSpot and n8n

A form submission arrived without the file somebody uploaded

WhyHubSpot's webhook sends text fields. The file is not in the payload and never was.

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.

On HubSpot and n8n

OUTPUT_VALUES_TOO_LARGE from a HubSpot custom code action

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

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.

On HubSpot and n8n

This action has been paused to stay within the configured rate limit

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

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.

On HubSpot and n8n

A retry never happens after a 429

WhyHubSpot only retries a custom code action if the error is thrown. Catching it quietly means HubSpot treats the execution as a success.

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.

On HubSpot and n8n

The node does not have the operation the workflow needs

WhyThe HubSpot node covers seven resources and no custom objects. That is the documented scope of it rather than a gap to work around.

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.

On HubSpot and n8n

Every Zap broke at once and nothing changed on your side

WhySomebody added a second Zapier connection to the same HubSpot account, which invalidates the previous one.

Reconnect, then agree who owns the connection. There is no way to run two, so this is a people problem with a technical symptom.

On HubSpot and Zapier

Dates arrive a day early, or at midnight

WhyHubSpot takes dates as UNIX timestamps and Zapier rounds date-time values down to UTC midnight.

Store the precise value in a separate property if you need it. Nothing in the mapping screen prevents the rounding.

On HubSpot and Zapier

The list you want is missing from Add Contact to List

WhyIt is an active list. Only static lists appear.

Write a property instead and let an active list pick the contact up by rule, which is what active lists are for.

On HubSpot and Zapier

The Zap is slow and it is not Zapier's fault

WhyA polling trigger on an account without polling control, or an app-imposed minimum interval.

Switch to an instant trigger if one covers your event. Deal Property Change is instant; most of the created-or-updated triggers are not.

On HubSpot and Zapier

Original source reporting is full of Zapier

WhyA record created by an automation is attributed to that automation.

Create the contact through the native form or the Forms API where attribution matters, and use the Zap for everything after creation.

On HubSpot and Zapier

Requests start failing in bursts

WhyHubSpot allows 190 requests per 10 seconds regardless of tier, so a Zap that fans out hits the rate limit before the daily cap.

Add a delay step or batch the work. A HubSpot upgrade raises the daily ceiling and leaves the burst limit where it was.

On HubSpot and Zapier

A scope needs removing and there is no way to do it

WhyMake states that once scopes are added to a connection they cannot be removed.

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.

On HubSpot and Make

Watch Notifications never fires

WhyThe scopes are needed in two places with two different names: on the HubSpot custom app and again as connection custom scopes in Make.

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.

On HubSpot and Make

A subscription needs adding to an existing webhook module

WhyMake warns that the Subscriptions field cannot be updated at a later time.

Rebuild the module with the full list. This is the one setting on this pair worth over-specifying at the start.

On HubSpot and Make

A second webhook will not attach to the custom app

WhyEach HubSpot custom application can be associated with only one webhook URL.

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.

On HubSpot and Make

The OAuth redirect fails on the advanced connection

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

Use it as documented, and leave the Install URL blank. Typing the make.com equivalent is the obvious mistake here.

On HubSpot and Make

Make an API Call returns a permissions error

WhyMake cannot infer the scopes for an arbitrary endpoint, so this is the one module where you select them yourself.

Add them under Connection, Custom Scopes in the module settings, remembering that they then cannot be removed from that connection.

On HubSpot and Make

A contact cannot be subscribed to an email address

WhyMake documents it as a plain constraint: you cannot subscribe a contact to an email address that is already subscribed.

Check the subscription state first and branch, rather than treating the error as a failure to handle.

On HubSpot and Make

Somebody else's HubSpot integration started hitting limits

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

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.

On HubSpot and Make

Prospects are missing and nothing failed

WhyThey have no email address. HubSpot matches contacts on email and excludes records without one by default.

Open the Excluded column on the sync. These are listed there rather than raised as errors, which is why nobody finds them.

On HubSpot and Outreach, which needs a plan upgrade on one side

Opens and clicks are missing for some people

WhyEvent sync only applies to contacts HubSpot already holds, so engagement on a prospect who has not synced yet has nowhere to land.

Get the contact across first. The events do not backfill once it arrives.

On HubSpot and Outreach, which needs a plan upgrade on one side

A rep insists they emailed somebody and neither system shows it

WhyThey sent it from a mail client without the Outreach extension. Only email sent through Outreach or through a client running the extension reaches HubSpot.

This is a training and extension-deployment problem rather than a sync one. Nothing flags the gap.

On HubSpot and Outreach, which needs a plan upgrade on one side

The initial sync seems to have started over

WhySomebody saved the configuration again. HubSpot restarts the full index when you do.

Decide the configuration, save once and wait. Several days is documented for large record counts.

On HubSpot and Outreach, which needs a plan upgrade on one side

A filter is not keeping records out

WhyFilters limit which records sync initially. A record already synced keeps syncing on its field mappings regardless.

Filter before the first pass, or unsync the records individually. Changing the filter later does not reach back.

On HubSpot and Outreach, which needs a plan upgrade on one side

A field will not map

WhyIt is not a standard mapping, and custom field mappings need a Data Hub subscription.

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.

On HubSpot and Outreach, which needs a plan upgrade on one side

Every meeting appears twice in HubSpot

WhyCalls are being exported as HubSpot meetings while HubSpot is also syncing Google Calendar. Gong documents this combination as producing duplicate meetings.

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.

On HubSpot and Gong, which needs a plan upgrade on one side

Telephony calls appear twice

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

Switch to Gong Dialer calls only. This narrows what Gong claims rather than disabling the other tool, which is usually the easier conversation.

On HubSpot and Gong, which needs a plan upgrade on one side

A call happened and nothing is on the record after an hour

WhyNothing is wrong. Gong documents that exporting its data to HubSpot can take up to six hours.

Wait, then read the CRM export status report rather than the timeline. It distinguishes failed from not yet exported, which the record cannot.

On HubSpot and Gong, which needs a plan upgrade on one side

A meeting created no HubSpot activity at all

WhyNo external participant matched a HubSpot record. Gong requires at least one match before it creates an activity from a meeting invite.

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.

On HubSpot and Gong, which needs a plan upgrade on one side

One imported field is permanently empty in Gong

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

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.

On HubSpot and Gong, which needs a plan upgrade on one side

A rich text field lost its formatting after somebody edited it in Gong

WhyRich text has limited support. It displays without formatting, and an edit made in Gong writes back to HubSpot without it.

Keep rich text fields out of the imported set if anybody edits in Gong. The flattening is not recoverable from the HubSpot side.

On HubSpot and Gong, which needs a plan upgrade on one side

The integration stopped working and nobody changed anything

WhyThe connecting HubSpot user was deactivated, which is what the dedicated integration user recommendation exists to prevent.

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.

On HubSpot and Gong, which needs a plan upgrade on one side

Do not contact in Gong Engage never reaches the HubSpot contact

WhyThe opt-out permission is a separate authorisation, in addition to the regular integration permissions.

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.

On HubSpot and Gong, which needs a plan upgrade on one side

A campaign is running and HubSpot cannot be switched on

WhySmartlead states the campaign-level integration can only be set up while creating the campaign and not midway through an active one.

Either recreate the campaign, or build a SmartAgent instead, which works against campaigns that already exist. The second is almost always the better answer.

On HubSpot and Smartlead

The CRM is connected and no campaign is syncing

WhyConnecting HubSpot to the Smartlead account does not sync it with any campaign. It has to be enabled per campaign, every time.

Enable the toggle in each new campaign's creation flow, and select the HubSpot list and group while you are there.

On HubSpot and Smartlead

HubSpot shows as disconnected after authorising

WhySmartlead lists this as its first troubleshooting case: the OAuth account may lack the necessary CRM permissions.

Re-authorise from SmartAgents, Integrations, with an account that has CRM permissions. Tool connections are one-time otherwise and do not need periodic reconnection.

On HubSpot and Smartlead

The Configuration Required notice will not clear

WhySlack is the usual culprit. The SmartAgents app has to be present in the target channel before the agent can be deployed.

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.

On HubSpot and Smartlead

The agent ran and the contact is not in HubSpot

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

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.

On HubSpot and Smartlead

The agent runs but contacts are never updated

WhyThe Upsert Contact step is not receiving the right lead data, or the connection logic between the fetch step and the HubSpot step is wrong.

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.

On HubSpot and Smartlead

The trigger is wrong and cannot be changed

WhySmartlead states that event-based triggers cannot be edited after the agent is created.

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.

On HubSpot and Smartlead

Nothing about replies or opens is reaching anywhere

WhyThose are webhook events rather than part of this integration: email_sent, email_reply, email_open, email_link_click, lead_unsubscribed and lead_category_updated.

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.

On HubSpot and Smartlead

Every call shows as Connected whatever the rep marked

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

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.

On HubSpot and lemlist

Opens and clicks are nowhere in the Email object

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

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.

On HubSpot and lemlist

A field mapped last week is still empty on older contacts

WhyField mapping is not retroactive. It applies from the moment it is set, not to records already imported.

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.

On HubSpot and lemlist

A contact is not being created in HubSpot at all

WhyMandatory properties are enabled and the lead does not meet the required field conditions, so lemlist declines to create the record.

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.

On HubSpot and lemlist

Activity is landing with the wrong owner

WhyUser mapping is missing or incorrect, so the fallback owner is being used. The fallback is configured per sync direction and applies to everything unmapped.

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.

On HubSpot and lemlist

A call has no transcript or summary on the HubSpot record

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

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.

On HubSpot and lemlist

Somebody edited a call note in HubSpot and it reverted

Whylemlist rebuilds the note on every refresh rather than merging it, so a manual edit is replaced.

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.

On HubSpot and lemlist

A manual unsubscribe never reached HubSpot

Whylemlist only pushes the unsubscribe when the lead unsubscribed themselves from the campaign. A lead added to the Unsubscribe section by hand is not pushed.

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.

On HubSpot and lemlist

A rep cannot connect their inbox at all

WhyA View-Only seat, or a Gmail account enrolled in Google's Advanced Protection Program. Neither is supported for an individual work email.

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.

On HubSpot and Google

Emails from the shared address stopped logging properly

WhyThe same account is being used as both an individual work email and a team email, which HubSpot does not allow.

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.

On HubSpot and Google

Logging works and tracking does not

WhyThey are separate features. Tracking needs an assigned Sales Hub seat, and it does not work with customised Gmail layouts.

Check the seat, then have the rep turn off the custom layout in Gmail and retest.

On HubSpot and Google

An email logged against nobody

WhyIt was sent from an address that is not a user, a connected address or a configured alias.

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.

On HubSpot and Google

Opens are not registering for some contacts

WhyData privacy settings are on, and opens are only tracked for contacts with an assigned legal basis for processing.

That is a legal configuration rather than a bug. Your legal team decides the basis; the tracking follows it.

On HubSpot and Google

Meetings from the second calendar never arrive

WhyThe integration syncs one calendar.

Move the meetings that matter onto the connected calendar, or accept that the other one is invisible to the CRM.

On HubSpot and Google

The migration fails on phone numbers

WhyAttio validates country and area codes and expects the format plus country code followed by the subscriber number including the area code.

Normalise them in HubSpot before exporting. Hyphens are fine; a missing or wrong country code is not.

On HubSpot and Attio, which needs a plan upgrade on one side

Domain values are rejected

WhyAttio verifies that domains are valid and stores only the root. A full URL or a malformed prefix errors rather than being tidied up.

Strip to the root domain in HubSpot first. attio.com and www.attio.com are both accepted formats.

On HubSpot and Attio, which needs a plan upgrade on one side

Fewer people arrived than HubSpot had

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

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.

On HubSpot and Attio, which needs a plan upgrade on one side

A deal import failed with everything apparently present

WhyAttio notes that some objects, Deals among them, have required attributes that must be included for a successful import.

Check the required attributes for each object you enabled, rather than assuming the rules that worked for contacts apply.

On HubSpot and Attio, which needs a plan upgrade on one side

There are attributes in the workspace nobody created

WhyThe migration creates attributes to hold what it found. Attio tells you to review them after the sample migration and update or archive as needed.

Do that review at the sample stage. After a full run they are mixed in with everything else and much harder to attribute.

On HubSpot and Attio, which needs a plan upgrade on one side

The migration needs redoing from scratch

WhyThere is no partial undo. Attio documents a bulk delete as the way back.

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.

On HubSpot and Attio, which needs a plan upgrade on one side

An error appears mid-migration with no obvious cause

WhyImport2 is running the migration, not Attio, so the diagnostic path leaves Attio.

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.

On HubSpot and Attio, which needs a plan upgrade on one side

Something in HubSpot changed after the migration and Attio does not know

WhyBy design. This is a one-time move with no ongoing sync in either direction.

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.

On HubSpot and Attio, which needs a plan upgrade on one side

Salesforce

69 documented failures across ten integrations, all of them on the Salesforce hub.

The embedded profile does not appear on a record page

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

Work down that order rather than guessing. Try another browser first because it costs nothing, then check the layout on all four objects.

On Salesforce and LinkedIn, which needs a plan upgrade on one side

The sync disconnected after somebody changed role

WhyThe refresh token belonged to a personal admin account that was revoked or had its permissions changed.

Un-sync and re-sync using a dedicated integration user. This is the failure the integration-user recommendation exists to prevent.

On Salesforce and LinkedIn, which needs a plan upgrade on one side

Everything stopped and there was no warning

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

On Salesforce and LinkedIn, which needs a plan upgrade on one side

The first import looks half finished

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

Check the last sync timestamp in Admin Settings rather than counting records. Do not re-run the setup, which restarts the clock.

On Salesforce and LinkedIn, which needs a plan upgrade on one side

Insufficient access despite holding the permission set

WhyManaged package permission sets cannot include certain standard fields used as URL parameters.

Clone the set and add field-level access: Website, Industry and BillingAddress on Account, and ConvertedAccountId, Company, Website, Industry and Address on Lead.

On Salesforce and LinkedIn, which needs a plan upgrade on one side

A record is matched to the wrong person

WhyMatching is score-based and picks a best guess, which is occasionally the wrong one.

Use Match Correction from the embedded profile. The correction is shared across the contract, so one person fixing it fixes it for everybody.

On Salesforce and LinkedIn, which needs a plan upgrade on one side

Only some contacts get the Not at Company flag

WhyContact validation rules are failing the bulk API update for the rest.

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.

On Salesforce and LinkedIn, which needs a plan upgrade on one side

Reports credit every activity to one person

WhyThe licence holder owns the shared information, so activity reports attribute to them rather than to the seat that did the work.

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.

On Salesforce and LinkedIn, which needs a plan upgrade on one side

OAUTH_APPROVAL_ERROR_GENERIC on sign in

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

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.

On Salesforce and Clay, which needs a plan upgrade on one side

Bad value for restricted picklist

WhyThe text Clay sent does not match a picklist option. Spelling and case both count.

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.

On Salesforce and Clay, which needs a plan upgrade on one side

A multi-select picklist writes only the first value

WhyThe wrong delimiter. Salesforce expects semicolons between values and Clay will happily send commas.

Use semicolons. This is the one error on the list where the symptom looks like a truncation rather than a format problem.

On Salesforce and Clay, which needs a plan upgrade on one side

A field refuses a value that looks correct

WhyA display label was used where the API name is required. The two are different strings and only one of them works.

Read the API name in Salesforce Setup and use that. A field somebody renamed years ago is the usual case.

On Salesforce and Clay, which needs a plan upgrade on one side

A report import stopped at 2,000 rows

WhyThat is the documented cap, and it applies to a list view that is not SOQL-compatible as well.

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.

On Salesforce and Clay, which needs a plan upgrade on one side

The same records arrived twice from a report

WhyNo uniqueness fields were set, so Clay identified each row by the entire row. Two rows differing in one whitespace character are two records.

Set Uniqueness fields on the report source. The account ID or a normalised domain is what belongs there.

On Salesforce and Clay, which needs a plan upgrade on one side

The run completed and Salesforce has none of it

WhyValidation rules, required fields, duplicate rules or an Apex trigger rejected the rows. The rejection is loud in Salesforce and quiet in Clay.

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.

On Salesforce and Clay, which needs a plan upgrade on one side

Lead conversion associated the wrong account

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

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.

On Salesforce and Clay, which needs a plan upgrade on one side

Everything is set up and nothing happens in Slack

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

Open Manage Salesforce Organizations in Slack, select the connection and click Activate. Confirm it reads active before you debug anything else.

On Salesforce and Slack, which needs a plan upgrade on one side

The app works for admins and not for the team

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

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.

On Salesforce and Slack, which needs a plan upgrade on one side

Some members are not matched to a Salesforce user

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

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.

On Salesforce and Slack, which needs a plan upgrade on one side

Features fail intermittently for no visible reason

WhySalesforce IP restrictions. Slack documents them as a cause of features not working as expected, which presents as flakiness rather than as a permission error.

Check the org IP restrictions against the Slack connection before spending a day in debug logs.

On Salesforce and Slack, which needs a plan upgrade on one side

The connection broke after a Salesforce change

WhyThe org URL changed. The stored connection still points at the old one.

Update the connection in Slack with the new org URL.

On Salesforce and Slack, which needs a plan upgrade on one side

A notification stopped firing, or says the wrong thing

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

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.

On Salesforce and Slack, which needs a plan upgrade on one side

A shared channel with a customer gets none of this

WhySales Cloud for Slack does not support Slack Connect channels.

Keep the record-linked channel internal and treat the customer channel as a separate surface. There is no setting that changes this.

On Salesforce and Slack, which needs a plan upgrade on one side

System.LimitException: Too many callouts: 100

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

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.

On Salesforce and Reverse Contact

The transaction died partway through a batch of records

WhyThere is a cumulative timeout of 120 seconds across every callout in one transaction, on top of the 10-second default on each individual call.

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.

On Salesforce and Reverse Contact

You have exceeded your daily API call limit

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

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.

On Salesforce and Reverse Contact

REQUEST_LIMIT_EXCEEDED while nowhere near the daily number

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

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.

On Salesforce and Reverse Contact

The Flow failed on a contact who is not in the database

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

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.

On Salesforce and Reverse Contact

The API key turned up in a change set

WhyA key pasted into a Flow variable or an Apex constant is metadata, and metadata travels through change sets, retrieves and version control.

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.

On Salesforce and Reverse Contact

A live refresh never came back

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

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.

On Salesforce and Reverse Contact

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.

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.

On Salesforce and Reverse Contact

The connection window never appeared

WhyA popup blocker. ZoomInfo opens the Salesforce authorisation in a popup and says so.

Disable the blocker for the Admin Portal and reconnect. Nothing is wrong with the credentials.

On Salesforce and ZoomInfo, which needs a plan upgrade on one side

Credits went in a single run

WhyCredit Usage Limits defaults to No limit, so the job enriched every record it matched.

Set a per-run credit limit before the next schedule, and test any new filter against ten records first.

On Salesforce and ZoomInfo, which needs a plan upgrade on one side

Created contacts are invisible to everybody except one user

WhyA Salesforce contact with no account relationship is private to its creator, which is Salesforce behaviour rather than ZoomInfo behaviour.

Make sure created contacts attach to an account. Practitioners use a placeholder account everyone can see, or route to the Lead object instead.

On Salesforce and ZoomInfo, which needs a plan upgrade on one side

Records come back as No Match in bulk

WhyThey matched but fell below the accuracy threshold, and the reason field says so.

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.

On Salesforce and ZoomInfo, which needs a plan upgrade on one side

Reps say the data is wrong and they fixed it last week

WhyAn Update Option set to overwrite on a field people type into, or Person Has Moved rewriting an employer.

Switch those mappings to complete only if missing, and check the Person Has Moved setting, which is on unless somebody turned it off.

On Salesforce and ZoomInfo, which needs a plan upgrade on one side

Other integrations in the org started failing

WhySalesforce API consumption. Instant Enrich costs two calls per record and a small batch size multiplies scheduled calls, all drawn from one shared daily allowance.

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.

On Salesforce and ZoomInfo, which needs a plan upgrade on one side

A feature in the guide is missing from your org

WhySome capabilities need the ZoomInfo Sales native application at version 1.33 or higher.

Upgrade the AppExchange package before raising a support ticket about a missing screen.

On Salesforce and ZoomInfo, which needs a plan upgrade on one side

The connection refuses admin credentials

WhyOutreach lists this first among connection errors: the credentials used must be a Salesforce administrator, for sandbox and production alike.

Connect with an admin account, ideally the dedicated integration user rather than a person.

On Salesforce and Outreach, which needs a plan upgrade on one side

The connection drops every day or two

WhySalesforce session timeout settings, which Outreach calls out specifically for sandboxes breaking every 24 to 48 hours.

Check the session timeout in Salesforce rather than reconnecting repeatedly, which treats the symptom.

On Salesforce and Outreach, which needs a plan upgrade on one side

Records sync for some users and not others

WhyIncorrect user mappings, one of the five errors Outreach lists as common, alongside unmapped lead queues.

Open the plugin logs, which export the last 10,000 errors, and fix the mappings rather than the records.

On Salesforce and Outreach, which needs a plan upgrade on one side

Writes fail with no obvious pattern

WhyValidation errors or required fields missing on the Salesforce side, which the plugin surfaces rather than the record does.

Filter Activity by System Update, Plugins, Plugin Sync Error. The failures are there and nowhere else.

On Salesforce and Outreach, which needs a plan upgrade on one side

A field keeps changing back

WhyBoth systems are writing it. Conflict resolution merges field by field, so the last writer wins quietly rather than erroring.

Decide an owner for that field and stop one side writing it. Nothing in the plugin will flag the fight.

On Salesforce and Outreach, which needs a plan upgrade on one side

The org ran out of API calls overnight

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

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.

On Salesforce and Outreach, which needs a plan upgrade on one side

Activities are missing and nothing errored

WhyThe integration user's permissions are too limited. Gong says exactly this: activities may be missing until the setup is adjusted.

Widen record access on the objects concerned, using View All Records where the role hierarchy is the constraint.

On Salesforce and Gong, which needs a plan upgrade on one side

Calls log but Gong has no CRM context

WhyThe Salesforce Integration licence, which carries field-level permissions for importing Salesforce data, is not assigned.

Assign both permission set licences. The symptom points at Gong and the cause is a Salesforce licence.

On Salesforce and Gong, which needs a plan upgrade on one side

Gong cannot create tasks or events

WhyThe other licence. The Salesforce API Integration licence carries the system permissions for that.

Same fix from the other direction, which is why the grid above lists them separately.

On Salesforce and Gong, which needs a plan upgrade on one side

The whole integration stopped on a Monday

WhyThe integration user was deactivated, most often in a routine leavers process.

Use a dedicated integration user on the licence Salesforce provides for the purpose, and add it to whatever list protects service accounts from deactivation.

On Salesforce and Gong, which needs a plan upgrade on one side

Historic Gong data disappeared from a field

WhyThat field was removed from the Gong field configuration, which deletes the data imported through it.

There is no undo in the configuration screen. Treat field removal as a data decision requiring the same care as a Salesforce field delete.

On Salesforce and Gong, which needs a plan upgrade on one side

Long picklist values look truncated

WhyGong displays a maximum of 120 characters for picklists and strings.

Shorten the values, or accept the trim. This is display rather than storage, so the data is intact in Salesforce.

On Salesforce and Gong, which needs a plan upgrade on one side

This connection to Salesforce appears to no longer be working

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

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.

On Salesforce and Zapier

Please check your username and password, on a connection that is correct

WhySandbox was selected and the account does not support a sandbox environment. Zapier quotes this exact message for that case.

Connect to production instead. The credentials are not the problem.

On Salesforce and Zapier

A trigger never fires for certain records

WhyUser, object or field permissions on the connecting user. Zapier documents these as able to prevent triggers and actions from working.

Check field-level security as well as object permissions, and test as the connecting user rather than as an admin.

On Salesforce and Zapier

A new custom field is missing from the Zap editor

WhyZapier documents a delay before newly created Salesforce fields and objects appear in its dropdowns.

Refresh the fields from the trigger step, and wait before rebuilding anything.

On Salesforce and Zapier

The Zap worked in testing and misbehaves live

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

Test against a real record of the right object before turning the Zap on.

On Salesforce and Zapier

Marketing Cloud will not connect

WhyThe Salesforce integration does not support Marketing Cloud accounts.

There is no setting. Marketing Cloud needs its own route entirely.

On Salesforce and Zapier

One person sees previews and another sees a bare link

WhyOnly personal connections are supported. The second person has not authorised their own.

Have them connect from the ClickUp App Center. No admin action will do it on their behalf.

On Salesforce and ClickUp, which needs a plan upgrade on one side

The integration is not available in the App Center

WhyThe ClickUp plan is below Business Plus.

That is a plan question for both halves, Connected Search and Salesforce Sync alike.

On Salesforce and ClickUp, which needs a plan upgrade on one side

A Salesforce URL does not render as a preview

WhyNot every Salesforce URL type generates a dynamic preview, and the preview type can be set by hand.

Hover over the link and change the type from the ellipsis menu before concluding it is unsupported.

On Salesforce and ClickUp, which needs a plan upgrade on one side

Nobody uses the creation commands

WhyThey live in the AI Command Bar as typed commands rather than as visible buttons.

Tell the team the exact phrases. Discoverability is the whole problem here.

On Salesforce and ClickUp, which needs a plan upgrade on one side

A Salesforce admin cannot find the upgrade

WhyWith an earlier version installed, the button reads Upgrade rather than Install.

Use it. ClickUp documents that upgrading keeps the existing data.

On Salesforce and ClickUp, which needs a plan upgrade on one side

Authentication fails from n8n Cloud with nothing useful in the message

WhyThe connecting user's profile is missing Approve Connected Apps for Non-Admins. n8n states this is not enabled by default even for administrator profiles.

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.

On Salesforce and n8n

External client app is not installed in this org

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

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.

On Salesforce and n8n

The callback URL will not save, or the redirect 404s

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

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.

On Salesforce and n8n

The credential authorises and stops working months later

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

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.

On Salesforce and n8n

A write failed and the workflow reported success

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

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.

On Salesforce and n8n

A SOQL search returned far more than expected and the workflow stalled

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

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.

On Salesforce and n8n

Nothing the workflow needs is in the resource list

WhyLead conversion and anything newer than the node are not modelled. That is the documented scope of it rather than a bug.

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.

On Salesforce and n8n

Someone else's integration started returning errors after your backfill

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

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.

On Salesforce and n8n

Clay

59 documented failures across eight integrations, all of them on the Clay hub.

The column came back empty on somebody you know is real

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

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.

On Clay and Reverse Contact

Find Professional Profile returned a person with no work history

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

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.

On Clay and Reverse Contact

The enrichment works and nothing ever reaches the CRM

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

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.

On Clay and Reverse Contact

The bill is bigger than the number of rows that got enriched

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

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.

On Clay and Reverse Contact

There is no freshness check in the action list

WhyThe Clay listing carries four actions, the two Find and the two Enrich ones. The free check endpoints are not among them.

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.

On Clay and Reverse Contact

A live call never returns a record

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

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.

On Clay and Reverse Contact

Everything stopped at once, including the calls that were free

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

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.

On Clay and Reverse Contact

The table re-ran and spent credits on rows that were already done

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

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.

On Clay and Reverse Contact

Enrich Person returns almost nothing on a lot of rows

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

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.

On Clay and Apollo

Rows come back skipped from Add Contact to Sequence

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

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.

On Clay and Apollo

Add Contact to Sequence will not run at all

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

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.

On Clay and Apollo

Apollo filled up with duplicate contacts

WhyRun Dedupe was turned off, or the rows carry none of the three things it matches on: email, LinkedIn URL, or name plus organisation.

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.

On Clay and Apollo

A Find Account by ID or Find Contact by ID column is empty

WhyBoth require an Apollo ID, and nothing earlier in the table produced one. These are follow-up actions rather than entry points.

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.

On Clay and Apollo

The bill went up after bringing your own Apollo key

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

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.

On Clay and Apollo

Find People at Company By Job Title returns fewer people than expected

WhyThat action caps the limit at 10, where Find People from Apollo goes to 1,000. They read like the same action and are not.

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.

On Clay and Apollo

A table stopped mid-run and the credits are gone

WhyClay documents that requests already sent still consume their Data Credits when actions are stopped partway through.

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.

On Clay and Apollo

The sync stops and says the audience is too small

WhyFewer than 300 matchable records. LinkedIn will not build an audience below that, and Clay checks before uploading rather than after.

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.

On Clay and LinkedIn, which needs a plan upgrade on one side

The audience never leaves Building

WhyLinkedIn processing, which takes about 48 hours. Clay notes specifically that it will not be the 300 record minimum, because that fails before upload.

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.

On Clay and LinkedIn, which needs a plan upgrade on one side

The match rate is far lower than expected

WhyWork emails with no enrichment. Clay publishes 60 to 70% for work emails alone against 90 to 95% with a hashed personal email added.

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.

On Clay and LinkedIn, which needs a plan upgrade on one side

LinkedIn shows a smaller audience than Clay sent

WhyNothing is wrong. LinkedIn reports a deduped member count and does not count records that resolve to no member profile.

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.

On Clay and LinkedIn, which needs a plan upgrade on one side

A list larger than 300,000 arrived incomplete

WhyThe cap trims rather than rejects, so the sync looks successful and the audience is short.

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.

On Clay and LinkedIn, which needs a plan upgrade on one side

Title-based targeting is matching the wrong people

WhyLong job titles were truncated by a field character limit, silently, so the value LinkedIn received is a cut-off string.

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.

On Clay and LinkedIn, which needs a plan upgrade on one side

Leads are not being added to the campaign

WhyClay's first documented troubleshooting entry: all Smartlead actions need a campaign that exists and is active in Smartlead.

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.

On Clay and Smartlead

Some leads were skipped and they are all in other campaigns

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

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.

On Clay and Smartlead

Update or Remove will not run

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

Run Lookup lead in campaign first and map its Id output into the Lead ID field. The same applies to Update lead category.

On Clay and Smartlead

Bounced addresses are reaching the campaign

WhyAllow Leads from Community Bounce List is on by default, so leads on Smartlead's shared list are added unless you switch it off.

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.

On Clay and Smartlead

The personalisation column did not reach the campaign

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

Add it under Custom Fields on the add or update action, with the field name exactly as the campaign expects it.

On Clay and Smartlead

A push succeeded and you cannot tell what it did

WhyAdd lead to campaign and Update lead in campaign both confirm success and return no output fields, by design.

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.

On Clay and Smartlead

The table pushed rows you were still working on

WhyAuto-update was on while the filters were still being built, so rows added to the table went straight out.

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.

On Clay and Smartlead

Nothing about replies is coming back

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

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.

On Clay and Smartlead

The OAuth flow will not complete and Attio is never connected

WhyThe person connecting is not an Attio workspace admin. Clay documents that only workspace admins can authorise this connection.

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.

On Clay and Attio, which needs a plan upgrade on one side

The filter on an import is doing nothing

WhyA saved View is selected on the same source. Clay documents that the View takes precedence and the Filter is ignored when both are present.

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.

On Clay and Attio, which needs a plan upgrade on one side

The import returned the entire object

WhyNeither a View nor a Filter was set. Clay documents that all records are returned when neither is provided.

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.

On Clay and Attio, which needs a plan upgrade on one side

Attio is filling up with duplicates

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

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.

On Clay and Attio, which needs a plan upgrade on one side

Multiselect values disappeared after an update

WhyMultiselect Behavior was set to overwrite rather than append, so the incoming values replaced the existing ones.

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.

On Clay and Attio, which needs a plan upgrade on one side

429 Too Many Requests from Attio during a bulk write

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

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.

On Clay and Attio, which needs a plan upgrade on one side

A backfill that worked before now hits limits

WhyAttio states it may reduce the rate limit during incident response, and may permanently lower it for specific APIs that handle a lot of data.

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.

On Clay and Attio, which needs a plan upgrade on one side

The webhook accepted rows for months and has quietly stopped

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

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.

On Clay and n8n, which needs a plan upgrade on one side

There is no Clay node to add in n8n

Whyn8n does not publish one. Its documentation sitemap has no Clay entry and n8n.io/integrations/clay returns a 404, whatever a forum answer says.

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.

On Clay and n8n, which needs a plan upgrade on one side

Clay has no option to call an external URL

WhyHTTP API integrations are a Growth feature. On Free and Launch the capability is absent rather than limited.

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.

On Clay and n8n, which needs a plan upgrade on one side

The row arrives in Clay as a single column holding everything

WhyThe body reached Clay as a string rather than as JSON, so there was one value to make a column from.

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.

On Clay and n8n, which needs a plan upgrade on one side

The webhook returns an authentication error after working yesterday

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

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.

On Clay and n8n, which needs a plan upgrade on one side

An execution has been waiting for days

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

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.

On Clay and n8n, which needs a plan upgrade on one side

The lead was not added to the sequence

WhyThe sequence is not Active in Outreach. Clay states this requirement on the Add to sequence action itself.

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.

On Clay and Outreach

Add to sequence will not run at all

WhyIt needs three inputs and most tables only have two. Prospect ID, Sequence ID and Mailbox ID are all required.

Run Lookup mailbox by email address once to resolve the mailbox, and carry the prospect ID forward from Create or Lookup prospect.

On Clay and Outreach

The same person was enrolled twice

WhyNothing in the push checks existing enrolment unless you ask. Lookup prospect has an Include Sequences switch and it is not on by default.

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.

On Clay and Outreach

Update prospect is failing on rows that have an email

WhyUpdate requires the ID as well as the email. An email alone is enough for Create and not for Update.

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.

On Clay and Outreach

Emails went out from the wrong address

WhyAdd to sequence sends from whatever mailbox the Mailbox ID names, and a single hard-coded ID applies to every row.

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.

On Clay and Outreach

An Outreach admin is asking why Clay can see opportunities

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

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.

On Clay and Outreach

Nothing is coming back from Outreach

WhyBy design. The five actions write and look up; there is no engagement read.

Read performance in Outreach, and join it to the list in whichever CRM both tools already write to.

On Clay and Outreach

Credits went on rows that were never enrolled

WhyThe enrichment columns upstream run before the enrolment column decides anything, and each one spends an Action per record.

Move the qualifying condition as far up the table as it will go. Clay bills per record enriched regardless of what happens downstream.

On Clay and Outreach

400 LEAD_ALREADY_IN_CAMPAIGN

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

Use the Update Lead in Campaign action for anybody already there, gated on a lookup column. Nothing was written by the refused call.

On Clay and lemlist

409 LEAD_ALREADY_IN_OTHER_CAMPAIGN

WhyDeduplication is on and the contact has a lead in a different campaign.

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.

On Clay and lemlist

A lead was refused and its details changed anyway

WhyThe lead is always new, and the contact and company it matches are updated with whatever fields you sent regardless.

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.

On Clay and lemlist

A populated field came back empty after a push

WhyupdateStrategy defaults to overwrite, where a sent value replaces the stored one and an empty value clears it.

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.

On Clay and lemlist

A merge tag is not resolving in the campaign

WhyThe custom variable name was rewritten on storage. Only letters, digits, underscore, hyphen, space and hash are kept, and anything else becomes an underscore.

Name the Clay column with characters lemlist keeps, and match the merge tag to the stored name rather than the one you typed.

On Clay and lemlist

A company field you wrote shows up on other people's leads

WhyCompany-prefixed fields reach the company record the lead is matched to, which is shared by every lead linked to it.

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.

On Clay and lemlist

Requests started failing during a bulk run

Whylemlist rate-limits all routes at 20 requests per 2 seconds, per API key.

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.

On Clay and lemlist

Nobody can find the API key

Whylemlist shows it once at creation and never again.

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.

On Clay and lemlist

Slack

50 documented failures across seven integrations, all of them on the Slack hub.

The channel went quiet and nobody noticed for a fortnight

WhyA silent integration and a working integration look identical in Slack, because the absence of a message is not an event.

Post a heartbeat on a schedule, or have the orchestrator post its own failures to the same channel. A channel that has never told you it is broken has not proved it is working.

On Slack and Reverse Contact

Everybody muted the channel

WhyThe trigger was too broad, so the channel fired more often than anyone could read, which is the failure mode of every integration on the Slack hub.

Narrow the trigger rather than the message. One event type, one channel, one named owner, and move everything else to a report nobody has to read in real time.

On Slack and Reverse Contact

The eleventh lookup in a minute did nothing

WhyWorkflow webhook triggers are limited to 10 per minute, and the eleventh is refused rather than queued.

Move the busy case to a scheduled sweep and keep the on-demand trigger for the occasional question. If people genuinely need to ask eleven times a minute, the answer belongs on the record rather than in a channel.

On Slack and Reverse Contact

Messages stopped appearing in one busy channel but not the others

WhyPosting is limited to one message a second per channel, by chat.postMessage and incoming webhooks alike, and sustained excess is throttled.

Batch into one message rather than posting a line at a time, which is better for the reader as well. Slack shows the reader an error about undisplayed messages that the sending app never sees, so watch the channel rather than the logs.

On Slack and Reverse Contact

The app could suddenly only read fifteen messages at a time

Whyconversations.history and conversations.replies moved from Tier 3 to Tier 1 for commercially distributed apps that are not Marketplace approved, with a maximum of 15 objects and one request a minute.

If this is your own app for your own workspace it is an internal customer-built app and is explicitly unaffected, so check how it was registered before rewriting anything. If it is genuinely distributed, Marketplace approval is the documented route back.

On Slack and Reverse Contact

A custom step will not install

WhyApps carrying workflow steps have to be org-ready, and custom steps cannot be developed on a Free plan.

Confirm the plan and the org-readiness before building, not after. Where neither is available, the orchestrator route reaches the same channel with none of these conditions.

On Slack and Reverse Contact

A beautifully formatted message about somebody who left the company

WhyThe enrichment returned a current employer and nothing compared it with the account the alert was about.

Compare currentPosition.companyName against what you already hold and say so when they disagree. It is the highest-value check on the response and it is two values rather than a new field.

On Slack and Reverse Contact

Everything stopped, including the calls that were free

WhyBelow 2 Reverse Contact credits the free Check endpoints are paused as well and answer 402 NO_CREDITS, because the fetch a check precedes can itself cost 2.

Watch quotas.workspace.credits.left, which rides on every response, and check GET /v2/usage on a schedule because it keeps answering whatever the balance.

On Slack and Reverse Contact

A channel is missing from the Slack channel picker

WhyIt is a private channel and Gong has not been added to it. groups:read only shows private channels the app is in.

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.

On Slack and Gong, which needs a plan upgrade on one side

The Slack channel option is not offered on a stream

WhyEither the company is not connected to Slack, or the stream type is not Standard. Gong requires both.

Check the connection in Admin center, Settings, Ecosystem, Slack, then set the stream type to Standard in step 5 of the stream form.

On Slack and Gong, which needs a plan upgrade on one side

Notifications arrive as direct messages and never in a channel

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

Build a stream with filters and point it at the channel. There is no setting that redirects a personal notification.

On Slack and Gong, which needs a plan upgrade on one side

A stream is collecting nothing

WhyIf the filter uses an AI tracker that is inactive, or the company has insufficient credits, Gong documents that matching calls are not collected.

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.

On Slack and Gong, which needs a plan upgrade on one side

The channel is unusable because of the volume

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

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.

On Slack and Gong, which needs a plan upgrade on one side

A stream nobody else can see

WhyIt was saved to Your library, which is private, rather than Company library.

Choose the library location when creating the stream. It is a field on the same form and easy to leave at its default.

On Slack and Gong, which needs a plan upgrade on one side

The connection stopped working after an app update

WhyGong updates the Gong for Slack app from time to time and the new version needs re-authorising.

Click Authorize when prompted. Gong notes this on the connection article, and it is a permissions prompt rather than a reinstall.

On Slack and Gong, which needs a plan upgrade on one side

A Gong admin cannot complete the setup

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

Get the Slack install done as a separate task. Two admins on two teams is the real cost of this ten-minute integration.

On Slack and Gong, which needs a plan upgrade on one side

A channel is missing from the list when setting up

WhyClickUp names three reasons: the channel was deleted, you have not joined it, or it is new.

Join the channel, then wait. A newly created or joined channel can take five minutes to appear, and no logout is needed.

On Slack and ClickUp

Private channels cannot be selected at all

WhyA Workspace connection syncs to public channels only. A personal connection reaches both.

Decide which you want. Changing it means reconnecting, so it is worth settling before the mapping work.

On Slack and ClickUp

An admin cannot add a new ClickUp location to a channel

WhyOnly the creator of the Workspace connection can add locations. Admins and owners can map existing messages to more locations and nothing else.

Go back to the connection creator, or recreate the connection under an account the team will keep.

On Slack and ClickUp

Search does not find a message that is definitely there

WhyIndexing. A new message takes up to ten minutes to become searchable, and the initial index can take 24 hours.

Check the progress in the AI Command Bar before reconnecting anything.

On Slack and ClickUp

Somebody saw a task they should not have

WhyA link unfurl shows the title and description preview to the channel, whatever that person's ClickUp permissions are.

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.

On Slack and ClickUp

A contractor cannot use any of it

WhyGuests and limited members are excluded from the integration.

A full member seat is the only route. Plan around it rather than troubleshooting it.

On Slack and ClickUp

A user cannot see Slack in their notification settings

WhyOutreach answers this one directly: Slack must be enabled by an Outreach admin and mapped to the user's account.

Confirm the instance-level connection exists, then check the user mapping. Outreach maps users automatically after connecting, so an unmapped person usually joined afterwards.

On Slack and Outreach, which needs a plan upgrade on one side

Nothing happened after the admin connected it

WhyCorrect behaviour. The admin connection enables the channel and switches nothing on; each user toggles their own notifications.

Send people to Personal Settings, General, Notifications. This is the single most common reason the integration is reported as broken on day one.

On Slack and Outreach, which needs a plan upgrade on one side

Opens and clicks never arrive in Slack

WhyThey are browser notifications rather than Slack ones. Outreach states that not all notifications support all channels.

Enable browser notifications and grant the OS-level permission. There is no configuration that routes engagement events into Slack.

On Slack and Outreach, which needs a plan upgrade on one side

Browser notifications are enabled and still nothing appears

WhyPopups are blocked, or the OS permission was never granted. Outreach says the browser asks after you press Enable browser notifications.

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.

On Slack and Outreach, which needs a plan upgrade on one side

The channel selector is missing on an account

WhyEither Slack is not connected to the Outreach org, or the account-channel feature has not been enabled by an admin.

An admin connects the integration and enables the feature in Org info. You also need edit permission on the account you are configuring.

On Slack and Outreach, which needs a plan upgrade on one side

An account channel receives nothing but meeting summaries

WhyThat is the full list. Outreach supports only the Kaia meeting summary at account level today.

Use personal notifications for everything else. Outreach notes additional types may come in future releases, which is not something to plan around.

On Slack and Outreach, which needs a plan upgrade on one side

The meeting summary arrived late

WhyIt is triggered post-call and sent after Kaia has processed the recording. Outreach documents a short delay.

Wait rather than reconfiguring. If it never arrives, check the call was actually associated with that account.

On Slack and Outreach, which needs a plan upgrade on one side

Account notifications are visible to people who should not see them

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

Treat channel membership as the access control, because it is. This is a decision to take before enabling the feature across the org.

On Slack and Outreach, which needs a plan upgrade on one side

A Zap never fires on messages posted by another tool

WhyMessages preceded by indentation, which is how bots, slash commands and integrations post, cannot trigger a workflow.

Trigger on something else, or extract the attachment using Zapier's documented route. A chain of Zaps posting to each other will not work.

On Slack and Zapier

The Zap fires constantly during a busy conversation

WhyThread replies trigger the same way top-level messages do.

Add a filter on the thread timestamp field, which Zapier always returns, including on messages that are not in a thread.

On Slack and Zapier

The message posted but nobody was notified

WhyA plain mention in an action is text. Slack needs Zapier's special formatting for mentions and notifications to work.

Use the documented formatting. There is no error to find, because the post succeeded.

On Slack and Zapier

A slash command in an action did nothing

WhyIt posts as text rather than running.

Call the underlying thing directly from the Zap instead, or trigger the automation another way.

On Slack and Zapier

Messages are dropping during a burst

WhySlack allows about one message per second per channel, tolerating short bursts and rate-limiting sustained ones.

Batch into a single message. A loop that posts per row will hit this on any list worth automating.

On Slack and Zapier

Zapier cannot be installed at all

WhyA free Slack workspace at its ten-app limit, or a workspace that restricts app installs.

Free a slot, or get a workspace owner or admin to approve it. Neither is a Zapier setting.

On Slack and Zapier

The trigger will not authenticate

WhyIt is configured with OAuth2. n8n requires an API access token for the Slack Trigger node.

Create a second credential of the access token type against the same Slack app.

On Slack and n8n

A custom bot icon is ignored

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

Switch that workflow to the access token credential. There is no error to find, which is why this one survives upgrades.

On Slack and n8n

A scope cannot be granted

WhySome scopes do not exist for bot tokens at all, including channels:write and stars:read.

Check n8n's list before designing around the operation. This is a redesign rather than a permission request.

On Slack and n8n

An event n8n does not list is needed

WhyThe node exposes a set of events, and yours is not in it.

Add the event as a bot event in Slack, then select Any Event in the node and branch on the payload.

On Slack and n8n

Search returns only twenty results

WhyFrom node version 2.7 search returns 20 per request and is limited to roughly 10 requests a minute.

Paginate deliberately and narrow with the Channel Types and date filters rather than fetching everything.

On Slack and n8n

Messages drop during a loop

WhySlack's posting limit of roughly one message per second per channel, with no guarantee beyond short bursts.

Batch the output into a single message. This is the same constraint every Slack integration in this directory hits.

On Slack and n8n

A channel receives no calendar notifications at all

WhyThe Google Calendar app has not been invited to that channel. It is a per-channel step, not an app-wide setting.

Type /invite @google calendar in the channel. Then configure the notifications from the app's Home tab under Channel Notifications.

On Slack and Google

Events are missing or out of date in the app

WhyThe authorisation has gone stale. Slack documents this as its own fix rather than a support path.

Open the Google Calendar page in the Slack Marketplace, Configuration tab, click Revoke under Your Authorization, then Add to Slack to reconnect.

On Slack and Google

There is no daily or weekly schedule option

WhyThe workspace is on the Free plan. Slack marks the recurring schedule notification as a paid-plan feature in two places.

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.

On Slack and Google

The integration works for the admin and nobody else

WhyInstalling the app and connecting an account are different jobs. The admin who installed it connected themselves in the process.

Either chase every member through the Home tab, or enable domain-wide authentication and connect everybody at once.

On Slack and Google

A member wants to disconnect their Google account and cannot

WhyDomain-wide authentication is enabled, and Slack documents that members cannot disconnect while it is.

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.

On Slack and Google

Drive is connected and Calendar is not, or the reverse

WhyThey are two separate apps with separate installs, separate authorisations and separate Add domain steps.

Repeat every step for the second app. A domain verified for one is not verified for the other.

On Slack and Google

Somebody shared a Drive file nobody in the channel can open

WhySlack prompts to adjust file permissions when members lack access, and the prompt can be dismissed.

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.

On Slack and Google

The Agents and tools tab is not in the sidebar

WhySlack renamed it, and older workspaces still show the previous label.

Look for a Tools tab instead, and click More if neither is visible. Slack notes this on both app articles.

On Slack and Google

Apollo

37 documented failures across five integrations, all of them on the Apollo hub.

The waterfall never returns a phone number

WhyApollo requires a webhook_url on every waterfall request and phone results are not in the synchronous response.

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.

On Apollo and Reverse Contact, which needs a plan upgrade on one side

The credit burn is far higher than the pilot suggested

WhyA waterfall was ordered by coverage rather than by what a miss costs, so the rows nobody could resolve were discovered expensively.

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.

On Apollo and Reverse Contact, which needs a plan upgrade on one side

A search was run on rows that already had an email

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

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.

On Apollo and Reverse Contact, which needs a plan upgrade on one side

The verified emails bounced

WhyResolution and deliverability are two different claims, and neither provider's match is a delivery guarantee.

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.

On Apollo and Reverse Contact, which needs a plan upgrade on one side

A 429 from Apollo on a backfill

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

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.

On Apollo and Reverse Contact, which needs a plan upgrade on one side

429 DAILY_EXTRACTION_LIMIT_EXCEEDED on an Unlimited plan

WhyReverse Contact's covered calls are unmetered up to 100,000 profiles per workspace per UTC day and refused after that until midnight UTC.

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.

On Apollo and Reverse Contact, which needs a plan upgrade on one side

The two providers disagree about where somebody works

WhyA cached database is as current as its last refresh, and the two corpora are refreshed on different schedules.

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.

On Apollo and Reverse Contact, which needs a plan upgrade on one side

The comparison chart somebody sent does not match either vendor's site

WhyVendors publish figures for their competitors. ZoomInfo's own site gives Apollo 270M contacts and 70M companies while Apollo publishes 240M and 30M.

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.

On Apollo and Reverse Contact, which needs a plan upgrade on one side

There is no Connect option beside Slack

WhyThe Slack integration is team-wide and only an Apollo admin can connect it.

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.

On Apollo and Slack

Notifications were configured and half of them never arrive

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

Set both. Apollo documents the separation explicitly, and it is the most common misconfiguration on this pair.

On Apollo and Slack

No recommendations ever arrive unprompted

WhyAgents need a professional or organization plan. On a lower plan this is a surface you use rather than one that contacts you.

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.

On Apollo and Slack

Email opens and clicks are not reaching Slack

WhyThey are in neither notification screen. Apollo routes engagement alerts through the Chrome extension or through workflows.

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.

On Apollo and Slack

A rep cannot do something in Slack that a colleague can

WhyWorking 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 the permission profile in Apollo rather than looking for a Slack setting. There is no Slack-side permission model to adjust.

On Apollo and Slack

Credits went down faster than anybody expected

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

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.

On Apollo and Slack

A request returned nothing useful

WhyApollo's own guidance is to be specific and to chain requests rather than asking for everything at once.

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.

On Apollo and Slack

A sequence could not be added to

WhyThe documented chain adds contacts to lists and sequences that already exist. Creating them is not part of it.

Build the sequence in Apollo first. This is the same prerequisite every sequencer pair in this directory has.

On Apollo and Slack

The extension stopped returning anything on LinkedIn pages

WhyLinkedIn states that tools in this category may become non-operational without notice, and practitioners report exactly that happening.

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.

On Apollo and LinkedIn

Credits are gone and nobody did a bulk job

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

Agree as a team when a phone number is worth revealing. The habit, not the volume, is what empties the allowance.

On Apollo and LinkedIn

Legal asked who approved this and nobody had

WhyThere is no admin install. One rep adds a browser extension and the company has adopted a tool.

Decide the policy explicitly. This is the only integration in the directory where the governance gap is the default state rather than a misconfiguration.

On Apollo and LinkedIn

EU contacts are in a sequence that should not have them

WhyApollo does not remove EU-based or UK-based contacts, and says so.

Filter before the sequence, in Apollo or in whatever sits downstream. Nothing upstream will do it.

On Apollo and LinkedIn

An email bounced that Apollo showed as verified

WhyVerification is a claim about the address at some point in time, not a guarantee of deliverability today.

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.

On Apollo and LinkedIn

Insufficient access on cross reference ID

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

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.

On Apollo and Salesforce, which needs a plan upgrade on one side

Syncing started before the mapping was finished

WhyThe six hour configuration window expired. On a paid plan Apollo enables syncing automatically at that point, whether or not anybody was ready.

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.

On Apollo and Salesforce, which needs a plan upgrade on one side

Apollo is still writing after push was switched off

WhyPush settings govern net new contacts saved in Apollo and ones imported from a CSV. Updates to contacts that already exist push automatically regardless.

Control the field mapping rather than the push toggle. A field Apollo must never write is a field Apollo must not be mapped to.

On Apollo and Salesforce, which needs a plan upgrade on one side

A contact landed on the wrong account

WhyThe contact matched more than one existing Salesforce account, and Apollo documents assigning one at random in that case.

Use consistent account naming, or push only contacts whose accounts already exist. There is no tie-break setting to configure.

On Apollo and Salesforce, which needs a plan upgrade on one side

Accounts are appearing that nobody pushed

WhyPushing a net new contact creates or updates its linked account even with Push accounts off, because Salesforce requires every contact to have one.

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.

On Apollo and Salesforce, which needs a plan upgrade on one side

Contacts with no stage are not reaching Salesforce

WhyPush based on certain stages excludes contacts with no stage unless No stage is explicitly selected in the list.

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.

On Apollo and Salesforce, which needs a plan upgrade on one side

A sync error survived upgrading the Salesforce edition

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

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.

On Apollo and Salesforce, which needs a plan upgrade on one side

The migrate option for the managed package is not there

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

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.

On Apollo and Salesforce, which needs a plan upgrade on one side

The team cannot see most of the Outreach sequences

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

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.

On Apollo and Outreach, which needs a plan upgrade on one side

A sequence you just created is not in the list

WhyApollo's cached copy of Outreach sequences and mailboxes is stale, or the sequence is inactive.

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.

On Apollo and Outreach, which needs a plan upgrade on one side

A push of 200 enrolled 170

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

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.

On Apollo and Outreach, which needs a plan upgrade on one side

A merge field is rendering empty in Outreach

WhyThe field is outside the documented thirteen, or Apollo does not hold it for that contact. Neither case produces an error.

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.

On Apollo and Outreach, which needs a plan upgrade on one side

Insufficient credits when the workspace clearly has credits

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

Try a smaller batch, and review the waterfall enrichment settings, which is what Apollo's own documentation suggests for this error.

On Apollo and Outreach, which needs a plan upgrade on one side

Mailbox rotation is not available on a CSV push

WhyDocumented: rotation cannot be selected when contacts are added by CSV.

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.

On Apollo and Outreach, which needs a plan upgrade on one side

A contact in Apollo has no Outreach shortcut

WhyThe push did not complete. Apollo creates the shortcut between the two records as part of a successful push.

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.

On Apollo and Outreach, which needs a plan upgrade on one side

Contacts added by a workflow are not in the sequence yet

WhyA workflow or the outbound copilot enrols on its own trigger and schedule, such as hourly or daily, rather than immediately.

Check the workflow's trigger conditions before debugging the integration. This is the one route where a delay is expected rather than a symptom.

On Apollo and Outreach, which needs a plan upgrade on one side

LinkedIn

25 documented failures across four integrations, all of them on the LinkedIn hub.

A list exported six months ago is full of wrong job titles

WhyA profile export is a snapshot, and LinkedIn data ages faster than most because the field that matters most is the one people change.

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.

On LinkedIn and Reverse Contact

The backfill cost nearly three times the estimate

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

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.

On LinkedIn and Reverse Contact

429 DAILY_EXTRACTION_LIMIT_EXCEEDED on an Unlimited plan

WhyThe covered calls are unmetered up to 100,000 profiles per workspace per UTC day, after which they are refused until midnight UTC.

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.

On LinkedIn and Reverse Contact

The matches look plausible and the campaign underperformed

WhyA thin identifier such as a name and a company was accepted without a precision threshold, so low-confidence matches were written as facts.

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.

On LinkedIn and Reverse Contact

Legal asked which agreement covers this and nobody had an answer

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

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.

On LinkedIn and Reverse Contact

A rep's LinkedIn account was restricted

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

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.

On LinkedIn and Reverse Contact

Everything stopped, including the calls that were free

WhyBelow 2 Reverse Contact credits the free Check endpoints are paused as well and answer 402 NO_CREDITS.

Watch quotas.workspace.credits.left on every response, and check GET /v2/usage on a schedule because it keeps answering whatever the balance.

On LinkedIn and Reverse Contact

The tile shows an error such as CRM not connected

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

Reproduce it in Sales Navigator itself. If it happens there too, it is a LinkedIn support conversation and no Outreach setting will touch it.

On LinkedIn and Outreach, which needs a plan upgrade on one side

The tile found the wrong person or company

WhyMatching picked an incorrect record.

Expand the window and select Not the right person to unlink, then search for the correct match.

On LinkedIn and Outreach, which needs a plan upgrade on one side

The tile found nobody at all

WhyNo match, which is a normal outcome rather than a failure.

Use the back button beside the not-found message to search for the individual or the company by hand.

On LinkedIn and Outreach, which needs a plan upgrade on one side

A rep saved a lead and it never appeared in Outreach

WhySave as a lead creates a lead in Sales Navigator, not a prospect in Outreach.

Nothing to fix. Tell the team what the button does, because the label invites exactly this mistake.

On LinkedIn and Outreach, which needs a plan upgrade on one side

LinkedIn activity is missing from Salesforce

WhyThe Outreach Salesforce plugin is out of date, which is what syncs LinkedIn tasks across.

Update the plugin. The tasks already completed will not retroactively appear, so do this before the first sequence rather than after the first report.

On LinkedIn and Outreach, which needs a plan upgrade on one side

You cannot scroll inside the tile

WhyThere are no scrollbars in the embedded view.

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.

On LinkedIn and Outreach, which needs a plan upgrade on one side

There is no LinkedIn trigger in the dropdown

WhyThere are none. Zapier documents that no triggers are available for LinkedIn.

Trigger the Zap from somewhere else. If the LinkedIn event itself is what you need, this integration cannot provide it.

On LinkedIn and Zapier

You cannot look up a person or a company

WhyNo search actions are available either.

Use a data provider with an API for the lookup and keep Zapier for the posting step.

On LinkedIn and Zapier

The company update action fails

WhyYou are not an administrator of the page.

Get the role, or post from the profile instead. This is a LinkedIn permission rather than a Zapier one.

On LinkedIn and Zapier

Posts stop going out for no visible reason

WhyLinkedIn applies rate limits to its APIs and does not publish numbers for this surface.

Space the posts out and treat the schedule as a budget. There is no figure to design against, which is itself the answer.

On LinkedIn and Zapier

The organisation post fails and the error says nothing about the URN

WhyThe full urn:li:company:03262013 form was entered where n8n documents the bare number 03262013.

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.

On LinkedIn and n8n

Posting as the organisation is refused although the scope is ticked

Whyw_organization_social needs LinkedIn's Community Management App Review completed. Requesting the scope and passing the review are two different things.

Submit the review, and post as a member in the meantime. There is no configuration that substitutes for it.

On LinkedIn and n8n

The app cannot be created at all

WhyA LinkedIn Company Page is a prerequisite for a developer app, not an optional association.

Create the page during app creation, which LinkedIn allows. A personal account with no page cannot complete the step.

On LinkedIn and n8n

The credential authorises but the profile call returns nothing

WhyAn older app may be issuing r_liteprofile and r_emailaddress where the newer products issue profile and email. The two sets are not interchangeable.

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.

On LinkedIn and n8n

429 responses with no idea what the limit was

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

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.

On LinkedIn and n8n

A 429 arrived although usage looked fine

WhyLinkedIn documents returning 429 in rare cases as infrastructure protection rather than as a quota breach, and says service returns to normal automatically.

Retry with a backoff rather than redesigning. If it persists across a day, it is a quota rather than protection.

On LinkedIn and n8n

The quota warning email arrived after the workflow had already failed

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

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.

On LinkedIn and n8n

A workflow was supposed to start when something happened on LinkedIn

WhyThere is no LinkedIn trigger node and no read operation. Nothing on LinkedIn can start an n8n workflow through the sanctioned route.

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.

On LinkedIn and n8n

Outreach

fourteen documented failures across two integrations, all of them on the Outreach hub.

The first email went out with the old job title in it

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

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.

On Outreach and Reverse Contact

A beautifully personalised email reached somebody who left the company

WhyThe enrichment wrote a title and nobody compared the returned current employer with the account the prospect sits under.

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.

On Outreach and Reverse Contact

A 429 and a rateLimitExceeded error

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

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.

On Outreach and Reverse Contact

The limit changed and the backfill stopped halfway

WhyOutreach states that it reserves the right to adjust API rate limits at any time to safeguard platform performance and ensure fair use.

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.

On Outreach and Reverse Contact

The prospect record was updated and the cadence step did not change

WhySteps already rendered and sent are gone, and a step scheduled for later picks up the current record. There is nothing to re-render.

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.

On Outreach and Reverse Contact

Everything stopped, including the calls that were free

WhyBelow 2 Reverse Contact credits the free Check endpoints are paused as well and answer 402 NO_CREDITS, because the fetch a check precedes can itself cost 2.

Watch quotas.workspace.credits.left, which rides on every response. GET /v2/usage keeps answering whatever the balance, so a scheduled balance check never fails for the reason the lookup did.

On Outreach and Reverse Contact

The resolved rate is far below the published match rate

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

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.

On Outreach and Reverse Contact

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.

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.

On Outreach and Reverse Contact

The same prospect got two first-touch emails

WhyAdd Prospect to Sequence was run twice. The action has no duplicate protection and reports success both times.

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.

On Outreach and Zapier

A Zap that enrols people stopped working after somebody edited the sequence

WhyThe Sequence ID was hard-coded and rebuilding a sequence changes it.

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.

On Outreach and Zapier

The trigger takes a quarter of an hour to fire

WhyIt is Completed Sequence Task, the only polling trigger, which Zapier checks every 15 minutes on the Free plan.

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.

On Outreach and Zapier

Create Prospect fails on a missing or invalid id

WhyThe action takes Account ID, Opportunity IDs, Stage ID, Persona ID and Owner ID, and none of those accepts a name.

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.

On Outreach and Zapier

A bulk run exhausted somebody's Outreach allowance

WhyOutreach meters 10,000 requests an hour per user, and the connection authenticated as a person rather than as a service account.

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.

On Outreach and Zapier

The Zapier bill is far higher than the number of Zaps suggests

WhyThe meter is per step. An enrolment is at least two steps, and a filter and a lookup make it four.

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.

On Outreach and Zapier

Attio

eight documented failures across one integration, all of them on the Attio hub.

The Parse JSON block failed and the workflow stopped

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

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.

On Attio and Reverse Contact

The attributes came back empty and nothing errored

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

Nothing is broken. Put a Condition block before the record update so an empty answer writes nothing, rather than writing nothing over something.

On Attio and Reverse Contact

A value a rep typed has been replaced by a blank

WhyThe record update block wrote the empty result of an unresolved lookup, because no condition stood between them.

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.

On Attio and Reverse Contact

The request is rejected and the header looks right

WhyAttio supports custom headers, states that forbidden header names are not supported, and says it may block others as needed to maintain platform security.

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.

On Attio and Reverse Contact

Everything stopped at once, including the free checks

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

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.

On Attio and Reverse Contact

A 429 on a workflow that was fine yesterday

WhyReverse Contact applies a minute limit per workspace, shared with every other integration on it, and answers 429 past it.

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.

On Attio and Reverse Contact

The HTTP block timed out

WhyAttio documents a 20-second timeout on Send HTTP request, and the live endpoints answer with a task rather than a record.

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.

On Attio and Reverse Contact

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.

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.

On Attio and Reverse Contact

Pipedrive

eight documented failures across one integration.

The webhook action is not in the automation builder

WhyPipedrive states that if webhooks are not pre-built you cannot add the webhook action, and that existing webhooks cannot be re-used for automations.

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.

On Pipedrive and Reverse Contact

The webhook will not save and the URL looks fine

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

Add the trailing character. It is the least guessable requirement on this page and it produces no useful error message.

On Pipedrive and Reverse Contact

The automation fires and nothing is ever enriched

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

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.

On Pipedrive and Reverse Contact

The whole automation execution failed

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

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.

On Pipedrive and Reverse Contact

429 on the write-back, with the daily budget nowhere near spent

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

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.

On Pipedrive and Reverse Contact

A 403 and an HTML page from Cloudflare

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

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.

On Pipedrive and Reverse Contact

The budget ran out earlier in the day than expected

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

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.

On Pipedrive and Reverse Contact

The reset did not happen when the day did

WhyPipedrive documents that the token budget resets at midnight in the server timezone, which may not be aligned with the timezone you are in.

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.

On Pipedrive and Reverse Contact

Zoho

eight documented failures across one integration.

There is no option to create a function anywhere

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

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.

On Zoho and Reverse Contact

The function was terminated partway through

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

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.

On Zoho and Reverse Contact

The function hit the lines of execution limit

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

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.

On Zoho and Reverse Contact

The API credit pool emptied and nothing called the API

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

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.

On Zoho and Reverse Contact

TOO_MANY_REQUESTS from a function making very few calls

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

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.

On Zoho and Reverse Contact

The function wrote an empty value over a real one

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

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.

On Zoho and Reverse Contact

A live refresh timed out inside the workflow function

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

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.

On Zoho and Reverse Contact

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.

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.

On Zoho and Reverse Contact

monday

eight documented failures across one integration.

DAILY_LIMIT_EXCEEDED halfway through the afternoon

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

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.

On monday and Reverse Contact

The webhook will not register at all

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

Implement the challenge before anything else. It is four lines in most frameworks, and no webhook exists until it passes.

On monday and Reverse Contact

An end user turned the integration off

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

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.

On monday and Reverse Contact

The write reported success and the column is empty

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

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.

On monday and Reverse Contact

ComplexityException on a query that looks small

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

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.

On monday and Reverse Contact

Retries made everything worse

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

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.

On monday and Reverse Contact

The lookup came back empty and the column was blanked

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

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.

On monday and Reverse Contact

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.

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.

On monday and Reverse Contact

ZoomInfo

eight documented failures across one integration, all of them on the ZoomInfo hub.

The ZoomInfo credits lasted and the record limit did not

WhyRe-enriching a record under management consumes no credit and still counts against the record limit, which are two separate budgets.

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.

On ZoomInfo and Reverse Contact, which needs a plan upgrade on one side

A 429 from ZoomInfo while well under the per-second limit

WhyThree windows are evaluated simultaneously, and the hour and day windows are rolling rather than fixed, so a burst an hour ago still counts.

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.

On ZoomInfo and Reverse Contact, which needs a plan upgrade on one side

The rate-limit headers are not there

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

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.

On ZoomInfo and Reverse Contact, which needs a plan upgrade on one side

A bookmarked ZoomInfo doc now redirects

Whydocs.zoominfo.com returns a permanent redirect to docs.gtm.ai.

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.

On ZoomInfo and Reverse Contact, which needs a plan upgrade on one side

The waterfall produced a worse list than the single provider did

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

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.

On ZoomInfo and Reverse Contact, which needs a plan upgrade on one side

The two providers disagree about where somebody works

WhyTwo corpora refreshed on different schedules will differ, and the difference is usually recency rather than accuracy.

Compare update dates instead of values. Reverse Contact's free check returns when the profile was last updated, which settles most disagreements for nothing.

On ZoomInfo and Reverse Contact, which needs a plan upgrade on one side

429 DAILY_EXTRACTION_LIMIT_EXCEEDED on an Unlimited plan

WhyReverse Contact's covered calls are unmetered up to 100,000 profiles per workspace per UTC day and refused until midnight UTC after that.

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.

On ZoomInfo and Reverse Contact, which needs a plan upgrade on one side

A comparison chart does not match either vendor's own site

WhyVendors publish figures about competitors. ZoomInfo's own site gives Apollo 270M contacts and 70M companies while Apollo publishes 240M and 30M.

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.

On ZoomInfo and Reverse Contact, which needs a plan upgrade on one side

n8n

eight documented failures across one integration, all of them on the n8n hub.

The workflow stops on a contact who is not in the database

WhyThe HTTP Request node reports success only on a 2xx by default, and a confident null is not a 2xx.

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.

On n8n and Reverse Contact

A 429 on a run that worked fine on a shorter list

WhyReverse Contact applies a minute limit per workspace, shared with every other integration on it, and answers 429 past it.

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.

On n8n and Reverse Contact

The poll loop never finishes

WhyA live job ends at succeeded or errored, and Reverse Contact documents the wait as usually seconds and possibly tens of minutes.

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.

On n8n and Reverse Contact

A live call returned nothing to map

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

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.

On n8n and Reverse Contact

The result never arrived and the credit was spent anyway

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

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.

On n8n and Reverse Contact

Everything failed at once, including the calls that were free

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

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.

On n8n and Reverse Contact

An endpoint that worked last week returns nothing

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

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.

On n8n and Reverse Contact

A search cost far more than the number of requests suggested

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

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.

On n8n and Reverse Contact

Zapier

eight documented failures across one integration, all of them on the Zapier hub.

The Zap reports success and the field in the CRM is empty

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

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.

On Zapier and Reverse Contact

The task count is far higher than the number of records

WhyZapier charges a task for every step that runs, not per Zap and not per record, so step count multiplies the bill.

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.

On Zapier and Reverse Contact

The Zap re-enriches people it already enriched

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

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.

On Zapier and Reverse Contact

Everything stopped, including the steps that were free

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

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.

On Zapier and Reverse Contact

A 429 on a Zap that was working yesterday

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

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.

On Zapier and Reverse Contact

A live refresh never returns anything to map

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

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.

On Zapier and Reverse Contact

Credits expired before they were spent

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

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.

On Zapier and Reverse Contact

A search returns far more results than expected and costs more than expected

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

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.

On Zapier and Reverse Contact

Make

eight documented failures across one integration.

The module succeeded and the record got an empty field

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

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.

On Make and Reverse Contact

The operations count is far higher than the number of records

WhyMake charges an operation per module per bundle, so an iterator over a hundred records multiplies every module behind it by a hundred.

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.

On Make and Reverse Contact

The call you need has no module

WhyThe app publishes four modules. The freshness check, company lookup from a domain, search and the live endpoints are not among them.

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.

On Make and Reverse Contact

Everything stopped, including the calls that cost nothing

WhyBelow 2 credits the free Check endpoints are paused too and answer 402 NO_CREDITS, because the fetch a check precedes can itself cost 2.

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.

On Make and Reverse Contact

A 429 from a scenario that worked on a smaller list

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

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.

On Make and Reverse Contact

The poll loop runs forever

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

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.

On Make and Reverse Contact

A webhook result arrived as a delivery failure

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

Poll GET /v2/webhooks/:webhookId to collect the result you already paid for. The job is not lost, only the delivery was.

On Make and Reverse Contact

Credits expired before the scenario spent them

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

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.

On Make and Reverse Contact

Smartlead

eight documented failures across one integration.

The email went out with the fallback text instead of the enriched value

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

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.

On Smartlead and Reverse Contact

The upload reported success and the lead is not in the campaign

WhyAdd lead to campaign requires a campaign that already exists and is active. Campaigns are built in Smartlead, not through this pipeline.

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.

On Smartlead and Reverse Contact

429 after about a thousand requests

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

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.

On Smartlead and Reverse Contact

429 from one specific endpoint while everything else works

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

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.

On Smartlead and Reverse Contact

The API key turned up in a log

WhySmartlead documents authentication as api_key in the query string, and request lines are logged by proxies, error trackers and anything that records a URL.

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.

On Smartlead and Reverse Contact

A campaign reached somebody who left the company

WhyThe enrichment wrote a title and nothing compared the returned current employer against the company on the row.

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.

On Smartlead and Reverse Contact

Everything stopped, including the calls that were free

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

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.

On Smartlead and Reverse Contact

Credits expired before a campaign used them

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

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.

On Smartlead and Reverse Contact

lemlist

eight documented failures across one integration, all of them on the lemlist hub.

An authentication error that looks like a bad key

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

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.

On lemlist and Reverse Contact

The retry loop fired immediately and made things worse

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

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.

On lemlist and Reverse Contact

429 from a parallel worker

WhyThe limit is 20 requests per 2 seconds, applied to all routes and metered per API key rather than pooled across a team.

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.

On lemlist and Reverse Contact

The key is gone and nobody wrote it down

Whylemlist states that you will not be able to see the key again after generating it.

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.

On lemlist and Reverse Contact

A third of the campaign went out with fallback text

WhyA missing variable renders the fallback rather than stopping the send, which is the behaviour you want and makes an unenriched row invisible.

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.

On lemlist and Reverse Contact

The enrichment bill is double what the filled fields suggest

WhyTwo overlapping providers running unconditionally both charge for every row they can resolve, and most rows resolve on both.

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.

On lemlist and Reverse Contact

A connection request reached somebody who changed job

WhyNothing compared the returned current employer against the company on the row, and a multichannel campaign acts on more than one channel per row.

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.

On lemlist and Reverse Contact

Everything stopped, including the calls that were free

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

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.

On lemlist and Reverse Contact

Salesloft

eight documented failures across one integration.

A 429 on a sweep that worked in a test account

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

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.

On Salesloft and Reverse Contact

The backfill got slower the further it went

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

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.

On Salesloft and Reverse Contact

A call that used to be cheap is now expensive

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

Read x-ratelimit-endpoint-cost from live responses rather than holding a table of costs. The header is there precisely because the numbers move.

On Salesloft and Reverse Contact

Webhook events are being marked failed during deploys

WhyA failing webhook gets three retries 15 seconds apart and is then marked failed, which gives the receiver about 45 seconds in total.

Accept the webhook immediately, queue the work, and enrich asynchronously. A receiver that answers with the enrichment result cannot survive a restart.

On Salesloft and Reverse Contact

The private app stopped working when somebody left

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

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.

On Salesloft and Reverse Contact

A well-personalised email reached somebody who changed job

WhyThe enrichment wrote a new title and nothing compared the returned current employer against the account the person sits under.

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.

On Salesloft and Reverse Contact

Everything stopped, including the calls that were free

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

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.

On Salesloft and Reverse Contact

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.

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.

On Salesloft and Reverse Contact

Instantly

eight documented failures across one integration.

The pipeline worked in development and fails in production

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

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.

On Instantly and Reverse Contact

Two bulk jobs each got half the speed they expected

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

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.

On Instantly and Reverse Contact

429 from one endpoint while everything else runs fine

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

Take those out of any loop. No upgrade or pacing on the main budget affects them, because they are not governed by it.

On Instantly and Reverse Contact

The email went out with fallback text instead of the enriched value

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

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.

On Instantly and Reverse Contact

Thousands of people got an email they should not have

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

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.

On Instantly and Reverse Contact

Nobody can tell you which providers the registry holds

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

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.

On Instantly and Reverse Contact

Everything stopped, including the calls that were free

WhyBelow 2 Reverse Contact credits the free Check endpoints are paused as well and answer 402 NO_CREDITS, because the fetch a check precedes can itself cost 2.

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.

On Instantly and Reverse Contact

A quarter of the credits went in an afternoon

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

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.

On Instantly and Reverse Contact

ClickUp

eight documented failures across one integration, all of them on the ClickUp hub.

The Call webhook action is not in the list

WhyTask webhooks are listed as unavailable on Free Forever and on Unlimited and Core.

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.

On ClickUp and Reverse Contact, which needs a plan upgrade on one side

Every Automation in the Workspace stopped at once

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

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.

On ClickUp and Reverse Contact, which needs a plan upgrade on one side

The enrichment ran and the custom field is still empty

WhyThe automation sent the payload and nothing wrote the answer back. The Call webhook action has no documented way to read the HTTP response.

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.

On ClickUp and Reverse Contact, which needs a plan upgrade on one side

A 429 from ClickUp halfway through a backfill

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

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.

On ClickUp and Reverse Contact, which needs a plan upgrade on one side

Nobody can tell which API key the webhook is using

WhyClickUp states that URL headers are sensitive and that once saved the values cannot be viewed to edit them.

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.

On ClickUp and Reverse Contact, which needs a plan upgrade on one side

The dashboard shows the enriched field for one List only

WhyA custom field has to be added to the other Spaces and Lists before data from them can be combined in a single card.

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.

On ClickUp and Reverse Contact, which needs a plan upgrade on one side

A task that failed on Friday cannot be diagnosed on Monday

WhyAutomations usage history is one day on Free, Unlimited, Core and Business, and 30 days only from Business Plus.

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.

On ClickUp and Reverse Contact, which needs a plan upgrade on one side

Everything stopped, including the calls that were free

WhyBelow 2 Reverse Contact credits the free Check endpoints are paused as well and answer 402 NO_CREDITS.

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.

On ClickUp and Reverse Contact, which needs a plan upgrade on one side

Gong

eight documented failures across one integration, all of them on the Gong hub.

Reverse Contact is not in the data partner dropdown

WhyGong Enrich supports LeadIQ, Wiza, RocketReach, Lusha, ZoomInfo and Findymail, and the list is not extensible by the customer.

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.

On Gong and Reverse Contact

Enrich reported that the contact has left and did nothing else

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

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.

On Gong and Reverse Contact

A Gong credit was charged for an email we could not use

WhyReturned addresses are validated and a failing one is discarded, and Gong charges the credit anyway because the partner returned data.

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.

On Gong and Reverse Contact

Enrich again did nothing on a record we know is stale

WhyWithin 90 days Enrich skips data partners it has already queried for that contact, so a second attempt may have nobody left to ask.

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.

On Gong and Reverse Contact

A 429 from Gong halfway through a backfill nobody else was running

WhyThe limit is 3 calls a second and 10,000 a day at company level, shared with every other integration connected to Gong.

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.

On Gong and Reverse Contact

The sweep read one page of calls and reported success

WhyList endpoints page with a cursor, and a response carries a records field with the page size, page number and total.

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.

On Gong and Reverse Contact

A region came back with no data at all

WhyGong's enrichment controls carry settings to exclude people located in the European Union and people in California.

Check the exclusion settings before concluding anything about coverage. This is a configured policy rather than a gap in anybody's database.

On Gong and Reverse Contact

The integration broke after an endpoint rename

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

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.

On Gong and Reverse Contact

Google

eight documented failures across one integration, all of them on the Google hub.

The enrichment landed on the wrong person

WhyThe write was keyed on a row number and somebody sorted, filtered or inserted a row while the run was going.

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.

On Google and Reverse Contact

Exceeded maximum execution time

WhyApps Script allows 6 minutes per script execution and 30 seconds per custom function, on every account type.

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.

On Google and Reverse Contact

Credits were spent and the rows still look untried

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

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.

On Google and Reverse Contact

Two people ran it and one set of answers vanished

WhyA spreadsheet has no row locking, so concurrent writes resolve to whichever one landed last with no error raised.

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.

On Google and Reverse Contact

A formula in a cell is spending credits on its own

WhyA custom function re-runs whenever the sheet recalculates, and each run is another billed API call.

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.

On Google and Reverse Contact

Service invoked too many times for one day: urlfetch

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

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.

On Google and Reverse Contact

A 429 from the Sheets API during a write-heavy run

WhyWrites are limited to 60 a minute per user per project and 300 a minute per project, counted separately from reads.

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.

On Google and Reverse Contact

The whole thing broke and the only person who understood it has left

WhyA script in one person's account with the logic in their head, which is the normal end state of a spreadsheet pipeline.

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.

On Google and Reverse Contact

If a symptom you hit is not here, it is not in the dataset either, and that is worth telling us about rather than working around: the change log records our own corrections alongside the vendors' changes.

Most of these are a field that was never filled. That part we can fix.

A surprising number of integration failures are not failures: the record moved and arrived empty, so the sequence sent to a title nobody holds any more. Reverse Contact resolves an email, a domain or a profile URL into a verified people and company record, so the row is complete before anything reads it.

Free trial, no card required, and 500 credits to start.

FAQ

The error index, asked and answered

What is in it, where it came from, and what it is not.

Where do these come from?

Each one was read off a vendor's own knowledge base, developer documentation or pricing page while the integration guide for that pair was being written, and the guide cites the document it came from. None of them is reproduced from a forum post, and none is a guess about what might go wrong.

Why is the fix sometimes "buy a different plan"?

Because that is sometimes the honest answer. 196 of the 494 entries sit on an integration that needs a plan upgrade or a paid licence on one side, and in those cases no setting will do it. Saying so is more useful than a workaround that does not work.

My error message is not here.

Then it is not in the dataset, which covers 68 integrations rather than every integration that exists. The symptoms here are the ones a vendor documents for a pairing we have checked; a message produced by a browser extension, a plugin or a middleware layer in between will not be among them.

Is this the same text as the integration guides?

Yes. The symptom, the cause and the fix are the same three fields, rendered from the same records, because a second copy of a fact is a second thing that can go stale. This page indexes them by symptom and a guide reads them in the context of one pairing.

Does the filter hide anything from a crawler?

No. All 494 entries are in the HTML of this page whatever is typed in the box, and the filter only sets the hidden attribute. That is the same decision the integration matrix makes about its columns.

Checked by

Reverse Contact

We sell B2B people and company data, and we publish this directory. Every number on this page is derived from those records rather than typed, and each record was read from a vendor's own knowledge base, developer documentation or pricing page on the date below. Nothing on it is restated from a press release or a third-party listing.

Where a vendor publishes no public figure, this page says so rather than estimating, which is why no page here prints a cost per enriched record. Reverse Contact appears in this directory as a data provider and publishes it. No other vendor pays for placement, and every link out of a listing or a citation carries nofollow, including the ones that point at Reverse Contact. The only followed links on this page are the two calls to action and the reviewer.

Tier requirements, sync behaviour and documented limits change without notice. Confirm against your own contract before you budget. What has changed since · How we checked, and what we will not claim

Researched and written by

Eugene Suslov

Researched and wrote every page in this directory, and checked every tier requirement, sync direction and documented limit against the vendor's own knowledge base, developer documentation or pricing page.

Verified
2026-10-28
Sources
2 vendor documents
Paid placement
None

Tier requirements, sync behaviour and limits read from each vendor's own documentation in September, October and November 2026. Vendors change these without notice.

Reverse Contact appears in this directory as a data provider and publishes it. Every other tool is here on merit and nobody pays for placement.

Ask an assistant