Job & Workflow Management
Automate Jobs with rules
Set up automation rules that change a Job's status, tags, assignees or dates when a date passes, a tag is added, the status changes, a Job is created, a subtask is completed or a client request is sent or completed, and add automations to a Job template or a single Job.
Automation rules do routine Job updates for you. Each rule has a trigger (When), optional conditions (Only if) and one action (Then). An owner or admin manages rules in Settings → Automations, and rules count toward your plan’s automation allowance. See pricing for plan details.
This article covers rules that act on Jobs. Rules can also create a Job when a client is added or a proposal is accepted, see Automate client onboarding, and handle incoming email, see Automate incoming email.
To move one kind of Job along as its own subtasks, sections and client requests are done, add automations to its Job template instead. See Add automations to a Job template or a Job.
Create a Job automation rule
- Go to Settings → Automations and click New rule.
- Enter a Name your team will recognize, such as “Flag Jobs due this week”.
- Under When, choose what starts the rule.
- Under Only if, click Add condition if the rule should only run for some Jobs.
- Under Then, choose what the rule does and fill in its details.
- Click Save & Close.
The Quick templates at the top of a new rule fill in common setups, such as Start date passed → Ready to Start. Job automation rules run on Jobs only, never on subtasks or Job templates.
Job automation triggers
A Job automation rule starts from one of these triggers under When:
- A date has passed: runs when the chosen Date field (Start Date, Due Date, Internal Due Date or Extended Due Date) is before today. Tidyflow checks date rules every hour.
- A date is approaching: runs when the chosen date is within the number of Days before you enter.
- A tag is added: runs when the tag you choose is added to a Job.
- A Job status changes: runs when a Job moves to the status you choose, or to any status when you choose Any status, from any screen, the board, a bulk edit or another rule.
- A Job is created: runs when a new Job is created. Under Created, choose Any way, By a repeat, From a template or Added directly. Added directly covers the New job form, duplicating a Job, the API and Tidyflow Agent. Jobs imported from a spreadsheet do not trigger it.
- A subtask is completed: runs each time a subtask on a Job is completed. Client requests have their own triggers below.
- All subtasks are completed: runs each time the last open subtask on a Job is completed, client requests included.
- A client request is sent: runs each time a client request on a Job is sent to the client, whether you send it, it sends automatically or you send several at once.
- A client request is completed: runs when a client request on a Job is completed, either once every required item is in or when the client submits it, and no other request sent on that Job is still waiting on the client.
Date triggers skip completed Jobs.
To move a Job when work starts, whichever subtask is done first, use A subtask is completed with a condition on the status new Jobs start in, such as Status is Not Started (or Status is not set if new Jobs have no status), and the action Set job status. To show which Jobs are waiting on the client, pair A client request is sent with A client request is completed: add and remove a tag such as Waiting on client, or set a status such as Waiting on documents and move it on with the condition Status is Waiting on documents.
To move a Job when one particular subtask is done, use that subtask’s Automation setting instead. See Update a Job’s status automatically from a subtask.
Limit a Job automation rule with conditions
Conditions under Only if narrow which Jobs a rule acts on. A Job must match every condition:
- Status is or Status is not: one or more statuses.
- Status is not set: Jobs with no status yet.
- Has tag or Does not have tag: one tag.
- Assignee: Job has no assignee or Job has an assignee.
- Job template is: one or more Job templates. Matches Jobs created from those templates, and their repeats and copies. Jobs created before this condition existed match only when Tidyflow recorded the template they came from.
For example, a rule that assigns new work can use Job has no assignee so it never replaces someone your team already chose.
Job automation actions
A Job automation rule does one of these under Then:
- Set job status: moves the Job to the status you choose. Choosing Completed completes the Job.
- Add a tag or Remove a tag.
- Assign: adds a teammate or an agent teammate to the Job. When you assign Tidyflow Agent, describe the work in Agent instructions. See Agent teammates. On the Pro plan the rule can assign a client role instead, such as the Reviewer on that Job’s client, and Replace current assignees hands the Job over. See Assign work by client role.
- Set dates: sets or clears the Job’s dates. See the next section.
- Add folders from a template: adds a folder template’s folders to the Job’s client. Only folders the client doesn’t have yet are added, shared the way the template says. See Folder templates.
On the Pro plan, Send webhook tells another system about the Job. See Send webhooks from automation rules.
Set a Job’s dates with an automation rule
The Set dates action handles each of Start date, Internal due date, Due date and Extended due date separately. For each one, choose:
- Don’t change: leaves the date as it is.
- Clear: removes the date.
- Day it runs: sets the date to the day the rule runs, in your workspace’s time zone.
- Days after it runs: sets the date the number of Days you enter after the day the rule runs.
- On a date: sets the date to a Month and Day, such as 15 October. The date is the next time that day comes round, counting the day the rule runs, so the rule keeps working each year. It is not moved when it falls on a weekend.
For example, to give extended returns their extension deadline, use the trigger A Job status changes with your Extended status and set Extended due date to On a date, 15 October.
A rule never sets a start date or internal due date later than the Job’s due date, or its extended due date when the Job has an extension. A date that would land later is set to the due date instead.
Dates set by a rule apply to that Job only. They do not change when a repeating Job’s next start date or internal due date falls, so a rule that clears those dates on each repeat keeps working every time. See How recurring jobs work.
How often a Job automation rule runs
Most rules run once per Job. Moving a Job back to a status, or removing and adding a tag again, does not run the same rule a second time.
Date rules are the exception: if you change the Job’s date, the rule can run again for the new date. Subtask and client request rules run every time their event happens, so add a condition when the rule should only act once, such as Status is Not Started before moving a Job to In Progress. Send webhook rules send every time their event happens.
New date rules start turned off. When you save or turn on a date rule that already matches Jobs, Tidyflow asks Apply to existing jobs? and shows how many Jobs match. Click Run on existing jobs to apply it to them now. Other triggers only run for changes made after the rule is saved.
Add automations to a Job template or a Job
A Job template or a Job can have its own automations that run when one of its subtasks, sections or client requests is sent or completed. Use them to hand work from one person to the next, or to move a Job out of a waiting status when the client sends what you asked for. These automations belong to that template or Job only, and they don’t count toward your plan’s automation allowance.
- Open the Job template from Settings → Job templates, or open a Job.
- In the side panel, under Automations, click Add automation, then click Add automation again in the window that opens.
- Under When, choose a subtask, a section or a client request. For a client request, choose whether it is sent or is completed. A section is completed when every subtask in it is completed.
- Under Then, click Add action and choose one or more actions:
- Set status: moves the Job to the status you choose. Only statuses that apply to the Job’s service are offered.
- Assign to: replaces the people on the Job with a person or a client role. The new assignee is notified and follows the Job. Agent teammates on the Job stay assigned.
- Set internal due date, Set due date or Set extended due date: choose After and a number of days from when the automation runs, or On and a fixed day, such as 15 October for an extension.
- Click Save, then Done.
A subtask or client request shows the same Automations, counting the ones that wait for it, and opens the Job’s list. A new automation added there starts with that item chosen.
Jobs created from the template carry its automations. Changing the automations on one Job leaves the template and other Jobs as they are. Each subtask, section or client request event can have one automation, with as many actions as you need. A subtask’s own Automation setting is the same as an automation for that subtask with Set status, so it shows in this list too.
How Job template and Job automations run
Automations on a Job run every time their event happens, so reopening and completing a subtask again runs its automation again. They run after workspace rules for the same event, so the Job’s own automation wins if both change the same thing.
A client request automation set to is completed runs when that request is completed, even if other requests on the Job are still waiting. If nobody holds the chosen client role on the Job’s client, Assign to leaves the assignees as they are. Client roles are part of the Pro plan.
For example, on a tax return template that sends the client an organizer:
- When the organizer is sent: Set status to a status such as “Waiting on client”.
- When the organizer is completed: Set status to a status such as “In progress”, Assign to your preparer or the Preparer client role, and Set internal due date After 2 days.
- When the tax return delivery is completed: Set status to a status such as “Ready to file”.
- When the preparation section is completed: Assign to your reviewer or the Reviewer client role, and Set internal due date After 3 days.
On a monthly bookkeeping template, when the bank statements request is completed: Assign to the Bookkeeper client role and Set internal due date After 5 days.
Each person then sees their own deadline as the internal due date while the Job’s due date stays the same.
Example Job automation rules
These rules show how triggers, conditions and actions combine. Create any statuses and tags they use first in Job statuses and tags.
- Flag work due soon: A date is approaching, Due Date, 7 days, then Add a tag “Due this week”.
- Mark overdue work: A date has passed, Due Date, then Set job status to a status such as “Overdue”.
- Route new work from a template: A Job is created, From a template, Only if Job has no assignee, then Assign a user.
- Set up folders for a type of work: A Job is created, Only if Job template is Quarterly sales tax, then Add folders from a template with your sales tax folders.
- Start the clock when the client’s information arrives: A Job status changes to a status such as “Information received”, then Set dates with Start date Day it runs and Internal due date Days after it runs, 14.
- Leave dates blank on each repeat: A Job is created, By a repeat, then Set dates with Start date and Internal due date set to Clear.
- Hand reviewed work back: A tag is added “Review done”, then Set job status to a status such as “Ready to file”.
Related articles
Was this page helpful?
What went wrong?
Thanks for your feedback.
- Previous
- Add a Job
Last updated November 17, 2026