Integrations
Every tool Naski connects to
The catalogue that ships with the product, grouped as it appears in Settings. Naski stores your credential encrypted and performs the calls on your agent's behalf; agent code names an operation and never sees the key.
Documents and productivity
- Google WorkspaceConnect button
- Google SheetsConnect button
- Microsoft 365Connect button
- NotionConnect button
- ConfluenceYour own instance
- DropboxConnect button
- AsanaConnect button
- Trello
- Calendly
- Typeform
Messaging and email
- SlackConnect button
- Intercom
- SendGrid
- Brevo
CRM and revenue
- SalesforceConnect buttonYour own instance
- HubSpotConnect button
- Pipedrive
- Zoho CRMYour own instance
- Sellsy
- Axonaut
- Monid
Finance and accounting
- Stripe
- QuickBooks OnlineConnect button
- Pennylane
- Qonto
Engineering
- GitHubConnect button
- GitLabConnect button
- LinearConnect button
- JiraYour own instance
Operations and support
- ShopifyYour own instance
- ZendeskYour own instance
- Airtable
- OdooYour own instance
- DocuSignYour own instance
Reading this list
- Connect button — where the provider is enabled on your deployment, you press Connect and approve on its own screen. No key is copied anywhere.
- Your own instance — the service lives at your company's own address, so installing it asks for that address and refuses without it.
- Everything else takes an API key, entered in Settings and stored encrypted. Never in a chat message.
Not on the list?
A connector is data, not code: a base address, an auth shape and a list of operations. The chat can author one for a service that is not in the catalogue, and remote MCP servers cover tool-shaped services the same way.