Core

Connectors

Connectors expose the API operations of the third party services that you will be integrating with Tray.

If you were building an integration between Salesforce and Slack, you would need both Salesforce and Slack connectors. You will use the relevant operations on both connectors to build the integration.

What's a service inside the connector object?

A Tray connector essentially exposes underlying third party APIs (ex. a Salesforce connector has a corresponding Salesforce service in Tray). The service object contains the details about the service attached to the connector.

Different versions of the connectors may use different service versions. As third party services update their APIs, new service and it's associated connector is added to Tray.

Tray regularly deprecates services and the connectors that use those services regularly. Unless you specififcally want to use the old APIs of a third party service, you should go with the latest service and the latest connector version associated to it.

List Connectors

This endpoint is non-billable.

Returns a list with all the available connectors from Tray's connector library.

A connector can have multiple versions. the following key data is returned:

Call Connector

This endpoint is billable. Every call to this endpoint is billed as one task.

Executes an operation of a connector and returns the result as the response.

  • The input is a regular json object that must fit the input schema of the operation as retrieved from Get connector operations.

  • The authId field should be the id of a previously created authentication. The output is also a regular json object containing the response from the 3rd party.

  • The outcome field indicates whether or not the execution was successful.

Note:

List Connector Operations

This endpoint is non-billable.

Returns a list with all the available operations for a given connector

Each connector operation has an input and output schema that can be used by a frontend to build a form or validate data.

You can then use the schema to correctly construct your inputs for the 'Call connector' operation.

Was this page helpful?