EN
Log in Start for free
Features Industries Customer Service AI Pricing Blog Log in Start for free
AUTOMATIONS When → If → Then, in plain language

Repetitive work, done on its own.
And explained.

Assign, notify, chase the stalled task, create the task every Monday: the rule does it on its own and tells you why it did. You build it as a sentence, simulate it on the last 30 days before turning it on, and undo it if you don't like it.

Start for free See how it works
On every plan, including Free 17 ready-made templates No credit card
app.tasskee.com
Tasskee automation list: each rule with its trigger, plain-English sentence, scope, runs this month and status
How a rule reads

Three blocks, one sentence, and the reason behind every run

No flowchart with fifty little boxes. The rule is a sentence anyone on the team understands, and each time it acts, what happened is written down.

WhenSomething happens on the task, a deadline arrives, a time hits or a system calls.
IfOnly on the tasks that matter: project, type, priority, assignee, tag, field.
ThenOne or more actions, in order: assign, notify, change, create, comment, call.
WhyThe history tells the event, the conditions and what each action did. And it undoes.
How it works

Six screens, one menu: Automations

Real Tasskee screens, with a demo agency's rules actually running.

Automations › Rules
List of rules with trigger, sentence, scope, runs this month and status
Organization, project, or personal Runs this month Duplicate and turn off
1 · Build

A plain sentence, not a diagram.

Choose the trigger, filter with conditions and stack the actions. While you build it, Tasskee writes alongside what the rule will do — and that sentence is what shows in the list for the rest of the team.

  • WhenAn event on the task or ticket, a form submitted, a deadline approaching or passed, a stalled task, a schedule or an inbound webhook.
  • IfProject, workstream, type, status, priority, assignee, reporter, tag, title, description, custom field, and due date — with AND or OR.
  • ThenActions run in list order, and each one already sees the task as changed by the previous one.
  • Applies to whomThe whole organization, one project, or just your personal tasks.
Chase a task stalled for 5 days
Editor for the Chase stalled task rule: trigger, Review status condition, internal comment action and the sentence in plain English
2 · What you can automate

16 triggers and 19 actions, for tasks, tickets and personal tasks

The same engine serves the project team, support and each person's private list. The task type is just one more condition.

When

On the task or ticket

Created · Status changed · Field changed · Assignee set · Comment · Attachment · Tag · Approval approved or rejected · Dependency released

Over time

Deadline approaching · Deadline passed · Stuck in the same status for N days

From outside

Form submitted · Recurring schedule · Inbound webhook (Zapier, Make, your own system)

Then

On the task

Change status or priority · Assign an assignee · Add a watcher · Move to a sprint or workstream · Set a deadline in business days · Add or remove a tag · Apply a checklist

Create and communicate

Create a task or subtask with variables · Comment (internal or not) · Notify people · Send email · Call a webhook

With AI

Set the priority · Suggest the assignee · Summarize in a comment · Generate subtasks

3 · Simulate before turning on

Know what the rule would do before it does it.

The fear with every automation is turning it on and messing up five hundred tasks. Here, one button runs the rule against the last 30 real days and shows the result, without changing anything.

  • How many times"36 triggers across 176 events in the last 30 days": you see the volume before it turns into a notification in someone's inbox.
  • On which tasksThe list with the code and title of each task the rule would have reached.
  • Time doesn't go backwardTurning on "notify when due" on an old account doesn't fire five hundred notifications at once: it applies from the day the rule is created onward.
Simulation
Simulation result beside the editor: number of triggers and the tasks affected
4 · History that explains

A rule that acts silently is a rule nobody trusts.

Every run is saved in the history with the task, the result and what was done. One click on "Why?" opens the event, each condition that passed or failed and the message from each action.

  • Also when it didn't trigger"Conditions were not met": the question "why didn't the rule run?" has an answer, with a date.
  • Undo the runThe fields the rule changed go back to their previous value — only the ones nobody touched afterward. What can't be undone, like a notice already sent, the screen tells you.
  • Signature on the taskWhatever the automation changes shows up in the audit log and in comments as "Automation: rule name". No one mistakes it for a person.
Automations › History
Automation run history, with the result and what each run did

Why the rule did this

The event, the task, the condition that passed and the result of each action, with date and duration. It's what you show in the meeting when someone asks "who touched this?".

Detail of a run: event, condition status is Review approved, internal comment and notification to the assignee

And on the task itself

The comment the rule wrote comes signed by the automation, and marked as internal when the client shouldn't see it.

Internal comment signed by Automation: Chase a task stalled for 5 days, in the task's Comments tab
5 · Start without a blank screen

Pick a template, or ask in your own words

In both cases the rule opens in the editor for you to review. Nothing is turned on without your confirmation.

17 ready-made templates

Notify the requester on completion, high-priority bug, deadline reminder, escalate the overdue one, chase the stalled one, ticket with reply and deadline, recurring task, routine with checklist, month-end close, AI triage and more.

Gallery of ready-made automation templates

Create with AI

"When an urgent ticket arrives in the Client Portal, assign it to Camila, set a 1-business-day deadline and notify Rafael." The AI returns the finished rule, with the sentence, for you to check and save.

Create with AI window with the rule description in plain English and examples
6 · What else it solves

Recurring task, integration, and email, with no screen of its own

Recurring tasks

"Every Monday at 9 a.m., create the Weekly report — week {{week}} in the Client Portal, for Camila, with a checklist." The schedule works by day, by weekday or by day of the month, and the title accepts variables.

Incoming webhook

Each rule gets its own URL: Zapier, Make or your site create the task with a POST.

Send email

To your team or to outside recipients, through your organization's Gmail account — the client gets it from you, not from us.

Personal rules

Each person automates their own list: the Friday review, the deadline reminder.

AI actions

Sets the priority, suggests who should handle it, summarizes and breaks it into subtasks — with your own AI key.

Through MCP and the API

Automations are also MCP capabilities: your team's AI agent lists, creates, simulates, turns on, turns off and reads the history of rules, with the permissions of whoever asked. The REST API does the same for your system.

Secure by design

Powerful enough to work on its own. Restrained enough for you to sleep.

No infinite loopsThe same rule doesn't act twice on the same task within 60 seconds, and chained rules stop at the third level.
Quota in plain viewThe month's counter stays on screen, the owner is notified at 80% and 100%, and the rule that stops says why.
Permissions by profileWho can view automations and who can edit the organization's are separate permissions. A personal rule only reaches your own tasks.
Sending limitNotifications and emails have an hourly cap. A configuration mistake doesn't turn into spam for the team or the client.
Less manual work

What comes off the coordinator's plate

No automation

  • Remembering to tell the client the task is done
  • Asking the group who picked up the new ticket
  • Finding out on Friday about a task that has been stalled since Monday
  • Recreating the same task by hand every week
  • Nobody knows why the priority changed

Tasskee

  • When it's completed, the reporter is notified
  • The ticket arrives with a deadline, a response time and an assignee
  • Stalled for five days, the rule chases it
  • Every Monday, the task creates itself
  • Every change says which rule made it, and why

And all in the same place as tasks, tickets and customer service — with no Zapier in the middle for everyday work.

On every plan, with a monthly quota: 100 on Free, 1.000 on Start, 10.000 on Pro and unlimited on Max.AI actions and Create with AI use Pro's AI, with your key. The free trial unlocks everything for 15 days.
View plans
Questions

Questions from people who will automate operations

Do I need to know how to code to create an automation?
No. A rule is built from three blocks — When, If and Then — and Tasskee shows next to it, in plain English, what it will do: "When the status changes to Completed, then notify the reporter." You can start from one of the ready-made templates or describe the rule in your own words and let the AI build it.
What triggers an automation?
An event on the task or ticket (created, status changed, field changed, assignee set, comment, attachment, tag, approval, dependency cleared), a submitted form, time (due date approaching, overdue, task stuck in the same status), a recurring schedule or an external call through the incoming webhook.
How do I know why a rule acted (or didn't)?
The history. Each run shows the event, the task, who caused it, each condition that passed or failed and what each action did. When a rule doesn't act because a condition wasn't met, that is logged too, with the reason.
What if a rule does something silly?
Before turning a rule on, use "Simulate": Tasskee shows how many times and on which tasks the rule would have acted in the last 30 days, without changing anything. Once it is on, every run can be undone: fields go back to their previous value, except the ones someone has changed again since. Comments and notifications already sent are logged as not reversible.
Can one rule trigger another and cause a loop?
It can chain, but it won't loop. The same rule doesn't act twice on the same task within 60 seconds, and a chain of rules stops at the third level. When that happens, the history shows "stopped by loop".
Who can create automations?
Organization and project rules belong to people whose profile has permission to edit automations. Anyone on the team can create personal rules, which only act on their own personal tasks. What the automation changes shows up on the task as "Automation: rule name".
Does the automation send emails and notify the team?
It notifies through Tasskee's bell icon, and the unread notice goes into the person's email digest. To email customers or outside addresses, the "Send email" action goes out through your organization's Gmail account, not through a sender of ours.
How many runs does my plan include?
Automations are available on every plan; what changes is the monthly run quota: 100 on Free, 1.000 on Start, 10.000 on Pro and unlimited on Max. The counter is visible on screen, the account owner is notified at 80% and 100%, and nothing fails silently. AI actions and "Create with AI" use the Pro plan AI, with your organization's key.
Does it work with Zapier, Make and my own system?
It works both ways. The "Incoming webhook" trigger gives each rule its own URL: Zapier, Make or your system send a POST and the rule creates or changes the task. And the "Call webhook" action notifies your system when something happens here. The AI in your MCP client can also create, simulate and debug rules.

Turn on your first rule today.

Create your account, pick a template, simulate it on your last 30 days and turn it on. By tomorrow morning the history already shows what it did.

Start for free See all features
15 days with everything unlocked No credit card Support in Portuguese
Contact us