Automation triggers

Connect API calls fire the same automation events as console actions. The Connect API isn’t a separate event surface — every POST /connect/table_entries/ triggers the same flows as a lead created via the console UI.

Which events fire from Connect

Endpoint	Events fired
POST /connect/table_entries/	table.entry.added, table.entry.leadState.changed (initial)
PATCH /connect/table_entries/:id	table.entry.leadState.changed (only when leadStateId changes)
POST /connect/calendar_bookings/	calendar.appointment.booked (immediate), calendar.appointment.hasStarted (at start), calendar.appointment.hasEnded (at end)
DELETE /connect/calendar_bookings/:id	calendar.appointment.deleted (cancels pending hasStarted/hasEnded)

Trigger context

When a flow is triggered by a Connect API call, the run’s context carries:

• apiTokenId — the token used for the request.
• memberId — null (no human user attribution for Connect-triggered runs).

Console-triggered events have apiTokenId: null and the actual memberId. Both surface in activityLogs and the run history view, so you can attribute side effects back to the integration that caused them.

Related

• Platform → Automations → Triggers — full event catalog including form widget and ingress webhook surfaces.
• Leads resource — endpoints that fire table.entry.*.
• Bookings resource — endpoints that fire calendar.appointment.*.