Skip to main content

Hi GHL Team,

I’m facing an issue while connecting Gravity Forms (via Zapier) to GoHighLevel using LeadConnector’s “Add/Update Contact” action.

Here’s what I’ve tried:

  • Gravity Form is sending data correctly (First Name, Last Name, Email, Phone)

  • LeadConnector app is authenticated in Zapier

  • Sub-account (Location) used is xxxx, with Location ID:xxxxxx

  • The LeadConnector account name in Zapier shows as xxxxx

  • Even after reconnecting the account and ensuring proper Location selection, I get this error:

 

pgsql

CopyEdit

Failed to create a contact in LeadConnector The app returned "Invalid URL".

I’m not using the full location URL, only the Location ID when manually trying to test.
I’ve already reconnected the app, re-created the Zap, and ensured all required fields (Name + Email) are present.

Can someone from the team confirm:

  • Is this a known issue with Location-based routing in LeadConnector via Zapier?

  • Is there any workaround or manual fix?

  • Do we need to configure anything differently in the sub-account API settings?

Any help would be appreciated.

Thanks!

Hi ​@Alamgeer 

Help links for using LeadConnector in Zaps: https://zapier.com/apps/leadconnector/integrations#help

 

For us to have more info, post screenshots showing how your Zap step is configured along with the encountered error.

Make sure you are using the current version of the LeadConnector Zap app integration: https://zapier.com/app/connections

 

Workaround involve using the GHL API: https://help.gohighlevel.com/support/solutions/articles/48001060529-highlevel-api

Resources for using app APIs in Zaps: 

 


Hey ​@Alamgeer, welcome to the Community! 🎉

Is this a known issue with Location-based routing in LeadConnector via Zapier?

I had a look but couldn’t find any bug reports that mention that error, so it doesn’t appear to be.

Is there any workaround or manual fix?

It seems to be an issue with one of the values that’s been entered. If you have a custom Location URL field which is expecting a URL but it’s only getting the location ID then that’s likely what’s causing the error.

If you enter the full URL for that location does the contact get created/updated successfully?
 

Do we need to configure anything differently in the sub-account API settings?

I wouldn’t have thought so as it seems to be more of a field validation issue, than an issue with the setup of the sub-account.
 

That said, can you share some screenshots of the current setup of that Add/Update Contact action, as Troy mentioned? That’ll help us to get a bit more context on the setup so we can better advise you here. Make sure to blur/remove any personal info (names, emails etc.) before sharing using a tool like Zappy.

Looking forward to hearing from you!