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 Kit connector page.

How webhooks are set up

StackOne creates and manages the webhook subscription automatically when the account is connected, and removes it when the account is disconnected. There is nothing to configure in Kit and no URL to paste.

1

Connect your Kit account

Connect your Kit account in StackOne using OAuth 2.0. StackOne creates one Kit webhook endpoint named StackOne, subscribed to every event you enable. It appears on the Kit webhooks page. Do not edit or delete it there.

2

Enable the events you need

Enable the Kit events you want in StackOne. The endpoint subscribes to the enabled events only, so Kit does not send events that are not selected.

Available webhook events

The following Kit events can be enabled. Only events selected in StackOne are included in the subscription. Kit will not deliver events that are not subscribed.

1

Review subscriber lifecycle events

Events related to a subscriber’s status on the account.

  • Subscriber Created (subscriber.created) — Fired when a subscriber is added to the account.
  • Subscriber Activated (subscriber.activated) — Fired when a subscriber transitions into the active state.
  • Subscriber Unsubscribed (subscriber.unsubscribed) — Fired when a subscriber unsubscribes.
  • Subscriber Bounced (subscriber.bounced) — Fired when a subscriber’s email address hard-bounces.
  • Subscriber Complained (subscriber.complained) — Fired when a subscriber reports an email as spam.
2

Review subscriber engagement events

Events related to a subscriber’s forms, sequences, tags, and custom field values.

  • Subscriber Subscribed to Form (subscriber.subscribed_to_form) — Fired when a subscriber joins a form. Includes the form.
  • Subscriber Added to Sequence (subscriber.added_to_sequence) — Fired when a subscriber starts a sequence. Includes the sequence.
  • Subscriber Sequence Completed (subscriber.sequence_completed) — Fired when a subscriber finishes the last email of a sequence.
  • Subscriber Tag Added (subscriber.tag_added) — Fired when a tag is added to a subscriber. Includes the tag.
  • Subscriber Tag Removed (subscriber.tag_removed) — Fired when a tag is removed from a subscriber. Deleting a tag does not fire this event (see Tag Deleted).
  • Subscriber Custom Field Value Updated (subscriber.custom_field_value_updated) — Fired when a custom field value changes on a subscriber, once per changed field. Includes the field and its new value.
3

Review tag and custom field events

Events related to tags and custom fields defined on the account.

  • Tag Created (tag.created) — Fired when a tag is created.
  • Tag Deleted (tag.deleted) — Fired when a tag is deleted. It is removed from every subscriber at once, with no per-subscriber Tag Removed events.
  • Custom Field Created (custom_field.created) — Fired when a custom field is created.
  • Custom Field Deleted (custom_field.deleted) — Fired when a custom field is deleted.
4

Review sequence events

Events related to sequences (automated email series).

  • Sequence Created (sequence.created) — Fired when a sequence is created.
  • Sequence Deleted (sequence.deleted) — Fired when a sequence is deleted.
  • Sequence Published (sequence.published) — Fired when a sequence is published.
  • Sequence Disabled (sequence.disabled) — Fired when a sequence is disabled.
5

Review broadcast and post events

Events related to broadcasts and published posts. These carry a summary. Fetch the full content from the Kit API.

  • Broadcast Created (broadcast.created) — Fired when a broadcast is created.
  • Broadcast Sent (broadcast.sent) — Fired when a broadcast finishes sending.
  • Broadcast Deleted (broadcast.deleted) — Fired when a broadcast is deleted.
  • Post Published (post.published) — Fired when a post is published.

Delivery format

Details of how Kit delivers events to StackOne.

1

Review batched payloads

Each request carries a delivery_id and a list of events of the same type. A request usually contains a single event, but Kit batches bulk activity into requests of up to 100 events. StackOne splits the batch and routes each event to its handler.

2

Review retries and deduplication

Each event has a UUID id that stays the same if Kit re-sends it. Kit retries failed deliveries up to 8 times over about 41 hours, so the same event can arrive more than once. The emitted event ID is the ID of the affected subscriber, tag, custom field, sequence, broadcast, or post.

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.