Tray Platform / Using Connectors / Authenticating Connectors

Authenticating Connectors

Just as when you have to log in to gmail, Facebook, Salesforce, LinkedIn, etc., any services you wish to use in your workflows will require an authentication.

There are two ways of creating authentications:

  1. From within a workflow:

  1. From within the Authentications section of the dashboard you can create an authentication for any service:


Authentications can be Personal (used only by you) or Organization (e.g. a company login to be used by anyone in your organization).

Please see the Managing Authentications page for guidance on how to manage authentications within your organization and instructions on creatin auths from the dashboard.

Read on for an overview of the different types of authentication you will come across!

Then you can go to the Service Connectors page to find the specific instructions for the service you need to authenticate.

API token-based authentication

If you are using a service such as Stripe and the API uses simple token-based authentication then a box to enter the API token will be displayed:


OAuth-based authentication

APIs that use OAuth or OAuth2 display a more complex box. From here you can reduce the permission 'scopes'. Be careful - reducing the scopes might prevent the connector from functioning properly (required scopes are described in individual connector docs).


Please take note that every connector authentication window is unique! There are many variables involved that are dependant on the service's own requirements and API calls.

Individual service connector documentation gives more specific details on how to set up a connector's authentication.

Generic Authentications for the HTTP Client

The HTTP Client (Universal Connector) can be used to connect to any service that is not included in our list of connectors.

You can add new services at

To reference a service when creating an authentication with the HTTP Client you can, for example, choose a name for your auth token and then enter the actual token value. This auth token can then be used in your API call (for example, as a parameter) by including the path $.auth.token_name.

Please see the HTTP Client guide for an illustration of how this generic approach works.

Certificate-based Authentication

Tray can also support certificate-based authentications. Please contact us if you need a custom certificate-based authentication built for your service.