How to Use the If/Else Workflow Action in Sparkforge
The If/Else action in Sparkforge workflows splits contacts down different paths based on conditions. Use static values, dynamic values from earlier steps, or company fields to build branching logic with a fallback None branch.
The If/Else action routes contacts down different paths in a Sparkforge workflow based on conditions. With dynamic values, you can compare against live data from earlier steps or stored fields instead of hard-coding numbers.
What If/Else does
If/Else evaluates contact data and splits the workflow into branches. Each branch is a path a contact follows depending on whether its conditions match. This lets workflows adapt to behavior, attributes, and calculated values rather than running one-size-fits-all.
Why it matters
- Conditional logic — route contacts on real-time data.
- Less duplication — replace parallel workflows with branches.
- Scalable segmentation — handle complex logic in one place.
- Visual clarity — see decision points in the builder.
Add an If/Else action
- Open the workflow.
- Click + to add a new action.
- Select If / Else.
Choose a logic setup method
Build manually with Build My Own, or start from a prebuilt recipe with common conditions.
Configure the first branch
- Pick the field to evaluate.
- Choose an operator.
- Set the comparison value.
- Click Add Segment to add more condition groups.
- Use AND / OR to control how conditions combine.
Add more branches
Click Add Branch to define another condition group. Each branch is a separate workflow path.
The None (Else) branch
The None branch is created automatically. It runs when no other branch's conditions match. It cannot have conditions and cannot be removed, but you can rename it and add fallback actions.
Dynamic values in If/Else
The right-hand side of an If/Else condition can pull a dynamic value — output from an earlier step, a stored field, or a company field — instead of a hard-coded value.
Supported field types for dynamic values
- Numeric — scores, counts, totals.
- Date — appointment dates, renewal dates.
- Select / Dropdown — advanced; requires option IDs, not display names.
- Monetary — invoice totals or amounts.
How to set up a dynamic value
- Add the If/Else action.
- Configure the left-hand field as usual.
- Switch the right-hand input value type to Dynamic Value.
- Pick an earlier workflow step output or a stored field.
- Choose the operator.
- Save and publish.
Company fields
Company fields appear alongside contact fields in the picker. They resolve only when the contact is associated with a company — otherwise the value is blank. Useful for branching on company address, name, or other account-level attributes.
Action details
| Field | Description | Required |
|---|---|---|
| Action Name | Label for the action in the workflow | Yes |
| Condition | Rule evaluated to determine the branch | Yes |
| Branches | Workflow paths created by the action | Yes |
| Segments | Groups of conditions combined with AND/OR | No |
Example: follow-up based on email engagement
- Trigger: promotional email sent.
- If/Else condition: Email Event > Is Opened.
- Yes branch: send a thank-you email with an offer.
- No branch: resend with a different subject line.
Example: branch on proposal value
Capture a proposal amount earlier in the workflow. In an If/Else step, compare that amount dynamically: if it is $25,000 or more, route to a priority path; otherwise, continue with the standard process.
Frequently Asked Questions
How do I control when the If/Else condition is evaluated?
Can I edit a branch after publishing?
Is the None branch required?
Why does my Select/Dropdown dynamic value not match?
What happens to a contact with no associated company when I use a company field?
Was this article helpful?
Thanks for the feedback.