Planned maintenance: Tue Dec 8, 11:30pm–12:30am ET (8:30–9:30pm PT / Wed 5:30–6:30am CET). Brief downtime possible (up to 15 minutes).

Status page
Skip to main content

How can we help?

Need help? Check out our documentation or contact support

Search

When Bevy sends a webhook

  • Updated

Bevy pushes a JSON webhook when a subscribed record is created or updated. Use this page to see which actions send a payload for each update type — not the field catalog.

When webhooks are configured and an update type is enabled, Bevy sends a POST to your HTTPS URL after a matching record is created or updated. Hard deletes are not announced as a separate webhook event. Field-level JSON shape lives in Webhook payloads — this page does not include sample payloads.

Turn update types on or off in Configure webhooks. If a type is off, Bevy does not send that payload — even when the record changes.

Note: Delivery is near real time after a subscribed save. It is not a fixed clock interval you schedule. For how webhooks work at a high level, see Introduction to webhooks in Bevy.

Chapter member — chaptermember

A payload is sent when a chapter member record is created or updated, if Send chapter member updates is enabled.

  • Someone joins a chapter — A new chaptermember record is created. Check created_date.
  • Someone leaves a chapter — The chaptermember record is updated. Check departure_date.

Tip: Chapter membership changes are not sent on the user webhook. Enable Send chapter member updates to receive them.

Chapter — chapter

A payload is sent when a chapter record is created or updated, if Send chapter updates is enabled.

  • A new chapter is created — A chapter record is created.
  • Chapter details change — The chapter record is updated (name, description, location, timezone, and other chapter fields).

Note: Chapter team membership can appear inside the chapter payload (chapter_team) when a chapter webhook fires. Adding or changing a chapter team member alone does not send a chapter webhook. Save a chapter field (or another chapter update) if you need a fresh chapter delivery that includes the current team list.

Event — event

A payload is sent when an event record is created or updated, if Send event updates is enabled. That includes status transitions.

  • A new event is created — An event record is created, often with status: Draft.
  • Event details change — Title, dates, venue, description, visibility, and similar fields.
  • An event is published or canceled — Check status: Draft, Published, or Canceled.
  • An event’s end date has passed — Bevy can send another event update while status remains Published so receivers can treat the event as concluded. Use status and the end date together — there is no separate “completed” webhook type.

Tip: Filter programmatically with status values: Draft, Published, Canceled.

Note: Calculated event values such as total_attendees or check-in counts do not by themselves trigger an event webhook. Those values change without saving the event record.

Attendee — attendee

A payload is sent when an attendee record is created or updated, if Send attendee updates is enabled. That covers registration, check-in, and cancellation.

  • Someone registers — An attendee record is created. status is registered.
  • Registration details change — The attendee record is updated.
  • Someone is checked in — The record is updated. status becomes checked-in and checkin_date is set.
  • Someone cancels — The record is updated. status becomes deleted and deleted_date is set. The row is not hard-deleted.

Important: Cancellations arrive as an update, not a delete event. Always check status and deleted_date.

Event survey entry — eventsurveyentry

A payload is sent when a survey entry is created, if Send event survey entry updates is enabled. Entries are not re-sent when someone later edits answers on the same submission. Use survey_type to see which survey was completed.

  • Pre-order form during registration — survey_type: pre_order. This is a separate eventsurveyentry from the attendee record created at the same time.
  • Post-order form — survey_type: post_order.
  • Post-event survey — survey_type: post_event.
  • Chapter team post-event survey — survey_type: post_event_team.

Event people — person

A payload is sent when a key person record is created or updated, if Send event people updates is enabled. Key people are speakers and similar roles managed from the event dashboard.

  • A key person is added — A person record is created.
  • Key person details change — Name, company, title, bio, photo, social handles, and similar fields.

User — user

A payload is sent when a user record is updated (including profile field changes), if Send user updates is enabled.

  • Someone creates an account or becomes a prospective user — After the account and profile are saved, you can receive a user payload. Prospective users are accounts created on someone else’s behalf (for example when adding an attendee or importing members with an email that is new to Bevy). Check date_joined for new accounts.
  • Profile data changes — Name, email, company, role, and other profile fields.

Note: Updating only last_login does not send a user webhook. Logins alone will not produce a delivery for every sign-in.

Important: Do not depend on a user webhook to detect account removal. When a user is removed or marked deleted, Bevy does not reliably send a user payload. Chapter membership changes also do not use the user webhook — enable Send chapter member updates for those.

Quick reference

Payload type When Bevy sends Watch for
chaptermember Created, updated created_date, departure_date
chapter Created, updated Chapter field saves — not team-only changes
event Created, updated status, dates; not calculated counts alone
attendee Created, updated status, checkin_date, deleted_date
eventsurveyentry Created survey_type (pre_order, post_order, post_event, post_event_team)
person Created, updated Key person create and field changes
user Updated (profile saves) Profile fields; not last_login-only; not reliable for removal

What does not send a webhook

  • An update type that is turned off in Webhooks settings.
  • Hard deletes of supported records (no separate delete event type).
  • last_login-only user updates.
  • Calculated event metrics that do not save the event row.
  • Chapter team roster changes that do not also save the chapter record.
  • Edits to survey answers after the original survey entry was created.

Next steps

  1. Confirm types and defaults in Configure webhooks.
  2. Map fields with Webhook payloads.
  3. Build verification and retries with Webhooks best practices.