# Activepieces

Connect Activepieces as a webhook data source: how the Instasent piece posts contacts and events into the Instasent ingest stream, what it syncs, how fields map to attributes, and how consent is controlled through the data you send.

**Language:** en
**Audience:** platform
**TLDR:** Webhook platform: Instasent creates the source and gives you the credentials (project UID, data source ID and API key) that you use in the Instasent piece, already preinstalled on Activepieces. Your flow posts contacts and events in real time. Consent depends on the attributes you map in the payload.
**Translation key:** platform.data-sources.connectors.activepieces
**Search keywords:** Activepieces, piece, Instasent piece, webhook, automation, no-code, workflow, ingest stream, connect Activepieces, Activepieces integration, send contacts, send events
**Related pages:** /platform/es/data-sources/connectors/activepieces, /platform/en/data-sources/connectors, /platform/en/data-sources/connectors/make, /platform/en/data-sources/connectors/zapier, /platform/en/data-sources/api-webhooks, /platform/en/consent
**Docs index (every page):** https://docs.instasent.com/llms.txt
**This zone's index:** https://docs.instasent.com/platform/en/llms.txt
**This page:** https://docs.instasent.com/platform/en/data-sources/connectors/activepieces/ (HTML) · https://docs.instasent.com/platform/en/data-sources/connectors/activepieces.md (Markdown)
**Other language (es):** https://docs.instasent.com/platform/es/data-sources/connectors/activepieces.md

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](/platform/en/data-sources/connectors#webhook-platforms-we-give-you-the-credentials)**:
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. Add the data source

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

#### 2. Configure the source

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

#### 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. 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. 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](/platform/en/data-sources/api-webhooks).

![The Activepieces connector page with its description, what it imports, and the contact fields it maps, with Install Activepieces to start](/platform/en/data-sources/images/activepieces--1-connect.png)
*The Activepieces connector page: what it brings into Instasent and the contact fields it maps, with Install Activepieces to start.*

## 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](/platform/en/data-sources/managing#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.** {/* VERIFY: this connector carries no dedicated marketing-consent signal; consent depends entirely on the attributes you map. */} 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](/platform/en/consent/marketing-preference-vs-suppression).

---

This is one page of the Instasent documentation. For the complete machine-readable index of every guide and API reference, fetch https://docs.instasent.com/llms.txt — start there for full context.