Sistava

Taskade Automations: Triggers, Actions, and Setup

How-to — — by Mahmoud Zalt

How to build a Taskade automation from scratch: add a trigger, add steps, pass variables, test it in History, and turn it on without breaking anything.

Automations are the part of Taskade that turns a task list into something that does work while you are asleep. They are also the part where people build something clever, forget to switch it on, and conclude it does not work.

This walkthrough goes through the build in the order the interface presents it, then covers the two screens that matter after you save: History and the on toggle.

The mental model is deliberately plain: if this happens, then do these things. Taskade calls the first half a trigger and the second half steps or actions, and everything else in the builder is detail hanging off those two ideas.

Where do automations live, and how do you start one?

Automations sit in their own tab in a workspace or app, next to projects and agents. Taskade documents three ways to create one, and they are worth knowing before you pick.

For a first automation, build one from scratch even if a template exists. You want to know which panel holds the conditions before an automation misbehaves, not after.

Build an automation from scratch

  1. Open the Automations tab and click Start from scratch — You land in an empty builder with nothing but an invitation to add a trigger.
  2. Click Add Trigger and pick your event — Taskade documents more than 40 trigger types, from in-app events such as Task Added and Task Completed to webhooks and external services including Gmail, Slack, Google Sheets, and HubSpot.
  3. Configure the trigger in the right-hand panel — For Task Completed you choose a Project, and optionally a Block inside it. Leaving the project blank means all projects are watched, which is rarely what you want.
  4. Click Add Step and choose an action — Actions include native ones such as Create Project, Add Task, and Ask AI, plus integrations with Slack, Gmail, Google Workspace, HubSpot, Stripe, Shopify, GitHub, Discord, Telegram, and many more.
  5. Pass data between steps with variables — Variables carry information from the trigger into the actions and are referenced with the @ symbol. The builder shows you which values the chosen trigger exposes.
  6. Click Save changes — Saving is not enabling. A saved automation sits there doing nothing until the next step.
  7. Toggle the automation on in the top right — This is the step everyone forgets. Nothing runs until the toggle is on.

Once it is running, three tabs matter. Build returns you to the editor, Preview shows the automation as other people see it when it involves a form, and History lists previous and active runs so you can see which one failed and why.

How do you debug an automation that did not fire?

Start with History rather than the editor. A run that appears in History and failed is a configuration problem in a step. No run at all is a trigger problem or an off toggle.

For failed runs, Taskade provides a retry control so you can re-run a step after fixing it, instead of manufacturing a fresh event to test against. That saves a lot of fake tasks in a real project.

Useful things to build first

Skip the ambitious workflow. The automations that survive contact with real work are small ones that remove a recurring copy-and-paste.

If wiring the path is not the part you wanted to own

Choosing a trigger, scoping it to the right project, mapping variables into each step, testing on a scratch project, then owning that chain every time a tool changes is genuine engineering work in a friendly wrapper. Taskade does it well, and the integration list is long enough that most paths you can imagine are buildable.

That set-up work is exactly what we removed at Sistava. Instead of wiring a trigger to an action and testing the path, you hire an AI Employee and tell it in plain English what you want handled. The tools are connected already, it asks you when it is unsure, and there is no flow to maintain when something upstream changes.

The honest split: a flow builder is better when the path is fixed and you need it to run identically every single time. A briefed teammate is better when the path changes and the outcome is what you care about.

FAQ

How do I create an automation in Taskade?

Open the Automations tab, click Start from scratch, click Add Trigger and pick an event, then click Add Step for each action you want. Configure conditions in the right-hand panel, click Save changes, and toggle the automation on in the top right. You can also use Create With AI to draft one from a description, or start from a template.

Why is my Taskade automation not running?

Check the on toggle in the top right first, because saving an automation does not enable it. Then open the History tab. A failed run means a step is misconfigured, while no run at all usually means the trigger is scoped to the wrong project or the event you expected is not the event you selected.

What triggers does Taskade support?

Taskade documents more than 40 trigger types. These include in-app events such as Task Added, Task Completed, and a manual task trigger, plus webhooks and events from external services including Gmail, Slack, Google Sheets, and HubSpot. The full current list appears in the Add Trigger dropdown.

Can an automation trigger on every project at once?

For the Task Completed trigger, leaving the Project field blank means all projects are monitored by default. That is powerful and easy to regret, so scope it deliberately. If you do pick a project, you can also narrow the trigger further to a specific Block within it.

How do I pass information from the trigger into an action?

Taskade uses variables, referenced with the @ symbol, to carry data from the trigger into later steps. The builder surfaces the values the selected trigger makes available, so open that picker rather than typing a variable name from memory.

Can an AI agent be part of an automation?

Yes. Taskade documents Ask Agent and Run Agent Command as steps you can add to a workflow, so a configured agent handles the part that needs judgment. There is also an Add Knowledge to Agent action, which lets an automation keep an agent's knowledge sources up to date.

Sources

Build the flow when the path must never vary. When the outcome matters more than the path, hand the outcome to someone who can figure the path out.