Heroku icon

CONNECT APP

Build with Heroku

Cloud infrastructure

Infrastructure & Cloud

  • OAuth

MCP

Give your agent Heroku tools

Every Heroku action is exposed as an MCP tool on Pipedream's remote server. Point a client at it with your end user's ID and Connect resolves that user's Heroku account for each tool call — you store no tokens.

// accessToken: mint a short-lived token with the Connect SDK — see the MCP guide
const transport = new StreamableHTTPClientTransport(
  new URL("https://remote.mcp.pipedream.net/v3"),
  {
    requestInit: {
      headers: {
        Authorization: `Bearer ${accessToken}`,
        "x-pd-project-id": "{project_id}",
        "x-pd-environment": "production",
        "x-pd-external-user-id": "{external_user_id}", // any stable ID for this user in your system
        "x-pd-app-slug": "heroku",
      },
    },
  },
)

const mcp = new Client({ name: "my-agent", version: "1.0.0" })
await mcp.connect(transport)

const { tools } = await mcp.listTools()

// e.g. run List App ID Options:
const result = await mcp.callTool({
  name: "heroku-list-app-id-options",
  arguments: {},
})

API PROXY

Call the Heroku API directly

For an endpoint with no pre-built tool, the Connect proxy forwards your request to the Heroku API with the connected user's credentials attached. You store no tokens and write no refresh logic.

const resp = await pd.proxy.get({
  externalUserId: "{external_user_id}", // any stable ID for this user in your system
  accountId: "apn_xxxxxxx",
  url: "https://api.heroku.com/account",
})

// Any allowed Heroku endpoint works here. Pipedream attaches the
// connected account's credentials to the outgoing request.

SDK

Run Heroku actions from your backend

Connect a user's Heroku account once, then run List App ID Options on their behalf from your own code — TypeScript, Python, or plain HTTP.

import { PipedreamClient } from "@pipedream/sdk"

const pd = new PipedreamClient({
  projectId: process.env.PIPEDREAM_PROJECT_ID!,
  clientId: process.env.PIPEDREAM_CLIENT_ID!,
  clientSecret: process.env.PIPEDREAM_CLIENT_SECRET!,
  projectEnvironment: "production",
})

const result = await pd.actions.run({
  id: "heroku-list-app-id-options",
  externalUserId: "{external_user_id}", // any stable ID for this user in your system
  configuredProps: {
    heroku: { authProvisionId: "apn_xxxxxxx" },
  },
})

TOOLS

Heroku actions

On-demand operations your product or agent can configure and run on behalf of a connected user.

MULTI-APP

Use Heroku with other popular apps

Most products don't stop at one integration. Pair Heroku with the other apps your users rely on, and ship use cases that span both.

REFERENCE

App details

Reference metadata for the Heroku connector in the Pipedream registry.

App slug
heroku
Authentication
OAuth
Categories
Infrastructure & Cloud
Actions
1
Triggers
1
API proxy
Available

OAuth scopes

These are the scopes Pipedream's managed Heroku OAuth client requests when one of your users connects an account. Supply your own OAuth client to request a different set.

  • global