To build flows to and from Google Contacts, start by creating an HTTP connection.
Note: Your exports and imports must also be built with the same adapter type.
To set up your connection, you will need authentication information from the app’s API guide:
- Base URI
- Relative URI
- Type of scopes
- Refresh token
- Refresh token path
A. Set up a Google Contacts connection
Start establishing a connection to Google Contacts in either of the following ways:
- From the Resources menu, select Connections. Then, click + Create connection at the top right.
– or –
- While working in a new or existing integration, you can add an application to a flow simply by clicking Add source or Add destination/lookup.
In the resulting Application list, select HTTP.
The Create connection pane opens with required and advanced settings.
B. Supply required Google Contacts account information
At this point, you’re presented with a series of options for providing Google Contacts authentication.
Name (required): Provide a clear and distinguishable name. Throughout integrator.io imports and exports, you will have the option to choose this new connection, and a unique identifier will prove helpful later when selecting among a list of connections that you’ve created.
Application (required, non-editable): A reminder of the app you’re editing.
Mode (required): Select one of the following options:
- Cloud to connect to a publicly accessible server application
- On-premise to connect to a server that is publicly inaccessible and has integrator.io agent installed on it
Agent (required, if On-premise selected for Mode; otherwise not displayed): Select an agent from the list. To connect to an on-premise application, integrator.io requires that an agent be installed on a networked computer. An agent is a small application that allows you to connect to data behind your firewall. When installing an agent, you will specify a unique access token, which then populates the Agent drop-down list. The installed agents connect to integrator.io and establish a reverse SSH tunnel, allowing secure communication without the need to whitelist integrator.io IP addresses in your firewall settings. A single agent can be used by multiple different connections.
Expand the Application details section of the Create connection page and enter the Base URI and the Media type.
Base URI (required): Enter
Media type (required): Select JSON from the drop-down menu.
Expand the Configure auth section and enter the following configuration settings.
Authentication type (required): Select Token.
Token (required): Paste the token. You can use the following steps to retrieve your token.
- Go to Google Playground.
- On the left, under Step 1: Select & authorize APIs, click the down arrow next to your app’s API.
- Choose your scopes. Note: Scopes are the type of access you want authorization for. You can find out more about each scope in your API guide.
- In the left panel, click Exchange authorization code for tokens.
- At the bottom right, in the code next to access_token, copy the string of characters. Note: Only copy the characters, not the quotation marks or comma.
- At the bottom, in the code next to refresh_token, copy the string of characters. (Copy only the characters, not the quotation marks or comma.)
How to send token?
Location (required): Select Header.
Header name (required): Select Authorization.
Scheme (required) Select Bearer.
Configure token refresh (required): Check this box to enable token refresh.
How to refresh token?
Refresh token (required): Enter the refresh token. See Google's Authorization documentation for information on retrieving the refresh token.
Refresh relative URI (required): Enter the relative URI to retrieve the token.
Refresh media type (required): Select JSON.
Refresh method (required): Select GET.
Refresh token path (required): Enter the refresh token path.
C. Test the connection
Once you have configured the Google Drive connection, you have a couple options for continuing:
- Save & authorize – click this button to test the connection, commit the new connection so that it will be available to all integrations for your account (and applied to the current source or destination app, if you created it within a flow)
- Cancel – click to exit without saving any new changes