> For the complete documentation index, see [llms.txt](https://docs.stackai.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stackai.com/integrations/catalog/tray.io.md).

# Tray.io

Tray.io is a low-code automation and integration platform. Trigger Tray workflows via their webhook trigger URLs, or use a master-token connection to list end users, solutions and solution instances, and to provision or toggle automations for your end users.

## Connectors

Choose the connector that matches your authentication method. The options below use the names shown in StackAI.

| Connector              | Authentication |
| ---------------------- | -------------- |
| Tray.io (Master Token) | Credentials    |

### Tray.io (Master Token)

Connect to Tray Embedded with an org-wide master token to list end users, solutions and solution instances, and to provision or toggle automations for your end users.

#### Set up in Tray.io

1. Prepare the Tray.io account or service that the workflow will access. Grant access to the required resources and operations.
2. **Master Token:** A Tray Embedded master token, minted by an Embedded admin or owner under Settings > Tokens. It reaches every end user and solution instance in the org, so create a dedicated token for StackAI rather than reusing one shared with another system.

#### Set up in StackAI

1. Open **Settings → Connections**, add a connection, and select **Tray.io (Master Token)**.
2. Enter the credentials and connection details in the fields below.
3. Save the connection and check its connection status. Select this saved connection when configuring an action or feature that uses it.

**Connection fields**

| StackAI field | Required                 | What to enter                                                                                                                                                                                                                                                                                                                                                              |
| ------------- | ------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Master Token  | Yes                      | A Tray Embedded master token, minted by an Embedded admin or owner under Settings > Tokens. It reaches every end user and solution instance in the org, so create a dedicated token for StackAI rather than reusing one shared with another system. [Provider instructions](https://tray.ai/documentation/developer/getting-started/prerequisites/master-and-user-tokens). |
| Region        | Optional / as applicable | The AWS region this Tray Embedded org runs in: 'us', 'eu', or 'ap'. Must match where the master token was minted, or every call fails as unauthorized.                                                                                                                                                                                                                     |

### Verify the connection

Check that the connection is healthy. Then run a read operation against a resource the connected account can access. A successful connection check confirms authentication; it does not guarantee permission for every action.

If access is denied, check the credential or OAuth permissions, the selected account or environment, and access to the specific resource. Update expired credentials or reconnect after permissions change.

## Use an action

1. Add the required **Tray.io** action to the workflow.
2. Select a connection when the action requests one.
3. Complete the required fields. Use the reference picker when a value comes from another workflow step.
4. Run the workflow and inspect the action’s output. Check the result before using it in a later step.

## Actions

### Trigger Workflow

Trigger a Tray.io workflow by sending a JSON payload to its webhook URL.

#### Inputs

| Field       | Type   | Required | Description                                                                                                                          |
| ----------- | ------ | -------- | ------------------------------------------------------------------------------------------------------------------------------------ |
| Webhook URL | secret | Yes      | The workflow's public trigger URL. In Tray, open the workflow's webhook trigger menu and select 'Copy public URL'.                   |
| CSRF Token  | secret | No       | Only needed if the workflow's webhook trigger has a CSRF token configured in its advanced settings. Sent as the X-CSRF-TOKEN header. |
| Body        | object | No       | JSON payload sent to the workflow as the trigger event body.                                                                         |

#### Outputs

| Field         | Type   | Description                                             |
| ------------- | ------ | ------------------------------------------------------- |
| Status Code   | number | HTTP status code returned by the Tray.io webhook.       |
| Response      | object | Response parsed as JSON, when the webhook returns JSON. |
| Response Text | string | Raw response body returned by the webhook, if any.      |

### Trigger Workflow and Await Response

Trigger a Tray.io workflow and wait for its reply, up to 30 seconds. The workflow's trigger must use 'Await workflow and respond'.

#### Inputs

| Field             | Type    | Required | Description                                                                                                                                                                    |
| ----------------- | ------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Webhook URL       | secret  | Yes      | The workflow's public trigger URL. The workflow's webhook trigger must use the 'Await workflow and respond' operation and end with a Trigger Event Reply step.                 |
| CSRF Token        | secret  | No       | Only needed if the workflow's webhook trigger has a CSRF token configured in its advanced settings. Sent as the X-CSRF-TOKEN header.                                           |
| Body              | object  | No       | JSON payload sent to the workflow as the trigger event body.                                                                                                                   |
| Timeout (seconds) | integer | No       | How long to wait for the workflow's reply before failing. Use the fire-and-forget Trigger Workflow action for workflows that run longer. Minimum: 1. Maximum: 30. Default: 15. |

#### Outputs

| Field         | Type   | Description                                                      |
| ------------- | ------ | ---------------------------------------------------------------- |
| Status Code   | number | HTTP status code set by the workflow's Trigger Event Reply step. |
| Response      | object | Workflow reply parsed as JSON, when the reply is JSON.           |
| Response Text | string | Raw reply body returned by the workflow, if any.                 |

### List Workflows

List the Tray Embedded workflows your end users have set up, with the trigger URL of each workflow that has a public trigger.

#### Inputs

| Field           | Type            | Required | Description                                                                                      |
| --------------- | --------------- | -------- | ------------------------------------------------------------------------------------------------ |
| End user        | select (string) | No       | Only show items owned by this Tray Embedded end user. Options load from the selected connection. |
| Solution        | select (string) | No       | Only show instances of this solution. Options load from the selected connection.                 |
| Maximum results | integer         | No       | How many results to return at most.                                                              |
| Continue from   | string          | No       | Paste the next\_cursor from a previous run to continue where it stopped.                         |

#### Outputs

| Field       | Type          | Description                 |
| ----------- | ------------- | --------------------------- |
| Workflows   | object\_array | The workflows found.        |
| Next cursor | string        | Pass this back to see more. |

### Enable or Disable Solution Instance

Turn an end user's Tray automation on or off.

#### Inputs

| Field             | Type            | Required | Description                                                                  |
| ----------------- | --------------- | -------- | ---------------------------------------------------------------------------- |
| Solution instance | select (string) | Yes      | The automation to turn on or off. Options load from the selected connection. |
| Enabled           | boolean         | Yes      | On to enable the automation, off to disable it. Default: true.               |

#### Outputs

| Field                | Type    | Description               |
| -------------------- | ------- | ------------------------- |
| Solution instance id | string  | The instance.             |
| Name                 | string  | Instance name.            |
| Enabled              | boolean | State after the call.     |
| Changed              | boolean | Whether anything changed. |

### Create Solution Instance

Set up one of your Tray solutions for an end user.

#### Inputs

| Field         | Type            | Required | Description                                                                            |
| ------------- | --------------- | -------- | -------------------------------------------------------------------------------------- |
| End user      | select (string) | Yes      | The end user who will own the new instance. Options load from the selected connection. |
| Solution      | select (string) | Yes      | The solution to set up. Options load from the selected connection.                     |
| Instance name | string          | Yes      | A name for this end user's copy of the solution.                                       |

#### Outputs

| Field                | Type          | Description                                                         |
| -------------------- | ------------- | ------------------------------------------------------------------- |
| Solution instance id | string        | The new instance.                                                   |
| Name                 | string        | Instance name.                                                      |
| Enabled              | boolean       | Whether it is on.                                                   |
| Already existed      | boolean       | True when a matching instance was returned instead of creating one. |
| Workflows            | object\_array | The instance's workflows.                                           |

### List Solutions

List the Tray Embedded solutions you offer to end users.

#### Inputs

| Field           | Type    | Required | Description                                                              |
| --------------- | ------- | -------- | ------------------------------------------------------------------------ |
| Maximum results | integer | No       | How many results to return at most.                                      |
| Continue from   | string  | No       | Paste the next\_cursor from a previous run to continue where it stopped. |

#### Outputs

| Field       | Type          | Description                 |
| ----------- | ------------- | --------------------------- |
| Solutions   | object\_array | The solutions.              |
| Next cursor | string        | Pass this back to see more. |

### List End Users

List the end users in your Tray Embedded account.

#### Inputs

| Field            | Type    | Required | Description                                                              |
| ---------------- | ------- | -------- | ------------------------------------------------------------------------ |
| External user id | string  | No       | Find the end user with this id from your own system.                     |
| Maximum results  | integer | No       | How many results to return at most.                                      |
| Continue from    | string  | No       | Paste the next\_cursor from a previous run to continue where it stopped. |

#### Outputs

| Field       | Type          | Description                 |
| ----------- | ------------- | --------------------------- |
| End users   | object\_array | The end users.              |
| Next cursor | string        | Pass this back to see more. |

## Important behavior

Actions that create, update, send, or delete data can change the connected service. Review their inputs before running them. A retry can repeat an operation; consider this when configuring retries for actions that change data.

The catalog lists the fields and capabilities available in the supplied provider definition. Availability can also depend on your deployment and organization’s Feature Access settings.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.stackai.com/integrations/catalog/tray.io.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
