Currently, workflows triggered by the Scheduler run without a Contact context. Because the Math Operation action requires a Contact, it gets skipped even when the calculation only involves global Custom Values.

This creates an unnecessary limitation for scheduled automations that do not need any Contact data.

Use Case:

For example, we have a global Custom Value that stores the current date of a recurring onboarding event.

A Scheduler workflow runs daily and checks whether the current date matches the onboarding date. Once the date is reached, the workflow should automatically calculate the next onboarding date by adding a certain number of days and update the global Custom Value.

The logic would be:

Scheduler

→ Check current date

→ Compare with global Custom Value

→ Math Operation: Add X days to the date

→ Update global Custom Value

Currently, the Math Operation is skipped with:

“This action requires a Contact and none has been provided.”

Even though no Contact data is involved in the calculation.

Requested Improvement:

Please allow Math Operations to run without a Contact context when the inputs and outputs are global Custom Values.

This would make Scheduler workflows much more flexible and would avoid having to create artificial Contacts or external workarounds just to perform simple calculations.

Expected Behavior:

If a Math Operation only references global Custom Values, it should be executable inside a contactless workflow.

This could also potentially apply to other workflow actions that technically do not require Contact-specific data but currently still depend on a Contact context.