Validate and Troubleshoot Your OnePageCRM Integration
Ensure your OnePageCRM integration is working correctly in both directions.
Verify Your Workflows Are Active
Before troubleshooting data issues, confirm your Zapier workflows are active and running:
- Log in to your Zapier account.
- Navigate to "Zaps" to see all your workflows.
- Check that all your OnePageCRM workflows show as "Active".
- Review the "Zap Runs" for each workflow to see recent executions by entering the workflow and clicking the option on the left-hand side.
- If a workflow is paused or off, publish it to turn it back on.
Test With Sample Data
To verify your workflows are configured correctly:
- In Zapier, open one of your OnePageCRM workflows.
- Click "Test" on each step to run it with sample data.
- Verify that each step completes successfully without errors.
- Check that the final action step (Create Contact or Update Lead) shows success.
- Look in the destination platform to confirm the record was created.
Troubleshoot WhatConverts to OnePageCRM Workflows
Issue: Contacts Not Being Created in OnePageCRM
Possible causes and solutions:
- Workflow is paused or turned off: Check your Zapier dashboard and turn the workflow back on
- API credentials expired: Reconnect both your WhatConverts and OnePageCRM accounts in Zapier
- Required fields missing: Verify that the WhatConverts lead has all required information (name, email, or phone)
- Trigger not firing: Check WhatConverts to confirm new leads are actually being tracked
Issue: Lead ID Not Storing in OnePageCRM
Possible causes and solutions:
- Custom field not created: Verify you created the custom field in OnePageCRM for storing Lead IDs on Contacts
- Field not mapped: Check your workflow to ensure the Lead ID from WhatConverts is mapped to the correct custom field in OnePageCRM
- Field type mismatch: Ensure the custom field in OnePageCRM is set to the correct field type
- Wrong field type: Make sure you created the custom field on Contacts, not another field type
Issue: Duplicate Contacts Being Created
Possible causes and solutions:
- No duplicate checking: OnePageCRM may not automatically prevent duplicate contacts. Consider adding a "Find Contact" step before creating to check for existing contacts and only continue if no match is found.
- Different contact information: If phone or email formatting differs slightly, OnePageCRM may not recognize them as duplicates
- Workflow triggering multiple times: Check your Zapier task history to see if the workflow is running multiple times for the same lead
Troubleshoot OnePageCRM to WhatConverts Workflows
Issue: Leads Not Being Updated in WhatConverts
Possible causes and solutions:
- Lead ID not stored: If the OnePageCRM contact doesn't have a WhatConverts Lead ID in the custom field, the update can't find the correct lead
- Lead ID field not mapped: Verify your workflow is pulling the Lead ID from the correct custom field in OnePageCRM
- Wrong lead ID value: Check that the stored Lead ID actually corresponds to an existing lead in WhatConverts
- Find Lead step failing: If using the Find Lead approach, ensure the phone or email exactly matches the lead in WhatConverts
- Deal not associated with contact: Ensure the deal in OnePageCRM is associated with a contact that has the Lead ID stored
Issue: Quote/Sales Values Not Updating Correctly
Possible causes and solutions:
- Wrong field mapping: Verify you're mapping the correct OnePageCRM deal amount to Quote Value and Sales Value in WhatConverts
- Data type mismatch: Ensure the values being sent are numbers, not text
- Empty values: Check that the OnePageCRM deal actually has an amount value
- Field mapping to the wrong WhatConverts field: Confirm you're updating the correct fields (Quote Value vs Sales Value)
- Deal status not triggering: Ensure your trigger is configured to fire on the correct deal status changes
Issue: Workflow Updates Wrong Lead
Possible causes and solutions:
- No Lead ID stored: Without the stored Lead ID, the Find Lead step may match the wrong lead if multiple leads share similar contact information
- Search criteria too broad: If searching by partial phone or email, you may match incorrect leads. Use exact match criteria
- Multiple leads with the same contact info: Some businesses may have legitimate duplicate contact information. This is why Lead ID storage is critical
Issue: Trigger Firing Too Often
Possible causes and solutions:
- Trigger set to any deal update: If your trigger is "Updated Deal" without filters, it will fire on any field change. Add trigger filters to only fire on specific deal status changes
- Bulk updates in OnePageCRM: If you're doing bulk updates in OnePageCRM, this may trigger many workflow runs. Consider temporarily pausing the workflow
- Integration loops: Ensure you don't have workflows that create circular updates between the platforms
Validate Data Accuracy
For WhatConverts to OnePageCRM workflows
- Create a test lead in WhatConverts with known details.
- Wait for the workflow to trigger (usually within 1-15 minutes).
- Check your OnePageCRM account for the new contact.
- Verify all mapped fields are populated correctly.
- Confirm the Lead ID is stored in the custom field.
For OnePageCRM to WhatConverts workflows
- Update a deal in OnePageCRM or change its status to "Won".
- Ensure the associated contact has a WhatConverts Lead ID stored in the custom field.
- Wait for the workflow to trigger.
- Check WhatConverts to confirm the lead was updated with the correct deal values.
- Verify the update was applied to the correct lead (check using the Lead ID).
Check API Connection Status
If you suspect authentication issues:
- In Zapier, open your OnePageCRM workflow.
- Click on any OnePageCRM step.
- Click "Change" next to the connected account.
- Try reconnecting with your OnePageCRM credentials.
- Repeat for the WhatConverts connection if needed.
- Test the connection by running a sample through the workflow.
Related Topics
Get a FREE presentation of WhatConverts
One of our marketing experts will give you a full presentation of how WhatConverts can help you grow your business.
Schedule a Demo