Skip to content
Tallyfy

Using conditional logic in Power Automate

Conditional logic makes your Power Automate flows smart. Instead of running the same actions every time, your flow checks Tallyfy data and picks a different path based on what it finds — sending escalation emails for high-priority tasks, routing approvals to different teams, or skipping steps entirely when they don’t apply.

How conditional logic works with Tallyfy

Your flow asks a yes-or-no question about Tallyfy data, then takes one path if true, another if false. A customer support process is a good example — the flow checks a “Priority” form field on each task. High priority gets escalated immediately. Low priority gets logged for routine follow-up.

The Condition control

  1. Add a condition — click + New step, search for Condition, and select it from Controls.

  2. Structure — the Condition control gives you three sections:

    • IF: Your condition based on Tallyfy data.
    • IF YES (THEN): Actions that run when the condition is true.
    • IF NO (ELSE): Actions that run when it’s false.

  3. Define the condition:

    • Value 1: Pick dynamic content from a Tallyfy connector action (like the output of Get User Tasks) or type a static value.
    • Operator: Choose a comparison — is equal to, contains, is greater than, starts with, is empty, and their opposites.
    • Value 2: The value you’re comparing against (dynamic content or static).

Building a conditional flow with Tallyfy

Here’s a practical scenario: you’ve set up a Tallyfy webhook1 that fires when someone completes a task. Your Power Automate flow receives that webhook data, then sends different email notifications based on the task’s priority level.

  1. Trigger: “When an HTTP request is received.”

    • Start a new automated cloud flow.
    • Use the When an HTTP request is received trigger, then paste the generated URL into your Tallyfy webhook configuration.
    • The webhook payload from Tallyfy includes task details and form field values.

  2. Action: Tallyfy - “Get User Tasks” (optional). If you need additional form field data beyond what the webhook provides, add the Tallyfy connector’s Get User Tasks action to pull more details.

  3. Control: “Condition”. Add a Condition control.

    • Value 1: Select the priority field from the webhook body or Tallyfy action output.
    • Operator: Select is equal to.
    • Value 2: Type High.

  4. IF YES branch: When priority equals “High”:

    • Add action: Send an email (V2).
    • To: Manager or escalation contact.
    • Subject: Urgent: Tallyfy task '[Task Name]' needs attention.
    • Body: Include the task details and a link to the Tallyfy task.

  5. IF NO branch: When priority isn’t “High”:

    • Add action: Send an email (V2).
    • To: The assigned team member.
    • Subject: Tallyfy task '[Task Name]' completed - routine follow-up.
    • Body: Summary of the task and next steps.

  6. Save and test your flow. (See managing and monitoring flows for testing tips.)

Visualizing the conditional flow

Diagram

The diamond is the decision point. Two paths branch from it — each leading to a different email action based on the form field value.

Multiple conditions with AND/OR

You’ll often need to check more than one piece of Tallyfy data at once.

  • Adding rows: Inside a Condition, click + Add > Add row.
  • AND logic: The default — all conditions must be true.
  • OR logic: Switch the operator at the top to OR — any single true condition is enough.

Example (AND): IF a Tallyfy task’s Priority form field is “High” AND its deadline has passed, THEN send an escalation alert.

Nested conditions

Need 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, nest another condition to check whether the order value (form field) exceeds $10,000.

When nesting gets messy, switch to a Switch control instead (see advanced conditions and expressions).

Switch control for multiple options

The Switch control works better than nested conditions when you’re checking one Tallyfy value against several options. More detail in our advanced conditions and expressions article.

  • Structure: Pick a value to switch on (like a Tallyfy form field). Create multiple CASE branches for each possible value. The DEFAULT branch catches everything else.

Example: A Tallyfy task has a “Support Ticket Category” form field with values like “Billing Issue” and “Technical Problem.”

  • SWITCH ON “Support Ticket Category”:
    • CASE “Billing Issue”: Notify finance.
    • CASE “Technical Problem”: Create an urgent task in a Tallyfy “Tech Support” process.
    • DEFAULT: Notify general support.

Tips for conditions with Tallyfy data

  • Match data types — use expressions like int() to convert Tallyfy text values when comparing against numbers.
  • Handle case sensitivity — wrap text in toLower() for case-insensitive comparisons.
  • Use Tallyfy connector outputs — data from Tallyfy connector actions should drive your conditional logic.
  • Test every branch — run through each path with different Tallyfy data inputs to catch edge cases.

Automations > Logic operations explained

Tallyfy automations use simple IF-THEN rules instead of complex flowcharts to watch user inputs and automatically adjust workflows by showing or hiding steps and reassigning tasks and changing deadlines based on conditions that can be combined with AND/OR logic and evaluated left to right in the order you add them.

Automations > Conditionals

Tallyfy’s conditional logic lets workflows make automatic decisions using simple “IF X happens” rules based on form field answers and step statuses so processes adapt in real time without manual intervention or complex flowcharts.

Footnotes

  1. Tallyfy webhooks send HTTP POST requests to your flow’s URL when events happen — like task completions or process launches ↩

Get in touch
About Tallyfy