Pabbly Connect

Pabbly Connect 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 of the apps Pabbly Connect supports that don't have a native connector.

How to connect

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

1. 1

   Add the data source

   In Data sources, select Add data source and choose Pabbly Connect 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 Token. Keep them safe.

4. 4

   Add Instasent to your Pabbly workflow

   Add the Instasent shared app to your Pabbly Connect workflow and use its actions to send contacts and events, entering the credentials from the panel.

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

Pabbly Connect 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

Pabbly Connect 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.