API docsAgent tools

Workflow platforms

n8n integration

In short

How does Reply's n8n integration work?

Reply publishes a node for n8n, connected once with an API key and reused across workflows. It carries event triggers grouped by area and a focused set of contact and sequence actions: deliberately narrower than the full API, which remains available for anything the node does not cover.

At a glance

AvailabilityAvailable. The node is published for n8n; Reply-side access uses your API key
DirectionBoth: events out of Reply, actions into Reply
Sync timingEvent-driven, not on a sync cycle
What you needAn n8n instance, cloud or self-hosted, and your Reply API key
SurfacesSetup: in n8n, with your Reply API key. Note for agents: an assistant connected over MCP can perform the same contact and sequence actions directly, without a workflow in between
Does notCover the whole API – the node's action set is focused on contacts, statuses and sequences

Availability

The node is available in n8n's node library. Because n8n can be self-hosted, this is the usual choice for teams who want their automation to stay inside their own infrastructure.

Reply-side access is your API key, so the workflow acts with that key's permissions and counts against the same API limits as any other client.

How to connect n8n

Before you start

  • Copy your Reply API key from Settings → API key
  • Have an n8n instance ready, cloud or self-hosted

Connect

  1. In n8n, add a new step and search for Reply.
  2. Create a Reply API credential and paste your API key.
  3. Save. The credential is now available to every Reply node in every workflow.
  4. Choose a trigger or an action on the node.

What to expect

Triggers – events that start a workflow

The node groups its triggers by area, and each group also offers an all events variant that fires on anything in that group:

GroupEvents
Account healthEmail account connection lost · email account error
EmailSent · opened · link clicked · replied · bounced · reply categorized
LinkedInConnection sent · connection accepted · message sent · message replied · message categorized
SequenceContact called · contact finished · contact opted out

The all events variants are worth knowing about: they behave differently from selecting individual events, and picking one when you meant a specific event produces far more workflow runs than expected.

Actions: what a workflow can do in Reply

AreaActions
ContactsCreate · get · get many · update · delete
Contact statusUpdate status · clear status
SequencesAdd a contact to a sequence · get a sequence · archive a sequence

Where the node stops

The action set is focused on contacts, statuses and sequence membership. It is not the whole API. Reporting, templates, schedules, email accounts and the rest are reachable through an HTTP request node using the same API key; the node is a convenience layer, not a boundary.

Common problems

  • A workflow fires far too often – check whether you picked an all events trigger rather than a specific one.
  • The action you need is not on the node – use an HTTP request node against the API with the same key.
  • Nothing fires – confirm the event belongs to the API key's own scope; a teammate's activity does not reach it.
  • Actions started failing – a regenerated API key invalidates the credential everywhere it is used.

Pause or disconnect

Deactivate a workflow in n8n to stop it while keeping it. Deleting the Reply credential disables every workflow using it. Regenerating your Reply API key has the same effect.

FAQ

Is the node official?

Yes. Reply publishes it, and it is installed from n8n's node library.

Can I self-host?

Yes. Self-hosting n8n is the usual reason to choose it over a hosted automation platform.

Does the node cover the whole API?

No. It covers contacts, statuses and sequence membership. Use an HTTP request node with the same API key for anything else.

Why is my workflow running so often?

Most likely an all events trigger. Select the specific event instead.

Need help connecting n8n?

If the connection fails or data isn't syncing the way you expect, the Reply support team can check your integration settings with you. Open the Reply Help Center and send the team a message.

To get an answer faster, include:

  • which integration and which sync step is affected
  • what you expected to sync, and what happened instead
  • the error text from the integration's Logs, or a screenshot of it

Don't send passwords, API keys, or access tokens.

Build with Reply