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

# Integrations overview: all connectors and APIs

> Manage Simio connectors from Settings, browse the audit trail, and see which integrations are available today and which are coming later this year.

Simio can connect to a number of third-party tools. You manage every connector from **Settings > Integrations & developers > Connectors**, which shows a catalog of every available connector split into "Connected" and "Available" sections. Opening a connector shows an overview, an activity log of recent calls made to or from it, and a settings/credentials form.

Every connector is scoped to one company: a connector configured for Company A never sees or affects Company B's data. Inbound calls from external tools (where the third party calls into Simio) are authenticated with the company's unique Simio API key, the same key shown on the "API & webhooks" settings page.

## Activity log and audit trail

Every connector's detail page has an **Activity** tab showing a log of calls made to or received from that integration: the endpoint, direction (into Simio or out to the provider), timestamp, success/failure, and how long it took. For most connectors, failed outbound calls can be re-sent directly from this log ("rerun"), which is useful for troubleshooting a one-off delivery failure without needing engineering involvement. This audit trail exists for every connector and is a useful first stop when a customer asks "did this message/sync actually happen?"

## Available today

Simio groups connectors by function, not by product family, so that new integrations plug in cleanly as they ship.

### Marketing automation

<CardGroup cols={2}>
  <Card title="Brevo" icon="mail" href="/simio/integrations/brevo">
    Sync contacts and consent with Brevo email marketing, and trigger WhatsApp campaigns from Brevo automations.
  </Card>

  <Card title="Batch" icon="bolt" href="/simio/integrations/batch">
    Trigger Simio WhatsApp campaigns directly from a Batch marketing automation.
  </Card>
</CardGroup>

### Helpdesk

<CardGroup cols={2}>
  <Card title="Crisp" icon="message-circle" href="/simio/integrations/crisp">
    Reply to WhatsApp contacts from your Crisp inbox.
  </Card>

  <Card title="Easiware" icon="headphones" href="/simio/integrations/easiware">
    Handle WhatsApp conversations from Easiware.
  </Card>

  <Card title="Gorgias" icon="ticket" href="/simio/integrations/gorgias">
    Turn WhatsApp messages into Gorgias tickets and reply from Gorgias.
  </Card>
</CardGroup>

### Any other tool in your stack

If the tool you want to connect isn't covered by a connector, you can use the Simio API to build your own integration.

<CardGroup cols={2}>
  <Card title="Simio API" icon="code" href="/simio/api-reference/introduction">
    Send campaigns, trigger automations, and manage segments from any tool using the Simio API.
  </Card>
</CardGroup>

## Coming soon!

The following connectors are on the roadmap for Simio and will be documented here as they become available.

<CardGroup cols={2}>
  <Card title="Klaviyo" icon="mail-open">
    Sync contacts, trigger WhatsApp campaigns from Klaviyo flows, use custom properties, and run abandoned-cart automations.
  </Card>

  <Card title="Shopify" icon="shopping-cart">
    Collect opt-ins at checkout, sync order data, trigger order confirmation and back-in-stock automations.
  </Card>

  <Card title="Splio" icon="megaphone">
    Trigger Simio WhatsApp campaigns from Splio loyalty and marketing flows.
  </Card>

  <Card title="HubSpot" icon="user">
    Sync contact data with HubSpot CRM.
  </Card>

  <Card title="Zendesk" icon="headphones">
    Turn WhatsApp conversations into Zendesk tickets for your support team.
  </Card>
</CardGroup>

## Notes on other integration surfaces

Single sign-on connectors (Microsoft/Azure AD and Google Workspace) and the AI connector (Gaia) are configured from other areas of Settings, not from the Connectors catalog. See your organization and settings documentation for those.

## Troubleshooting a connector

A connector generally shows as **Connected** in the catalog once valid credentials have been saved for it. If an integration appears connected but data doesn't seem to be flowing, the Activity tab on that connector's detail page is the right place to check first. It shows exactly which calls were attempted, whether they succeeded, and the raw request/response involved, which is usually enough to tell whether the problem is a bad credential, a provider-side outage, or something on the Simio side worth escalating.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.