Wmorkan
Member
- Your Workflow URL
- https://connect.pabbly.com/workflow/mapping/IjU3NjYwNTZmMDYzMTA0M2Q1MjZmNTUzMjUxMzMi_pc
- Consent to Access & Modify
- I authorize Pabbly Support to log in to my account and make changes to the specified workflow for troubleshooting.
Hi Pabbly Team,
We’re seeing a regression in one of our production workflows. The flow was working fine, but today it started sending incomplete data to our CRM (Go High Level).
Workflow: “TAF – DriveTime Motors Integration”
Trigger: Email Parser (New Email Received)
Step 2: Router (Conditionally Run) → Route: “Subject: Lead: Request for financing (Multistep)”
Destination app: Go High Level (Create/Update Contact + custom fields)
What should happen (expected):
When a lead submits our website’s multistep finance form, the parser extracts all fields. The Router selects the “Subject: Lead: Request for financing (Multistep)” route and sends the mapped values to Go High Level so the contact is created with custom fields populated (e.g., Type Of Vehicle Looking For, Estimated Credit Rating, Date of Birth, etc.).
What happens now (actual):
Core fields (First Name, Last Name, Email, Phone) arrive in GHL, but several custom fields arrive blank even though the parser clearly captured the values and the Router route shows them mapped (see screenshots). Examples that arrive empty in GHL:
We’re seeing a regression in one of our production workflows. The flow was working fine, but today it started sending incomplete data to our CRM (Go High Level).
Workflow: “TAF – DriveTime Motors Integration”
Trigger: Email Parser (New Email Received)
Step 2: Router (Conditionally Run) → Route: “Subject: Lead: Request for financing (Multistep)”
Destination app: Go High Level (Create/Update Contact + custom fields)
What should happen (expected):
When a lead submits our website’s multistep finance form, the parser extracts all fields. The Router selects the “Subject: Lead: Request for financing (Multistep)” route and sends the mapped values to Go High Level so the contact is created with custom fields populated (e.g., Type Of Vehicle Looking For, Estimated Credit Rating, Date of Birth, etc.).
What happens now (actual):
Core fields (First Name, Last Name, Email, Phone) arrive in GHL, but several custom fields arrive blank even though the parser clearly captured the values and the Router route shows them mapped (see screenshots). Examples that arrive empty in GHL:
- Type Of Vehicle Looking For (e.g., “Car”)
- Estimated Credit Rating (e.g., “Good (650+)”)
- Date of Birth (e.g., “1985-10-19”)