Activities API & Webhooks
Overview
Activities can be managed programmatically through the Kizen API and webhooks, enabling external systems and internal automations to schedule, retrieve, and respond to Activity state changes in near real time.
Each subpage focuses on a specific use case, such as scheduling Activities, retrieving logged Activity details, or triggering external workflows when Activities are created or completed.
Each subpage in this section focuses on a specific use case, such as scheduling Activities, retrieving details, or triggering workflows.
How Activities Are Exposed Programmatically
Activities are available through APIs and webhooks in ways that align with their lifecycle:
Scheduled Activities support planning and coordination use cases
Logged Activities provide a durable record of completed interactions
Lifecycle events emit webhook notifications that can drive downstream workflows
All API and webhook behavior respects Activity Objects, permissions, and record associations, ensuring consistent behavior across UI, Automations, and external integrations.
When to Use APIs vs Webhooks
In general:
Use APIs when you need to create or access Activity data on demand
Use webhooks when you need to react automatically to Activity lifecycle events
Many integrations use both together, using APIs for data access and webhooks for event-driven workflows.
API Topics in this Section
What’s Next
Review the individual topics in this section to learn how to work with specific Activity endpoints, and webhook events. Each page includes an endpoint or event details, examples, and usage considerations.
Last updated
Was this helpful?