What does this automation do?
The document is read, an agent finds each commitment inside it, and every one becomes its own task with its own due date.
What can you do with it?
- Find the promises buried in a long document
- Give each commitment an owner and a deadline, not a bullet
- Stop re-reading the same notes to remember what was agreed
The Steps
This automation runs in 4 steps:
- When Google Docs — New Document
- Then Google Docs — Read Document
- Then Taskade AI — Ask Agent ("Commitment Reader")
- Then Loop over each commitment found — Add Task, Set Task Due Date
What makes this different from a Zapier-style flow?
The "Commitment Reader" step is not a one-off model call. It is a Taskade AI agent that knows your team, your projects and how your notes are written, remembers the commitments it has already raised from earlier documents, so every run builds on the last one instead of starting from an empty prompt.
A stateless "ask the model" step forgets everything the moment it returns. An agent keeps its knowledge and its memory between runs, carries its own tools, and can be handed work by other automations.
Who is this automation for?
Built for teams whose decisions live in notes nobody revisits. The document is read, an agent finds each commitment inside it, and every one becomes its own task with its own due date.
How do you set it up?
- Open the "Automations" tab in your workspace.
- Click ➕ Add automation, then start from scratch.
- Add the trigger "New Document" from Google Docs.
- Add the action "Read Document" from Google Docs.
- Add the action "Ask Agent" from Taskade AI. Point it at an agent called "Commitment Reader".
- Add a Loop step: Loop over each commitment found — Add Task, Set Task Due Date.
- Enable the toggle in the top-right corner to activate the automation.
Prefer to describe it instead? Click Build this flow with AI above and Taskade wires the trigger, the steps, and the agent for you.