Skip to main content
Integrations let daoco read and write data in connected commerce, site, mail, calendar, outreach, files, docs, creative, work, knowledge, analytics, CRM, sales, and Dev Testing tools through governed provider connections.
Each integration uses the Model Context Protocol (MCP) under the hood. In chat, use the /integration command to work with connected providers.

​
What is MCP?

MCP (Model Context Protocol) is an open standard for connecting AI tools to external apps and data. Many providers — Notion, Salesforce, Google, HubSpot, and others — expose an MCP server that daoco connects to after you approve OAuth or admin access. In daoco, we call these connections integrations. The /integration slash command is how you ask daoco to read from or write to a connected integration in brand chat, with approval gates on sensitive changes.

​
Connect integrations

1

Open Connections

Open Connections -> Integrations. Commerce & Website, Mail & Calendar, Files & Docs, Work & Knowledge, and CRM & Sales providers are available to every workspace.
2

Choose a provider

Select the provider card and complete its OAuth or tenant-access setup. Dev Testing providers remain workspace-gated.

​
Provider status

​
Current catalog

​
Provider guides

Shopify Admin

Legacy Commerce & Website connection for Shopify Admin stores.

Square

Connect Square merchant data through Square OAuth.

WordPress

Connect WordPress.com sites, pages, posts, and media.

Stripe

Preview billing and payments connection for Stripe.

Webflow

Connect Webflow sites, CMS content, and assets.

Wix

Connect Wix sites and business data.

Gmail Individual

Dev Testing connection for one Google user’s Gmail account.

Gmail Workspace

Connect admin-approved Google Workspace mailboxes.

Google Calendar

Dev Testing connection for one Google user’s Calendar data.

Klaviyo

Connect Klaviyo account and campaign data.

Outlook Workspace

Connect admin-approved Microsoft 365 mailboxes.

Smartlead

Connect Smartlead campaigns, leads, deliverability, and sender health with an API key.

Google Drive Individual

Dev Testing connection for one Google user’s Drive files.

Google Drive Workspace

Connect admin-approved shared drives and folders.

Dropbox

Connect Dropbox files and folders.

SharePoint Workspace

Connect selected SharePoint and OneDrive resources.

Notion

Connect Notion pages and databases.

Asana

Connect Asana tasks, projects, and workspaces.

ClickUp

Dev Testing connection for ClickUp tasks, lists, and workspaces.

Linear

Connect Linear issues, projects, and teams.

Atlassian

Preview Jira, Confluence, and Atlassian work data.

Figma

Connect Figma designs, FigJam boards, and design context.

Airtable

Connect Airtable bases, records, and schema.

monday.com

Connect monday.com boards, items, and workflows.

PostHog

Connect PostHog analytics, feature flags, and product data.

Higgsfield

Generate and iterate on cinematic images, videos, clips, and characters.

FLORA

Discover and run FLORA Techniques for creative generation and iteration.

Canva

Dev Testing connection for Canva designs and workspace assets.

HubSpot

Connect HubSpot CRM and marketing data.

Salesforce

Connect Salesforce hosted integration with an External Client App.

Clay

Connect Clay enrichment and CRM workflows.

Sprout Social

Connect approved Sprout Social analytics for published TikTok insights.

Google Ads

Dev Testing reporting with approval-bound campaign status and budget controls.

Google Analytics

Dev Testing connection to Google’s hosted read-only Analytics MCP endpoint.

Meta Ads

Dev Testing connection to Meta’s official hosted Ads MCP server.

TikTok Ads

Dev Testing connection to TikTok for Business’s hosted MCP server.

LinkedIn Ads

Dev Testing connection through daoco’s approval-bound read/write LinkedIn Marketing API service, including create, update, archive, and delete tools.

​
Use integrations from chat

Use /integration or ask about a connected provider.
Writes use the permissions you granted. Start with read-only prompts and review proposed changes before approving provider updates.

​
Approval preferences

Integration writes follow the same approval preferences as social scheduling. Brand owners and admins configure defaults under Settings → Brands → select a brand → Approval gate. Both Scheduled social posts and Provider write actions default to Auto when connected. For Provider write actions, the brand default controls whether non-destructive provider-authorized writes can run without an extra prompt when the connection is healthy. A non-destructive provider-authorized write creates or updates provider data without publishing public content or deleting resources, such as saving a draft or updating a non-public metadata field. Modes:
  • Always ask: provider writes pause for approval.
  • Learn after 3: after you approve the same action shape 3 times, the gate auto-allows it for 14 days; after that window expires, the next matching action asks again.
  • Auto when connected: non-destructive provider writes can run without prompting when the brand policy allows it and the connection is healthy.
Read-only integration calls remain automatic.
Chat instructions can guide how daoco plans provider work, but they do not grant permission to send, publish, update, delete, or bypass an approval gate.