n8n

Contacts and events from your n8n workflows.

The Instasent community node — n8n-nodes-instasent — installs from n8n's community nodes screen. After that any workflow can push contacts and events into your audience. It's the option technical teams tend to prefer: self-hosted, versionable, and yours.

What it brings in

Real time

Receives events in real time
An inbound webhook that accepts the n8n format.
Receives new contacts in real time
An inbound webhook that accepts contacts in the n8n format.
Triggers automations
Real-time events can start a flow the moment they arrive.
Feeds your segments
Use the contact data and the events to segment your audience.

Anything Instasent accepts

n8n does not bring a list of its own: it uses the Ingest API, so it can send any contact field and any event Instasent understands.

Event triggers

n8n does not bring a list of its own: it uses the Ingest API, so it can send any contact field and any event Instasent understands.

Ecommerce19
Contact behaviour10
CRM4
Meetings4
Payments4
Subscriptions3

See the full catalogue in the docs

How you connect it

This one runs the other way round. Instasent creates the data source and hands you the credentials — project UID, secret token and data source ID — and you finish the connection inside n8n.

You can create the Instasent side before you even have a n8n account. The data source waits, and starts filling up when data arrives.

1
In Instasent, add n8n and give the connection a name.
2
Copy the credentials Instasent shows you.
3
Install the Instasent app in n8n and paste them there.
4
Data starts arriving as soon as n8n sends the first one.

The step-by-step guide, the fields each connector maps and how consent is carried over live in our documentation. Read the setup guide

Once it's connected

Segment by real behaviour

What they bought, when they last bought, what they looked at and never came back to. The segment updates itself as new data arrives.

Send your first campaign

Message a segment directly, with RCS where the phone supports it and SMS everywhere else.

Trigger automations from events

An abandoned cart, a purchase, a form submission — the event arrives and the flow starts.

Ask Iris about it

Iris reads the data these connectors bring in, answers questions about your audience and prepares the campaign. You're the one who sends it.

Consent comes across with the contact

Marketing preferences are carried over with one rule: only an active opt-out becomes a refusal. Somebody who never said anything arrives with no preference set, not as a yes. It's the conservative reading, and it's the one that keeps you compliant.