What does this automation do?
A contract landing in Drive is converted to text, read against your standard terms, and opened as a project spanning the contract dates.
What can you do with it?
- Surface the dates, values and obligations on arrival
- Compare against the red lines you already gave the agent
- Put the contract term on the project, not in someone calendar
The Steps
This automation runs in 5 steps:
- When Google Drive — New File
- Then Media — Convert File to Text
- Then Taskade AI — Ask Agent ("Contract Reader")
- Then Taskade — Create Project
- Then Taskade — Set Project Date Range
What makes this different from a Zapier-style flow?
The "Contract Reader" step is not a one-off model call. It is a Taskade AI agent that knows your standard terms and your red lines, remembers the clauses it has flagged before, 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 legal, finance and agency teams handling agreements. A contract landing in Drive is converted to text, read against your standard terms, and opened as a project spanning the contract dates.
How do you set it up?
- Open the "Automations" tab in your workspace.
- Click ➕ Add automation, then start from scratch.
- Add the trigger "New File" from Google Drive.
- Add the action "Convert File to Text" from Media.
- Add the action "Ask Agent" from Taskade AI. Point it at an agent called "Contract Reader".
- Add the action "Create Project" from Taskade.
- Add the action "Set Project Date Range" from Taskade.
- 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.