App + chat connectors
Connect tools like Gmail, Slack, GitHub, Notion, and Drive once, then use them in chat, automations, and workflows — without pasting secrets into every prompt.
Connectors extend what Volnyn’s assistant and automations can do. You connect an account (OAuth or API key) once; Volnyn stores encrypted credentials on your user account and exposes tools the assistant can call when that connection is present.
Unlike Lovable’s “one connection linked into a published app runtime,” Volnyn’s primary model today is:
- Chat / agent tools — the assistant reads and acts while you build
- Automations & workflows — scheduled or graph runs that call the same connected accounts
- Site-specific integrations — some features (for example GitHub sync, Google Analytics) live on the site settings pages
Where to connect
Open Connectors from the chat UI (and related connector entry points in the dashboard). Each provider shows Connect, status, and Disconnect when supported.
Routes follow patterns such as:
/user/connectors/{provider}/connect/user/connectors/{provider}/callback/user/connectors/{provider}/disconnect
Exact providers depend on which OAuth apps and API keys are configured on your Volnyn server.
How connections work
- You authorize with OAuth or paste an API key.
- Volnyn stores tokens on a ConnectorAccount for your user (encrypted at rest).
- Chat tools, automations, and workflow nodes that need that provider become available.
- Disconnecting revokes Volnyn’s stored grant; revoke at the provider too if you want the app removed from their side.
Connections are per user account, not a separate workspace catalog with project-linking UI like Lovable’s app+chat model. Share outcomes (sites, artifacts) rather than expecting one teammate’s Gmail grant to silently power another teammate’s chat.
Connection types
| Type | How you authenticate | Examples |
|---|---|---|
| Bespoke OAuth | Dedicated connect/callback controllers | GitHub, Gmail, Google Drive, Google Sheets, Google Calendar, Slack, Notion, HubSpot, Shopify, Discord, Figma, Asana, Airtable, Jira, Dropbox, Outlook Mail/Calendar, YouTube, Canva, Intercom, Vercel, Supabase, Meta Ads, Instagram, … |
| Generic OAuth | Shared OAuth engine + config | Zoom, Box, Salesforce, Pipedrive, Xero, Zoho, Wix, LinkedIn, Twitter/X, and others listed in config |
| API key | Paste a provider key | ClickUp, Todoist, Calendly, Typeform, Klaviyo, Bitly, ElevenLabs, Perplexity, Firecrawl, … |
| Hosted / custom MCP | MCP server URL or catalog entry | Directory of MCP-capable tools; custom MCP / custom API from chat |
| Site integrations | Site settings pages | GA4 / PostHog IDs, GitHub repo link |
The connector catalog can list many tools. Some entries require server-side client IDs, admin keys, or a custom MCP URL before Connect works. If a button is disabled or the flow errors, the provider is not fully configured on this deployment.
Using connectors in chat
Once connected, ask the assistant to use the tool:
List my open GitHub pull requests.
Draft a reply to the latest unread Gmail from Acme.
Add a row to our Google Sheet with today’s signup count.
Prefer letting the assistant call the connector over asking for copy-paste workarounds when the account is already linked.
Write actions may require confirmation depending on the tool and UI. Read-only list/search calls are usually safer defaults.
Automations and workflows
- Automations can poll connected sources (for example Gmail, Drive, Notion) when those connectors exist.
- Workflows expose tool nodes for providers you’ve connected. The palette hides tools you cannot reach yet (example: GitHub nodes appear after GitHub is connected).
See Automations and Workspace for how graphs and runs fit together.
First-class site connectors
Some integrations are documented on their own pages because they attach to a site, not only chat:
| Integration | Docs |
|---|---|
| GitHub source sync | Git sync overview |
| Google Analytics / PostHog | Google Analytics |
Security notes
- Tokens are stored encrypted on the server; do not paste long-lived secrets into chat if a connector exists.
- Disconnect when a contractor finishes or a key may be leaked.
- Rotate provider keys/OAuth apps if a laptop or token is compromised.
- Published AI sites do not automatically inherit your personal Gmail/Slack grants — site visitors don’t get your chat connectors.
FAQ
Who can use my connection?
You — the account that completed OAuth or pasted the key. Teammates connect their own accounts unless you build a shared automation under a shared operator account (use carefully).
Why is Connect disabled for a tool?
Usually the server lacks OAuth client credentials, an API key, or an MCP endpoint for that catalog entry.
Is this the same as team SSO?
No. Connectors authorize third-party apps. SSO authenticates people into Volnyn via your IdP.
Can published apps call Slack as each end user?
Volnyn’s chat connectors are builder/operator credentials. Per-visitor “sign in with Slack” inside a customer app is a different product pattern and is not what this page covers.