REST API: actions

The Actions API manages the actions of an agent that are configured on the server. Before you replace the current configuration, read it. If you only want to enable or disable an existing action, use the toggle endpoint. Copying actions is useful for a controlled setup. After you copy actions, read back the configuration. Do not assume that environment-specific credentials or routing rules stay the same after the copy.

Action logs and their aggregate statistics are operational signals. They are not a permanent audit record. Use the logs to investigate a specific execution. Correlate failures with your own job logs. Then decide whether to change a configuration. Calendar helper endpoints show the available event types from Calendly or Cal.com. Before you save a scheduling configuration, check the Cal.com key.

Do not use this API to promise browser-side custom actions. The browser action registration has no complete bridge for widget execution. To collect visitor data, use the supported embedded forms with a server-side workflow. Keep mutation requests behind a write-scoped key. See the reference for the exact configuration shape.