Integrations Overview

Integrations give your agents real context from code, tickets, docs, web pages, drives, and provider tools. Configure credentials once, link only needed sources, and validate with focused known-answer tests.

Personal vs workspace integrations

Dawn has two kinds of integration, set up in different places.

  • Workspace integrations are shared sources connected by an owner or manager from the workspace Integrations screen. Each linked source is assigned to the agents that should use it. Code repositories, work trackers, docs spaces, marketing and analytics sources, and provider tools are workspace integrations.
  • Personal connections are connected by an individual user under account settings → My connections. They stay scoped to that user, are never exposed workspace-wide, and treat changes such as sending mail as write actions that need explicit confirmation. Gmail and Google Calendar are personal connections. See Personal Connections for the dedicated guide.

A few providers support both. Google Drive, OneDrive, Dropbox, and Box can be a shared workspace source or a personal connection, depending on which screen you use to connect them.

The rest of this page covers the workspace setup flow. For personal connections, see the Personal Connections guides listed below.

Connection vs Source

  • Connection stores provider credentials and API base details.
  • Source is the concrete item the agent can use (repo, issue source, wiki, board, project, drive).
  • An agent uses only the sources you bind or allow for its profile/workspace.

Setup flow

  1. Create integration connection.
  2. Validate credentials in Dawn before linking any sources.
  3. Discover and link sources.
  4. Bind source set to the intended agent profile.
  5. Start with one narrow source set, then test with a known repo, ticket, or document and confirm the reply cites or clearly names that linked source.

Current integration notes

  • Trello: create a Trello app or Power-Up first, then generate the API key from that app’s API Key tab and create the token from the same page.
  • Bitbucket Cloud: create a Bitbucket API token from your Atlassian account flow, then enter it in Dawn as email:api_token. Raw bearer tokens are only for true bearer-token credentials.
  • Jira Cloud: create a regular Atlassian account API token, then enter your Jira site URL, Atlassian email, and token separately in Dawn.
  • Confluence: the current path is also manual Atlassian credentials. Use the Confluence Cloud site URL, Atlassian account email, and a regular Atlassian API token.
  • Notion: discovery only sees root pages that were explicitly shared with the internal integration. If a page tree does not appear, share the root page with the integration first, then refresh discovery.
  • Trello search: Dawn exposes board list or column context through card search results, so agents can work with requests like cards in To Do as well as title-based card lookups.
  • Google Drive: the current runtime is text-focused. Dawn can browse folders, read text files, and search text content, but binary files are not supported.
  • Dropbox: read-only. Link All files/folders or specific root folders. Agents can browse, read text files, open binary files through Dawn’s document tools, and search within the linked boundary. Search coverage depends on Dropbox indexing.
  • Box: read-only. Link All files/folders or specific root folders. Agents can browse, read text files, open binary files through Dawn’s document tools, and search within the linked boundary. Search coverage depends on Box indexing and supported file types.
  • Notion search: Dawn treats Notion as a page-tree source with title and path oriented lookup. It should not be treated as exhaustive full-text workspace search in v1.
  • Figma: discovery is URL-driven. Connect first, then paste a file or node URL on the source step to discover the exact Figma resources you want to link.
  • Framer: use the project editor URL, not the published site URL. Discovery comes from that project and returns the site, pages, and reusable styles.
  • FourA: connect a FourA API key to give assigned agents web scraping and exploration tools for public pages and HTTP APIs.
  • MailJet: link source scopes for contact lists, templates, and campaigns. Agents can search by default; contact/template/campaign changes and sends require integration write tools.
  • SendGrid: link source scopes for contact lists and segments, dynamic templates, and campaigns. Agents can search by default; contact/template/campaign changes and sends require integration write tools.
  • MCP Gateway: connect hosted HTTPS MCP servers, validate the endpoint, then link only the capabilities agents should use. Dawn does not run local stdio MCP servers.
  • Google Analytics: read-only. Discovers GA4 properties as sources. Agents can inspect property metadata, list available dimensions and metrics, and run bounded reports.
  • Google Ads: read and reporting only, no campaign editing. Discovers accessible and manager-linked customers as sources.
  • Google Search Console: read-only. Discovers verified sites as sources, including domain and URL-prefix properties. Agents can query search analytics, list and read sitemaps, and inspect URL indexing data.
  • Gmail and Google Calendar: these are personal connections, set up by each user under account settings → My connections, not the workspace Integrations screen. They stay scoped to the user who connected them. Write actions such as sending mail or changing an event with attendees require explicit confirmation.

Integration guides

Code Repositories

Work Tracking

Design

Documents and Wikis

Email Platforms

Web Data

Marketing and Analytics

Personal Connections

Personal connections are set up by each user under account settings → My connections, separate from the workspace sources above, and stay scoped to the user who connected them. Google Drive, OneDrive, Dropbox, and Box can also be connected this way.

Custom tools

Validation checklist

  • Connection test passes after save and after app reload.
  • At least one linked source appears in the Sources panel.
  • Agent can browse/read/search data from linked source.
  • A known source item can be retrieved or cited by name, not just described in generic terms.
  • Provider-specific credential format matches the guide for that provider.
  • Permission errors are explicit and actionable.
Validation Prompts

Use these prompts in Dawn chat to quickly validate this setup area. 

List all integration connections, linked sources, and their health state.
Which linked sources are unused by any agent profile?
Completion Checklist
  • All required providers connected.
  • Sources discovered and linked.
  • Sources assigned to intended agent profiles.
  • Read/search validation prompt passes for each critical source.