Dreamdata ACTION
Send Batch
Submit a raw batch of Dreamdata analytics events (
identify, track, page, group, alias) to Dreamdata's ingestion API. Use this when you need full control over event shape. See the documentation.- Action
- Writes data
- API key
- SDK
- MCP
IMPLEMENTATION
Call this tool
Connect a user's Dreamdata account once, then configure and run Send Batch 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: "dreamdata-send-batch",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
dreamdata: { authProvisionId: "apn_xxxxxxx" },
events: ["Events"],
sentAt: "Sent At",
},
})
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": "dreamdata-send-batch",
"configured_props": {
"dreamdata": { "authProvisionId": "apn_xxxxxxx" },
"events": ["Events"],
"sentAt": "Sent At"
}
}'// 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": "dreamdata",
},
},
},
)
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: "dreamdata-send-batch",
arguments: {
events: ["Events"],
sentAt: "Sent At",
},
})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 |
|---|---|---|
events Events | string[] | Array of event objects. Example entry: { "type": "track", "event": "Signed Up", "userId": "usr_123", "properties": { "plan": "Pro" } }. Each entry must include type; most event types require either userId or anonymousId. Missing messageId and timestamp values are generated automatically. Max payload size is 500 KB per request. Required |
sentAt Sent At | string | ISO-8601 timestamp when the batch was sent. Example: 2026-05-27T15:04:05Z. Defaults to the current time if omitted. Optional |
messageId Message ID | string | A unique identifier for this message. Defaults to a generated UUID if omitted. Use a deterministic value to make calls idempotent. Example: msg_order_2026_05_27_0001. 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
- dreamdata-send-batch
- Version
- 0.0.2
- App
- Dreamdata
- Authentication
- API key
- Read-only
- No
- Destructive
- No
- Open world
- Yes
- Source
- View on GitHub ↗