QStash ACTION
Publish Endpoint Message
Publish a message a callback endpoint
- Action
- Writes data
- API key
- SDK
- MCP
IMPLEMENTATION
Call this tool
Connect a user's QStash account once, then configure and run Publish Endpoint Message from your backend or agent.
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: "qstash-publish-endpoint-message",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
qstash: { authProvisionId: "apn_xxxxxxx" },
endpoint: "Callback Endpoint",
body: "Body",
},
})
console.log(result)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": "qstash-publish-endpoint-message",
"configured_props": {
"qstash": { "authProvisionId": "apn_xxxxxxx" },
"endpoint": "Callback Endpoint",
"body": "Body"
}
}'// 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": "qstash",
},
},
},
)
const mcp = new Client({ name: "my-agent", version: "1.0.0" })
await mcp.connect(transport)
const { tools } = await mcp.listTools()
// listTools() hands your model this tool's input schema, so it can
// fill the arguments itself:
const result = await mcp.callTool({
name: "qstash-publish-endpoint-message",
arguments: {
endpoint: "Callback Endpoint",
body: "Body",
},
})SCHEMA
Inputs
Pipedream supplies the connected account. Your application provides the operation-specific values below. Dynamic inputs are resolved against that user's account.
| Property | Type | Description |
|---|---|---|
endpoint Callback Endpoint | string | The endpoint that will be receiving these events Required |
body Body | object | The body is forwarded to your endpoints in the HTTP request Required |
retries Retries | integer | How often should this messasge be retried in case the destination API is not available. Optional |
deduplicationId Deduplication ID | string | Provide an ID that will be used to detect duplicate messages. If a duplicate message is detected, the request will be accepted but not enqueued. Learn more. Optional |
contentBasedDeduplicationEnabled Content Based Deduplication Enabled | boolean | If true, the message content will get hashed and used as deduplication ID. If a duplicate message is detected, the request will be accepted but not enqueued. Optional |
delay Delay | string | Format for this header is a number followed by duration abbreviation, like 10s. Available durations are s (seconds), m (minutes), h (hours), d (days). Optional |
cron Cron | string | You can use a tool like Crontab.guru to generate cron expressions. Optional |
REFERENCE
Tool details
Behavior hints are published with the component in the Pipedream registry and surface as MCP tool annotations, so an agent can reason about a tool before it calls it.
- Registry key
- qstash-publish-endpoint-message
- Version
- 0.0.2
- App
- QStash
- Authentication
- API key
- Read-only
- No
- Destructive
- No
- Open world
- Yes
- Source
- View on GitHub ↗