Skip to main content
Question

GHL Custom Fields are not showing up in Zapier to map!

  • November 14, 2025
  • 11 replies
  • 51 views

I’m running into an issue where my GoHighLevel custom fields aren’t showing up inside Zapier. I’ve already created the fields in GHL, but when I go to map them in Zapier, they don’t appear in the dropdown.
So,What can i do to get them in zap?

I already refresh the map data fields but still didn’t get solved the problem.
Here’s what need to do:
When some create project in Basecamp, an corresponding Opportunity should create in GHL. So, for this to happen, Data coming from Basecamp should be mapped in GHL custom fields. But I’m stuck to find any custom fields in Zapier.
 

 

11 replies

AndrewJDavison
Forum|alt.badge.img+11
  • Zapier Solution Partner
  • November 14, 2025

According to this earlier post from ​@SamB custom field support was added 2 years ago.. so they should show.

As suggested, it’s probably best to submit a support ticket to Zapier about it. They can access your zaps and troubleshoot more directly.

 

 


Troy Tessalone
Zapier Orchestrator & Solution Partner
Forum|alt.badge.img+14
  • Zapier Orchestrator & Solution Partner
  • November 14, 2025

Hi ​@Karl Seidel 

The scrollbar in the LeadConnector step appears to indicate there are many fields available.

Try scrolling down.

You can also use the search feature to search for the name of the custom field to narrow down the fields.

 


  • Author
  • Beginner
  • November 14, 2025

Hi ​@Karl Seidel 

The scrollbar in the LeadConnector step appears to indicate there are many fields available.

Try scrolling down.

You can also use the search feature to search for the name of the custom field to narrow down the fields.

Hi ​@Karl Seidel 

The scrollbar in the LeadConnector step appears to indicate there are many fields available.

Try scrolling down.

You can also use the search feature to search for the name of the custom field to narrow down the fields.

 

 

 

Yes i did that as well and even search manually one by one but there’s not any custom fields options.

 


  • Author
  • Beginner
  • November 14, 2025

According to this earlier post from ​@SamB custom field support was added 2 years ago.. so they should show.

As suggested, it’s probably best to submit a support ticket to Zapier about it. They can access your zaps and troubleshoot more directly.

 

 

Thanks Andrew!
But zapier support is not available for free account I  think.


Troy Tessalone
Zapier Orchestrator & Solution Partner
Forum|alt.badge.img+14
  • Zapier Orchestrator & Solution Partner
  • November 14, 2025

@Karl Seidel 

GHL help link for using Custom Fields: https://help.gohighlevel.com/support/solutions/articles/48001161579-how-to-use-custom-fields

There are 2 types of GHL Custom Fields: Contact vs Opportunity

Your LeadConnector Zap step for Opportunity, so make sure you have added GHL Custom Fields for Opportunities.

 

There are only about 17 default GHL Opportunity fields (top ones in the Zap step), so the rest would be custom fields.

 

If you need to hire help, there is a directory of Zapier Partners: https://zapier.com/partnerdirectory


Sparsh from Automation Jinn
Forum|alt.badge.img+6

Hey ​@Karl Seidel,

Please also ensure that you are latest version of the app connection. You can also try deleting the connection and reconnecting it again.

For us to have more context and understand whether it’s a bug or just something in the logic please post screenshots of full configure tab of Add/ Update opportunity action and also the screenshot of custom fields created on the GHL side.

Hope it helps!

PS: If you need more active help, I’m happy to connect through my Zapier Solution Partner page if you’d like to reach out here- https://zapier.com/partnerdirectory/automation-jinn


  • Author
  • Beginner
  • November 14, 2025

@Karl Seidel 

GHL help link for using Custom Fields: https://help.gohighlevel.com/support/solutions/articles/48001161579-how-to-use-custom-fields

There are 2 types of GHL Custom Fields: Contact vs Opportunity

Your LeadConnector Zap step for Opportunity, so make sure you have added GHL Custom Fields for Opportunities.

 

There are only about 17 default GHL Opportunity fields (top ones in the Zap step), so the rest would be custom fields.

 

If you need to hire help, there is a directory of Zapier Partners: https://zapier.com/partnerdirectory

yes yes I know the difference and have added GHL Custom Fields for Opportunities.
and other than default GHL Opportunity fields, remaining are additional info fields but custom fields are not included in this.


  • Author
  • Beginner
  • November 14, 2025

other than default fields, remaining fields are additional info from GHL  but not the custom fields. below are the custom fields i created for this project: 6 in total yet
 

The last one SS is showing the opportunity data coming from zapier although it was dummy. but this not included custom fields only the dummy to do list name passed to the mapped pipeline and stage.


Troy Tessalone
Zapier Orchestrator & Solution Partner
Forum|alt.badge.img+14
  • Zapier Orchestrator & Solution Partner
  • November 14, 2025

@Karl Seidel 

Issue might be related to the custom field itself in GHL, which looks like it has an emoji for the #.

Try testing by adding a new custom field that has a plain text name.

 

Otherwise, the workaround is to use the GHL API.

Resources for using app APIs in Zaps: 

 

 


Sparsh from Automation Jinn
Forum|alt.badge.img+6

Hey ​@Karl Seidel,

If it’s important for you there is workaround through API, try using POST /opportunities/ endpoint for creating opportunities with custom fields. See more about it here-https://marketplace.gohighlevel.com/docs/ghl/opportunities/create-opportunity
 

See more about how to query the API using Webhooks in Zapier here- https://help.zapier.com/hc/en-us/articles/8496326446989-Send-webhooks-in-Zaps. Hope it helps!


SamB
Community Manager
Forum|alt.badge.img+11
  • Community Manager
  • November 19, 2025

Hey ​@Karl Seidel, just checking in! 👋

How are things going on this? Was it the emojis in the field names that were preventing them from appearing? 

Let us know whether you still need any help at all, happy to lend a hand! 🙂