If-this-then-that rules and why they matter now

If-this-then-that rules are the invisible wiring behind every automated decision, from a smart plug turning on your coffee maker to a purchase approval routing through three departments. Here is how we think about conditional logic at Tallyfy and why it matters more than ever.

We’ve been following rules since we were born. Some voluntarily. Others… not so much.

Why do we have so many rules? For some people, rules feel like restrictions. But without them, modern life would be pure chaos. Think about a marketplace where everybody just does whatever they want. How long before it all falls apart?

The same thing applies to how businesses run. If you’re leading an organization or you’ve been running a company for years, you already know this. At the very least, a core set of understood rules keeps everything moving. What nobody warned us about when working with operations directors at mid-size property management and professional services firms is the pattern that keeps repeating: teams that define conditional rules explicitly outperform those that leave them implicit.

Business rules, in their simplest form, are instructions that define or constrain how a business operates. They weren’t born out of technology. They came from the effort to figure out the best approach to business operations. Technology just made them faster to enforce.

Here is what trips people up right now. The agent revolution arrived without its most critical dependency: defined processes. IEEE Spectrum reports 40% of enterprise apps will feature task-specific AI agents by the end of 2026, up from less than 5% in 2025. But over 40% of agentic AI projects will be canceled by end of 2027 due to unclear value and escalating costs. The missing piece? Defined processes with clear if-then rules that agents can actually follow.

Three types of business rules

When rules are part of a process, they grow from three kinds of assertions:

1. Structural assertion - a fact about how your organization is built that shapes decisions. Who reports to whom. Which department owns what.
2. Action assertion - a set of conditions that control what the organization does next. If the invoice is over $10,000, route it to the CFO.
3. Derivation - knowledge that comes from combining other pieces of knowledge. If a vendor has a preferred status AND the order is under $5,000, skip the second approval.

Within those assertions, rules break down further:

• Coordination rules - general requirements that must be met for a process to continue. “All required fields must be filled.” These keep work moving without rework. Simple.
• Qualification rules - filters that determine whether something should be included or excluded. Think of a vacation request where the dollar value and days requested determine which manager level needs to approve. They prevent wasted time and effort.
• Decision rules - evaluations that assign a next step, like approved or rejected. They represent related conditional decisions in a clear if-this-then-that structure.

Templates with conditional if-this-then-that rules

Example Procedure

Multi-Tier Purchase Approval Authority Matrix Workflow

1Supplier approval (Tier 1 - Manager Level)

2Purchase authorization (Tier 2 - Director Level)

3Vendor acknowledgement and PO confirmation

4Define approval thresholds by tier

5Assign approvers by role and backup coverage

+3 more steps

View template

Example Procedure

PTO & Vacation Request Approval Workflow

1Submit leave request details

2Sales/Marketing Manager - Approve or reject leave request

3IT Manager - Approve or reject leave request

4HR Manager - Approve or reject leave request

5Leave request approved

+6 more steps

View template

Example Procedure

Internal Purchase Order Request

1Submit Purchase Order Request Form

2Finance Manager: Review Standard Purchase Order (Under $10k)

3Update Procurement System Status to Rejected

4Notify Employee: Purchase Order Rejected

5Generate Official Purchase Order Number (Standard PO)

+10 more steps

View template

Why you should separate business rules from process logic

In traditional automation, business rules get hard coded directly inside process workflows. That approach is rigid. It works until the business needs to change a policy, and then everybody’s waiting on a developer. Business logic changes over time. That’s just reality. Organizations need to stay responsive, and at Tallyfy, we believe separating business rules from process logic is essential for that agility. Research on agile business rule development consistently shows that treating rules as separate, manageable artifacts gives organizations the flexibility to update policies without rewriting workflows from scratch. Workflow management software like Tallyfy lets organizations model business rules independently from automated processes. What does that mean in practice? Your process experts, the people who actually know how the business works, can make updates without involving developers or touching the core infrastructure. One thing that keeps coming up in our conversations with mid-market operations teams is that the people closest to the work should own the rules, not the IT department.

This drives me crazy about legacy BPM tools. They assume that only developers should touch the logic. The BPM Institute makes the same point: business process models and business rules work together, but separating them gives you the ability to change one without breaking the other.

How if-this-then-that rules actually work

One of the fundamental principles here is dead simple: input determines output.

If one thing happens, make something else happen automatically.

If I arrive at home, put my phone on silent. If a candidate’s immigration status is “Foreign National,” show the extended onboarding plan instead of the standard one.

Let’s walk through a real example. Company X is US-based. They’ve just hired someone through their standard process: advertise the position, assess applications, run interviews, make an offer, candidate accepts, HR contacts legal for onboarding.

Company X has set up if-this-then-that rules in Tallyfy for their onboarding process. The HR team sees different steps triggered by input options:

• If immigration status = US citizen, then show Plan X
• If immigration status = Foreign National, then show Plan Y

The ability to branch and hide tasks before they’re needed is one of those features that doesn’t sound exciting on paper but transforms how people feel about their work. Nobody wants to open a to-do list and see forty tasks when only twelve apply to them.

Tallyfy provides variable process trees based on inputs. That’s something most project management tools simply can’t do.

Middleware moves data. Tallyfy moves tasks between people.

This distinction matters more than most people realize.

All the integration tools like IFTTT, Zapier, and Microsoft Power Automate are “middleware” platforms. They move data between apps using rules. Tallyfy does something different. It moves tasks between people using rules.

IFTTT is probably the simplest automation tool out there. You set a trigger and an action between two apps. These integrations are called “applets” and each one has a specific job. Want to automatically post a birthday wish on Facebook? You can set that up in about two minutes.

IFTTT is best for simple, personal automation. Home automation, device triggers, basic app connections. But in discussions we’ve had with IT managed service providers, we consistently hear that organizations outgrow IFTTT the moment they need multi-step conditional logic. Different due diligence paths based on deal type, security deployment workflows that branch based on requirements… IFTTT wasn’t built for that.

Pros: simple, ready-made applets, free tier. Cons: limited triggers and actions, applets don’t always work as expected.

Zapier is the heavyweight middleware platform. It connects a huge range of business apps and supports multi-step automation called “Zaps.” It uses the same if-this-then-that structure but handles far more complexity than IFTTT. Need a weather forecast texted to you every morning? Zapier can do that. Need Slack notifications linked to Trello boards? Also covered.

Pros: massive app ecosystem, multi-step chains, advanced features. Cons: no mobile apps, no smart home support. Zapier is best when you need a data pipeline between business tools, not for casual or personal tasks. To read more about the differences between Zapier and IFTTT, check here.

Tallyfy is a workflow management platform designed to eliminate repetitive workflows through task automation between people. Similar to IFTTT, Tallyfy has three main rule types in an if-this-then-that structure: trigger on task completion, trigger on form field response, and trigger on approve/reject response.

The difference? Tallyfy handles complex multi-action flows and automates them between humans, not just between apps.

When to use what

I think the choice comes down to one question: are you moving data between apps or moving tasks between people?

IFTTT is perfect for simple home automation. Turn on the coffee maker at 7am. Done.

Zapier and Tallyfy handle professional and corporate automation. But they solve different problems. Think about all those email attachments in your Gmail that you’ve been meaning to save to Dropbox. Zapier automates that. Data moves between apps. No human judgment needed.

Tallyfy moves tasks between people. A purchase requisition needs three different approvals based on the dollar amount? If the form field value is $100,000 or more, or the purchase type is Professional Services over $60,000, then show the “Provide Complete Specifications” task. That’s Tallyfy.

The real power of if-this-then-that rules isn’t in connecting apps. It’s in connecting people to the right work at the right time. And with AI agents now entering the picture, having structured conditional rules becomes even more important. An AI agent without a defined workflow is just an LLM with aspirations but no operational backbone.

The AI agent connection most people miss

Here’s where this gets interesting.

My guess is that most organizations rushing to deploy AI agents haven’t thought about this: an AI agent is only as good as the workflow it follows. Agentic workflows rely on conditional logic, loops, and branching as their fundamental control structures. That’s just if-this-then-that rules with a fancier name.

If your processes aren’t defined with clear conditional rules, AI agents have nothing to work with. They can’t decide which approval path to take. They can’t determine who should see which tasks. They can’t branch based on form field responses.

That’s the whole reason Tallyfy exists. The same if-this-then-that rules that route tasks between people today will route tasks between people and AI agents tomorrow. The rules don’t change. The executors do.

A mistake we made early on was assuming teams would figure out conditional rules on their own. But operations teams tell us the same story: organizations that invested in defining their conditional rules before adding automation were the ones that succeeded. The ones that tried to automate undefined processes? They spent more time fixing the automation than they’d saved.

If-this-then-that isn’t just a cute name for a smart home app. It’s the foundation of every workflow that works, whether a human follows it or an AI agent does. Get the rules right first. Everything else follows.