Overview
Your project already holds the facts. A new task means new work. A passed due date means a slip. A field flipped from "draft" to "ready" means something needs to ship. Project events make perfect automation starts.
TL;DR: Open the Automations tab in your workspace, create a new automation, and pick a project event as the first step. Task Added, Task Due, Field Updated, and Comment Added all watch a project you choose. Add one or more actions, and the automation runs every time that event fires. This is the Memory to Execution arc of Workspace DNA in practice.
The Memory to Execution arc
Your project sits in the Memory layer. The action you trigger lives in Execution. The trigger is the wire between them.
Every workspace change that matters becomes a possible automation start. Every action that runs can write back into the same project. That loop is what makes Workspace DNA self-reinforcing.
What a project trigger watches
A project trigger is a small listener tied to one project. It sits quietly and fires when a specific change happens.
- Task Added fires when a new task appears in the project.
- Task Due fires when a task's due date passes.
- Task Completed fires when a task is checked off.
- Field Updated fires when a custom field changes value.
- Comment Added fires when someone leaves a comment on a task.
Pick the trigger that matches the moment you care about. The closer the trigger is to the real event, the cleaner your automation behaves.
Build your first project-triggered automation
You only need a project, a trigger, and one action. Five minutes start to finish.
- Open the Automations tab in your workspace.
- Click New Automation and give it a clear name.
- Click Add Trigger and pick the project event you want to listen for. Task Added is a great first choice.
- In the trigger settings, pick the project to watch.
- Click Add Action and pick what should happen next. A Slack message, a row in Google Sheets, an email, an AI step, anything from 100+ integrations.
- Toggle the automation On at the top right.
The next change in that project fires the automation. No code, no polling, no checking back.
Common patterns to copy
These are the easiest wins. Each one is two or three steps total.
| Event in your project | What you want to happen | Trigger + actions |
|---|---|---|
| A new lead lands in your CRM project | Notify the sales channel | Task Added → Slack message |
| A task is marked complete | Log the win in a sheet | Task Completed → Google Sheets row |
| A custom field flips to "Ready" | Email the client | Field Updated → Send Email |
| A due date passes without a check | Ping the assignee | Task Due → Slack DM |
| A comment lands on a support task | Tag a teammate by AI | Comment Added → AI Categorize → assign |
The fastest builders treat triggers as small reflexes. One project event, one tidy reaction. Stack them as you learn.
Narrow what counts as a trigger
A raw event can be too broad. A retail team does not need a Slack ping for every task in the project. Only the high-priority ones.
- Add a Filter Data step right after the trigger. The automation only continues if the filter passes.
- Filter on task text, on the assignee, on a custom field, or on tags.
- Combine filters with an AI Categorize step to route by meaning instead of exact match.
A good filter turns a noisy trigger into a precise one. Less chatter for your team. More signal in every notification.
Test before you turn it on
Automations stay quiet in draft mode until you flip the switch. Use that time well.
- Open the project and create a test task that should fire the trigger.
- Open the automation's Runs tab to confirm the trigger picked it up.
- Step through each action's output to confirm the data looks right.
- Once a real run passes end to end, turn the automation on for everyone.
This is the difference between an automation that earns trust and one that gets switched off in a week.
Related guides
- Task Added Trigger. The most-used project trigger in Taskade.
- Automation Triggers. Every trigger type at a glance.
- How Taskade Genesis Works: Workspace DNA. The Memory to Execution loop in context.
- Filter Data. Narrow a trigger before the rest of the automation runs.
- Field Updated. React to custom field changes inside a project.