Automated workflows become powerful when they can make decisions. Power Automate’s conditional logic lets you build flows that adapt to different situations and perform different actions based on specific criteria from your Tallyfy processes. You’ll create flexible automations that actually think.
Introduction to conditional logic for Tallyfy integrations
Conditional logic lets your Power Automate flow answer questions about Tallyfy data - then act on the answers. When a condition related to a Tallyfy task or process is true, the flow takes one path. False? It takes another.
Why does this matter? Picture a customer support process in Tallyfy. Your flow checks the “Priority” form field in each task. High priority? The flow escalates it immediately. Low priority? It logs it for routine follow-up. All automatic.
The “Condition” control for Tallyfy data
Adding a condition: In your flow, click + New step and search for Condition. Select it from the Controls category.
Structure: The Condition control gives you an if-this-then-that structure for evaluating Tallyfy data:
IF: Define your condition(s) based on Tallyfy data.
IF YES (THEN): Actions here execute when the Tallyfy-related condition is true.
IF NO (ELSE): Actions here execute when the Tallyfy-related condition is false.
Defining the condition:
Value 1: Select dynamic content from Tallyfy (e.g., output of a Tallyfy connector action like “Get task details”) or enter a static value.
Operator: Select a comparison operator from the dropdown menu. Common operators include:
is equal to / is not equal to
contains / does not contain (for text)
is greater than / is less than (for numbers or dates)
starts with / ends with (for text)
is empty / is not empty (to check if a field has a value)
Value 2: Click in the second box (“Choose a value”). This can be dynamic content or a static value that Value 1 gets compared against.
Building a flow with simple conditional logic for Tallyfy
Here’s a real scenario: When someone completes a Tallyfy task, you want to check the “Approval Outcome” form field and send different email notifications based on what it says.
Select the Tallyfy trigger When a task is completed.
Configure it to monitor a specific Tallyfy procedure template (Blueprint ID).
Action: Tallyfy - “Get task details”.
Add this action to grab all the form field data.
Task ID: Use the Task ID dynamic content from the trigger.
Control: “Condition”.
Add a Condition control.
Value 1: From dynamic content, select the output from “Get task details” for your “Approval Outcome” form field (e.g., outputs('Get_task_details')?['body/forms/ApprovalOutcome/value']).
Operator: Select is equal to.
Value 2: Type Approved.
IF YES branch actions:
When the “Approval Outcome” equals “Approved”:
Add action: Send an email (V2).
To: Relevant stakeholder.
Subject:Tallyfy Task '[Task Name from Get task details]' was Approved.
Body: Include details and link to the Tallyfy task.
IF NO branch actions:
When the “Approval Outcome” isn’t “Approved”:
Add action: Send an email (V2).
To: Tallyfy task assignee (Assigned To Email from “Get task details”).
Subject:Action Required: Tallyfy Task '[Task Name]' outcome was '[Approval Outcome]'.
AND logic: Default for multiple rows - all conditions must be true.
OR logic: Change the operator at the top of the conditions group to OR - any single condition being true is enough.
Tallyfy Example (AND): IF Tallyfy task Priority (form field) is “High” AND its Due Date (from Tallyfy) is in the past, THEN send an escalation alert.
Nested conditions for complex Tallyfy logic
Want more complex decision trees? Place a Condition control inside another Condition’s branch.
Example: First, check if the Tallyfy process type is “Sales Order.” If yes, add a nested condition to check whether the order value (a Tallyfy form field) exceeds $10,000.
Introduction to Switch control (for multiple distinct options from Tallyfy)
The Switch control beats multiple nested conditions when you’re checking one Tallyfy value against many options. We cover this in detail in our advanced conditions and expressions article.
Structure: Pick a value to switch ON (like dynamic content from a Tallyfy form field). Create multiple CASE branches - one for each possible Tallyfy value. The DEFAULT branch catches everything else.
Tallyfy Example: A Tallyfy task has a form field “Support Ticket Category” with values like “Billing Issue,” “Technical Problem.”
SWITCH ON Tallyfy “Support Ticket Category”:
CASE “Billing Issue”: Action - Notify finance.
CASE “Technical Problem”: Action - Create urgent task in a Tallyfy “Tech Support” process.
DEFAULT: Action - Notify general support.
Tips for using conditions with Tallyfy data
Data types: Make sure data types match. Use expressions (like int()) to convert Tallyfy text field values when comparing to numbers.
Case sensitivity: For case-insensitive text comparisons of Tallyfy data, use expressions like toLower().
Leverage Tallyfy outputs: Data from Tallyfy connector triggers and actions should drive your conditional logic.
Test all paths: Test every single branch with different Tallyfy data inputs. Really.
Power Automate’s advanced conditional techniques including expressions grouped logic and Switch controls enable sophisticated decision-making in Tallyfy workflows by handling complex data scenarios multiple conditions and edge cases that basic if-then logic cannot accommodate.
Tallyfy’s automation logic uses simple IF-THEN rules that watch user inputs and automatically adjust workflows based on conditions like form selections task approvals or specific requirements while combining multiple conditions with AND/OR logic to create intelligent processes that adapt to different business scenarios.
Tallyfy automations use conditional logic to automatically handle tasks and decisions by checking step statuses or form field content with various operators like “contains” “is completed” or “is approved” to trigger specific actions without manual intervention.
Conditional logic in Tallyfy enables automated decision-making within processes through simple IF-THEN rules that respond to form answers step completions user roles time triggers and other conditions to create adaptive workflows while reducing manual work and ensuring consistency.
