Developer & CI · wired today
Tray.io, wired into your agent workforce
Build, review and release state is where agents earn their keep. The Tray.io connector is one of 205 executable connectors and gives agents 6 read-only tools, with the credential held in the vault and every call receipted.
Connecting Tray.io takes one credential
You provide access token from your Tray.io account; Quox sends it as a bearer token. The credential is stored encrypted in the vault and resolved just-in-time, so agents use it without ever seeing it.
Where to get it: Tray.io's own API documentation ↗ covers creating and scoping the credential.
What agents can run against Tray.io
get_current_userGet the Tray.io account the access token belongs to (who am I)
get_viewerGet the Tray.io viewer (the GraphQL identity behind the token) with its name and email
list_workflowsList Tray.io workflows visible to the token (id, title, enabled state, creation time)
list_solutionsList Tray.io solutions (the reusable templates customer instances are created from)
list_solution_instancesList Tray.io solution instances (per-customer deployments of a solution) with their enabled state
list_authenticationsList the Tray.io authentications (stored third-party service credentials) the token can see, by service
Every tool above is read-only. Write surfaces ship only after live testing, and always behind approval gates.
How proven is this?
This connector was blind shape-proven against the real Tray.io API: every endpoint it declares answered measurably differently from a deliberately bogus control request, without any account or credential involved. It is Beta: proven against the live API surface, not yet run with a real credential.
Tray.io integration FAQ
What can Quox agents do with Tray.io?
Agents can run 6 read-only tools against Tray.io: get current user, get viewer, list workflows, list solutions, list solution instances and more. Every call is receipted in the evidence trail.
What does the Tray.io integration need?
You provide access token from your Tray.io account; Quox sends it as a bearer token. The credential is stored encrypted in the vault and resolved just-in-time, so agents use it without ever seeing it.
Do agents see my Tray.io credentials?
No. Credentials live encrypted in the Quox vault and are resolved server-side at call time. Agents invoke tools; they never receive the underlying secret.
How proven is the Tray.io connector?
This connector was blind shape-proven against the real Tray.io API: every endpoint it declares answered measurably differently from a deliberately bogus control request, without any account or credential involved. It is Beta: proven against the live API surface, not yet run with a real credential.