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

# Integrations Overview

> Connect your CRM, billing, support, call recording, Slack, and product usage systems to Quivly. What's available, how connections work, and what data syncs.

Integrations feed Quivly's unified customer model. Connect a system once and its data flows into the right customer profile automatically.

All integrations live in **Settings → Integrations**.

## Available integrations

| Category        | Available now                                                                                                                                                                                              | How it connects                                      |
| --------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------- |
| CRM             | [Salesforce](/integrations/crm/salesforce), [HubSpot](/integrations/crm/hubspot)                                                                                                                           | OAuth                                                |
| Billing         | [Stripe](/integrations/billing/stripe)                                                                                                                                                                     | OAuth                                                |
| Support         | [Pylon](/integrations/support/pylon)                                                                                                                                                                       | OAuth                                                |
| Call recordings | [Fireflies](/integrations/call-recordings/fireflies), [Fathom](/integrations/call-recordings/fathom), [Granola](/integrations/call-recordings/granola)                                                     | OAuth                                                |
| Communication   | [Slack](/integrations/communication/slack)                                                                                                                                                                 | OAuth (workspace bot + optional personal connection) |
| Agent tools     | [Gmail](/integrations/communication/gmail), [Google Calendar](/integrations/communication/google-calendar), [Calendly](/integrations/communication/calendly)                                               | OAuth, per user                                      |
| Product usage   | [Snowflake](/integrations/warehouses/snowflake), [BigQuery](/integrations/warehouses/bigquery), [PostHog](/integrations/product-usage/posthog), [Usage Push API](/integrations/product-usage/api-overview) | Credentials / API key                                |
| Developer       | GitHub (for [skill import](/developers/github-skill-import))                                                                                                                                               | GitHub App install                                   |

Tiles for Attio, Chargebee, Zendesk, Intercom, Gong, Jira, Amplitude, Mixpanel, Redshift, and Google Sheets appear in the app as **coming soon** — you can't connect them yet. Email [support@quivly.ai](mailto:support@quivly.ai) if one of these is blocking you.

## Two kinds of integrations

**Data sources** (CRM, billing, support, calls, warehouses, PostHog) sync records into Quivly — customers, contacts, opportunities, subscriptions, invoices, tickets, call transcripts, usage metrics. These are read-only: Quivly never writes back to them. Each has a detail page with sync logs.

**Agent tools** (Gmail, Google Calendar, Calendly) don't sync any data. They let [agents](/product/agents) and [actions](/product/actions) do things — send an email, create a calendar event — as the connected user. Each teammate connects their own account, so an agent can send as the account owner rather than a bot.

Slack is both: the workspace bot ingests conversations from mapped customer channels *and* sends messages, and teammates can optionally connect a personal Slack so messages send as them.

## After connecting

<Steps>
  <Step title="Check the sync">
    Open the integration's detail page to see sync activity and logs.
  </Step>

  <Step title="Map your fields">
    Data-source records map to Quivly's customer model. Review and customize under **Settings → Objects**. See [field mappings](/field-mappings/introduction).
  </Step>

  <Step title="Verify customer matching">
    Records from different systems are linked to the same customer. See [cross-system linking](/field-mappings/cross-system-linking).
  </Step>
</Steps>

## FAQ

<AccordionGroup>
  <Accordion title="Does Quivly write data back to my CRM or billing system?">
    No. Data-source integrations are read-only. Only agent tools (Gmail, Calendar, Slack) send anything outbound, and only through steps you configure.
  </Accordion>

  <Accordion title="What's the difference between an org-wide and a per-user connection?">
    Data sources are connected once for the whole organization by an admin. Agent tools like Gmail and Calendly are connected per teammate, so outbound messages can be sent as a specific person.
  </Accordion>

  <Accordion title="I don't see my product analytics tool. How do I get usage data in?">
    Use your data warehouse (Snowflake or BigQuery), connect PostHog directly, or push events to the [Usage Push API](/integrations/product-usage/api-overview) from your own backend.
  </Accordion>
</AccordionGroup>