CONNECT APP
Build with Better Stack
Web & App Development
- API key
MCP
Give your agent Better Stack tools
Every Better Stack 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 Better Stack 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": "better_stack",
},
},
},
)
const mcp = new Client({ name: "my-agent", version: "1.0.0" })
await mcp.connect(transport)
const { tools } = await mcp.listTools()
// e.g. run Acknowledge Incident:
const result = await mcp.callTool({
name: "better_stack-acknowledge-incident",
arguments: {
incidentId: "Incident ID",
acknowledgedBy: "Acknowledged By",
},
})# access_token: mint a short-lived token with the Connect SDK — see the MCP guide
headers = {
"Authorization": f"Bearer {access_token}",
"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": "better_stack",
}
async with streamablehttp_client("https://remote.mcp.pipedream.net/v3", headers=headers) as (read, write, _):
async with ClientSession(read, write) as session:
await session.initialize()
tools = await session.list_tools()
# e.g. run Acknowledge Incident:
result = await session.call_tool("better_stack-acknowledge-incident", {
"incidentId": "Incident ID",
"acknowledgedBy": "Acknowledged By",
})API PROXY
Call the Better Stack API directly
For an endpoint with no pre-built tool, the Connect proxy forwards your request to the Better Stack 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://uptime.betterstack.com/api/v2/monitors",
})
// Any allowed Better Stack endpoint works here. Pipedream attaches the
// connected account's credentials to the outgoing request.# The path segment is the target URL, URL-safe base64 encoded:
# https://uptime.betterstack.com/api/v2/monitors
curl "https://api.pipedream.com/v1/connect/{project_id}/proxy/aHR0cHM6Ly91cHRpbWUuYmV0dGVyc3RhY2suY29tL2FwaS92Mi9tb25pdG9ycw?external_user_id={external_user_id}&account_id=apn_xxxxxxx" \
-H "Authorization: Bearer {access_token}" \
-H "x-pd-environment: production"SDK
Run Better Stack actions from your backend
Connect a user's Better Stack account once, then run Acknowledge Incident 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: "better_stack-acknowledge-incident",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
better_stack: { authProvisionId: "apn_xxxxxxx" },
incidentId: "Incident ID",
acknowledgedBy: "Acknowledged By",
},
})from pipedream import Pipedream
pd = Pipedream(
client_id="{oauth_client_id}",
client_secret="{oauth_client_secret}",
project_id="{project_id}",
project_environment="production",
)
result = pd.actions.run(
id="better_stack-acknowledge-incident",
external_user_id="{external_user_id}", # any stable ID for this user in your system
configured_props={
"better_stack": {"authProvisionId": "apn_xxxxxxx"},
"incidentId": "Incident ID",
"acknowledgedBy": "Acknowledged By",
},
)curl -X POST https://api.pipedream.com/v1/connect/{project_id}/actions/run \
-H "Content-Type: application/json" \
-H "X-PD-Environment: production" \
-H "Authorization: Bearer {access_token}" \
-d '{
"external_user_id": "{external_user_id}",
"id": "better_stack-acknowledge-incident",
"configured_props": {
"better_stack": { "authProvisionId": "apn_xxxxxxx" },
"incidentId": "Incident ID",
"acknowledgedBy": "Acknowledged By"
}
}'TOOLS
Better Stack actions
On-demand operations your product or agent can configure and run on behalf of a connected user.
-
Acknowledge Incident
actionAcknowledges an incident, marking it as acknowledged in Better Stack. See the documentationWritev0.0.2 -
Create Incident
actionInitiates an incident that signals the team. See the documentationWritev0.0.2 -
Resolve Incident
actionBrings a closure to an incident by resolving it with optional resolution details. See the documentationWritev0.0.2
EVENTS
Better Stack triggers
Event sources your backend can deploy for users and receive through a webhook.
No Better Stack triggers are available yet.
MULTI-APP
Use Better Stack with other popular apps
Most products don't stop at one integration. Pair Better Stack with the other apps your users rely on, and ship use cases that span both.
- App slug
- better_stack
- Authentication
- API key
- Categories
- Web & App Development
- Actions
- 3
- Triggers
- 0
- API proxy
- Available