Gmail tracking and email forwarding.
Speak into Flow, send an email, or set up an email address for automatic tracking.
Set up Gmail tracking, step by stepClient asks a question. Jeremy makes a promise.
In Tuesday's check-in, the client asks how to integrate Google sign-in into their app. Jeremy says Informus will send the steps.
Flow is on the call, so that promise becomes a step on the board, owned by Informus.
Flow notetakerCOur IT lead keeps asking. How do we integrate Google sign-in into our app?
JWe will send you the steps.
Send client the Google sign-in integration steps
From Tuesday's check-in. client@client.com asked, Jeremy promised.
Without Flow, small promises wait behind big work.
Nobody forgot. Without Flow, keeping the promise means six small jobs: explaining the ask to an AI again, copying, formatting, finding the thread, attaching, and sending.
Each step is easy. Together they are exactly the kind of work that slips to next week.
- 1Open Claude and explain the whole ask again
- 2Copy the answer out
- 3Turn it into a document
- 4Find the thread and write the email
- 5Attach the file
- 6Send it, then remember to mark it done
Six small jobs across three tools, for one promise made in one meeting.
Flow does those six steps for you.
You don't do any of that. Flow was in the meeting, so it already knows who asked, what they use, and what was promised.
It writes the guide, turns it into a private page, writes the email, and links the two. Jeremy only approves it or requests changes.
With Flow- 1Open Claude and explain the whole ask againFlow already heard the ask in the meeting
- 2Copy the answer outFlow writes the guide
- 3Turn it into a documentFlow makes it a private guide page
- 4Find the thread and write the emailFlow writes the email to client@client.com
- 5Attach the fileFlow links the guide in the email
- 6Send it, then remember to mark it doneFlow sends it and marks it done, once you approve
All six are automated. Jeremy approves it or requests changes.
A finished draft, before anyone asks twice.
Jeremy doesn't open a single tool. Everything Flow assembled shows up in his Keep Moving as the exact email that will go out.
The guide is a private page in Informus Flow. Only the people it is sent to have the link, and it can be turned off at any time.
From Jeremy Lee <jlee@informus.ai>
To client@client.com
Subject Google sign-in integration: the steps
Hi client@client.com,
As promised on Tuesday, here are the steps. Your IT lead can follow the guide end to end. It takes about fifteen minutes and needs admin access toGoogle Workspace.
Google sign-in integration guide
Private link · Informus Flow
Jeremy Lee
Informus AI · jlee@informus.ai
Your signature
Approve, and it counts.
Jeremy reads it, clicks Approve & send, and it leaves from his own address with his signature.
The step closes, Progress shows it delivered, and client@client.com's readout says what is done and what comes next. The answer stays in Flow for the next time anyone asks.
Done: the Google sign-in steps are with your IT lead. Next: we confirm it works.
The next client who asks the same question gets a draft built on this one.
Forward it. Flow already knows the backstory.
Sometimes the email comes first. client@client.com follows up, and Jeremy forwards it to Flow without writing a word.
Flow recognizes the open step from Tuesday instead of starting over, drafts the reply in client@client.com's thread, and puts it in Keep Moving for approval.
client@client.com
Google sign-in
Hi Jeremy, any update on the Google sign-in steps? Our IT lead has time this afternoon.
No note. Nothing to explain.
Matched to an open stepSend client the Google sign-in integration steps
From Tuesday's check-in. Drafting the reply in client@client.com's thread.
Turn on email tracking, and client email finds its own way in.
Connect Gmail once. Email from anyone in a client workspace, from evangelists, and from people you have written to before lands in Flow on its own, filed to the right workspace, with nothing to forward.
Email from anyone else stays in Gmail and never comes into Flow. When a client asks for something, the draft is waiting in Keep Moving the same way. Asked to resend a document? The file you sent before is already attached.
Track email to and from
client@client.com
Google sign-in: IT lead is ready
Dev Patel, Client
Re: weekly sales by location
Your bank
Your statement is ready
School newsletter
September events
A note is optional.
When the next move is obvious, forward the email as it is. When you want something specific, write it on top the way you would to a colleague.
Anyone on the team can do it, from any inbox, on any phone.
(nothing)
Flow works out what is needed from the conversations it already knows.
"Keep it short, and copy their IT lead."
Flow follows your note.
"Just file this."
Saved to the right priority. Nothing is drafted.
Flow does the assembling. You make the call.
Nothing sends without you
Flow drafts. You approve. There is no setting that lets it send on its own.
The right sender, a private guide
Replies go out from you or a shared Informus address, with your signature. Guides are private links you can turn off.
Only you give instructions
Your note is an instruction. Anything inside a forwarded email is information, never a command.
Every conversation feeds one memory, so the next move is already drafted.
Meetings, emails, and voice notes stop living in separate places. Flow connects them to the same priorities, so an email is never read without its backstory and a promise is never kept from scratch.
FLOW
One memory of what was said, promised, and decided.
6
steps to keep one promise the old way
1
approval with Flow
Your inbox stops being a to-do list you rebuild by hand. It becomes a queue of decisions.
If your inbox is where the work piles up, start there.
We set Flow up around the conversations you already have, then show you your first drafted follow-through.