Built for startups,
scaled for unicorns
Successfully submitted!
Error! Please try again
Not every team uses HubSpot or Salesforce. If you're running your sales on Pipedrive, Zoho CRM, Close, Copper, or any other CRM, Zapier is your bridge to getting GrowSurf referral data into your pipeline. The integration works the same way regardless of CRM β the key is mapping GrowSurf's referral data to the right CRM fields.
This guide provides a universal approach to syncing GrowSurf referrals to any CRM through Zapier. You'll learn the data mapping patterns, field creation strategy, and workflow setup that works across all CRM platforms, with specific tips for popular options.
Before building the Zap, create custom fields in your CRM to store referral data. The field names may differ by CRM, but the data types are universal.
Create the main Zap that pushes new referral data from GrowSurf to your CRM.
Prevent duplicate contacts by checking if the referred person already exists in your CRM before creating a new record.
Automatically create a deal or opportunity in your CRM pipeline when a referral occurs.
Create a separate Zap that updates CRM records when referrals reach milestones or convert.
Verify your Zap works correctly and set up ongoing monitoring.
// Universal CRM field mapping for GrowSurf referrals
// These mappings work across Pipedrive, Zoho, Close, Copper, etc.
const fieldMapping = {
// Standard CRM fields
"email": "{{email}}",
"first_name": "{{firstName}}",
"last_name": "{{lastName}}",
"phone": "{{phone}}",
// Custom referral fields (name varies by CRM)
"referral_source": "GrowSurf",
"referred_by": "{{referredBy__email}}",
"referral_code": "{{referralCode}}",
"referral_date": "{{zap_meta_human_now}}",
"referral_status": "Referred",
// CRM-specific lead source values:
// Pipedrive: "Lead Source" custom field
// Zoho CRM: "Lead Source" standard field (set to "Referral")
// Close: "Source" field (set to "Referral Program")
// Copper: "Source" dropdown
};
// Zapier Path Configuration for Deduplication:
// Path A: Contact Found
// Condition: [CRM] Find Contact > Id > Exists
// Action: [CRM] Update Contact with referral fields
// Path B: Contact Not Found
// Condition: [CRM] Find Contact > Id > Does Not Exist
// Action: [CRM] Create Contact with all fieldsMost CRMs have a built-in "Lead Source" or "Origin" field. Set this to "Referral" or "Referral Program" so referral leads appear correctly in your CRM's standard source reports without needing custom reporting.
Add a note to the CRM contact record with context about the referral: who referred them, when, and through which campaign. Sales reps find this context invaluable when making their first outreach β they can reference the mutual connection.
If your program generates bursts of referrals, add a short delay (1-2 minutes) to your Zap to prevent API rate limiting on your CRM. This is especially important for CRMs with strict rate limits like Close or Copper.
Any CRM with a Zapier integration works. The most popular choices are Pipedrive, Zoho CRM, Close, Copper, Freshsales, and Insightly. The setup is nearly identical for all of them β the main difference is field naming and where you create custom fields.
Yes. Create a second Zap that triggers on CRM events (e.g., deal closed won) and uses GrowSurf's Zapier actions to update the participant or trigger a conversion. This creates a two-way sync where deal outcomes in your CRM automatically trigger rewards in GrowSurf.
Use the deduplication pattern described in Step 3. Search for the contact by email first. If found, update the existing record with referral data. If not found, create a new record. This enriches existing contacts without creating duplicates.
Trusted by marketing and product teams at fast-growing B2C, fintech, and SaaS companies
