Skip to main content
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 Data → Integrations.

​
Available integrations

Tiles marked coming soon, such as Chargebee, Zendesk, Gong, Jira, Amplitude, Mixpanel, and Google Sheets, cannot be connected yet. Email 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 let agents and 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. Gmail and Google Calendar also sync customer-linked email threads and meetings into Communications. These records have visibility controls; connecting your account does not make every message or meeting visible to the whole organization. Calendly is used as an agent tool. 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

1

Check the sync

Open the integration’s detail page to see sync activity and logs.
2

Map your fields

Data-source records map to Quivly’s customer model. Review and customize under Data → Objects. See field mappings.
3

Verify customer matching

Records from different systems are linked to the same customer. See cross-system linking.
CRM records also follow any configured account import scope. Receiving source data does not mean every prospect becomes a customer in Quivly. Monaco and Octolane require an explicit initial scope and saved object mappings.

​
FAQ

Data ingestion reads your connected sources. Separately, supported AI actions can propose changes in Quivly or connected apps for review, and published workflows can run the steps your team configures. Connecting a source alone does not authorize outbound changes. See security and compliance.
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.
Use your data warehouse (Snowflake, BigQuery, or Redshift), connect PostHog directly, or push events to the Usage Push API from your own backend.