Activepieces

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

How to connect

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

The Instasent piece is preinstalled and already available on Activepieces, so on the cloud version there's nothing to install — you just use its actions with your credentials. On a self-hosted instance where it isn't present, install the @activepieces/piece-instasent piece.

1. 1

   Add the data source

   In Data sources, select Add data source and choose Activepieces 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

   Use the Instasent piece

   In your Activepieces flow, add the Instasent piece and use its actions to send contacts and events, entering the credentials from the panel. On self-hosted instances without it, install @activepieces/piece-instasent first. Contacts are added to your audience immediately.

5. 5

   Watch the stream log

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

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

What it syncs

Activepieces sends whatever your flow posts — typically contacts and events, in real time as the flow 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 flow which values go into which fields, and confirm the mapping. See field mapping.

Consent mapping

Activepieces has no consent mapping of its own — it simply passes through the data your flow 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.