Google Accounts
Google integration · 1 node(s).
00Overview
Every field below is exactly what you see in the Flomation editor. Fields marked ● live picker let you choose from a list pulled live from your account — no IDs to look up.
01Connecting Google Accounts
Google Accounts nodes have no credential fields — there is no API key or secret to add as an environment secret. Fill in each node's own fields, listed below, and run the flow.
02Accounts
Manage Google Connections
google/accounts · Action
Manage the user's Google account connections for calendar, email read, and email send. Lists which accounts are connected and for which purposes (calendar, email read, email send), provides OAuth links to connect new permissions, and can disconnect specific accounts/purposes. Use this when the user wants to connect or manage their Google accounts.
| Field | Type | Details | |
|---|---|---|---|
| What to do with Google account connections | string | Required | choices: List accounts with purposes and get connect links, Disconnect an account or specific purpose |
| Email (for disconnect) | string | user@example.com | |
| Purpose to disconnect (calendar, email_read, email_send) — empty removes all | string | choices: Calendar access, Email read access, Email send access |
Returns: tool_result, accounts, auth_urls, success, error
03Notes & Limitations
Behaviours and constraints worth knowing before you build with these nodes.
- Disconnecting an account without choosing a purpose removes every connected purpose (calendar, email read and email send) for that account at once, so specify a purpose when you only mean to revoke one.
- Each purpose is authorised separately, so an account already connected for calendar still needs its own connect step before it can read or send email.
- New connections are finished by opening the OAuth link this node returns and granting access in the browser; the node surfaces and revokes permissions but cannot complete a sign-in on its own.