Skip to content
Cloud 66 logo

Connectors / Developer tools · HTTP Connector

Automate Cloud 66 with Tray.ai

Create a stack, add an environment variable and create a backup in Cloud 66, and start a workflow when Cloud 66 sends “Application update started”.

Great — a couple more details

This helps us connect you with the right person. Optional, and you can skip it.

See all connectors

What can you do with Cloud 66 on Tray.ai?

Cloud 66 is a deployment platform that builds, deploys and scales web applications and databases on servers in your own cloud account or data center. Tray.ai connects to Cloud 66 through the HTTP Connector, so your workflows can call the Cloud 66 API alongside the rest of your stack.

  • When Cloud 66 sends “Application update failed”, page the on-call engineer.
  • When Cloud 66 sends “Managed backup failure”, open an incident in your incident management tool.
  • Post to the engineering channel in your team chat when Cloud 66 sends “Application update succeeded”.
  • Redeploy a stack in Cloud 66 when a release is approved in your change management process.
Connects through
HTTP Connector
Authentication
OAuth 2.0 or a bearer token

Set it up

Connect Cloud 66 to Tray.ai

Each step uses Cloud 66's own API details, from its documentation.

Step 1

Sign in to Cloud 66 with OAuth 2.0

Set up an OAuth 2.0 authentication with the client ID and secret of an OAuth app you register with Cloud 66. Sign in once and every step reads the token from there.

Step 2

Import a request from Cloud 66's docs

Add an HTTP Client step and paste a cURL example from Cloud 66's API docs. Tray.ai fills in the method, URL, headers, and query.

Step 3

Start with “List stacks”

It's one of 19 documented actions, under Stacks. The response comes back as data the next step can map into your other apps.

Step 4

Start workflows from Cloud 66 events

Give Cloud 66 the URL of a Tray.ai webhook trigger. “Application update started” can then start a workflow, and so can 6 other events.

What the Cloud 66 API covers

5 resources and 19 documented actions, each one a call the HTTP Connector can make from a Tray.ai workflow. Connecting it takes a few clicks: here's how.

Stacks

  • List stacks
  • Get a stack
  • Create a stack
  • Run a stack action
  • Reboot stack servers

Deployments

  • List deployments
  • Get a deployment
  • Redeploy a stack

Servers

  • List servers
  • Get a server
  • Reboot a server

Environment variables

  • List environment variables
  • Add an environment variable
  • Update an environment variable
  • Delete an environment variable

Backups

  • List backups
  • Get a backup
  • Create a backup
  • Get a backup file

Events Cloud 66 can send to a Tray.ai webhook trigger

  • Application update started
  • Application update succeeded
  • Application update failed
  • Application health check failed
  • Server stopped
  • Server back online
  • Managed backup failure

Checked against Cloud 66's own documentation on 2026-10-22

developers.cloud66.com/v3

Frequently asked questions

What can a Tray.ai workflow do in Cloud 66?

+

The Cloud 66 API documents 19 actions across 5 resources (Stacks, Deployments, Servers, Environment variables, Backups). For example: List stacks; List deployments; List servers. A workflow can make any documented call through the HTTP Connector.

How does Tray.ai authenticate with Cloud 66?

+

The Cloud 66 API uses OAuth 2.0 and a bearer token. You save it once as a Tray.ai authentication, and the HTTP Connector adds it to every request.

Which Cloud 66 events can start a Tray.ai workflow?

+

Cloud 66 sends 7 events to a webhook URL, for example: Application update started; Application update succeeded; Application update failed; Application health check failed; Server stopped; Server back online; Managed backup failure. A Tray.ai webhook trigger receives them and starts a workflow.

See Cloud 66 working against your stack.

We'll walk through a tailored demo with your systems plugged in.

Great — a couple more details

This helps us connect you with the right person. Optional, and you can skip it.