Google Workspace (OpenConnector)
Google Sheets, Docs, Drive, and Calendar as 30 per-operation actions grouped by product, acting as a Google account connected centrally in FloMorphic → Connect (OpenConnector / oomol). Holds no Google credentials; proxies each action over the flomorphic.svc.oc.* NATS subjects.
- SDK
- Go
- Protocol
inflowv1- Actions
- 30
- Version
- v0.1.0
- Author
- FloMorphic
- Runs on
- flomorphic — needs Connect / OpenConnector proxy
- Categories
- Files and storageUtility
Reach for it when
Sheets, Docs, Drive and Calendar — thirty per-operation actions, under a centrally connected account.
The use people don't expect
Writing to a Sheet is often the honest last mile. The people who need the output already live there, and a flow that ends in a spreadsheet gets adopted where a dashboard doesn't.
A flow that uses it
Each one is a shape of flow, not a template to copy. Node names are the labels as they appear on the canvas; a name with a slash means either would do.
Ending where the readers already are
Starts withThe end of any flow whose result a team has to act on.
- DUCKDB / POSTGRES
Produces the figures.
- Google Workspace (OpenConnector)
Writes the rows into the sheet the team already opens every morning.
- Google Workspace (OpenConnector)
Drafts the summary doc, and puts the review in the calendar.
What you getAdoption, mostly. The flow meets people in the tool they already have open instead of asking them to learn one.
The reference, not the pitch
This page is about what the plugin is for. Every action, every connection field, the ports, the install one-liner and the caveats are in the catalog entry, which is the thing the maintainer updates.
Near it in the catalog
The task is "do this, here, on this machine" rather than "answer this" — and you want the work to stop and ask when it hits a decision nobody delegated.
CODEX AGENTCodex AgentSame shape as Claude Agent, over Codex — reach for it when you want the workspace fence enforced by the operating system rather than by the model behaving well.
DUCKDBDuckDBThe data is files — CSV, Parquet, JSON, Excel — on disk, over https, or in a bucket. SQL over them in place.