AsyncAPI channel · ActiveCampaign · ActiveCampaign Webhooks

/activecampaign/webhook

Single subscriber endpoint that receives every ActiveCampaign webhook event configured for the registered URL. The `type` field on the form body identifies the event class. ActiveCampaign sends one event per HTTP POST.

Provider: ActiveCampaign AsyncAPI: v2.6.0 Spec: ActiveCampaign Webhooks Operations: 1 Messages: 27

Channel address

/activecampaign/webhook

Operations

publish
receiveActiveCampaignWebhook
Receive an ActiveCampaign webhook event

Messages

subscribe
A new contact is subscribed to a list.
Content-Type: application/x-www-form-urlencoded
unsubscribe
A contact unsubscribed from a list (optionally tied to a campaign).
Content-Type: application/x-www-form-urlencoded
update
A contact's details (fields, name, phone, etc.) were updated.
Content-Type: application/x-www-form-urlencoded
subscriber_note
A new note was added to a contact.
Content-Type: application/x-www-form-urlencoded
contact_task_add
A new task was assigned to a contact.
Content-Type: application/x-www-form-urlencoded
account_add
A new account record was created.
Content-Type: application/x-www-form-urlencoded
account_update
An existing account record was updated.
Content-Type: application/x-www-form-urlencoded
account_contact_add
A contact was associated with an account.
Content-Type: application/x-www-form-urlencoded
account_contact_update
An account contact association was updated.
Content-Type: application/x-www-form-urlencoded
list_add
A new list was created.
Content-Type: application/x-www-form-urlencoded
sent
A campaign starts sending.
Content-Type: application/x-www-form-urlencoded
open
A campaign message was opened by a contact.
Content-Type: application/x-www-form-urlencoded
click
A link in a campaign message was clicked by a contact.
Content-Type: application/x-www-form-urlencoded
reply
A contact replied to a campaign message.
Content-Type: application/x-www-form-urlencoded
forward
A contact forwarded a campaign using the built-in forward feature.
Content-Type: application/x-www-form-urlencoded
share
A contact shared a campaign to a social network.
Content-Type: application/x-www-form-urlencoded
bounce
A campaign message bounced.
Content-Type: application/x-www-form-urlencoded
deal_add
A new deal was created.
Content-Type: application/x-www-form-urlencoded
deal_update
An existing deal was updated.
Content-Type: application/x-www-form-urlencoded
deal_note_add
A note was attached to a deal.
Content-Type: application/x-www-form-urlencoded
deal_pipeline_add
A new sales pipeline was created.
Content-Type: application/x-www-form-urlencoded
deal_stage_add
A new pipeline stage was created.
Content-Type: application/x-www-form-urlencoded
deal_task_add
A task was added against a deal.
Content-Type: application/x-www-form-urlencoded
deal_tasktype_add
A new task type was defined for deals.
Content-Type: application/x-www-form-urlencoded
sms_sent
An SMS message was sent.
Content-Type: application/x-www-form-urlencoded
sms_reply
A recipient replied to an SMS message.
Content-Type: application/x-www-form-urlencoded
sms_unsub
A contact unsubscribed via SMS.
Content-Type: application/x-www-form-urlencoded

About AsyncAPI

The AsyncAPI specification describes event-driven APIs the way OpenAPI describes request/response APIs. A channel is the named pipe — a webhook URL, a Kafka topic, a WebSocket route, an MQTT subject — that producers and consumers publish or subscribe to. Each channel carries one or more messages with structured payloads, and an operation declares whether a given party sends or receives on that channel.

Browse every event-driven channel on the APIs.io network or compare with the broader Naftiko capability, Agent Skill, and MCP server surfaces of the same providers.