Automations

Allow Math Operations on Global Custom Values in Contactless Scheduler Workflows
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.
0
·
Enhancement
Incoming webhook: Assignment reference shows no test requests even though the webhook receives requests and confirms them with 200
Hi everyone, I'm currently building a workflow with an incoming webhook trigger and I'm facing a problem that I'm stuck with, maybe someone of you has already had that. The trigger itself works flawlessly: Requests arrive, the webhook responds with HTTP 200, I've tested this several times directly via the browser (both with content type text/plain and application/json, both without difference). The problem is the assignment reference (i.e. the field mapping for the trigger): There, despite multiple incoming test requests, simply no sample data set is displayed. Even the “Check if there are new requests” button does not make any changes, no matter how often I click on it. Without this assignment reference, however, the trigger cannot be saved at all; GHL shows the message “An assignment reference is required for an incoming webhook trigger.” What I've ruled out so far: The webhook URL is correctly stored and accessible. The content type of the request makes no difference. The problem occurs regardless of which source the test request comes from. My guess is that the assignment reference only accepts an example request if the trigger step in the workflow editor is active in the “Waiting for test data” state at the exact moment when the request arrives, and each request before or after that is acknowledged with 200 but is not adopted as an example. Can anyone confirm this or does another approach to reliably get the assignment reference filled? Thank you guys in advance!
2
Load More