Quickstart
NONE | ON_START | ON_TOOL_CALL (defaults to NONE).
Prerequisites
API key with access to your workspace (
x-api-key).At least one integration enabled (managed or custom). For first runs, prefer a managed and read-only integration.
OpenAPI spec is downloadable here.
Enable an integration
Go to integrations
Enable an integration (or upload a custom integration) - For this demo we recommend "Google Calendar" or "Outlook Calendar"

Get your API key
Head over to API keys section in console

Generate an API key

Copy and Save the API key

Export the api Key
Create your first Run
A Run is the execution of an intent with guardrails.
Request Fields
intent
String
✅
What outcome you want (natural language).
context
String
✅
Hidden, technical details (timezone, constraints). Keep sensitive data here; don’t show to end users.
userId
String
✅
Identity whose tokens/permissions apply (act‑as‑user).
selectedCustomerIntegrationIds
string[]
✅
Allow‑list of connections, or ["*"] for all active.
approvalStrategy
enum
-
NONE | ON_START | ON_TOOL_CALL (defaults to NONE).
outputSchema
object
-
Define the expected output format by providing JSON Schema Draft-07 object
Example intent (declarative, long‑form)
Create the run (cURL):
Watch the live execution
Inspect the Run and result
Production tips
Intent: be outcome-focused and testable. Prefer declarative language (what), let the system decide (how).
Context: keep sensitive details here; do not surface to end users.
Approvals: start with
ON_TOOL_CALLfor writes for your agent;ON_STARTif you need human to review the plan.Least privilege: choose a
userIdwith only the permissions needed.Scoping: For QuickStart user ["*"] for integrations to select all that have been enabled
Observability: use SSE in staging/early prod to watch real behavior.
Last updated