Skip to main content

Connect services with OAuth 2.0

Connect a service that uses OAuth 2.0 once, then choose that connection in Send API request so your automation can call the service with your sign-in.

Written by Leo

An OAuth 2.0 connection is a saved sign-in to another service (you approve access once, and Tape then signs requests for you without storing your password in the automation). Connections are meant to help you call services that don't accept a plain request, such as a calendar or a customer database.

You can use connections for many things, including:

  • Creating an event in a calendar when a showing is booked.

  • Updating a contact in another customer system when a lead changes.

The action Send an API request in a new automation for Expenses, with Choose a connection open, showing No connection found and Add connection

Note:

  • A connection is saved for your whole organization. You can choose the same connection in any Send API request action.

  • Without a connection, Tape skips the step. The step doesn't fail, but no request is sent.

  • Only public services can be reached. Tape blocks requests to private or internal addresses.

Who can use connections?

  • Automations are available on all plans: Free, Plus, and Premium. The number of automation actions per month depends on your plan. See the limits for your plan on our pricing page.

  • Only organization admins can add, verify, edit, or delete OAuth 2.0 connections, and choose a connection in Send API request.

  • A connection is shared across your organization, so any automation can use it once an organization admin has set it up.

Add the Send API request action

To call a service with a connection:

  1. Open the app and click the automations icon at the top right (Create and view automations).

  2. Open an automation, or select New automation and choose a trigger.

  3. Select Add action → Send API request.

  4. Select the method (GET, POST, PUT, PATCH, or DELETE), then enter the URL.

  5. Open Choose a connection and select a connection, or select Add connection to set up a new one.

  6. Add the data you send in Request. Select Show headers → Add header for headers.

  7. Select Save changes.

In a new automation for Expenses, selecting Add action and Send API request, changing GET to POST, typing <a href="https://api.acme.com/notes" rel="nofollow noopener noreferrer" target="_blank">https://api.acme.com/notes</a> in URL, then opening Choose a connection with No connection found and Add connection
The action Send an API request using GET method and save response in API response, with Connection, URL, and Request

The answer is saved in a variable called API response. Use it in later actions with @. Learn more about record values and variables →

Set up a connection

Any service that supports OAuth 2.0 works. To set up a connection:

  1. In Send API request, open Choose a connection and select Add connection.

  2. Enter a Connection name.

  3. Enter the Client ID, Client secret, Authorize URL, and Token URL from the service's API documentation.

  4. Add Scopes (optional) and Resource owner details URL (optional) if the service needs them. Without a resource owner details URL, you can't verify the connection later.

  5. Select Save connection and approve access at the service.

The connection form of an API request action with the name Acme accounting, Client ID, Client secret, Authorize URL, Token URL, Scopes (optional), Resource owner details URL (optional), and Save connection

Each connection in the list shows Active or Broken. Select ••• next to a connection to Verify, Reauthorize, Edit, or Delete it. Verify is only available if the connection has a Resource owner details URL (optional).

Send API request settings

  • Connection: the sign-in that Tape uses to sign the request.

  • Method: GET, POST, PUT, PATCH, or DELETE.

  • URL: the address of the service. You can add record values with @.

  • Request: the body of the request. It's empty if you leave it out.

  • Show headers: opens a list of headers. Select Add header and fill in Header and Value. Select Hide headers to close the list.

  • Action menu: Follow redirects follows 3xx answers (off by default), and Continue on error lets the run go on if the request fails.

Let's look at an example

Let's say your sales team keeps contacts in a customer system that uses OAuth 2.0. Here's how to add a note when a lead is won:

  1. Set the trigger to When a record is updated and add a filter so the automation only runs when Status is Won.

  2. Select Add action → Send API request and choose POST.

  3. Enter the address of the notes endpoint of your customer system in URL.

  4. Select your connection under Connection.

  5. In Request, enter the note and insert the lead's name with @.

  6. Select Save changes.

When a lead is won, the note appears in the customer system.

OAuth 2.0 connection errors

  • The connection expired or was removed. The service no longer accepts the saved sign-in, and requests fail. A connection that no longer works shows Broken. Open Choose a connection, select ••• next to it, then Reauthorize.

  • The request is rejected with a permission error. The connection may not have the permission the service needs. Select ••• next to the connection, then Edit, change the Scopes (optional), and select Save connection. Then reauthorize the connection.

  • The request never leaves Tape. The address may point to a private network. Tape only calls public services.

  • The service blocks the request. Add the IP addresses of Tape to the allowed list of the service. Learn more about IP addresses →

Test, pause, or edit a connection

  • Use Manual run to send a real request once, to check the setup.

  • To change the connection of an action, open the automation, select the Send API request step, choose another connection, then select Save changes.

  • To remove a connection, open Choose a connection, select ••• next to it, then Delete. Automations that use it become Broken.

Learn more

FAQs

What's the difference between Send HTTP request and Send API request?

Send HTTP request sends exactly what you enter. Send API request also signs the request with a connection, so you use it for services that need OAuth 2.0.

Can I use one connection in several automations?

Yes! Connections are shared across your organization, so you can use one connection in many automations.

Can I create a connection with the API?

No. In the automation API, you can only reference a connection that an organization admin already set up in Tape.

Why does my request fail after a few weeks?

The connection may have expired. If it shows Broken, select ••• next to it, then Reauthorize.

Can I use my own API key instead of a connection?

Yes. Add the key as a header in Send HTTP request. Anyone who can edit the automation can read the key, so use a key with limited access.

Are you a developer using the Tape API for automations?

The automation API has its own documentation for developers. Full reference: authenticated_http_call in the developer docs →

Still have questions? Find answers and get help from community experts in the Tape community →

Did this answer your question?