Documents and files

Answer from the document, and say which document

A workflow searches and reads files as the connected account, then cites the file and revision behind every claim it makes.

Join the waitlist See the Google Drive example

Google Drive with Aestus

Keep the tool. Change what the team can see.

The hard part of a question like "which pricing sheet did we actually sign" is never the reasoning. It is that six files have almost the same name and one of them is right. Aestus searches Drive as the account you connected, opens the one file it settles on, and then shows its working: the answer cites the document and revision, and the candidates it passed over are listed underneath.

That listing does more work than it looks like it does. An answer with no sources is either right or wrong and you cannot tell which. An answer that names five files it rejected lets somebody who knows the folder spot the mistake in a second.

Reach is decided twice. The connected account fixes what is visible at all, and an organization policy decides separately whether workflows may use the toolkit even when a person has connected it. Connected for people and closed to runs is a position you can hold.

Good first workflows

Find the version that was signed
Search by content rather than filename and get the revision back with the answer.
Ground a report in real documents
Let a workflow read the source files it cites instead of restating what somebody remembers.
Keep the scope to one account
The connected account's own access is the boundary, so nothing reaches a file it could not already open.

A complete Google Drive example, from trigger to proof.

The example names the people, task event, tool boundary, returned evidence, and acceptance state. The run row below it is a fixed product example, not customer data.

Example — fictional team and data. Not a live run or customer result.

Inside the connected tool

What the Drive connection can and cannot do

Search and read run as the connected account and need no approval. Creating, editing, moving or sharing a file is held.

workspace@meridian.example · connectedRead-only

Runs without an approval

Search the files this account can open
Read one file and its revision

Held for a named person

Create, edit, move or share a file

Example — fictional team and data. Not a live run or customer result.

Concrete workflow example

Answer a question from the document nobody could find

Somebody asks which pricing sheet was signed. The workflow searches Drive, reads the one file that matches, and cites it.

TriggerA question is asked from the automations catalog

1
Aestus workflow
Searches the connected account's files
The search runs as the connected account, so it reaches exactly what that account can already open.
search · 6 candidates
2
Aestus workflow
Reads only the file it decided on
One file is opened. The other five are named in the answer as considered and rejected.
1 read · 5 listed
3
Aestus workflow
Answers with the file behind every claim
Each figure carries the document and the revision it came from, so the answer can be checked.
EXAMPLE-GD-01 · 4 citations
4
Tomas · Finance
Opens the cited file and confirms it
Nothing in Drive was renamed, moved or shared; the run only read.
read-only · no approval needed

Example — fictional team and data. Not a live run or customer result.

Illustrative product example — not a production run

Find the signed pricing sheet

Example run		Runtime	Outcome
EXAMPLE-GD-01	Aestus workflow	aestus	Completed	$0.0118	16.8s

Tokens in / out: 7,400 / 260
Failure code: —
Agent: —

Illustrative Aestus workflow; actual costs and results vary

Example run cost

$0.0118 in the illustrative product example

A fixed example standing for one question answered from 7,400 input tokens of file content. Finding and reading the file is inside that run.

Set it up in four steps.

Follow the real Google Drive connection path. Provider steps link to the provider documentation. Aestus steps name the contract they follow.

01
Connect Drive from its settings card
Settings, Integrations has a Google Drive card of its own. Connecting it mirrors the pattern the GitHub card already uses.
Aestus product guide
02
Choose the account whose reach you want
A run sees exactly the files the connected account can already open. Connect a service or team account rather than a personal one when the scope matters.
Read the provider docs
03
Narrow the toolkits an organization allows
An organization policy decides which connected toolkits a workflow may reach at all, so Drive can be connected for people and withheld from runs.
Aestus product guide
04
Ask a question that needs a file
Run a workflow whose answer depends on a document. The reply comes back naming the file it was taken from.
Aestus product guide

The boundary stays visible while the work moves.

See what Google Drive can do, where a person still decides, and what Aestus records for every governed run.

Where control lives

The account is the boundary

Nothing reaches a file the connected account could not already open. Sharing has not changed; only who is asking has.

Reading passes without a gate

Search and read change nothing in Drive, so they do not hold a run up waiting for somebody to press a button.

Changing a file is a write

Creating, editing, moving or sharing is a write, and a write is a named decision recorded against the task that wanted it.

What Aestus records

The file behind the answer

Each claim names the document and revision it came from, so a wrong answer can be traced to a stale file rather than argued about.

What was considered and dropped

Candidates the search returned but the run did not use are listed, which is how you notice it read the wrong version.

Run economics

Tokens, latency, cost and failure code stay on the run. A file read is part of that run's record.

Questions teams ask

Can it see files nobody shared with us?

No. The connection acts as the account you connected. If that account cannot open a file, neither can a run, and the answer says the file was not reachable.

Does it change anything in Drive?

A reading workflow does not. Creating, editing, moving or sharing a file is a write, which is held for a named person and recorded.

How do we know it read the right version?

Every cited claim carries the file and revision, and the files it considered but did not use are listed beside the answer.

See all integrations See the security controls

Start with one Google Drive run.

Bring one real run. Map its actors, boundary, evidence, cost, and acceptance step.

Talk to us

Example — fictional team and data. Not a live run or customer result.

Concrete workflow example

Answer a question from the document nobody could find

Somebody asks which pricing sheet was signed. The workflow searches Drive, reads the one file that matches, and cites it.

TriggerA question is asked from the automations catalog

1
Aestus workflow
Searches the connected account's files
The search runs as the connected account, so it reaches exactly what that account can already open.
search · 6 candidates
2
Aestus workflow
Reads only the file it decided on
One file is opened. The other five are named in the answer as considered and rejected.
1 read · 5 listed
3
Aestus workflow
Answers with the file behind every claim
Each figure carries the document and the revision it came from, so the answer can be checked.
EXAMPLE-GD-01 · 4 citations
4
Tomas · Finance
Opens the cited file and confirms it
Nothing in Drive was renamed, moved or shared; the run only read.
read-only · no approval needed

Example run

Runtime

Outcome

EXAMPLE-GD-01

Aestus workflow

aestus

Completed

$0.0118

16.8s

Questions teams ask

Can it see files nobody shared with us?

No. The connection acts as the account you connected. If that account cannot open a file, neither can a run, and the answer says the file was not reachable.

Does it change anything in Drive?

A reading workflow does not. Creating, editing, moving or sharing a file is a write, which is held for a named person and recorded.

How do we know it read the right version?

Every cited claim carries the file and revision, and the files it considered but did not use are listed beside the answer.

Answer from the document, and say which document