REST API: actions
Configure actions, review logs, and validate scheduling integrations.
The Actions API manages the agent actions that are configured server-side. Read the current configuration before replacing it, and use the dedicated toggle endpoint when the only intended change is enabling or disabling an existing action. Copying actions is useful for controlled setup, but it should be followed by a readback so environment-specific credentials or routing rules are not assumed to transfer unchanged.
Action logs and their aggregate statistics are operational signals, not an immutable audit ledger. Use them to investigate a specific execution, correlate failures with your own job logs, and decide whether a configuration should be changed. Calendar helper endpoints expose available Calendly or Cal.com event types; validate a Cal.com key before saving a scheduling configuration.
Do not use this API to promise browser-side custom actions. The current browser action registration surface has no complete widget execution bridge. For visitor collection flows, use supported embedded forms and a server-side workflow. Keep mutation requests behind a write-scoped key and use the reference for the exact configuration shape.