ActiveCampaign

This connector uses the ActiveCampaign API v3.

Setup:

1. Sign in to ActiveCampaign → Settings → Developer. Two values:
   • URL (your account's API URL): https://{ACCOUNT}.api-us1.com (or .api-eu1.com, etc.)
   • Key: a long alphanumeric API key.
2. Set ACTIVECAMPAIGN_API_URL = the full URL from step 1 (no trailing slash, no /api/3).
3. Set ACTIVECAMPAIGN_API_KEY = the key.

Authentication: custom header Api-Token: ${ACTIVECAMPAIGN_API_KEY}.

Account-scoped base URL: every account has its own subdomain. The adapter substitutes {{ACTIVECAMPAIGN_API_URL}}/api/3 as the base. If you use OAuth2 instead of the API key, the URL is the same.

Contact model: every contact has email (primary key), plus optional firstName, lastName, phone. Custom fields are 'field values' — separate POSTs to /fieldValues. The adapter exposes both contact CRUD and field-value management.

Lists are static, Tags are flexible: lists need explicit subscribe operations and trigger double-opt-in by default. Tags are unlimited, free-form labels — easier for segmentation.

Status values for contact-list memberships: 1=Active, 2=Unsubscribed, 0=Pending double-opt-in confirmation. Pass these as integers in contactList.status.

Deals are CRM-side: separate from contacts (one deal links to one primary contact + one organization). Has stage_id (pipeline position), value, currency.

Pagination: most list endpoints support limit (max 100) + offset. ?include=... side-loads related resources.

Rate limits: ~5 req/sec per account on Plus/Pro, higher on Enterprise. On 429, back off.

Out of scope here: campaign content composition (use UI), automation creation (UI-only), site tracking JS, deep CRM custom-object schemas, eCommerce integrations.