Skip to main content

Prerequisites

The connector should already be set up, with a Connector Profile and a Linked Account. See Getting Started on the ActiveCampaign connector page.

How ActiveCampaign webhooks are set up

There is nothing to configure in ActiveCampaign and no URL to copy. StackOne registers a single webhook on your account pointing at its own receiver, carrying every event you enable, and removes it again when the account is disconnected.

  • No callback URL to paste, and no verification step to complete.
  • The webhook is registered on the ActiveCampaign account that the API URL and API Key belong to.
  • Only the events you enable in StackOne are included in the subscription and delivered.
  • You can see it in ActiveCampaign under Settings > Developer > Webhooks, listed as StackOne.

When events fire

ActiveCampaign only sends an event if the action that caused it matches the webhook’s configured sources. StackOne enables all four, so events reach you however they happen.

  • By a contact — the contact subscribes, opens a campaign, clicks a link.
  • By any user — someone makes the change in the ActiveCampaign admin area.
  • By the API — an API call causes it, including calls StackOne makes on your behalf.
  • By system processes — ActiveCampaign automations, bounces and automated campaigns.

Available webhook events

The following ActiveCampaign events can be enabled. Only events selected in StackOne are included in the subscription — ActiveCampaign will not send events you have not subscribed to.

1

Contact and list events

Events on contacts, their notes and tags, and on lists.

  • Contact Tag Added (contact_tag_added) — Fires when a tag is added to a contact
  • Contact Tag Removed (contact_tag_removed) — Fires when a tag is removed from a contact
  • List Created (list_add) — Fires when a new list is created
  • Contact Subscribed (subscribe) — Fires when a contact is added (subscribes to a list)
  • Contact Note Added (subscriber_note) — Fires when a note is added to a contact
  • Contact Unsubscribed (unsubscribe) — Fires when a contact unsubscribes
  • Contact Updated (update) — Fires when a contact’s details are updated
2

Campaign and email events

Events on campaign sending and on how contacts engage with emails.

  • Email Bounced (bounce) — Fires when an email bounces after a campaign is sent
  • Campaign Link Clicked (click) — Fires when a contact clicks a link in a campaign
  • Campaign Forwarded (forward) — Fires when a contact forwards a campaign through the forward link
  • Campaign Opened (open) — Fires when a contact opens a campaign
  • Campaign Replied To (reply) — Fires when a contact replies to a campaign
  • Campaign Sending Started (sent) — Fires when a campaign starts sending
  • Campaign Shared (share) — Fires when a contact shares a campaign to Facebook or Twitter
3

Deal events

Events on deals, their notes and tasks, and on pipelines, stages and task types.

  • Deal Created (deal_add) — Fires when a new deal is created
  • Deal Note Added (deal_note_add) — Fires when a note is added to a deal
  • Deal Pipeline Created (deal_pipeline_add) — Fires when a new deal pipeline is created
  • Deal Stage Created (deal_stage_add) — Fires when a new deal stage is created
  • Deal Task Added (deal_task_add) — Fires when a task is added to a deal
  • Deal Task Completed (deal_task_complete) — Fires when a deal task is completed
  • Deal Task Type Created (deal_tasktype_add) — Fires when a new deal task type is created
  • Deal Updated (deal_update) — Fires when an existing deal is updated
4

SMS events

Events on SMS messages sent to and from contacts.

  • SMS Replied (sms_reply) — Fires when a contact replies to an SMS message
  • SMS Sent (sms_sent) — Fires when an SMS message is sent to a contact
  • SMS Unsubscribed (sms_unsub) — Fires when a contact unsubscribes via SMS

Verify

Your Connector should now be able to receive and process events. Try triggering an event and you should see an Event appear in the Connector logs.