All Collections
Adding an Automation
Adding an Automation

Build processes & workflows with powerful "IF THIS, THEN THAT" statements.

Brian Faust avatar
Written by Brian Faust
Updated over a week ago

Rather than being forced into adopting a certain process, Rindle’s flexible automations offer you the opportunity to control your workflow (saving you time).

Automations are Rules, Schedulers, and Batch Operations that contain triggers and actions. You can think of them as "IF THIS, THEN THAT" statements.

Create an Automation

Click on the Automations icon in the main navigation menu located on the left side of your screen.

You can go to the type of automation you want to create, then click the Create button

Or you can click the dropdown menu on the Create button and select the type you want to create.

In this case, we will create a new Rule. Select what the Rule will apply to:

  • Tasks

  • Boards

  • Lists

  • Users

Then apply a filter to the Rule by clicking the Customize button.

Typically you may want to limit the Rule to a specific board or two, or maybe a specific group of boards. Click Apply when finished.

If you select ALL BOARDS, the Rule will apply to every single board that already exists in your Rindle, and any board created in the future.

Use this feature with EXTREME CAUTION as it could produce unwanted results.

Name your rule by clicking in the rule name field. For example, if you want to create a rule to mark tasks complete when you move them to Done, you might name your rule “Mark task complete when moved to Done” and put it in a group (optional).

Pro Tip: If you are creating a larger process, take a look at our suggested naming conventions.

Select a Trigger

Triggers define what event will execute, or trigger, the rule. It's the IF THIS" part of "IF THIS, THEN THAT". For example, if you wanted something to happen when tasks move to the Done list, then your trigger would be:

Moved or added task

In this case, the event will fire when a task is move or added to ANY LIST on boards in the group "Product". However, we want it to only fire when moved to Done.

To narrow it down to just the Done list, select ADD CONDITIONS

Then select LIST (text string), Equal (Case Sensitive), and enter Done as the value. This will ensure it only fires on lists specifically named Done.

The last field allows you to specify where the condition applies; Self (the task that triggered the Rule), Parent, or Dependent Task. Learn more about Perform Action On.

When finished, click APPLY

Learn more about Triggers

Select an Action

Actions define what will happen when the event is executed. It's the "THEN THAT" part of "IF THIS, THEN THAT". For example, if you wanted to mark the task complete, the action would be:

Mark task complete

Perform Action On defaults to Self, meaning the action will perform on the task that triggered the Rule, not the Parent task or Dependent Task. Learn more about Perform Action On.

Learn more about Actions

Save and Activate

Once you’re happy with your new rule and have set-up both a Trigger, Action, and any conditions, it is now time to enable it so that it’s up and running!

If you want the Rule to go into effect immediately, Enable the Rule before saving. If you don’t want to enable your rule just yet, simply click Save. 

Note: Automations will not run unless they are enabled.

Multiple Triggers & Actions in a Single Rule

You can add even more power to your rule by including multiple triggers and actions. Multiple triggers are treated as OR statements and multiple actions are treated as AND statements. 

For example, your triggers might be:
Moved or Added to Done OR When all sub tasks are marked complete

Use the "+" button to add another trigger to the automation.

For the actions, you might want:
Mark task complete AND Notify members by email

Use the "+" button to add another action to the automation.


Conditionals are a way to ensure actions get performed only on the items you want. With conditionals, you set a specific condition (e.g., when a "task title" field contains "urgent") to get to the granularity you need. When the data from your rule meets the conditions you set, it proceeds to execute the action(s) in your rule. If the condition is not met, the trigger or action will not be performed.

Did this answer your question?