Orchestration

The orchestration layer, and what it holds together

This is where the logic lives that no single vendor in the stack is willing to own.

orchestration 4 tools
layerOrchestration
forWorkflow and glue
tools here4
integrations23
with a guide23
checked Tool hubs 3 of 4
The short version

What this layer is actually for

Workflow and glue. In this directory that is Clay, n8n, Zapier and Make.

Orchestration tools exist because the integrations the vendors ship stop at the edge of what two companies agreed to build. Anything conditional, anything involving a third system, and anything the business changes monthly ends up here. That is what an iPaaS integration buys you: one connector that speaks HTTP to everything and belongs to no vendor in the chain.

The trade is explicit: these tools can reach anything with an HTTP API, and in exchange somebody has to maintain what they build. That is a different kind of cost from a native app, not a smaller one, and it is why this layer is usually where a stack is both most capable and most fragile.

In this layer

The 4 tools this directory covers in the orchestration layer

A tool can sit in more than one layer, and several here do. The layers on each card are the full set, not just this one.

The data layer

Whichever of these you connect, the integration moves the record. We fill it.

Start for free
Showing 4 of 4

n8n

Glue you can self-host
6 integrations
LayerOrchestration
Guides

n8n matters here because it removes the per-task meter and the data-residency argument in one move. If an integration in this directory has no native app and your security team will not accept a third-party cloud in the path, this is usually the answer.

  • Self-hostable, so records never leave infrastructure you control
  • An HTTP Request node covers any API without a dedicated node
  • Native HubSpot and Salesforce nodes for the common objects
Entry price$0 self-hosted Visit See the 6 integrations

Zapier

The widest app coverage, metered
6 integrations
LayerOrchestration
Guides

When a pair in this directory has no native integration, Zapier usually has both sides. You pay for that in tasks rather than seats, which is fine at low volume and stops being fine the moment an enrichment loop starts running per record.

  • HubSpot alone reaches 8,000+ apps through Zapier
  • The Zapier app has 173,000 installs on the HubSpot marketplace
  • Billed per task, so a per-record loop is the expensive shape
Entry price$0/mo Visit See the 6 integrations

Make

Branching logic without code
LayerOrchestration
Guides

Make earns its place in this directory on one specific job: custom field handling that native integrations skip. It comes up most often as the fallback when a native connector covers the standard objects and stops at the fields you actually filter on.

  • Full custom-field support where several native connectors have none
  • Visual branching, so one scenario can fan out per record type
  • Billed in operations, which counts every module run, not every record

A native integration is maintained by the vendor and shaped by them. An orchestrated one is shaped by you and maintained by you. Neither is free.

Across the edge

23 integrations that touch this layer

Each record carries the layers it spans, so an integration appears here when this layer is one of them. Start with how it is built, because a native app and a webhook you maintain are the same feature with completely different owners.

23 of these 23 have a full guide behind them, HubSpot and Clay and HubSpot and n8n among them. 4 of the 8 worked stacks here run on this layer, among them The CRM data layer and Signal to sequenced contact.

The data layer

Whichever of these you connect, the integration moves the record. We fill it.

Start for free
Showing 23 of 23
↔

HubSpot and Clay

Two-way sync
BuiltNativeBuilt on the API
WatchNeeds a higher plan

Read a filtered slice, fill the gaps, write it back, on a schedule. From Clay Growth up.

  • Moves: Contacts, Companies, Deals, Lists
  • Needs: Clay Growth or above, where CRM integrations start. Nothing extra on HubSpot.
Needs a higher plan · hours Read the guide
↔

HubSpot and Make

Two-way sync
BuiltZapier, Make or n8n
WatchNo app, you build it

A Super Admin has to approve it, and a scope added to a connection can never be removed.

  • Moves: Contacts, Companies, Deals, Custom objects
  • Needs: A HubSpot Super Admin to approve the app, and a developer account for webhook modules
Metered by usage · hours Read the guide
↔

Salesforce and Clay

Two-way sync
BuiltNativeBuilt on the API
WatchNeeds a higher plan

The same read, enrich, write loop, against an org with stricter rules.

  • Moves: Contacts, Companies, Deals, Lists
  • Needs: Clay Growth or above, a Salesforce edition with API access, and a full user licence to authenticate
Needs a higher plan · hours Read the guide
↔

Salesforce and Zapier

Two-way sync
BuiltZapier, Make or n8nMarketplace app

Five access tokens per org, and the sixth app silently revokes the first.

  • Moves: Contacts, Companies, Deals, Custom objects
  • Needs: A paid Zapier plan, a Salesforce edition with API access, and an admin to approve the app
Metered by usage · minutes Read the guide
↔

Salesforce and n8n

Two-way sync
BuiltZapier, Make or n8nBuilt on the API
WatchNo app, you build it

Connected Apps are on the way out, and n8n Cloud needs a permission admins lack by default.

  • Moves: Contacts, Companies, Deals, Tasks, Custom objects
  • Needs: An n8n instance, a Salesforce edition with API access, and an External Client App
Metered by usage · hours Read the guide
←

Clay and Apollo

One way, in
BuiltNative

A native provider column, and the cheapest first step in most waterfalls.

  • Moves: Contacts, Companies
  • Needs: Any Clay plan, plus your own Apollo account. Clay's catalogue marks every Apollo action as needing one.
Metered by usage · minutes Read the guide
→

Clay and LinkedIn

One way, out
BuiltNative
WatchNeeds a higher plan

An enriched audience pushed into Campaign Manager, people or whole accounts.

  • Moves: Contacts, Companies
  • Needs: Clay Growth or above, a LinkedIn Ads account with billing set up, and a role on that ad account above viewer
Needs a higher plan · minutes Read the guide
→

Clay and Smartlead

One way, out
BuiltNativeBuilt on the API

Push, look up, update and remove, on a campaign Clay cannot create.

  • Moves: Contacts, Lists
  • Needs: Clay Launch or above, a Smartlead API key, and a campaign that already exists
Metered by usage · minutes Read the guide
↔

Clay and Attio

Two-way sync
BuiltNative
WatchNeeds a higher plan

Write to objects you defined yourself, rather than to contacts and deals.

  • Moves: Contacts, Companies, Custom objects
  • Needs: Clay Growth or above, an Attio workspace, and an Attio workspace admin to authorise the connection
Needs a higher plan · hours Read the guide
↔

Clay and n8n

Two-way sync
BuiltBuilt on the APIZapier, Make or n8n
WatchNo app, you build itNeeds a higher plan

Webhook out of the table, into a workflow that can wait for an async job.

  • Moves: Contacts, Companies
  • Needs: An n8n instance, and Clay Growth or above, because both halves of this pair are Growth features
Needs a higher plan · hours Read the guide
→

Clay and Outreach

One way, out
BuiltNativeBuilt on the API

Four actions, and the one that matters adds an enriched row to a sequence.

  • Moves: Contacts, Lists
  • Needs: Clay Launch or above, an Outreach contract, and twelve read-write scopes you cannot refuse
Metered by usage · minutes Read the guide
→

Clay and lemlist

One way, out
BuiltNativeBuilt on the API

Three actions, an API key, and a campaign that has to exist first.

  • Moves: Contacts, Lists
  • Needs: Clay Launch or above, a lemlist API key, and a campaign that already exists
Metered by usage · minutes Read the guide
←
BuiltBuilt on the APIZapier, Make or n8n
WatchNo app, you build it

The route that handles async resolution, and the one a security team signs off on.

  • Moves: Contacts, Companies
  • Needs: An n8n instance, self-hosted or cloud, and a Reverse Contact API key
Metered by usage · hours Read the guide
←
BuiltNativeZapier, Make or n8n

A verified app with three modules and an escape hatch for everything else.

  • Moves: Contacts, Companies
  • Needs: A Make plan with enough operations, and a Reverse Contact API key
Metered by usage · minutes Read the guide
⋅

Slack and Zapier

Events only
BuiltZapier, Make or n8nMarketplace app

One message a second per channel, and a bot message cannot start a Zap.

  • Moves: Messages
  • Needs: A Zapier plan sized to your task volume, and a free app slot on a free Slack plan
Metered by usage · minutes Read the guide
↔

Slack and n8n

Two-way sync
BuiltZapier, Make or n8nBuilt on the API
WatchNo app, you build it

The trigger needs a bot token and the node wants OAuth, so you build both.

  • Moves: Messages
  • Needs: An n8n instance you host or rent, and a Slack app with the right token type
Metered by usage · hours Read the guide
↔

Outreach and Zapier

Two-way sync
BuiltZapier, Make or n8nMarketplace app

Five instant triggers, and the one you want most is the one that polls.

  • Moves: Contacts, Companies, Deals, Tasks, Activities
  • Needs: An Outreach contract, an Outreach account that can authorise the app, and a Zapier plan sized to your task volume
Metered by usage · minutes Read the guide
←

LinkedIn and Zapier

One way, in
BuiltZapier, Make or n8nMarketplace app

No triggers at all, so nothing on LinkedIn can ever start a Zap.

  • Moves: Messages
  • Needs: A Zapier plan, a LinkedIn account, and page admin rights for company posts
Metered by usage · minutes Read the guide
←

LinkedIn and n8n

One way, in
BuiltZapier, Make or n8nBuilt on the API
WatchNo app, you build it

One resource, one operation: create a post. That is the whole node.

  • Moves: Messages
  • Needs: An n8n instance and a LinkedIn app. Company posts need the organisation URN.
Metered by usage · minutes Read the guide
The data layer

Where Reverse Contact sits under this layer

Reverse Contact is not an orchestration tool and has no marketplace app in this layer. It is the data layer underneath it: one API that resolves an email, a domain or a profile URL into a verified people and company record, so that what this layer moves is worth moving. This directory documents 4 routes into this layer, 4 of them with a full guide.

Every documented route into a stack sits on the Reverse Contact hub.

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