Skip to main content
Beyond its own database, a Zite app can call third-party services: Slack, OpenAI, Stripe, Google Workspace, HubSpot, and more. Integrations run in your backend workflows, never in the browser, so credentials stay secret.

How integrations work

Everything your app can call falls into one of three buckets:
The database is not an “integration” you configure. It’s the workspace itself, reached through the runtime.

Supported services

Zite supports more than 50 connectable third-party services, including: Salesforce requires the Team plan.

Secrets

Secrets are never written in code. They’re provided to your workflows as environment variables:
  • Connected integrations expose a token like ZITE_SLACK_ACCESS_TOKEN or ZITE_OPENAI_ACCESS_TOKEN.
  • Your own secrets, added in the editor, are prefixed ZITE_ and read as process.env.ZITE_<KEY>.
Add a secret once for the whole workspace under Settings → Secrets in the workspace sidebar, and every app in the workspace can read it. An app can set its own secret of the same name, in the app’s own Secrets tab, to override the workspace value for that app only.
Connecting an integration requires an OAuth sign-in, which can’t be done by an agent headlessly. The agent hands you a link (setup_integration) to connect the service in Zite; once connected, the token is available to your workflows.

Environments

The ZITE_ENV variable selects the environment your workflows run against: process.env.ZITE_APP_URL is always set to your app’s public URL. Use it for building links instead of hardcoding a domain. For result-set caps, execution timeouts, and payload sizes, see Platform limits.