Make "Opportunity" Custom Fields available in Workflow Actions
complete
P
Patrick Zerarka
Currently we can create new custom fields in the "opportunity object " vs just standard fields (contact object). However, when creating a new custom fields in opportunity object they are not showing in WF/Actions The idea is to make them as available for automation [Triggers and/or Actions] similar to the standard fields so we're able to build WF around - Example: Opportunity Custom Field = "DATE PICKER"= Build WF for upcoming reminder just like we would have done it un Standard Fields. I know the same can be done in "Contact/Standard" but the functionality of it is more powerful when used in the Opportunity Window (object) especial when tracking "Future Closing/Sale Date" for that particular "opportunity"
Photo Viewer
View photos in a modal
Log In
P
Pallavi Kothari
Hi everyone, this is already available. Opportunity custom fields can be used in workflows today:
- Custom Date Reminder trigger: pick a supported opportunity date field (for example a Closing Date custom field) and set reminders before or after it. https://help.gohighlevel.com/support/solutions/articles/155000002674-workflow-trigger-custom-date-remimder
- Opportunity triggers (Opportunity Created, Opportunity Status Changed, Pipeline Stage Changed, Stale Opportunities) can be filtered on any standard or custom opportunity field.
- If/Else branches can use opportunity custom fields when the workflow starts from an opportunity trigger. https://help.gohighlevel.com/support/solutions/articles/155000002048-automating-opportunities
If something you need still isn't covered, reply here with the use case and we'll take a look.
Pallavi
C
Christopher Harris
Pallavi Kothari Hi Pallavi,
Thanks for the update. Those options all work when the workflow starts from an opportunity trigger. Our use case doesn't.
We sync quotes from an ERP into HighLevel. Each quote enters through an Inbound Webhook, one run per quote, and the only thing we have is the quote number, which lives in an opportunity custom field. What we need:
- Find Opportunity by a custom field value across the whole location. Today Find Opportunity only searches the enrolled contact's opportunities, so when the rep on a quote changes, it returns Not Found and we end up creating a duplicate.
- Use that found opportunity's custom field values in If/Else and other actions, even though the workflow didn't start from an opportunity trigger.
Right now we do both with a Custom Webhook search, Custom Code to read the result, and another Custom Webhook to update it. It works, but it's code doing what a native Find should do.
Same gap for custom objects: there's no native way to find or update a record by its unique field from a workflow.
P
Pallavi Kothari
Christopher Harris
Thanks for laying this out so clearly, it helps a lot.
Good news: this is covered in the new Opportunities private beta. In beta sub-accounts, Find opportunity can look up an opportunity across the whole location by a custom field value, like your quote number, so it no longer depends on the enrolled contact. Update opportunity then acts on the opportunity that Find returned, and its custom field values are available in If/Else and the steps after it. If a run has no contact, as with your Inbound Webhook, Create opportunity creates the opportunity without one instead of failing.
That should let you swap the Custom Webhook and Custom Code steps for native actions.
If you’d like to try it, fill in this short form with the sub-account you want it on and we’ll switch it on for you: https://api.leadconnectorhq.com/widget/form/SKdrNsiMIr9gIVrRYjh3
It’s a private beta, so some things may change before full release, and your feedback will shape what ships.
Pallavi
T
Ty Averett
Pallavi Kothari Thank you so much for you and your team's hard work!
What we're running into is that we want to use the find opportunity workflow action to find an opportunity that was created, for example, within the last 30 days. But when we go to put that in, the only option is a range of set dates. This is the case for both date custom fields and standard fields (such as date created)
This is weird to me because it limits this action to a very small range of use cases. And in most other workflow actions, when you're working with a date, it gives you a list of options. For example, in if/else actions, you can choose from a wide list of operators such as before, after, before date, after date, in the last, in the next, etc.
Workarounds are also limited by the fact that opportunity custom fields are still not listed in text formatter actions, math actions, and similar actions.
Photo Viewer
View photos in a modal
P
Pallavi Kothari
updated the status to
complete
R
Robert Robbins
This is important for service businesses that use opportunities as actual jobs/projects.
We need opportunity custom fields to be available in workflow triggers, conditions, messages, notifications, and update actions the same way contact fields are. Many details belong to the opportunity/job, not the contact, such as project address, gate/access instructions, products ordered, job type, install notes, and production details.
Without better opportunity field access, we have to copy information back and forth between contact fields and opportunity fields, which adds complexity and increases the chance of updating the wrong record.
Ideal solution:
* Opportunity custom fields available in workflow conditions
* Opportunity custom fields available in workflow messages/notifications
* Opportunity custom fields available in appointment-triggered workflows
* Ability to update opportunity fields from appointment/form submissions
* Ability to use opportunity custom fields in Teams/internal notifications
M
Mike Biagio
If I want to send a set number of automated reminder emails to a client to pay a quote for a certain matter, I need to use a counter with a math operation in the workflow - but I can't because this would be in the opportunity level as the same client may have a few different matters happening at the same time. Given that people have been clamouring for this for years and has huge support and it still hasn't been added, can we really expect GHL to get off their asses and make non-amateur hour software? This software is so limiting its almost like it started off being used for something completely different to actual sales and was adapted for sales after the fact. This is BASIC level stuff man! right now I am soooo frustrated at the time I have wasted on trying to set up this system only to be smashed with arbitrary roadblock after roadblock. WHY ON EARTH WOULD YOU LIMIT MATH OPERATIONS TO ONLY CONTACT LEVEL!!!! Which corporate schmuck decided this was a good idea?
I
Irvin Dominguez
Needed!
S
Sales & Marketing
Merged in a post:
Add Opportunity Custom Fields in MATH Operations
S
Sertan Djelal
There have been a few updates on math operations within workflows but we still can't select or use opportunity custom fields within Math Operations. We have several use cases where it needs to be done within an opportunity and not at contact level. E.g. calculating commission figures (10% of opp value for instance or based on another custom numerical or monetary field), dates (x-days before/after) etc. As these are unique to the opportunity and there could be multiple opportunities at any given time per contact, having it just at contact level isn't sufficient. 🙏
S
Sales & Marketing
Merged in a post:
Update Opportunity Custom Field Action
E
Edmund Lu
Currently when a form is submitted, it can only record data to Contact fields. It would be great if we could have an automation action which allows you to update Opportunity Custom Fields as we sometimes have leads that submit more than one form (and each opportunity is for a different service/enquiry type)
K
Keith Zellers
Really make all Custom Fields available in math operations. Custom Values are also useful. Example - Certain types of loans require 30% downpayment. Two years ago it was 25%. It would be nice to use a Custom Field from a LOAN Object "Purchase Price" and multiply it by Custom Value "Minimum Down Payment Percentage" to give a default Downpayment. If you can add range limits and make that minimum, for the answer that would be even better!!
D
Divyam Bhadoria
Merged in a post:
Opportunity Details
H
Hariata Ngoran
I think it will be great if users can have the opportunity to use custom fields in the opportunity object whether or not the trigger is related to opportunities
D
Divyam Bhadoria
Merged in a post:
opportunity.custom_field Math Operations
T
Trevor Shanahan
Math Operations should be able to utilize opportunity.custom_fields. Limiting math operations to only contact.custom_fields is extremely limiting. I can have 1 contact associated with multipe opportunities. With the current limitation I would need to create multiple contacts. This makes zero sense. If I see Contact A, three different products or services that is three different opportunities and shouldn't require 3 duplicate contacts. Especially when we are trying to calculate Monthly Recurring Charge (MRC) multipled by Term Agreement (12, 24, 36, 48, 60 months), and then calculate commissions MRC x Commission % = Monthly Recurring Commissions x Term Agreement and even Sub-Agent Commissions: Monthly Recurring Commissions x Sub Agent Commission % = Sub Agent Monthly Commission. All of this is specific to an Opportunity, NOT a contact.
Load More
→