What Is IFTTT Style Rule Builder?
IFTTT Style Rule Builder is a free online tool by TechnSols that builds if this, then that rules in your browser. You pick a trigger, such as a new email or a time of day, pick the action that follows, such as a message or a saved note, and the tool keeps the whole rule list in order.
An automation that lives only in your head is forgotten the first time you are busy, because the trigger fires and nobody acts on it. The Itigic guide to what IFTTT is explains the same idea: an applet is one trigger and one action, written down, so the connection between two apps never depends on memory.
This builder is for the rules only: it does not connect to your apps and it does not run the rules, because running them needs accounts and a server. If a rule must fire on a live payload, the Webhook Payload Viewer tool shows that payload in full before you write the rule.
People use it to design rules such as when a form is submitted, save the answers, or when it is 9 in the morning, send the daily summary, or when a file is added, back it up. It suits a small shop, a creator, or anyone who repeats the same small task every day and wants it written down as a rule.
How To Use IFTTT Style Rule Builder?
Here is how to build an if this, then that rule online in three quick steps. Using IFTTT Style Rule Builder is simple. There is no software to install and no account to make. Name the rule, pick the trigger, and pick the action. If the rule must run on a schedule, the Cron Job Manager tool manages that schedule.
Step 1: Name The Rule And Pick The Trigger
Type a rule name in plain words, such as Save Form Answers, then pick the trigger from the list: a form submitted, a new email, a file added, a time of day, or a webhook received. The trigger is the if half of the rule, and it must be an event you can actually notice, or the rule will never fire.
Step 2: Pick The Action That Follows
Pick the action from the list: send a message, save a note, add a row, send an email, or call a webhook. One rule holds one trigger and one action, so a job that needs two actions needs two rules, and each rule stays short enough to read in one line.
Step 3: Review The Rules And Export
Read the rule list from top to bottom, check that no two rules do the same job, and that the triggers cover the events that matter. Then press Export JSON to download the rule list as a file. If the rule list must be checked as data, the JSON Formatter tool formats that JSON so it reads cleanly.
The whole rule list takes about fifteen minutes to build, and it is the plan the real automation will be built from. Rules written down are rules a team can agree on, and that is the whole point of building them here.
Why IFTTT Style Rule Builder?
A rule list beats a set of habits because habits live in one person and leave when that person is away. The builder fixes the rules in one list, so the same trigger always leads to the same action, no matter who is on duty. If a rule must fire when a form is submitted, the Form Submission Tester tool tests that submission first.
The reason the if this, then that shape works is that it matches how people think about cause and effect: one event, one result, no hidden steps. The Cloudwards IFTTT guide makes the same point, that the simplest automation is a trigger and an action, and anything more complex starts as a list of simple rules.
One Trigger, One Action, No Hidden Steps
A rule with one trigger and one action is easy to test, easy to explain, and easy to fix when it is wrong. A rule with three triggers hides which one fired, and a rule with three actions hides which one failed. Keep each rule to a single pair, and the whole list reads like a set of plain sentences.
The List Is The Automation Plan
An automation platform asks for the same thing this builder writes: a trigger, an action, and a name, so the exported list is the exact plan you paste into the platform. Writing the plan here first means the platform setup takes minutes, because every decision is already made. If a rule must send an email, the Email Attachment Extractor tool extracts the attachments that email may carry.
Export Turns The Rules Into A File
The JSON export carries every rule with its name, trigger, and action, so the list can be handed to a developer, pasted into an automation platform, or kept as the record of what was agreed. The rules leave the browser as a file, and the file is the design that the real automation will be built from.
What Can You Do With IFTTT Style Rule Builder?
An if this, then that rule fits any small job that repeats on an event. These are the jobs this builder handles best.
Save Form Answers When Submitted
When a form is submitted, save the answers to a sheet, so no response is ever lost in an inbox. If the form answers must be turned into a service that other tools can call, the Docker Compose Builder tool builds that service definition.
Send The Daily Summary On Time
When it is 9 in the morning, send the daily summary, so the team starts the day with the same numbers. A time trigger is the simplest trigger of all, because it needs no app and no event, only a clock, and it is the rule most teams write first.
Back Up A File When It Is Added
When a file is added to a folder, back it up, so the copy exists before anyone can delete the original. A backup rule is a quiet rule: it fires every day and nobody notices, until the day the original is gone and the copy is the only one left.
Quality And Settings
The builder offers five triggers, form submitted, new email, file added, time of day, and webhook received, and five actions, send a message, save a note, add a row, send an email, and call a webhook. Rules are stored in your browser localStorage in the order you added them, and they export as a JSON file. If a rule must be drawn as part of a larger process, the API Documentation Builder tool draws that process step by step.
- Five triggers: form, email, file, time of day, and webhook.
- Five actions: message, note, row, email, and webhook call.
- Rules kept in order, so the list reads top to bottom.
- JSON export with name, trigger, and action per rule.
- Rules stored in your own browser localStorage, never on a server.
There are no other settings to learn, because a rule is a name, a trigger, and an action. Add the rules, read them back, and export the list when it is ready.
How IFTTT Style Rule Builder Works
The builder keeps the rules as a list in your browser, with each rule holding its name, its trigger, and its action, in the order you added them. The list reads that stored set each time it draws, so the rules look the same when you come back. If a rule set must be validated as data, the Process Flow Designer tool checks that JSON before you share it.
Two limits are worth knowing. The builder designs rules, and it does not execute them: nothing here can watch for a real trigger, connect to your apps, or run a real action, because that needs accounts and a server. It also stores the rules on one browser only, so the JSON export is the way to move the set to another device or hand it to a developer.
Privacy
Everything you type stays in your browser. The rule names, triggers, and actions are designed on your own computer, and nothing you enter is uploaded to a server, stored, or shared with anyone. The saved rule list lives in your own browser localStorage, so it never leaves your device.
Because no account is needed, there is no name, email, or history tied to what you design. Closing the tab ends the session, and the browser clears the input from memory, while the saved rules stay in your own browser until you delete them. That is the same protection on every tool here: your work stays yours, and nothing about it is kept, shared, or sold.
Tips
A few habits make IFTTT Style Rule Builder work smoother, whether this is your first rule or your fiftieth.
- Name the rule after the job it does, not after the trigger.
- Keep one trigger and one action per rule, so a failure is easy to trace.
- Put the rules that matter most at the top of the list.
- Read the list out loud: a rule that sounds wrong is wrong.
- Export the JSON before you clear the rules, as a backup.
When the rule list is ready, export the JSON and hand it to the person who builds the automation. If the rules must be scheduled as jobs, the JSON Validator tool manages that schedule.
More Tools For The Same Job
These tools handle the same kinds of jobs: triggers, rules, and checking data.
- Webhook Payload Viewer: shows a webhook payload in full.
- Cron Job Manager: schedules the jobs a rule may need.
- JSON Formatter: formats JSON so it reads cleanly.
- JSON Validator: checks JSON for errors before you share it.
- Form Submission Tester: tests what a form sends on submit.
- Email Attachment Extractor: extracts the attachments an email carries.
- Docker Compose Builder: builds the services a rule may call.
- API Documentation Builder: documents the services a rule may call.
- Process Flow Designer: draws a process flow step by step.
- Gantt Chart Maker: maps a longer project timeline from its dates.
FAQ
Common questions about building if this, then that rules, answered plainly.
Is IFTTT Style Rule Builder by TechnSols Free?
Yes, IFTTT Style Rule Builder by TechnSols is completely free to use, with no account, no sign-up, and no usage limit. You can build as many rule lists as you like, and everything you type stays in your browser, so nothing is uploaded or stored anywhere.
Does It Connect To My Apps?
No, this tool designs rules only, in your browser. It builds the rule list and exports it as a JSON file, but it cannot connect to your apps, watch for a real trigger, or run a real action. To run the rules, paste the exported list into an automation platform that connects to your apps.
What Triggers Can I Pick?
You can pick a form submitted, a new email, a file added, a time of day, or a webhook received, with one trigger per rule. Pick the trigger that matches the event you can actually notice, and add a second rule when a second event must start the same job. Each rule stays short and easy to test.
Where Are My Rules Saved?
Your rules are saved in your own browser localStorage, on the device and browser you used to design them. They stay there when you come back on the same browser, and they never leave your device. Export the JSON file when you need the rules on another device or want to share them with a developer.
How Many Rules Can I Add?
There is no set limit on the number of rules, because the list lives in your own browser storage. A normal set needs five to fifteen rules, and the list stays readable at that size. If the list grows past twenty rules, split it by app or by job, so each list has its own short set.
Name the rule, pick the trigger, and pick the action. Rules written down are rules a team can agree on, and that is the whole point of building them here.