Module 1: Convertri to GHL

Submit a test lead

Regardless of the platform or mechanism you're using, always submit a test lead first.

Watch this loom video first

Below is your fully structured SOP — a simple checklist first, then the full detailed steps.

Quick summary of the steps

• Submit a test lead in Convertri
• Open Zapier and capture the test data
• Go to GoHighLevel automations
• Create a new workflow with an "Inbound Webhook" trigger
• Copy the webhook URL into the Zapier POST step
• Map Convertri fields to the webhook fields
• Add UTM fields to the POST payload
• Test the webhook to pull sample data
• Clean placeholder UTM values
• Create the contact in GHL and map all fields
• Assign the contact to the correct user
• Add an internal note with the full field mapping
• Add the tag "Convertri – Demand Gen"
• Create an opportunity in the correct pipeline
• Duplicate any SMS/email automation steps needed
• Publish the workflow
• Submit a test lead to confirm the contact + opportunity are created

Set up the Zapier capture step

1. Open Zapier.
2. Use the Convertri test lead to populate Zapier's data preview.
3. Add a new step in Zapier: Action: Webhooks by Zapier · Event: POST
4. Leave this for now — you'll return to map data after generating the GHL URL.

Create a new workflow in GoHighLevel

1. In GHL, go to Automations.
2. Click Create Workflow → Start from Scratch.
3. Name it: FlipAnywhere – Convertri Webhook Intake
4. Choose trigger: Inbound Webhook

Generate the webhook URL

1. Once you select Inbound Webhook, GHL generates a webhook URL.
2. Copy this URL.
3. Go back to Zapier → paste this URL into the POST URL field.

Map Zapier POST data fields

In the Zap step:

1. Set Body Type: Form
2. Add the following fields: name, email, phone, address, motivation, price, utm_campaign, utm_source, utm_medium, utm_content, utm_term
3. Map each field to the matching Convertri fields from your test lead.
4. If Zapier shows blank UTM values (common during testing), temporarily type placeholders (e.g. "campaign") so GHL can ingest the test payload — you will delete these later.
5. Test the Zap step to send sample data to GHL.

Verify the webhook data in GHL

1. In the GHL workflow, click Fetch Sample.
2. Confirm the webhook pulled in: Name, Email, Phone, Address, Motivation, Price, and all UTM fields.
3. Remove any temporary placeholder UTM values.
4. Save the trigger.

Create the GHL contact

1. Add a new action: Create/Update Contact.
2. Map fields: Contact Name → name; Phone → phone; Email → email; Property Address → address; Custom Field: Motivation → motivation; Custom Field: Price → price.
3. Leave UTM fields unmapped if not needed, or map them if custom fields already exist.

Assign the contact to a user

1. Add action: Assign to User.
2. Select the correct user (Acquisitions Manager or client's rep).

Add a note with full lead details

Add action: Add Note, then use this template and replace each placeholder with the correct inbound webhook field:

Name: {{name}}
Phone: {{phone}}
Email: {{email}}
Address: {{address}}
Motivation: {{motivation}}
Price: {{price}}
UTM Campaign: {{utm_campaign}}
UTM Source: {{utm_source}}
UTM Medium: {{utm_medium}}
UTM Content: {{utm_content}}
UTM Term: {{utm_term}}

Add a Convertri-specific tag

1. Add action: Add Tag.
2. Create/select tag: Convertri

Create an opportunity in the correct pipeline

1. Add action: Create Opportunity.
2. Select: Pipeline (e.g. Max Value Home Buyers) · Stage (usually "New Lead")
3. Opportunity name format: {{name}} – {{address}}
4. Status: Open

Duplicate any additional workflow actions

If the client already has an established Facebook workflow:

• Review their existing workflow
• Copy over SMS steps, internal notifications, or opportunity updates as needed
• Only include steps the client explicitly requests

Publish the workflow

1. Click Publish.
2. Confirm status is Active.

Run a full end-to-end test

1. Go to the Convertri page → submit a new test lead.
2. Check GHL: Contact created? Assigned properly? Note populated? Tag applied? Opportunity created in the right pipeline & stage?
3. If you don't see the lead: check GHL permissions (you may not have full visibility), review the workflow Execution Logs, and confirm the Zapier POST ran successfully.

Review / quality control

For every new client setup:

• Confirm they have all required custom fields
• Confirm correct pipeline & stage
• Confirm correct user assignment
• Confirm the webhook URL is unique to their workflow
• Use real test leads (not just samples) to validate the flow
• Double-check note formatting & mappings for accuracy

Troubleshooting & common issues