Opportunity custom fields available to update via zapier | Voters

Opportunity custom fields available to update via zapier

Aaron Boone

Need custom feilds for opportunities to be able to be updated via zapier

September 13, 2023

Free Grafton

Agreed! Please expose the opportunity.custom fields from GHL to Zapier so those could be pulled in.

We've found a frustrating issue because only contact.custom fields are exposed when someone fills out a GHL form and uses the same email address again, it remembers ALL previous data filled in from the last form and sends that to Zapier! That's because they have Form questions mapped to contact data. So, once it's set it remembers it for every future form response from the same people. We got excited when we found an Opportunity custom field because those aren't tied to a contact record, so can be independent. However, we then found the opportunity custom fields weren't being passed over to Zapier.

Asif Khan

Alternative solution with Zapier:

Add Automations in GHL with trigger "Inbound Webhook", use zapier webhook to send the opportunity custom fields detail to the GHL inbound url, and we can update the opportunity custom fields in GHL automations.

Duane Zingale

With custom opportunity fields, one would think they can leverage those fields in add/ update opportunity in Zapier.
Hope this comes Soon!
Could use this in multiple instances.

Sam Whitehead

Is there any update on this?

Josh Jones

Can we add Make.com to this request

Noah Nagel

Hey folks, after a lot of frustration I have a couple of workarounds that may help depending on your use case. These will work if you're needing to update some custom fields in an Opportunity based on the result of some third party automation, like shortening a link.
I am assuming that many will be coming here because Zapier is the first line of defense when you need the Opportunity to interact with third parties. Despite these workarounds, updating custom fields via Zapier should be a top priority for GHL.
Both of these solutions don't involve interfacing with the HighLevel API directly, and you don't need to know how to code.
Option 1: Daisy chained inbound and outbound webhooks.
You can basically use any feature you'd like in Zapier from HighLevel if you send a webhook to Zapier, capture the hook with a Zap webhook trigger, run whatever workflow you want, and the final step in Zapier can be another webhook posted back to a HighLevel workflow that triggers on inbound webhook, after which you actually update those pesky custom fields in the opportunity.
So your workflow would look like this:
[GHL workflow (part 1)]
Whatever Opportunity trigger
Do what you can from GHL
Once you need Zapier to to do something, end the workflow with a final "Webhook" action step. Make sure to pass the contact id (it may come by default) and any custom fields you care about.
[Zapier]
Trigger the zap based on an inbound webhook. Take the URL from Zapier and load it into the webhook in step 3.
Do what you need to with third parties or whatever
End your Zapier workflow with another webhook action, get the url from the trigger in step 7. Make sure to pass the Opportunity name & contact id in the data section.
[GHL Workflow (part 2)]
Create a new workflow with an "inbound webhook" trigger. Connect it to Zapier's URL in step 6.
Run the "Find Contact" action, GHL needs it for identifying the opportunity for some reason. Match the contact id in the fields with the id from the inbound webhook.
Finally we can update the Opportunity's custom fields, create a "Create Or Update Opportunity" action, use the opportunity name from the inbound webhook. The opportunity name seems to be sufficient for matching the Opportunity back up to itself.
Option 2: Better for one-off third party requests
This is only better if you want to avoid having two workflows. Option 1 is likely better for most people and doesn't require you to read API docs.
If you just need to do something transactional with another service, you can create a custom webhook based on the third party's API. Look up API documentation, and if they're using a REST API (Most do), send a custom webhook to that service directly. Be mindful of headers, the authorization type, and the necessary body. Make sure 'Save the response from this webhook' at the bottom is checked. This will make the webhook WAIT until a response is received, and you can dig into that response to update your Opportunity's custom fields from the workflow.
Edit from a few weeks later: There's another, much simpler way to do this via custom webhooks. Set up your custom webhook, make sure "save response" is on, then send the request to Make/Integromat specifically using a webhook trigger. Do what you need with the workflow in Make, and use "Webhook response" as the final step. This will cause GHL to send the webhook and wait for the data coming back from Make before continuing the workflow. This is a much more straightforward way that doesn't require convoluted daisy chaining and the workflow can remain in GHL for the most part.

Noah Nagel

I'm dealing with this now as well. I'll try to figure it out with the API but very surprised with how limited opportunities are compared to contacts.

Tyler Peck

Is this really not possible? Checking our setup it seems not. We have multiple opportunities per contact and need each one to have some unique fields which are updated via API.

Shawn Moser

Hopefully this is next step after adding custom fields in opportunity. Fields are super useful if they can only be updated manually.

Amanda Nichols

Yes! Not just the custom fields in the contact

→