Integrations
Last reviewed: 2026-05-08
Owner: Support engineering
Source of truth:
https://dawnhq.ai/docs/integrationshttps://dawnhq.ai/docs/integrations/githubhttps://dawnhq.ai/docs/integrations/azure-devopshttps://dawnhq.ai/docs/integrations/gitlabhttps://dawnhq.ai/docs/integrations/bitbuckethttps://dawnhq.ai/docs/integrations/jirahttps://dawnhq.ai/docs/integrations/linearhttps://dawnhq.ai/docs/integrations/trellohttps://dawnhq.ai/docs/integrations/google-drivehttps://dawnhq.ai/docs/integrations/onedrivehttps://dawnhq.ai/docs/integrations/fourahttps://dawnhq.ai/docs/integrations/mailjethttps://dawnhq.ai/docs/integrations/sendgridhttps://dawnhq.ai/docs/integrations/mcp-gateway
Applies to: source linking and access troubleshooting
Refresh cadence: monthly
Facts
- Public integration docs cover GitHub, Azure DevOps, GitLab, Bitbucket, Jira, Linear, Trello, Google Drive, OneDrive, Confluence, Notion, Figma, Framer, FourA, MailJet, SendGrid, and MCP Gateway.
- Integration setup pattern: connect provider -> discover and link sources -> assign sources to the intended agent profiles -> validate read or search access.
- Agents use only the sources assigned to the active profile; a connected provider alone is not enough.
- Public Dawn docs position integrations as grounded read/search access to connected sources.
- Docs include provider-specific setup pages for GitHub, Azure DevOps, GitLab, Bitbucket, Jira, Linear, Trello, Google Drive, OneDrive, Confluence, Notion, Figma, Framer, FourA, MailJet, SendGrid, and MCP Gateway.
- FourA is a web scraping and exploration integration. It exposes one source named Web scraping and exploration, which must be linked and assigned to the agents that should inspect public pages and HTTP APIs.
- MailJet and SendGrid are email operations integrations. Source linking is scope-based: contact lists, templates, and campaigns rather than individual templates or campaigns.
- MailJet and SendGrid sends, contact changes, template changes, and campaign changes require integration write tools for the active agent profile.
- MCP Gateway is for hosted HTTPS MCP servers connected as workspace integrations. It is not the same as
/docs/mcp, which covers external MCP clients calling Dawn.
- MCP Gateway supports no auth, bearer token, static headers, and MCP OAuth when the server advertises compatible OAuth metadata.
- Dawn does not run local stdio MCP servers through MCP Gateway.
- MCP Gateway capabilities should be linked narrowly and assigned to the specific agent profiles that should use them.
- Write-capable MCP tools are still governed by each agent’s write-tool policy.
- Bitbucket docs now prefer
email:api_token for Bitbucket Cloud API tokens and list the recommended minimum read scopes for repo, pull request, and issue access.
- Bitbucket setup is not the same as Trello. Users create a Bitbucket API token from the Atlassian account flow, then enter it in Dawn as
email:api_token.
- Jira setup is also not the same as Trello. Users create a regular Atlassian account API token, then enter Jira URL, Atlassian email, and token separately in Dawn.
- Trello setup now explicitly points users to
https://trello.com/power-ups/admin, where they create a Trello app or Power-Up, generate the API key from its API Key tab, and then create the matching token.
- Trello docs now describe list or column-aware card search, including requests like
cards in To Do, and note that archived Trello cards map to the closed-card path.
FAQ snippets
- Why does the agent answer without source grounding? Integration may be disconnected, unlinked, or not bound to the current profile.
- Which integration should users start with? The one that contains highest-value operational data for the workflow.
- How to verify? Run a simple read/search against each critical linked source from the intended agent.
- Does connecting the provider automatically expose everything? No. The sources still need to be linked and assigned to the active agent profile.
- What Bitbucket credential format should users use? Prefer
email:api_token for Bitbucket Cloud API tokens; raw bearer tokens are only for true bearer-token credentials.
- Is Trello using the same token flow as Bitbucket or Jira? No. Trello uses an app or Power-Up API key plus token flow. Bitbucket and Jira use Atlassian account token flows.
- Can Dawn work with Trello status columns? Yes. Trello card search now exposes board lists or columns and can filter by list name.
- Is MCP Gateway the same as Dawn MCP API credentials? No. Dawn MCP API credentials let external clients call Dawn. MCP Gateway lets Dawn call hosted MCP servers.
- Can users connect a local stdio MCP server? No. MCP Gateway expects a hosted HTTPS MCP endpoint.
- Why does an MCP capability not appear? The endpoint may not validate, the server may not expose tools/resources/prompts, or Dawn may classify the capability as unknown or blocked.
- Does FourA replace web search? No. Web search helps find pages; FourA helps an assigned agent inspect a specific page or endpoint.
Escalation trigger
- OAuth/token appears valid but provider read operations consistently fail.