Understand the OnePageCRM Integration

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

Integration Architecture

The OnePageCRM integration uses Zapier workflows to connect WhatConverts and OnePageCRM in both directions. Each type of data you want to sync requires its own Zap.

Each Zap monitors one platform for specific events, such as new leads or deal updates, maps the relevant fields, and then creates or updates the corresponding record in the other platform.

This approach keeps data synchronized while giving you full control over what is sent and when.

Data Flow Options

The OnePageCRM integration supports two data flow directions:

From WhatConverts to OnePageCRM

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

From OnePageCRM to WhatConverts

• Deal updates in OnePageCRM trigger workflows that update existing leads in WhatConverts
• Deal values, closed amounts, and deal status flow back to WhatConverts
• The stored Lead ID custom field connects the OnePageCRM contact to the correct WhatConverts lead
• Trigger event is "Deal Won" or "Updated Deal"

WhatConverts to OnePageCRM 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 OnePageCRM with the lead information
• Store Lead ID: The WhatConverts Lead ID is saved as a custom field in the OnePageCRM contact record for future updates

OnePageCRM to WhatConverts Workflow Structure

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

• Trigger: A deal is updated in OnePageCRM (trigger events: "Deal Won" or "Updated Deal")
• Retrieve Lead ID: The workflow reads the WhatConverts Lead ID from the custom field in the associated OnePageCRM contact
• Update Lead: If the Lead ID exists, the workflow uses it to update the correct lead in WhatConverts with deal values
• Alternative - Find Lead: If no Lead ID is stored, the workflow can search for the lead in WhatConverts using contact information (phone or email) before updating

Integration Limitations

The OnePageCRM integration has several important limitations to consider:

• Manual Workflow Setup: Unlike some plug-and-play integrations, the OnePageCRM 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 OnePageCRM 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.
• Deal Association Required: When sending data from OnePageCRM to WhatConverts, the deal must be associated with a contact that has the Lead ID stored.

Related Topics

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