Overview

Who is this guide for? This guide is for administrators and RevOps professionals who are setting up data integrations for their organization.

What Are Integrations?

Integrations allow Quivly to connect to your existing business systems and automatically sync customer data. By connecting your CRM, billing platform, support system, and data warehouse, Quivly creates a unified view of each customer across all your data sources. Without integrations: Scattered data across multiple platforms, manual exports, incomplete customer views With integrations: Automatic data sync, complete customer 360, real-time insights

Integration Categories

Quivly supports 6 categories of integrations:

CRM

Salesforce, HubSpotSyncs customers (companies/accounts), contacts, opportunities (deals), and account owners

Billing

StripeSyncs revenue data, subscriptions, invoices, payment status, and MRR metrics

Support

PylonSyncs support tickets, issue status, response times, and customer sentiment

Call Recordings

FirefliesSyncs call transcripts, speaker identification, summaries, and sentiment analysis

Data Warehouses

BigQuery, Snowflake, PostgreSQL, MySQL, RedshiftSyncs product usage data and custom metrics from your data warehouse

Communication

SlackSends notifications and alerts to your team channels

How Integrations Work in Quivly

Authentication Methods

Quivly uses two types of authentication:

OAuth (CRM, Billing, Support, Calls)
Credentials (Data Warehouses)

How it works:

You click “Connect” in Quivly
You’re redirected to the external platform (HubSpot, Stripe, etc.)
You log in and approve Quivly’s access
You’re redirected back to Quivly with a secure token
Quivly uses this token to sync data automatically

Platforms using OAuth:

HubSpot
Salesforce
Stripe
Pylon
Fireflies
Slack

Benefits:

Secure (no passwords shared)
Scoped permissions (Quivly only gets read access)
Easy to revoke access
Automatically renews tokens

Data Sync Behavior

Sync Frequency

Integration Type	Sync Frequency	Description
CRM (Salesforce, HubSpot)	Every 15 minutes	Real-time customer and deal updates
Billing (Stripe)	Every 15 minutes	Near real-time revenue and subscription changes
Support (Pylon)	Every 15 minutes	Quick reflection of ticket status changes
Call Recordings (Fireflies)	Every 30 minutes	Transcripts available shortly after calls end
Data Warehouses	Every 6 hours (configurable)	Batch processing for large datasets
Slack	Real-time (outbound only)	Notifications sent immediately when triggered

Sync frequencies are defaults and can be adjusted in integration settings. More frequent syncs consume more API quota and may incur costs.

Initial Sync vs Incremental Sync

Initial Sync:

Runs once when you first connect an integration
Syncs all historical data (typically last 90 days to 12 months)
Can take 5 minutes to several hours depending on data volume
You’ll receive an email when complete

Incremental Sync:

Runs automatically at the configured frequency
Only syncs new or updated records since the last sync
Much faster (usually < 1 minute)
Happens in the background

Example:

Initial Sync (Jan 1):
  - Syncs all 500 HubSpot companies
  - Syncs all 1,200 contacts
  - Syncs all 300 deals
  - Takes 10 minutes

Incremental Sync (Jan 1, 12:15 PM):
  - Syncs 3 new companies created since initial sync
  - Updates 5 companies that changed
  - Syncs 2 new deals
  - Takes 15 seconds

Prerequisites by Integration Type

CRM Integrations (Salesforce, HubSpot)

HubSpot Prerequisites

Required:

HubSpot account (Professional or Enterprise tier recommended)
Admin access to authorize OAuth scopes
Permissions to view Companies, Contacts, and Deals

Recommended:

Custom properties already configured in HubSpot
At least 30 days of historical data
Clean data (no duplicate companies)

Salesforce Prerequisites

Required:

Salesforce account (any edition)
System Administrator role or API Enabled permission
Permissions to view Accounts, Contacts, and Opportunities

Recommended:

Custom fields already created if needed
Data standardization (consistent naming conventions)
Duplicate management rules in place

Billing Integration (Stripe)

Required:

Stripe account with active subscriptions
Admin or Developer role in Stripe
Permission to create restricted API keys

Recommended:

Subscription products already configured
Customer metadata populated
Consistent customer email addresses (for matching with CRM)

Support Integration (Pylon)

Required:

Pylon account
Admin access to generate API key
Active support tickets or issues

Recommended:

Tags and categories configured in Pylon
Customer linking already set up

Call Recording Integration (Fireflies)

Required:

Fireflies account
Admin access to generate API key
Call recordings available

Recommended:

Speaker identification enabled
Calls tagged or categorized

Data Warehouse Integrations

BigQuery Prerequisites

Google Cloud Platform project
BigQuery dataset with usage data
Permission to create service accounts
Tables structured in long format or wide format

Snowflake Prerequisites

Snowflake account and warehouse
Database and schema with usage data
Permission to create database users
Tables with customer identifiers

Planning Your Integration Strategy

Before connecting integrations, follow this recommended order:

Start with CRM (Required)

Connect Salesforce or HubSpot firstWhy: CRM contains your core customer list. All other integrations will link to these customer records.What you’ll get:

Customer names and domains
Contacts and stakeholders
Opportunities and deal stages
Account owners and territories

Add Billing (Highly Recommended)

Connect Stripe for revenue dataWhy: Revenue metrics are critical for health scores and churn prediction.What you’ll get:

MRR (Monthly Recurring Revenue)
Subscription status and plan details
Invoice history and payment status
Renewal dates

Add Support (Recommended)

Connect Pylon for ticket dataWhy: Support tickets indicate customer friction and product issues.What you’ll get:

Open and closed tickets
Response and resolution times
Issue categories and priorities
Customer satisfaction scores

Add Product Usage (Optional but Valuable)

Connect BigQuery or SnowflakeWhy: Usage data shows product adoption and engagement.What you’ll get:

Daily/weekly active users
Feature adoption metrics
Usage trends over time
Power users vs inactive accounts

Add Call Recordings (Optional)

Connect FirefliesWhy: Call transcripts provide qualitative insights and sentiment.What you’ll get:

Call summaries and key topics
Speaker identification
Sentiment analysis
Action items from calls

Add Slack Notifications (Optional)

Connect Slack for alertsWhy: Get notified when important events occur.What you’ll get:

Health score alerts
Renewal notifications
Market signal updates
Custom alerts

Data Matching Across Integrations

When you connect multiple integrations, Quivly needs to match customer records across systems. Example:

HubSpot company: “Acme Corporation” (ID: 12345)
Stripe customer: “Acme Corp” (ID: cus_abc123)
BigQuery: customer_id = “acme-corp-001”

How do we know these are the same customer?

Matching Strategies

By External ID
By Email Domain
By Company Name
Manual Linking

Best for: When your CRM stores IDs from other systemsHow it works:

Store Stripe customer ID in HubSpot custom field
Store BigQuery customer_id in Salesforce
Quivly matches using these foreign keys

Example HubSpot setup:

Custom Property: stripe_customer_id
Value: cus_abc123

Most accurate - Direct ID matching

Best for: B2B companies with unique email domainsHow it works:

Extract domain from email addresses
Match across systems by domain

Example:

HubSpot: domain = "acme.com"
Stripe: customer_email = "[email protected]" → domain = "acme.com"
Match!

⚠️ Good but not perfect - Can fail for generic domains (gmail.com)

Best for: When domain matching isn’t reliableHow it works:

Normalize company names (lowercase, remove punctuation)
Fuzzy matching with similarity scoring

Example:

HubSpot: "Acme Corporation"
Stripe: "Acme Corp"
Normalized: "acme corporation" ≈ "acme corp" (85% match)
Match! 

⚠️ Less accurate - May create false matches or miss valid ones

Configure your matching strategy in Settings → Objects → Customers → Cross-System Matching

Integration Health Monitoring

After connecting integrations, monitor their health regularly.

Status Indicators

Status	Icon	Meaning	Action Needed
Healthy	🟢	Syncing successfully, no errors	None - monitor periodically
Warning	🟡	Minor issues, some records failing	Review logs, may need attention
Error	🔴	Sync failed, authentication issue	Fix immediately - data is stale
Paused	⏸️	Manually paused by admin	Resume when ready

Common Health Issues

Authentication Expired

Symptoms:

Red error status
“Token expired” or “Access denied” in logs

Cause:

OAuth token revoked
Password changed
Permissions removed

Fix:

Go to Settings → Integrations → [Integration Name]
Click “Re-authenticate”
Log in and approve permissions again

Rate Limits Exceeded

Symptoms:

Yellow warning status
“Rate limit exceeded” in logs
Sync delays

Cause:

Too many API requests
Sync frequency too high
Other apps also using API quota

Fix:

Reduce sync frequency (e.g., from 15 min to 30 min)
Contact platform support to increase API limits
Review other integrations consuming quota

Data Quality Issues

Symptoms:

Yellow warning status
“X records skipped” in logs
Customers not appearing in Quivly

Cause:

Missing required fields (e.g., customer_id is NULL)
Invalid data types
Matching failures

Fix:

Review sync logs for specific errors
Fix data in source system
Trigger manual re-sync

Security and Permissions

What Permissions Does Quivly Request?

Integration	Permissions	Why Needed
HubSpot	Read Companies, Contacts, Deals, Owners	Sync customer and opportunity data
Salesforce	Read Accounts, Contacts, Opportunities, Users	Sync customer and opportunity data
Stripe	Read Customers, Subscriptions, Invoices, Products	Sync revenue and billing data
Pylon	Read Issues, Accounts	Sync support ticket data
Fireflies	Read Transcripts	Sync call recording data
BigQuery	BigQuery Data Viewer, Job User	Query usage data tables

Quivly NEVER requests write permissions. We only read data from your systems - we never modify, delete, or create records in your CRM, billing, or other platforms.

Data Storage and Privacy

Where is your data stored?

Quivly stores synced data in a secure, encrypted database (PostgreSQL)
Data is isolated by organization (row-level security)
All connections use TLS/SSL encryption in transit

Who can access your data?

Only users in your Quivly organization
Role-based access control (Admin, Member, Viewer)
Quivly employees cannot access your data without explicit permission

How long is data retained?

Active customer data: Retained indefinitely while integration is active
Deleted customer data: Soft-deleted for 90 days, then permanently removed
Audit logs: Retained for 12 months

Compliance:

SOC 2 Type II certified
GDPR compliant
CCPA compliant

Next Steps

Connect HubSpot

Step-by-step guide to connect HubSpot CRM

Connect Salesforce

Step-by-step guide to connect Salesforce CRM

Connect Stripe

Step-by-step guide to connect Stripe billing

BigQuery Setup

Connect your data warehouse for usage data

Need help?

Email support: [email protected]
Review troubleshooting: Common Issues
Platform setup guide: Admin Quick Start

Introduction

Integrations

Data Models

Field Mappings

Settings

What Are Integrations?

Integration Categories

CRM

Billing

Support

Call Recordings

Data Warehouses

Communication

How Integrations Work in Quivly

Authentication Methods

Data Sync Behavior

Sync Frequency

Initial Sync vs Incremental Sync

Prerequisites by Integration Type

CRM Integrations (Salesforce, HubSpot)

Billing Integration (Stripe)

Support Integration (Pylon)

Call Recording Integration (Fireflies)

Data Warehouse Integrations

Planning Your Integration Strategy

Data Matching Across Integrations

Matching Strategies

Integration Health Monitoring

Status Indicators

Common Health Issues

Security and Permissions

What Permissions Does Quivly Request?

Data Storage and Privacy

Next Steps

Connect HubSpot

Connect Salesforce

Connect Stripe

BigQuery Setup

Introduction

Integrations

Data Models

Field Mappings

Settings

​What Are Integrations?

​Integration Categories

CRM

Billing

Support

Call Recordings

Data Warehouses

Communication

​How Integrations Work in Quivly

​Authentication Methods

​Data Sync Behavior

​Sync Frequency

​Initial Sync vs Incremental Sync

​Prerequisites by Integration Type

​CRM Integrations (Salesforce, HubSpot)

​Billing Integration (Stripe)

​Support Integration (Pylon)

​Call Recording Integration (Fireflies)

​Data Warehouse Integrations

​Planning Your Integration Strategy

​Data Matching Across Integrations

​Matching Strategies

​Integration Health Monitoring

​Status Indicators

​Common Health Issues

​Security and Permissions

​What Permissions Does Quivly Request?

​Data Storage and Privacy

​Next Steps

Connect HubSpot

Connect Salesforce

Connect Stripe

BigQuery Setup

What Are Integrations?

Integration Categories

How Integrations Work in Quivly

Authentication Methods

Data Sync Behavior

Sync Frequency

Initial Sync vs Incremental Sync

Prerequisites by Integration Type

CRM Integrations (Salesforce, HubSpot)

Billing Integration (Stripe)

Support Integration (Pylon)

Call Recording Integration (Fireflies)

Data Warehouse Integrations

Planning Your Integration Strategy

Data Matching Across Integrations

Matching Strategies

Integration Health Monitoring

Status Indicators

Common Health Issues

Security and Permissions

What Permissions Does Quivly Request?

Data Storage and Privacy

Next Steps