Skip to main content
Flowmatic’s Google integration lets you authorize access to your Google account so you can use files stored in Google Drive as data sources inside your automation workflows. Rather than manually exporting and re-uploading spreadsheets, a connected Google account lets Flowmatic read Drive files directly — keeping your workflows in sync with the latest version of your data. This guide explains how to check your connection status and complete the OAuth authorization flow.

​
What the integration enables

Once your Google account is connected, Flowmatic can access Google Drive on your behalf. This means you can reference Drive-hosted spreadsheets as DATA_SOURCE inputs in your workflow graphs, eliminating the manual CSV-export-and-upload step you would otherwise need every time your data changes.
The Google integration uses the standard OAuth 2.0 authorization code flow. Flowmatic requests only the scopes it needs to read your Drive files — it does not request write access or access to other Google services such as Gmail or Calendar.

​
Checking your connection status

Before kicking off the OAuth flow, check whether your Google account is already connected. Send a GET request to the status endpoint:

​
Possible responses

If no Google account has been linked yet, the response is:
If an account is already connected, the response includes the email address of the linked Google account:
The email field lets you confirm which Google account is linked — useful if you manage multiple accounts or are onboarding a team member who may have connected the wrong account.

​
Connecting your Google account

1

Initiate the OAuth flow

To start the authorization process, you need to open the connect endpoint in a web browser. This endpoint responds with an HTTP 302 redirect to Google’s OAuth consent screen.The URL to open is:
You can construct a quick link with your access token by visiting the URL while logged into the Flowmatic web application, or by pasting the following into your browser’s address bar (substituting your actual token):
The connect endpoint must be opened in a browser, not called with curl or any other non-browser HTTP client. The endpoint issues an HTTP 302 redirect to Google’s OAuth consent page, which requires a full browser session to complete the interactive authorization steps. Calling it with curl will only return the redirect response without navigating to Google.
2

Authorize Flowmatic on the Google consent screen

After the redirect, Google displays its standard OAuth consent screen. You will see:
  • The name of the application requesting access (“Flowmatic”)
  • The specific Drive scopes being requested (read access to your files)
  • The Google account you are currently signed in with
Review the requested permissions and click Allow to grant Flowmatic access. If you want to use a different Google account than the one currently signed in, click Switch account before proceeding.
3

Return to Flowmatic

After you approve the request, Google redirects your browser back to Flowmatic with an authorization code. Flowmatic exchanges this code for long-lived access and refresh tokens, which are stored securely on the server and associated with your Flowmatic account.You will land back on the Flowmatic dashboard (or integration settings page, depending on where you initiated the flow) with a confirmation that your Google account has been linked.
4

Verify the connection

Confirm the integration is active by calling the status endpoint again:
You should now see a connected: true response with your Google account email:
Your Google account is now linked and ready to use as a data source in your workflows.

​
Status response field reference

​
What happens after connecting

Once connected, Flowmatic stores OAuth tokens on the server associated with your Flowmatic user account. You do not need to re-authorize on each workflow run — Flowmatic automatically refreshes the access token as needed using the stored refresh token. If you ever revoke Flowmatic’s access from your Google Account permissions page, the stored tokens will become invalid and the status endpoint will return { "connected": false }. You would need to go through the connect flow again to restore access.
If you see { "connected": false } unexpectedly after previously linking your account, it likely means the OAuth token was revoked or expired. Re-visit the connect URL in your browser to re-authorize. No workflow definitions are affected — only the ability to fetch data from Drive during a run is impacted until you reconnect.