CRM Integrations
Civic IQ connects directly to a CRM so outreach activity, contact data, and pipeline updates flow into the tools the team already uses — signals acted on in Civic IQ appear in the CRM, and deal progress stays consistent across both platforms.
To configure a CRM connection, navigate to Settings and select CRM under the Integrations tab.
Supported CRM Platforms
| CRM | Notes |
|---|---|
| HubSpot | Full two-way sync. Contacts, deals, and sequence activity log automatically. Recommended for teams already using HubSpot for inbound and outbound sales. |
| Salesforce | Enterprise-grade integration with bidirectional contact and opportunity sync. Suitable for larger sales teams with established Salesforce workflows. |
| Pipedrive | Lightweight deal and contact sync. Well-suited for smaller teams using Pipedrive as their primary sales tool. |
| Zoho CRM | Syncs leads, contacts, and activity from Civic IQ sequences directly into the Zoho account. |
| Attio | Modern CRM integration. Syncs contact and deal data from Civic IQ sequences and pipeline actions. |
| Monday.com | Project and deal board integration — Civic IQ pipeline items and contact updates flow into the Monday.com workspace. |
Connecting a CRM
- Connect — starts the authorization flow for that CRM; once authorized, the connection status shows as active
- Settings — once connected, configure sync behavior: which fields map to which CRM properties, how contacts are created or updated, and whether pipeline activity triggers deal creation
Logging Sequence Emails to the CRM
For CRMs that support BCC logging (HubSpot, Salesforce, Pipedrive):
- Open the connected CRM's Settings panel within Civic IQ
- Locate the BCC Logging Address field and copy the address provided
- Paste this address into the BCC field in Civic IQ's email settings
Once configured, every outbound sequence email is silently copied to the CRM, and replies from agency contacts are visible in the contact's activity history.
Export History
Every export to a connected CRM is logged and viewable, giving an audit trail of what was sent, when, and by whom. This is useful for two things:
- Troubleshooting — cross-checking export dates against CRM records to catch issues like duplicate profiles or failed syncs. Internally, the team uses this to trace when a bad export happened and correct the underlying field mapping.
- Oversight across a team — for accounts where one person manages CRM integration on behalf of multiple reps, Export History gives visibility into everyone's export activity rather than just your own, so nothing gets missed or double-handled.
If you notice unexpected duplicates or missing records in your CRM, Export History is the first place to check — it will show whether the record was actually sent, and when.
What Syncs Automatically
- A contact added from a signal's Contacts tab creates or updates that contact record in the CRM
- A signal moved to the Pipeline can trigger deal or opportunity creation
- Sequence emails sent and replies received are logged against the relevant contact
- Pipeline stage changes in Civic IQ can update the corresponding deal stage in the CRM
Exact behavior depends on the CRM and how field mapping is configured in Settings — review the Settings panel for the specific integration to confirm which sync actions are enabled.
Automatic Signal Export
By default, sending a signal to your CRM is a manual, per-signal action via the Sync to [CRM] button on the Signal Card. For teams that want every new signal to flow to the CRM without a manual step, there's an auto-sync option under Configure → CRM — once enabled, any new opportunity that appears in AI Mode is automatically pushed to the CRM as soon as it's generated.
Trade-off to flag: manual export lets you quality-check a signal in Civic IQ before it reaches your CRM. Auto-sync skips that check — everything gets exported, so QA has to happen on the CRM side instead. Teams with a rep manually reviewing each signal before it's worth sending to sales typically stick with manual export; teams that want zero manual steps and are comfortable doing QA downstream use auto-sync.
A related, narrower option exists at the List level: instead of syncing every signal, a specific List (e.g., a competitor-tracking list) can have its own "Export to CRM" button enabled, syncing just that list's agencies rather than the full signal feed.