Connectors
Connect Google Drive, Gmail, Notion, Slack, databases, and more to the Dynamiq Agent — once per user, toggled per conversation.
Connectors give the Dynamiq Agent access to your apps: read a doc from Google Drive, search your Notion, post to Slack, query your Postgres database. You connect each app once with an OAuth consent (or credentials, for a few special connectors), then toggle it on or off per conversation. Connectors are available in Dynamiq Agent mode only.
The Connect apps menu
Click the gear Connect apps button in the input bar. The menu shows:
- Preinstalled apps — Browser, Web Search, Nano Banana Pro (image generation), and ElevenLabs v3 (text to speech). These are always enabled and need no setup.
- Your connections — every app you've connected, each with a toggle.
- Connect more apps — opens the full catalog.
Connect an app
Open the catalog
Choose Connect more apps. The Connect apps dialog lists the catalog grouped by category — productivity, communication, developer tools, cloud, monitoring, analytics, security, and database — with a search box. The catalog includes Google Workspace (Drive, Gmail, Calendar, Docs, Sheets, Meet), Notion, Slack, Dropbox, Jira, Linear, HubSpot, Salesforce, Zendesk, GitHub, and many more.
Authorize
Click the + button on a connector card. For OAuth connectors a popup opens the provider's consent page — sign in and approve the requested access. A green check appears on the card once connected.
A few connectors use credentials instead of OAuth:
- AWS — Access Key ID and Secret Access Key, entered inline.
- Google Cloud — upload a service account key JSON file.
- GitHub — OAuth, with a checklist to trim the optional scopes before authorizing.
- Databases — PostgreSQL, MySQL, Vertica, ClickHouse, and Trino take host, port, credentials, SSL/TLS settings, and an optional SSH tunnel. These support multiple connections (for example, staging and production), managed with the Manage button on the card.
Toggle it per conversation
Back in the Connect apps menu, each connection has a switch. Inside a conversation, the switch controls that conversation only — disable Gmail for a research chat, enable it for an inbox-cleanup chat. Outside a conversation (a brand-new chat), the switch sets your personal default for new conversations.
Revoke access
To disconnect an app entirely, open Connect more apps and click the × (Disconnect) button on its card — or Manage for multi-connection connectors, then remove the specific connection. Disconnecting deletes the stored authorization for your user; reconnecting requires going through consent again.
Chat connectors are not workflow Connections. A Connector is a per-user OAuth authorization that only the Chat super agent uses, toggled per conversation. Workflows and deployed Apps use Connections — credentials stored at the project/org level and wired into nodes by builders. If you want each end user of a deployed App to authorize their own accounts, that is a third mechanism: End-User Connection Requirements.
How the agent uses connectors
Once a connection is enabled in the conversation, the agent discovers the app's tools and calls them as needed — you'll see the calls as steps in the reply, inspectable in the tool details panel. Database connections are queried through the agent's SQL tooling, which is instructed to use parameterized queries for any user-supplied value.
Check my Google Calendar for tomorrow, then draft a Slack message to #team
summarizing my availability.