Automations

The status chasing does itself.

Build a rule in three clicks: when this happens, if that is true, do these things. No code, no separate automation bill.

How it works

Automations, in three moves.

  1. 01

    Pick a trigger

    A status change, a due date, a merged pull request, an inbound webhook or a schedule.

  2. 02

    Add conditions

    Narrow it down by project, assignee, field value or sprint so the rule only fires when it should.

  3. 03

    Chain the actions

    Move, assign, comment, set a field, send to Slack, call a webhook — several in sequence.

In detail

What you get.

  • 40+ triggers and 30+ actions out of the box
  • Conditions with AND / OR grouping
  • Run history with replay and failure reasons
  • Test mode that shows what would have happened
  • Rules scoped to a project or the whole workspace
  • Included on every plan — no per-run pricing
“We stopped arguing about the tool in week two. That has never happened with anything else we have rolled out.”
Marcus KellHead of Delivery, Peakline

Frequently asked

For anything inside Taskzin plus the 200 native integrations, yes. For chaining five unrelated SaaS tools together, keep Zapier — our webhooks talk to it fine.

It is logged with the reason, the run is retried three times with backoff, and the rule owner is notified. Nothing fails silently.

Put Automations to work this week.

Set up a workspace in under two minutes. Import from ClickUp, Jira, Asana or Trello in one click.

No credit card • Free 14 days • Cancel anytime