Your data is not hostage
Build integrations with the documented public API, goal-oriented MCP tools, and read-only SQL over your own workspace. Inspect the generated schemas and permission requirements before connecting an agent.
A public API by default
Procedures are exposed unless there is a concrete safety reason not to. Campaigns, Unibox, dialer, inboxes, workflows, warmup, and domains are all addressable.
An MCP server for agents
Discover app capabilities as MCP tools. Connect with interactive sign-in, a scoped API key, or user-approved agent authentication. Every call checks the selected workspace and permissions.
SQL over your workspace
Read-only queries over curated, tenant-scoped views with a powerless database role. Credential columns are never in the views.
If you can do it in the app, you can do it with a key
The public API is an explicit allowlist that defaults to public: hundreds of documented operations generated from the same schemas the app uses, so the contract cannot drift from the product. API keys carry scoped permissions that mirror workspace roles, and every request is evaluated against local RBAC.
- OpenAPI contract generated from the app's own input schemas
- Campaigns, leads, Unibox, dialer, inboxes, workflows, warmup, domains
- Scoped API keys with the same permission model as workspace roles
- Cross-tenant and credential-ingesting endpoints deliberately excluded
Connect an AI agent with permissions you control
The remote MCP server exposes app capabilities as tools. An external agent can follow auth.md, ask you to approve its connection, and obtain a short-lived credential. Scheduler Zero limits each action to the agent's approved scopes and your current workspace permissions. Interactive MCP sign-in and scoped API keys are also supported.
- User-approved agent registration with short-lived access tokens
- An explicit workspace on every delegated-agent data call
- Agent access cannot exceed the authorizing user's permissions
- Zapier and Make automations use the same API
Ask your own data a question in SQL
Run read-only SELECT queries over curated views of your workspace. Each view bakes in the tenant filter, execution runs as a database role with no access to real tables, and columns are excluded by default so secrets cannot leak by omission. Soft-deleted mail is excluded so counts match what your team sees.
- Twelve curated views: campaigns, contacts, send history, threads, calls, and more
- Queries parsed with the real Postgres grammar and validated against an allowlist
- Runs as a role with zero grants on application tables
- Available as an API endpoint and as MCP tools
Integrate with this feature
Read the API and MCP reference, inspect schemas, and check the permissions your connection needs.
Frequently asked questions
Ready to see it in action?
Join the private alpha and run a sequence whose replies are followed up by email, phone, and SMS from one lead record.