Set temporary variable in workflow
under review
C
Clifford Paulick
I want to set a variable like this:
- if has tag "X", set var1 to "Xavier"
- if has tag "Y", set var1 to "Yancy"
Then both GoTo a step that creates/updates an Opportunity and the opportunity source = var1
Log In
S
Sales & Marketing
Merged in a post:
Set Fields Action
D
Daniel Marr
The ‘Set Fields’ action allows users to define and update specific variables that can be used throughout a workflow. This feature is designed to make it easier for non-technical users and clients to manage key workflow details without having to modify complex prompts or workflow logic directly.
Why We Need This:
We are incorporating more personalized AI-generated emails, but clients often struggle with understanding and managing variables. We also want to prevent them from accidentally altering prompts and breaking workflows.
Current Challenges with Existing Methods:
Using contact fields or custom values requires pre-defining variables, which can become confusing and difficult to manage.
Making adjustments requires navigating deep into workflows, which can be overwhelming for non-technical users.
Clients may unintentionally break prompts or misconfigure variables, leading to errors in automation.
How ‘Set Fields’ Simplifies This:
Provides a simple interface where users can define key details (e.g., offer details, pricing, landing page links) without touching the workflow itself.
Allows easy duplication of workflows—just update the fields, and everything updates automatically.
Eliminates the need for clients to understand variables—just fill in the predefined fields, and the system handles the rest.
Example Use Case:
An example of this would be for creating workflows for specific offers that create a personalised email follow up. The client can set the fields for the offer and the meta prompt uses that info to create a personalised email for that offer.
Instead of manually adjusting variables in larger prompts, users can simply set these fields in the workflow:
{{set_fields.2.field1.result}} – Company Details
{{set_fields.2.field2.result}} – Promotion/Offer
{{set_fields.2.field3.result}} – Offer Price
{{set_fields.2.field4.result}} – Offer Landing Page
Once these are set, the AI-generated emails will automatically use these values, ensuring consistency and making workflow updates quick and hassle-free.
This approach keeps things structured, user-friendly, and scalable while reducing the chances of errors.
Photo Viewer
View photos in a modal
A
Ashwin Raghunandan
Merged in a post:
"Set Variable" Action in Workflows
M
Modern Musician
It would be really helpful if we could "set a variable" in a workflow that we could reuse throughout the workflow.
That way we wouldn't have to maintain 5 different branches the entire time, but we could set a variable and use 1 branch with the dynamic variable.
Eg. We have 5 different variations of a subscription product, and I'd like to set those as a variable and keep everything else the same.
Currently, we need to create 5 different branches to do the exact same thing.
C
Charles Gucker
In workflow automations, I set custom variables within automations to set custom values that I then use in messaging. In isolation, this works well, but when multiple triggers are running at the same time, these custom values can cause data collisions because workflow trigger one runs, updates value, continues through the workflow. Workflow trigger two runs, updates value before workflow trigger one completes, tigger one then uses the value from tigger two and not one as intended in SMS message.
I believe this could be accomplished by adding a check box in the workflow automation for the Update Custom Value as temporary and keep the value in memory for the workflow operation and then discard it without saving it.
M
Modus Anomali
yes !!!
Core Platform
marked this post as
under review