Integration reference

ActiveCampaign Trigger and Action reference

Start Workflows from contact, campaign, deal, list, and SMS events, then manage CRM and marketing records through the ActiveCampaign API.

Authentication

Connect each customer's ActiveCampaign account with the API URL and API key from Settings → Developer. FastHook validates both values and stores them encrypted.

• Trigger account type: api_key; reconnect by replace_credentials.
• Action connection type: api_key; available modes: Connected ActiveCampaign account.

Create or reuse the account from a Trigger or Action dialog, or manage it under Settings → Connected accounts. See Authentication and permissions for scopes and access diagnostics, or Connected accounts for reuse, reconnect, revocation, and credential rotation.

Scopes and permissions

The Trigger manifest does not declare a fixed base OAuth scope list. Installation access, API credentials, or the selected event configuration can still control available resources.

Operation-specific requirements appear in the tables below. Custom event selections can add scopes dynamically, so the current Trigger or Action dialog remains authoritative for the exact consent request.

Use ActiveCampaign as a Trigger

The current provider manifest contains 27 available Trigger definitions. Representative definitions include:

• Contact Subscribed
• Contact Updated
• Deal Added
• Campaign Link Clicked

Choose the narrowest event definition that fits the Workflow. Configure provider-specific resource and event filters in the Source dialog before adding broader Workflow Filters.

Use ActiveCampaign Actions

The current Action manifest contains 39 operations. Representative Actions include:

• Create Contact
• Sync Contact
• Create Deal
• Add Contact to Automation

The Action editor reads its required permissions, fields, remote resource pickers, output schema, and rate limit from the provider manifest. Available fields can change with the selected operation and authentication mode.

Build a Workflow

1. Create a Source using a ActiveCampaign Trigger definition.
2. Create a Workflow with that Source as its Trigger.
3. Add the required ActiveCampaign Action and select the connected account.
4. Map Trigger or earlier-Step data into the Action fields with the field picker.
5. Add a Filter, Paths, Delay, or Transformation when the route needs it.
6. Activate the Workflow, produce a controlled event, and verify the run in Audit and in ActiveCampaign.

Troubleshooting ActiveCampaign

The account is missing or cannot be selected

Confirm the active FastHook team, provider, account status, and authentication mode. A disabled or revoked account cannot execute an Action.

A resource picker is empty

Verify that the connected provider identity can access the resource itself. OAuth consent does not add workspace, repository, channel, drive, project, base, or record permissions.

The editor asks for additional scopes

Reconnect the same account from the affected Trigger or Action so FastHook can request its current manifest scopes. Then reopen the editor and select the resource again.

An active Workflow returns 401, 403, or a permission error

Compare the selected operation’s access requirements below with the account recorded in Audit. Check provider-side membership and object access before repeating the Action.

The provider returns 429 or a temporary 5xx

Inspect the Step attempt and retryability in Audit. FastHook can retry temporary failures, but provider quotas and idempotency rules still apply.

Provider-specific checks

• Use the exact API URL shown under Settings → Developer. It normally ends in api-us1.com or activehosted.com and differs for every account.
• FastHook manages one account-level webhook containing the union of events used by active Sources. It updates that webhook when Sources change and removes it when no Source needs it.
• ActiveCampaign sends webhook fields as form data. FastHook expands bracketed field names into nested JSON, preserves the complete payload, and deduplicates repeat deliveries.
• Each managed webhook carries an encrypted private X-FastHook-Webhook-Token header. FastHook rejects callbacks whose header does not match before storing the event.
• The API permits five requests per second per account. FastHook schedules Actions within that limit and retries eligible rate-limit or service failures.
• Custom API Request is restricted to the connected account's /api/3 path and cannot override the host or Api-Token header.

Next

• Explore ActiveCampaign integrations
• Trigger configuration
• Action configuration
• Data mapping
• Error handling
• Authentication and permissions
• All automation integrations