Skip to main content

Trigger actions with inbound webhooks

Push external events into the platform to drive automations and updates.

Inbound webhooks let an external system (a CRM, e-commerce store, event platform, or your own app) notify the platform when something happens on your side — a purchase, a form submission, a status change — so the platform can react. A typical reaction is to add or update a subscriber, set a profile field, or start an automation that sends the right Edition at the right moment.

Before you begin​

  • An account with developer or admin permissions to create integrations and API credentials.
  • The inbound endpoint URL and any signing secret or API key issued for your account (confirm the exact steps in your account).
  • A destination for the event: the audience, profile field, or automation you want the webhook to affect.
  • The ability to send an HTTP POST request from your source system, and a JSON payload you control.

Steps​

  1. In the platform, create or open an inbound webhook / integration and note the generated endpoint URL and authentication secret.
  2. Map the fields in your incoming payload (for example email, name, or an event type) to subscriber profile fields, so the platform knows where each value goes.
  3. Choose the action to trigger — update the subscriber record, tag them, or enroll them in an automation.
  4. In your source system, configure it to POST the JSON payload to the endpoint on the relevant event, including the auth secret in the header your account expects.
  5. Send a test event and check the webhook's recent-activity or delivery log for a success response.

Result​

Each qualifying event from your external system reaches the platform, updates the matching subscriber, and fires the automation you selected — no manual import required.

Canonical terms: Author, Edition, Folder (Project Folder), Broadcast. See the Glossary.