Pro plan. ActiveCampaign works through a connection and HTTP steps, which are part of Pro and Agency (and the free trial). Anything you already have keeps working on every plan. See Plans and billing.
How it connects: ActiveCampaign’s API v3 with your key in the
Api-Token header. See ActiveCampaign’s Sync a contact’s data and Add a tag to contact docs. The requests and answers below follow ActiveCampaign’s docs.Before you start
- ActiveCampaign plan: the API is available on all plans; automations depend on the plan.
- Your API URL and key: in ActiveCampaign, open Settings > Developer.
- The tag’s id: create the tag (for example “LinkedIn reply”) and find its id in the tags list or with ActiveCampaign’s list tags endpoint.
1. Connect ActiveCampaign
In Kerux, open Integrations > Connections, click Connect on Custom API (under Developers):- How it signs in: API key in a header, Header name
Api-Token, paste the key. - Base URL: your API URL, for example
https://youraccount.api-us1.com
2. Sync the contact
In the follow-up campaign, add a Webhook / HTTP step namedac:
contact/sync finds the contact by email and updates it, or creates it. The answer (trimmed):
3. Add the tag
A second Webhook / HTTP step:20 with your tag’s id. In ActiveCampaign, start the automation with “Tag is added”.
Custom fields go in fieldValues inside contact, each with the field’s numeric id and the value (ActiveCampaign’s docs).
Test with one contact
In the follow-up campaign’s Builder, click Test to open Test on one contact. Check the contact, the tag and the automation in ActiveCampaign.Common errors
403 Forbidden
403 Forbidden
The key is wrong, or the Base URL belongs to another account. Copy both again from Settings > Developer.
422 with an email error
422 with an email error
The email is invalid. Check the contact’s email; a step whose email is empty waits instead of sending.
The automation doesn't start
The automation doesn't start
The tag id is wrong or the automation’s start trigger is a different tag. Check both in ActiveCampaign.