Stephen Turner
Akash Kumar
Jordan Lee
Taylor Scott
Connect Google Docs to Bridge: docs as meeting context, notes as docs
Connecting Google Docs lets Bridge pull relevant docs and folders into meeting context, so briefs and agents can work from your specs and notes. It also creates Google Docs from meeting content, such as an agenda before a call or a document from the recap. Bridge only reaches docs your Google account can already open.
What the connection does
The connection works in two directions. Your docs inform meetings, and meetings produce docs.
| Direction | What happens | Example |
|---|---|---|
| Docs to Bridge | Bridge pulls relevant Docs files and folders for meeting context | An agent answers a question during a meeting from your team's notes |
| Bridge to Docs | Bridge creates Google Docs from meeting content | A document is created from a recap's notes |
| Agents in Docs | Agents create docs and pull project context | An agent writes up a meeting summary as a doc |
Connect Google Docs
Bridge respects your existing Google permissions. Agents and automations only touch docs your account can access.
To remove the connection later, select Disconnect on the Google Docs card.
- Go to Account settings → Integrations and find the Productivity category.
- Select Connect next to Google Docs and sign in with Google.
- After you authorize, Bridge returns you to the integrations page.
Before a meeting: start from the right doc
Briefs for upcoming meetings draw context from earlier meetings and connected tools. With Google Docs connected, relevant docs can feed that context.
From an upcoming meeting's Assistant, choose Google Docs to create a document with the agenda and participant context. Share it with attendees before the call.
After a meeting: turn the notes into a doc
From a recap's Assistant, choose Google Docs to create a document from the meeting notes. Ask for the shape you need, such as a decision memo or a project update.
In a workflow plan, Google Docs steps appear as agent steps. You can approve, revise or skip each one before it runs.
Example: a weekly product review
This example is illustrative. Your team keeps a running spec in Google Docs. Before the weekly review, the brief pulls in that context, so you start from where the spec stands.
After the call, you open the recap's Assistant and create a doc listing the decisions and open questions. You link it from the spec.
Next week, the brief can draw on both docs. The review starts from last week's decisions instead of from memory.
Limits to know
- Bridge can only reach docs your Google account can open.
- Disconnecting Google Docs also affects Google Meet transcript imports, because both use the same Google connection.
- Custom agents and workflow plans need a paid plan.
- Read a generated doc before you share it outside the meeting's attendees.