← All integrations

Campayn

15 operations0 webhooks

Campayn plugin for Corsair

Get started with Campayn on Corsair Hub

Complete your first operation in <1 min

Get started

Supported operations

  • Create ContactWrite

    Create a new contact in a contact list.

  • Delete ContactDestructive

    Delete a contact by contact ID.

  • Get ContactRead-only

    Get full contact details by contact ID.

  • Get ContactsRead-only

    List contacts for a contact list, with optional contact keyword filtering.

  • Unsubscribe ContactWrite

    Unsubscribe contacts from a list by contact ID or by email address.

FAQ

Install corsair and @corsair-dev/campayn, add the Campayn plugin, and connect with an API key. Then call methods like corsair.campayn.api.contacts.createContact() from your app. Corsair syncs data per tenant.

Yes. Campayn requires an API key from your Campayn account or developer dashboard. Create credentials with access that matches what you automate, then paste them into Corsair or connect through managed auth in Hub.

Yes. One Corsair client can hit Campayn, GitHub, Notion, Stripe, and the rest. Trigger Campayn from a webhook, push updates to Slack, or chain actions across plugins. Same tenant context across integrations, plain TypeScript.

Teams use Corsair for campayn plugin for corsair. Common builds include sync jobs, admin tooling, and agents that call Campayn APIs from your backend. Local DB entities let you query synced Campayn records without hitting the API on every read.

The SDK is open source. Self-host and you pay Corsair nothing for the integration layer. Hub bills for hosted auth and execution, not per Campayn API call. Hub has a generous free tier. For hobby projects you can probably run the whole thing on free. Paid plans start to matter with more tenants or heavier traffic.

We maintain @corsair-dev/campayn in the open repo. When Campayn ships API changes, upgrade the package. Your call sites stay typed. You should not need to rewrite the integration layer each time.

No. Corsair does not read your Campayn data or hold individual access credentials. Credentials stay in your database. API calls run on your instance. We do not store Campayn data on your behalf.