.DkNUKaKx_ZLAT4m.webp?dpl=dpl_GGMVkuFGKgbEjJK9RAb8SNPk3QSp){kind=small}
Connectors / Developer tools · HTTP Connector
Automate Heroku with Tray.ai
Create an app, create a build and create a release in Heroku, and start a workflow when Heroku sends “App created”.
What can you do with Heroku on Tray.ai?
Heroku is a cloud platform for deploying and running web apps, where teams manage apps, builds, releases, dynos, add-ons and pipelines. Tray.ai connects to Heroku through the HTTP Connector, so your workflows can call the Heroku API alongside the rest of your stack.
- When Heroku sends “Release created”, post the release to the engineering channel in your team chat.
- When Heroku sends “Build updated”, alert the on-call engineer if the build failed.
- Roll back a release when your monitoring tool raises a critical alert right after a deploy.
- Log the access change for your security team when Heroku sends “Collaborator added”.
- Connects through
- HTTP Connector
- Authentication
- OAuth 2.0 or a bearer token
- Base URL
- https://api.heroku.com
Set it up
Connect Heroku to Tray.ai
Each step uses Heroku's own API details, from its documentation.
Step 1
Sign in to Heroku with OAuth 2.0
Set up an OAuth 2.0 authentication with the client ID and secret of an OAuth app you register with Heroku. Sign in once and every step reads the token from there.
Step 2
Point the HTTP Client at the API
Add an HTTP Client step and use https://api.heroku.com as the base URL. Or paste a cURL example from Heroku's API docs, and Tray.ai fills in the method, URL, and headers.
Step 3
Start with “List apps”
It's one of 23 documented actions, under Apps. The response comes back as data the next step can map into your other apps.
Step 4
Start workflows from Heroku events
Give Heroku the URL of a Tray.ai webhook trigger. “App created” can then start a workflow, and so can 11 other events.
Give your AI agents Heroku tools
Build an MCP server on Heroku in Agent Gateway and choose which actions your agents can call. Every call runs with access control and an audit trail. How Agent Gateway works
- List apps
- List builds
- List releases
- List dynos
- Get app config vars
- List domains
- Get an app
- Create an app
What the Heroku API covers
6 resources and 23 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.
Apps
- List apps
- Get an app
- Create an app
- Update an app
- Delete an app
Builds
- List builds
- Get a build
- Create a build
- Cancel a build
Releases
- List releases
- Get a release
- Create a release
- Roll back a release
Dynos
- List dynos
- Create a dyno
- Restart a dyno
- Stop a dyno
Config vars
- Get app config vars
- Update config vars
Domains
- List domains
- Create a domain
- Update a domain
- Delete a domain
Events Heroku can send to a Tray.ai webhook trigger
- App created
- App updated
- App deleted
- Build created
- Build updated
- Release created
- Release updated
- Dyno created
- Add-on created
- Add-on deleted
- Domain created
- Collaborator added
Checked against Heroku's own documentation on 2026-10-22
How Tray.ai makes this work
Heroku plugs into the whole Tray.ai platform
Intelligent Integration
Integrate and automate across 9,000+ apps, databases, APIs, and services with visual workflows, error handling, and observability.
Learn more →Agent Builder
Build AI agents that read, write, and take action in Heroku — with guardrails, audit, and human-in-the-loop.
Learn more →Agent Gateway for MCP
Expose Heroku actions as governed MCP tools — observable, rate-limited, authenticated.
Learn more →Tray Helix
Build apps on Heroku data with your AI assistant, then deploy, run, and govern them on Tray.ai.
Learn more →More developer tools apps on Tray.ai
Dedicated connectors and other apps Tray.ai reaches in the same category. See every developer tools connector →
Frequently asked questions
What can a Tray.ai workflow do in Heroku?
+
The Heroku API documents 23 actions across 6 resources (Apps, Builds, Releases, Dynos, Config vars, Domains). For example: List apps; List builds; List releases. A workflow can make any documented call through the HTTP Connector.
How does Tray.ai authenticate with Heroku?
+
The Heroku 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 Heroku events can start a Tray.ai workflow?
+
Heroku sends 12 events to a webhook URL, for example: App created; App updated; App deleted; Build created; Build updated; Release created; Release updated; Dyno created. A Tray.ai webhook trigger receives them and starts a workflow.
See Heroku working against your stack.
We'll walk through a tailored demo with your systems plugged in.
Thanks — someone from our team will be in touch soon.