Connectors

A connector is a native integration with an external platform. Unlike a CSV import, you authenticate once — with OAuth or an API key — and the connector then keeps the data flowing on its own: contacts, attributes and events, in real time or on a periodic sync. This page lists the connectors available in Instasent and explains how each connector page is laid out.

Available connectors

Connectors fall into two kinds in the creation grid.

Native integrations

Authenticate with the platform and Instasent reads its data directly:

• Shopify — ecommerce customers and orders.
• Klaviyo — contacts and events.
• ActiveCampaign
• WooCommerce
• PrestaShop
• Magento
• HighLevel (GoHighLevel)
• Hotmart
• Zoom
• Facebook Leads
• Google Sheets
• Salesforce (coming soon)
• Google Contacts
• MailChimp
• MailerLite — subscribers and groups.
• Intercom

Webhook platforms

No-code automation platforms that post into your ingest stream — the endpoint where Instasent receives incoming contacts and events. Instasent creates the source and gives you the credentials to finish on the other platform. Covered together with the Ingest API:

• Make, Zapier, Activepieces, n8n, Pabbly Connect, OptiMonk, Paperform, Typeform, StockAgile.

How connectors connect

Each connector connects in its own way, and the difference matters before you start: some need a credential you create on the source platform first, some hand you the credentials, and some need nothing more than your authorization. There are three types: Native OAuth, API key and webhook platforms.

Native OAuth

You authorize Instasent from the source platform: the panel sends you to the platform's own window, where you sign in and grant the requested permissions, and the platform returns you to Instasent already connected. You don't create or copy any key yourself. Shopify, Facebook Leads, Google Sheets and Google Contacts connect this way.

API key

You go to the source platform's settings first, create an API key there, and paste it into Instasent's connection screen. Instasent won't let you continue without a valid key — the credential is what authorizes the read. Klaviyo (a Public API Key and a Private API Key) and WooCommerce (a REST API key, which is a Consumer Key and Consumer Secret pair) are the documented examples.

Webhook platforms (we give you the credentials)

For the webhook platforms, Instasent creates the credentials and shows them to you. You pick the connector, fill in a short Configure step (Connection name, Default country, Regional settings / Locale, Timezone), and Instasent creates the source and displays its credentials under Setup instructions — the Project UID, the Secret token and the Data source ID. You then install the Instasent app on the other platform (Zapier, Make…) and finish there. You can create the Instasent side without even having an account or connection on the source yet — the source is created and waits for data in real time. Make, Zapier and the other webhook platforms work this way.

How a connector page is laid out

Every connector page follows the same four sections, in this order:

1. How to connect — the authentication and credentials it needs.
2. What it syncs — the data it brings in, the direction and the frequency.
3. Field mapping — how its fields map to Instasent attributes, and any quirks.
4. Consent mapping — how the platform's marketing status translates into Instasent's consent attributes. This is the critical, platform-specific part, and it always links to Consent.

Documented connectors

Every connector above is a leaf page built from the same four-section template; new connectors are added the same way as they ship.