n8n

n8n is a webhook platform: rather than reading your data directly, it lets you build a workflow that posts contacts and events into Instasent's ingest stream. Use it to connect Instasent to any tool n8n supports that doesn't have a native connector.

How to connect

n8n is a webhook platform: you don't create a credential on n8n's side — Instasent creates the source and gives you the credentials, and you use them in the Instasent nodes. You can do the Instasent side before you have anything set up on n8n; the source is created and waits for data in real time.

The Instasent nodes ship as a community package. Install them once from your n8n community-nodes settings by adding the n8n-nodes-instasent npm package; after that the Instasent nodes are available in your workflows.

1. 1

   Add the data source

   In Data sources, select Add data source and choose n8n from the Integrations section.

2. 2

   Configure the source

   Fill in the Configure step — Connection name, Default country, Regional settings / Locale and Timezone — and Instasent creates the source.

3. 3

   Copy your credentials

   Instasent shows the source's credentials under Setup instructions — the Project UID, the Data source ID and the API key. Keep them safe.

4. 4

   Install the Instasent nodes and build your workflow

   In your n8n community-nodes settings, install the n8n-nodes-instasent package. Then add an Instasent node to your workflow and use the credentials from the panel to send contacts and events to your source's stream.

5. 5

   Watch the stream log

   Back in Instasent, the source shows a stream log of the data arriving, so you can confirm your workflow is working.

For the endpoint shapes and the full credentials, see API & webhooks.

What it syncs

n8n sends whatever your workflow posts — typically contacts and events, in real time as the workflow runs. The payload follows the ingest format: a contact payload identifies the contact (contact_id); an event payload adds the event name and its parameters.

Field mapping

The fields you send are mapped to Instasent attributes the same way as any source — you decide in your workflow which values go into which fields, and confirm the mapping. See field mapping.

Consent mapping

n8n has no consent mapping of its own — it simply passes through the data your workflow sends. Consent is controlled by the columns and attributes you include in the payload. If you send the consent attributes (_accepts_marketing_*, _is_subscribed_*), the same rules apply as for any import: only set _accepts_marketing_* to false on an active opt-out; "no data" stays null. See Consent.