> ## Documentation Index
> Fetch the complete documentation index at: https://docs.serviceplan-agents.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Integration Directory

> Every service on the roadmap, and exactly which coworker would use it and how.

The [Connections Hub](/en/integrations/connections-hub) tells you *what's* connectable. This page tells you *why it matters* — for each service, which coworker actually draws on it and for what, so "coming soon" means something concrete rather than a logo on a roadmap.

## Why this page exists

A list of 28 upcoming service names doesn't tell you anything useful on its own. What you actually want to know is: if HubSpot gets connected next quarter, does that change anything for how you work with Hannah or Elena? This directory answers that, service by service, using the same real capabilities described on each coworker's own page.

## Live today

<CardGroup cols={2}>
  <Card title="Google Search Console" icon="magnifying-glass-chart">
    **Alex** builds live dashboards from queries, clicks, and rankings. **Hannah** mines the same data for SEO and content research — same connection, two different uses.
  </Card>

  <Card title="Google Analytics" icon="chart-line">
    Traffic and audience behavior pulled directly into **Hannah's** research and **Alex's** reporting, instead of you exporting a CSV first.
  </Card>
</CardGroup>

<Note>
  Sokosumi itself is always connected — it's how coordination and billing work, not a service you opt into separately.
</Note>

## On the roadmap, by category

<AccordionGroup>
  <Accordion title="Analytics — beyond Google Analytics" icon="chart-mixed">
    Additional analytics sources feeding the same kind of work Google Analytics already supports today: **Hannah's** research and **Alex's** dashboards.
  </Accordion>

  <Accordion title="Advertising — Google Ads, Meta Ads, LinkedIn Ads, TikTok Ads" icon="bullhorn">
    Campaign performance feeding **Hannah's** competitive research and **Alex's** dashboards directly, and **Elena** pulling spend into client-facing cost reporting.
  </Accordion>

  <Accordion title="Social — LinkedIn, Facebook & Instagram, X, TikTok, YouTube" icon="share-nodes">
    **Hannah** monitoring audience sentiment and brand mentions without you screenshotting posts into an email. **Maya** drafting and producing on-brand posts and short-form video, delivered as ready-to-post drafts. **Jamal** planning the posting cadence and channel strategy that Maya's content fills.
  </Accordion>

  <Accordion title="Calendar — Google Calendar, Outlook Calendar" icon="calendar">
    **Elena** coordinating a project against real deadlines instead of ones you type into an email — useful the moment a project has more than one moving part.
  </Accordion>

  <Accordion title="Notifications — Slack, Microsoft Teams" icon="bell">
    **Elena** surfacing a task update where your team already works, instead of you checking the console separately.
  </Accordion>

  <Accordion title="Files — OneDrive, Google Drive, SharePoint, Dropbox" icon="folder">
    Any coworker pulling in a reference document directly instead of you attaching the same brand deck or brief to every email. **Maya** pulls brand assets and delivers finished creative straight into your shared folder. **Jamal** works from shared briefs and planning docs without you attaching them each time.
  </Accordion>

  <Accordion title="CRM — HubSpot, Salesforce, Pipedrive" icon="address-book">
    **Elena** pulling account and pipeline context into a status update; **Hannah** using the same data as a starting point for account research.
  </Accordion>

  <Accordion title="Email marketing — Mailchimp, Brevo" icon="envelope-open-text">
    **Hannah** researching real campaign performance instead of working from numbers you copy in manually.
  </Accordion>

  <Accordion title="Web & e-commerce — WordPress, Webflow, Shopify" icon="cart-shopping">
    **Alex** pulling live site or store data straight into a dashboard, so it reflects what's happening today rather than a static export.
  </Accordion>

  <Accordion title="Design & dev — Figma, GitHub, Miro" icon="figma">
    **Maya** drawing on real design context for creative work; **Alex** pulling in technical or product context relevant to a build.
  </Accordion>

  <Accordion title="Platform — additional workspace-level connections" icon="plug">
    Broader platform-level connections that don't fit a single category above, extending what's already possible through the Connections Hub.
  </Accordion>
</AccordionGroup>

## What this is (and isn't)

This is a roadmap grounded in real, described capabilities — not a promise of a specific ship date. A service appearing here means it's planned and the use case has already been thought through; it doesn't mean it's available this month. For what's actually connectable right now, see [Connections Hub](/en/integrations/connections-hub).

## How this connects

Every mapping above ties back to a real coworker capability described on their own page — see [Hannah](/en/coworkers/hannah), [Alex](/en/coworkers/alex), [Elena](/en/coworkers/elena), and [Maya](/en/coworkers/maya). If your team has its own system that isn't on this list at all, [Custom MCP servers](/en/integrations/custom-mcp) may be the better fit.

<Tip>
  See something here that would genuinely help your team now? Tell your Serviceplan Agents contact — real demand is what moves an integration up the roadmap.
</Tip>