Integrations

An app, an automation or a team can act in the tools your company already uses. You declare which ones it needs. Claritty owns the sign-in and holds the credentials, so no key ever reaches your code.

How a connection is made

1
Declare it. Add the integration to intelligence.yaml. One line.
2
The user connects. Claritty renders a Connect button and runs the sign-in. You write no auth code and handle no callback.
3
Your agent acts. Call the tool. The platform attaches that user’s credentials on the way out.

intelligence.yaml

integrations:
  - id: gmail
    required: true
  - id: slack
    required: false

A required integration must be connected before the app will run. An optional one lets the app start without it and skip the steps that need it.

Credentials are held by the platform, per user, per app. They are never bundled into your app, never written to its database, and never visible to its code. A tool call carries a reference; the broker attaches the real token as it leaves.

37 services can be connected today. 14 of them support a full OAuth sign-in, where the user clicks Connect and nothing else. The rest ask for a token the service issues, which the user pastes once.

	Connect button	What the user does
OAuth	14 services	Clicks Connect, approves on the provider, comes back. No key changes hands.
Token	23 services	Creates a token in the service and pastes it once. Stored encrypted, shown only by its last 4 characters afterwards.

What you can connect

Comms

Slack (OAuth), Gmail (OAuth), Outlook (OAuth), Discord, Microsoft Teams, Telegram, Twilio

Work tracking

GitHub (OAuth), Jira (OAuth), Linear (OAuth), Asana (OAuth), GitLab, ClickUp, Trello, Notion (OAuth)

CRM

HubSpot (OAuth), Salesforce (OAuth), Pipedrive

Finance

Stripe, QuickBooks (OAuth), Xero (OAuth)

Files

Google Drive, Dropbox (OAuth), Airtable

Calendar

Google Calendar, Outlook Calendar, Calendly

LinkedIn (OAuth), X, Facebook, Instagram, TikTok

Marketing

Mailchimp

Data

PostHog, Brave Search

Models

OpenAI, Anthropic

A tool id is namespaced by its provider, like slack.post_message or gmail.send. An agent can only call tools whose integration the app declared. A call to an undeclared provider fails at load, not at run time.

Connecting on behalf of your users

When you publish an app other people install, each of them connects their own accounts. Your app sees their data under their credentials, never yours, and never anyone else’s. You do not have to build the connect screen: the platform renders it from what your manifest declared.

Something not on the list

An app can call any HTTP API directly with a credential the user supplies, and an automation can read a web page it has been shown how to reach. A listed integration is the shortcut, not the boundary.

NextAutomations →Put a connected account to work Build the code →Call a tool from an agent Go live →Ship it