Integrate with Google

Connect to Google and exchange data between Google services and Next Matter.

Prepare to integrate

Start by integrating a specific Google app in Next Matter.

  1. Set up your Next Matter account

    • Create an account: Sign up for Next Matter and set up your workspace.
  2. Create an account to connect Google services.

🚧

Use a specific Google user (or a service account) to easily control what files and sites Next Matter has access to. Such a user could be called [email protected]. We connect Google apps separately for you to control permissions and access better.
The default connection is read and write however it can be limited on your end.

  1. Connect Google services in Next Matter in Automations library (one-click connection).
    1. In Automations Library [ left-hand navigation panel], click Connect for the integration you want to connect.
    2. In the 3rd party pop-up, select the account you'll use for the integration (the service account). You'll be asked to log in to the 3rd party tool using this account.

      📘

      You can use the same service account to connect all integrations or use separate ones for each.

Check the required scopes to learn more about which data is shared between the apps.

Define account permissions

Tip: Think of the account as a user - anything the account has access to, the user logging in with this account also has access to. The connected user will authenticate Google requests within the scopes that the admin permits for the account. If you deactivate the account the integration stops working.
When the account is authenticated, you can use it with any resource to which the account has access and that is within the permitted scopes.

For example, if you want to use no-code Google Sheet steps, ensure spreadsheets are shared with the account connected to Next Matter. Otherwise, they won't appear in the dropdown.

📘

If you get a 401 error when running a connected integration step, it might mean that the connected account got deactivated or deleted. It might also show when the same account was connected in another environment and then disconnected. This disconnect leads to all workspaces being deauthorized.

Check which account is connected

If you need to check which account has been used to connect the integration, you can do one of the following:

Disconnect the account

You can disconnect an integration in the Automations library.