Understand the Capsule CRM Integration

This article explains how the Capsule CRM integration works, including the data flow, workflow structure, and technical implementation details.

Integration Architecture

The Capsule CRM integration operates through Zapier workflows that connect WhatConverts and Capsule CRM bidirectionally. This Zapier-based approach requires you to configure separate automated workflows (called Zaps) for each type of data you want to sync between the platforms.

Each Zapier workflow monitors one platform for specific events (new leads or contact updates), processes the data through search and mapping steps, then creates or updates corresponding records in the destination platform.

Data Flow Options

The Capsule CRM integration supports two data flow directions:

From WhatConverts to Capsule CRM

• New leads trigger workflows that create contact records in Capsule CRM
• Lead information includes name, phone, email, and other tracked details
• The WhatConverts Lead ID is stored as a custom field in Capsule for future reference

From Capsule CRM to WhatConverts

• Contact updates in Capsule CRM trigger workflows that update existing leads in WhatConverts
• Sales values, quote amounts, and deal status flow back to WhatConverts
• The stored Lead ID custom field connects the Capsule contact to the correct WhatConverts lead

WhatConverts to Capsule CRM Workflow Structure

The lead-to-contact workflow follows a simple structure:

• Trigger: A new lead is created in WhatConverts (from a phone call, form submission, or chat)
• Create Contact: The workflow creates a new contact in Capsule CRM with the lead information
• Store Lead ID: The WhatConverts Lead ID is saved as a custom field in the Capsule contact record for future updates

Capsule CRM to WhatConverts Workflow Structure

The sales tracking workflow follows a more complex structure to ensure proper data matching:

• Trigger: A contact is updated in Capsule CRM (typically when a deal closes or a quote is finalized)
• Retrieve Lead ID: The workflow reads the WhatConverts Lead ID from the custom field in the Capsule contact
• Update Lead: If the Lead ID exists, the workflow uses it to update the correct lead in WhatConverts with the quote and sales values.

The Importance of Lead ID Custom Fields

Storing the WhatConverts Lead ID as a custom field in Capsule CRM is critical for accurate data syncing. This Lead ID acts as a unique identifier that connects the Capsule contact to the specific lead in WhatConverts, ensuring that sales and quote updates are applied to the correct lead record rather than creating duplicates or updating the wrong lead.

Without the Lead ID stored in Capsule, you must rely on searching WhatConverts by phone number or email address, which can be less reliable if contact information changes or multiple leads share the same details.

Integration Limitations

The Capsule CRM integration has several important limitations to consider:

• Manual Workflow Setup: Unlike some plug-and-play integrations, the Capsule CRM integration requires you to manually configure each Zapier workflow
• Separate Workflows Required: You must create and maintain distinct Zapier workflows for each data flow direction
• Zapier Account Required: This integration relies on Zapier as the middleware platform, meaning you need an active Zapier account and your workflows count against any applicable Zapier usage limits
• Custom Field Management: You must manually create custom fields in Capsule CRM and properly map them in your Zapier workflows
• No Real-Time Sync: Data syncs based on Zapier's polling intervals (1-15 minutes depending on your Zapier plan), not instantly

Related Topics

• What is the Capsule CRM Integration?
• Connect WhatConverts to Capsule CRM
• Send Leads from WhatConverts to Capsule CRM
• Send Quote and/or Sales Value from Capsule CRM to WhatConverts