Math Operations and Calculations on Custom Object Fields
A
Alexis C
Workflows cannot perform mathematical operations (add, subtract, multiply, divide) on custom object fields. This prevents automatic calculations like capacity management, inventory tracking, or score aggregation.
USE CASE:
We have an Event custom object with fields:
- Capacity (total spots available)
- Registered_Count(current registrations)
- Available_Spots (calculated: Capacity - Registered_Count)
When an Attendee/Ticket object is created, we need to:
- Find the related Event object
- Increment Registered_Count by 1
- Calculate Available_Spots = Capacity - Registered_Count
- If Available_Spots = 0, mark event as full
Current Limitation:
Math operations only work on Contact/Opportunity fields.
Requested Feature:
Please add workflow Math Operation and Array actions for custom objects:
- Increment Field (add value to numeric field)
- Decrement Field (subtract value from numeric field)
- Calculate Field (perform formula: Field_A operator Field_B)
- Set Field Value (based on calculations from other fields)
Photo Viewer
View photos in a modal
Log In
A
Ahmed Walid
Right now, object-based workflows cannot perform any math operations (+ / − / * / ÷) directly on Custom Object number fields, which makes it impossible to:
Increment/decrement counters on the object itself (e.g. usage count, seats used, remaining capacity).
Calculate values between fields in the same Custom Object (Field A ± Field B, averages, percentages, etc.).
Keep “summary” or “capacity” fields in sync without sending data out to Google Sheets or external tools just to do simple arithmetic.
Requested enhancement (minimum viable version):
Allow Math Operation in object-based workflows to target Custom Object number fields (not only Contacts/Opportunities).
Support: Increase by X, Decrease by X, and “Set value = simple expression of other fields on the same object”.
Scope can be limited to number fields on the same Custom Object record (and later associated records).
This would unlock a lot of real-world use cases (capacity management, usage tracking, billing counters, progress tracking, pipeline metrics per account, etc.) without any external workarounds.
As agencies building production systems on HighLevel, this is becoming a core requirement, not just a “nice to have”.
S
Sales & Marketing
Merged in a post:
Custom object for math calculations.
U
Umer Ashraf
One can calculate commissions, etc, If the custom object has a math calculation feature
S
Sales & Marketing
Merged in a post:
Math operation in custom object actions
E
Eyas Bondouq
D
Daniel Marr
This is a huge barrier and just wasted a lot of time moving fields over to the company object then found out I cant do this :(
D
Daniel Marr
Just found out we can't use number variables either or any number field filters in if/else actions or update object actions at the moment as well.
J
Jarryd Pearce
I am trying to build the exact same workflow. Allowing math operations on custom objects (company) fields would allow this to be possible.
J
Jason Roper
This would be great for property developers where clients want add-ons to their property like air-conditioning, integrated appliances, discounts, etc
C
Cooper Wilburn
Would love this to help track vaccine expiration dates.
A
Alexis C
Current workaround: Send data to GPT(risk errors) or Zapier for functions (complex implementation)
D
Daniel Marr
Alexis C a better, cheaper and more reliable way for now is to use custom code something like this which takes the key value and adds 1:
const sum = inputData.key_name + 1
output = { result: sum }