Your agents work where
you already work.
Pull from Stripe, update Notion, post to Slack, open Linear issues, across 37 tools. You declare them; Claritty owns the OAuth and the keys.
Connect once. We hold the keys.
The hard, risky part of integrating, OAuth flows, secret storage, token refresh, per-user isolation, is the platform’s job. You focus on what the agent does with the data.
Declare it
One line in intelligence.yaml: ` - id: slack `. Reference its tools in your agent.
The user connects
The platform renders the Connect button and runs OAuth. You write zero auth code.
Your agent acts
Call ` slack.post_message `, ` github.create_issue ` … with the user’s live credentials.
Every integration, by category
32 providers you can connect to an account today, listed in full. A further 5 are built and waiting on provider sign-off before anyone can sign in to them, so they are not listed here: a name on this page should mean you can use it. Connect marked one click means the platform runs the whole OAuth sign-in and you only approve it. Paste a key means the service issues you a token and you hand it over once. Either way the credential is held server-side and never reaches automation code.
Comms
- Slackone click
- Gmailone click
- Discordpaste a key
- Telegrampaste a key
- Twiliopaste a key
Work tracking
- GitHubone click
- Jiraone click
- Linearone click
- Asanaone click
- GitLabpaste a key
- ClickUppaste a key
- Trellopaste a key
- Notionone click
CRM
- HubSpotone click
- Pipedrivepaste a key
Finance
- Stripepaste a key
- QuickBooksone click
Files
- Google Drivepaste a key
- Dropboxone click
- Airtablepaste a key
Calendar
- Google Calendarpaste a key
- Calendlypaste a key
Marketing
- Mailchimppaste a key
Data
- PostHogpaste a key
- Brave Searchpaste a key
Models
- OpenAIpaste a key
- Anthropicpaste a key
37 integrations, and counting,
not a single API key in your code.
Build an app that acts across your tools
Declare an integration, ship in minutes. The credentials are on us.
Start building