Rich events from a self-hosted stack.
Bland transcribes, summarizes, and extracts variables on its own infrastructure, so every webhook your workflow receives already carries the full call.
Bland + Pipedream
Run your own Node.js or Python on every Bland call with signed webhooks, or call a Pipedream workflow mid-conversation and speak the result.
What Bland does inside Pipedream.
Code on every call.
Point a post-call webhook at a Pipedream HTTP trigger and process each call in Node.js or Python steps with the full payload.
Mid-call lookups.
A webhook tool can call a workflow during the conversation and capture JSON paths from its response, so the agent can speak what your code returns.
Verify, then act.
Recompute the HMAC SHA-256 of the body in a code step and compare it with X-Webhook-Signature before anything downstream runs.
Calls from your workflows.
Call Bland's Send Call or batch endpoints from a step to dial a lead, with request_data for context and metadata for matching results.
Live events during the call.
Subscribe with webhook_events on a call request to receive progress events, like connected, transferred, and ended, while the call runs.
How it deploys.
Create a Pipedream workflow with an HTTP webhook trigger and copy its URL.
Paste the URL as the webhook on your Bland inbound number, or pass it as webhook on outbound call requests.
Write custom logic in Node.js or Python to verify the signature and process the call event.
Test by completing a call and checking the Pipedream execution log.
Our FDE team scopes the integration, maps Bland to your stack, and stays on through go-live. Enterprise deployments go live in 30 days.
Drop Bland into your editor.
MCP server runs in Claude Code, Cursor, and any MCP-aware editor. Or hit the REST API directly.
curl -X POST https://api.bland.ai/v1/calls \
-H "Authorization: $BLAND_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"phone_number": "+14155552120",
"task": "Qualify refi lead",
"voice": "june"
}'
Frequently asked questions.
How do I connect Bland to Pipedream?
Through webhooks, which work with any workflow. Create a workflow with an HTTP trigger, set its URL as the post-call webhook on your Bland number or call request, and each finished call runs your Node.js or Python steps with the full payload.
Can a Bland agent call a Pipedream workflow during a call?
Yes. Build a webhook tool that POSTs to the workflow URL and check the output fields you want back. The agent waits for the response, reads the values you mapped, and can route on success or failure.
How do I verify Bland webhooks in Pipedream?
Create a webhook signing secret in Bland. In a code step, compute an HMAC SHA-256 of the request body with that secret and compare it to the X-Webhook-Signature header before you run anything downstream.
Can I get events while the call is still running?
Yes. Add webhook_events to the Send Call request to stream progress events such as connected, transferred, and ended during the call. The post-call webhook still arrives with the full payload when the call finishes.
Can a Pipedream workflow start Bland calls?
Yes. Call Bland's Send Call API from a step with your API key, the number, and a task or pathway ID. Use metadata to carry your own IDs so the post-call webhook can be matched back to the right record.
Related integrations.
See every integration on the integrations hub.
With our team
Our FDE team scopes the integration with you.
They map Bland to your stack, design the rollout, and stay on through go-live. Enterprise deployments go live in 30 days.
On your own
Or drop Bland into your editor.
The Bland MCP server runs in Claude Code, Cursor, and any MCP-aware editor. Or hit the REST API directly. Free sandbox, no credit card.