Skip to main content
Account events are published whenever accounts, customer contacts, or account-related entities (activities, notes, tasks, relationships) are created, updated, or deleted. These events are delivered through the platform events system.

Developer quickstart

Minimal handler (accounts only)

Checklist

  • Use eventId for idempotency to avoid duplicate updates in CRM tools.
  • For relationship changes, rebuild affected hierarchies lazily.
  • For bulk imports, implement queueing/backoff to protect downstream services.

Core account events

Account lifecycle

account:created

Triggered when a new account is created. Payload structure:

account:updated

Triggered when an account is updated. Payload structure:

account:deleted

Triggered when an account is deleted. Payload structure:

Account attribute change events

These events are triggered when specific account attributes change:

account-health:changed

Triggered when an account’s health status changes.

account-status:changed

Triggered when an account’s status changes.

account-classification:changed

Triggered when an account’s classification changes.

account-industry:changed

Triggered when an account’s industry changes.

Account custom field events

account-custom_field_value:added

Triggered when a custom field value is added to an account. Additional payload:

account-custom_field_value:removed

Triggered when a custom field value is removed from an account. Additional payload:

account-custom_field_value:changed

Triggered when a custom field value is changed on an account. Additional payload:

Customer contact events

Customer contact lifecycle

customer-contact:created

Triggered when a new customer contact is created. Payload structure:

customer-contact:updated

Triggered when a customer contact is updated. Payload structure:

customer-contact:deleted

Triggered when a customer contact is deleted. Payload structure:

customer-contact:type:changed

Triggered when a customer contact’s type changes.

Customer contact custom field events

customer-contact:custom_field_value:added

Triggered when a custom field value is added to a customer contact.

customer-contact:custom_field_value:removed

Triggered when a custom field value is removed from a customer contact.

customer-contact:custom_field_value:changed

Triggered when a custom field value is changed on a customer contact.

Account relationship events

Account relationship lifecycle

account-relationship:created

Triggered when a new account relationship is created. Payload structure:

account-relationship:updated

Triggered when an account relationship is updated. Payload structure:

account-relationship:deleted

Triggered when an account relationship is deleted. Payload structure:

Account activity events

Account activity lifecycle

account-activity:created

Triggered when a new account activity is created. Payload structure:

account-activity:updated

Triggered when an account activity is updated. Payload structure:

account-activity:deleted

Triggered when an account activity is deleted. Payload structure:

Account activity comment events

account-activity:comment:created

Triggered when a comment is added to an account activity.

account-activity:comment:updated

Triggered when a comment on an account activity is updated.

account-activity:comment:deleted

Triggered when a comment is deleted from an account activity.

Account note events

Account note lifecycle

account-note:created

Triggered when a new account note is created. Payload structure:

account-note:updated

Triggered when an account note is updated. Payload structure:

account-note:deleted

Triggered when an account note is deleted. Payload structure:

Account note comment events

account-note:comment:created

Triggered when a comment is added to an account note.

account-note:comment:updated

Triggered when a comment on an account note is updated.

account-note:comment:deleted

Triggered when a comment is deleted from an account note.

Account task events

Account task lifecycle

account-task:created

Triggered when a new account task is created. Payload structure:

account-task:updated

Triggered when an account task is updated. Payload structure:

account-task:deleted

Triggered when an account task is deleted. Payload structure:

Account task comment events

account-task:comment:created

Triggered when a comment is added to an account task.

account-task:comment:updated

Triggered when a comment on an account task is updated.

account-task:comment:deleted

Triggered when a comment is deleted from an account task.

Event structure

All account events follow the standard platform event structure:

Integration examples

Account health monitoring

Customer contact synchronization

Task management integration

Best practices

  1. Account hierarchy: Use relationship events to maintain account hierarchies in external systems
  2. Data consistency: Process events in order using the timestamp to maintain data consistency
  3. Bulk operations: Be prepared for high-volume events during bulk imports or updates
  4. Custom fields: Monitor custom field events for account scoring and segmentation
  5. Activity tracking: Use activity events to build comprehensive account timelines

Event frequency

Account events have moderate frequency but can spike during:
  • Bulk imports
  • Account health reassessments
  • Custom field updates
  • Integration synchronizations
Consider implementing appropriate rate limiting and queuing strategies for downstream processing.