Action Types
Every entry on a lead's timeline is an action. Some actions are written by the public API; the rest are recorded automatically by telecrm when calls happen, messages are sent, integrations fire, or the lead's state changes.
This page lists action types in two groups:
- Used to create — types accepted by the create-actions endpoint.
- Used in search — types accepted as the
typefilter on the search-actions endpoint.
Used to create
These are the only types you can create or update through the API. Everything else is read-only and only appears via search results.
| Type | Description |
|---|---|
<custom code> | Workspace-defined custom action (e.g. 1001, 1002). Code is shown in Settings → Custom Actions. |
PAYMENT | Payment event with status, currency, amount. |
See Actions for input schemas, custom action code lookup, and the ACTION_ prefix rule (Async API only). Use POST /lead/{leadId}/action to write actions.
Used in search
The Sync API's search-actions endpoint accepts any of the types below as the type filter. Custom actions and payment actions are searchable too — the rest are recorded automatically by telecrm and exposed for read-only filtering.
Custom & payment
| Type | Description |
|---|---|
<custom code> | Workspace-defined custom action — pass the bare numeric code (e.g. "1001"). |
PAYMENT | Payment events on the lead. |
Calls
Voice calls, including those routed through telephony integrations.
| Type | Description |
|---|---|
INCOMING_CALL | Inbound call to a workspace number. |
OUTGOING_CALL | Outbound call from a team member. |
MISSED_CALL | Inbound call that was not answered. |
CALL_ACTION | Generic call event. |
MAQSAM_INCOMING_CALL | Inbound call via Maqsam. |
MAQSAM_OUTGOING_CALL | Outbound call via Maqsam. |
IVR_INCOMING_CALL | Inbound IVR call. |
IVR_OUTGOING_CALL | Outbound IVR call. |
MCUBE_INCOMING_CALL | Inbound call via MCube. |
MCUBE_OUTGOING_CALL | Outbound call via MCube. |
KNOWLARITY_INCOMING_CALL | Inbound call via Knowlarity. |
KNOWLARITY_OUTGOING_CALL | Outbound call via Knowlarity. |
CALLER_DESK_INCOMING_CALL | Inbound call via Caller Desk. |
CALLER_DESK_OUTGOING_CALL | Outbound call via Caller Desk. |
Messages
Chat and email events recorded against the lead.
| Type | Description |
|---|---|
INCOMING_WHATSAPP_MSG | Inbound WhatsApp message. |
OUTGOING_WHATSAPP_MSG | Outbound WhatsApp message. |
WHATSAPP_ACTION | Generic WhatsApp event. |
OUTGOING_SMS | Outbound SMS. |
OUTGOING_EMAIL | Outbound email. |
Lead lifecycle
Changes to the lead itself — assignments and status moves.
| Type | Description |
|---|---|
LEAD_ASSIGNMENT | Lead reassigned to a different team member. |
STATUS_CHANGE | Lead's status changed. |
Tasks & reminders
Scheduled follow-ups, meetings, and their completion events.
| Type | Description |
|---|---|
TASK_CREATION_ACTION | Task created on the lead. |
CALL_FOLLOWUP_COMPLETION_ACTION | Call follow-up completed. |
TODO_TASK_COMPLETION_ACTION | Todo task completed. |
GOOGLE_MEET_COMPLETION_ACTION | Scheduled Google Meet completed. |
Notes & system
Notes added to the lead and team-member field activity.
| Type | Description |
|---|---|
USER_NOTE | Note added by a team member. |
SYSTEM_NOTE | Note added by the system (e.g. lead enrichment). |
LOCATION_CHECK_IN_ACTION | Team member checked in at the lead's location. |
SALES_FLOW_ACTION | Sales flow step recorded against the lead. |