Outreach and follow-up workflows
The agent can gather lead context, draft messages, and prepare follow-up steps with approved communication actions.
lead context
message drafting
follow-up flow
Tool actions
Let the agent act through tools after you approve the path.
Integrations are not a logo wall. They are action surfaces the workspace agent can use to gather context, send messages, update files, publish outputs, and automate repeatable work.
120+ searchable actions for connected apps
Email, files, scraping, storage, and publishing in one run
Permissioned tool calls before external actions happen
Less tab-hopping, more execution from workspace memory
Research to publish workflows
Pull source signals, structure findings in docs, and publish or export when the output is ready for release.
source gathering
doc synthesis
publish handoff
File and knowledge operations
Read, organize, and update workspace-related files while keeping docs linked to the same task context.
file updates
structured notes
workspace memory
Repeatable automation loops
Run recurring action sequences with approvals in the loop so repeated jobs stay consistent and easy to supervise.
repeat jobs
approval checkpoints
less manual ops
Why it matters
Tool actions make the agent useful outside the editor
The point is not a long list of names. It is shortening the path from "the agent understands the task" to "the work is done or ready for approval."
Workflow loop
1
Gather context from approved connected tools
2
Use docs and models to plan the right output
3
Execute, update, or send after the user approves
Keep actions where workspace memory lives
Tools support the task. Docs remain the source of truth, and outputs stay attached to the workspace.