Pipedream API
Official vendor OpenAPI document · agent-readyDeveloper ToolsCi Cdbearer65 EndpointsREST
For Agents
Create and manage serverless workflows with event triggers, API integrations, and data transformations. Supports 65 endpoints for workflow automation, event sources, data stores, and execution monitoring.
Use for: I need to create a workflow that runs when a webhook is received, Deploy a workflow that polls an API every hour and sends results to Slack, Configure OAuth connection to Google Sheets for a workflow, Retrieve data from a workflow's key-value store
Not supported: Does not provide application hosting, real-time streaming, or database management - use for event-driven workflow orchestration and API integration automation only.
Pipedream is a serverless integration and workflow automation platform that connects APIs, databases, and services with event-driven workflows. The API provides programmatic access to create workflows, manage triggers, configure actions, handle event sources, store data, and monitor executions. Built for developers building automation platforms, no-code tools, integration marketplaces, and AI agents that need to orchestrate multi-step workflows across hundreds of APIs without managing infrastructure.
Install Jentic One Beta
Connect the Pipedream API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Pipedream API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fpipedream.com%2Fpipedream" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fpipedream.com%2Fpipedream" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Pipedream API.
Create and deploy serverless workflows with Node.js code and pre-built actions for 2000+ APIs
Configure event sources including webhooks, HTTP polling, email, RSS, and scheduled cron triggers
Connect to APIs using OAuth, API keys, and custom authentication stored securely per workflow
Store and retrieve workflow data in key-value stores without managing databases
Monitor workflow executions with logs, error tracking, and performance metrics
Share workflows as templates and publish custom actions for reuse across projects
Integrate with external services via HTTP requests, SQL queries, and file operations
Use Cases
Patterns agents use Pipedream API for, with concrete tasks.
★ AI Agent Multi-Step Workflow Orchestration
Enable AI agents to orchestrate complex multi-step workflows across APIs without writing integration code. Agents can create Pipedream workflows programmatically to chain API calls, handle conditional logic, store intermediate results, and retry failures. For example, an agent tasked with 'sync Salesforce contacts to Mailchimp' can create a workflow with a scheduled trigger, Salesforce query step, data transformation, and Mailchimp upsert - all through the Pipedream API.
Create a workflow triggered by webhook that (1) validates incoming lead data, (2) enriches it via Clearbit API, (3) creates a deal in HubSpot CRM, (4) sends notification to Slack, then deploy and retrieve the webhook URL
Event-Driven Integration Platform
Build event-driven integration platforms where users connect SaaS apps and define automation rules through a no-code UI, powered by Pipedream workflows under the hood. The API allows creating workflows from templates, configuring triggers (webhooks, schedules, email), adding actions from Pipedream's 2000+ app library, and managing user-specific OAuth connections. Users get serverless execution without infrastructure management.
Create a workflow from the 'New Stripe Payment to Google Sheets' template, configure user's OAuth connection to both services, customize the data mapping, and deploy with webhook trigger for their Stripe account
API Polling and Data Synchronization
Set up workflows that poll APIs at regular intervals to detect changes and sync data between systems. The API supports configuring scheduled triggers (cron expressions), HTTP polling logic with deduplication, and actions that upsert data to destination APIs. Ideal for keeping inventory, customer records, or order status synchronized across platforms without webhooks.
Create a workflow with hourly cron trigger that polls Shopify for new orders since last run, stores last check timestamp in data store, transforms order data, and upserts to Airtable with deduplication by order ID
Workflow Monitoring and Debugging
Monitor workflow executions, track errors, and debug failures programmatically. The API provides execution history with input/output for each step, error details, execution duration, and retry status. Development teams can build monitoring dashboards, alert systems, and automated error remediation workflows that respond to failed executions by retrying with different parameters or escalating to human operators.
Query all workflow executions from the last 24 hours, filter for failures with error type 'RateLimitError', extract the workflow IDs and error details, then send a daily report to operations team with retry recommendations
Key Endpoints
65 endpoints — pipedream is a serverless integration and workflow automation platform that connects apis, databases, and services with event-driven workflows.
METHOD
PATH
DESCRIPTION
POST
/v1/workflows
Create a new workflow
POST
/v1/workflows/{workflowId}/deploy
Deploy a workflow to production
POST
/v1/event_sources
Create an event source trigger
GET
/v1/workflows/{workflowId}/executions
Get workflow execution history
POST
/v1/data_stores/{storeId}/records
Store data in key-value store
GET
/v1/data_stores/{storeId}/records/{key}
Retrieve stored data
GET
/v1/connections
List OAuth and API connections
POST
/v1/workflows
Create a new workflow
POST
/v1/workflows/{workflowId}/deploy
Deploy a workflow to production
POST
/v1/event_sources
Create an event source trigger
GET
/v1/workflows/{workflowId}/executions
Get workflow execution history
POST
/v1/data_stores/{storeId}/records
Store data in key-value store
GET
/v1/data_stores/{storeId}/records/{key}
Retrieve stored data
GET
/v1/connections
List OAuth and API connections
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring Pipedream by hand means managing its bearer token, coordinating workflow, event-source, and data-store calls, and handling retries yourself. Through Jentic you install once, import Pipedream from the API Directory, store the token once, and your agent calls it.
Permission scoping
Pipedream puts the workflow id and data-store id in the URL path (/v1/workflows/{workflowId}, /v1/data_stores/{storeId}/records), so a rule can pin your agent to one workflow or store. You choose the operations it may call, so deploying a workflow or writing store records is not included unless you add it.
Credential isolation
Your Pipedream API token is stored once, encrypted, by your own Jentic One instance and injected as an Authorization header at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'create a workflow with a webhook trigger' or 'read a data-store record', and Jentic returns the matching Pipedream operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Pipedream API through Jentic.
What authentication does the Pipedream API use?
The API uses bearer token authentication with API keys generated in the Pipedream dashboard under Account Settings > API Keys. Each request includes an Authorization: Bearer {token} header. Through Jentic, bearer tokens are stored encrypted and injected automatically - they never appear in agent prompts.
Can I create workflows programmatically?
Yes. POST /v1/workflows accepts workflow definitions in JSON format including trigger configuration, step definitions with code or pre-built actions, and environment variables. After creation, POST /v1/workflows/{id}/deploy makes the workflow live. You can also create workflows from templates available in the Pipedream registry.
How do I manage OAuth connections for workflows?
POST /v1/connections creates OAuth connections by specifying the app (e.g., 'google_sheets') and initiating the OAuth flow. The API returns an authorization URL for user consent. Once authorized, the connection is available to workflows via connection ID. Pipedream securely stores and refreshes tokens.
What are the execution limits?
Free tier includes 100 workflow executions per day and 10 active workflows. Paid plans start at $19/month for 1,000 invocations and scale to unlimited workflows and executions. Workflow execution timeout is 5 minutes on free tier, 5-60 minutes on paid plans. Each workflow step has memory and CPU limits documented per plan tier.
How do data stores work?
Data stores are serverless key-value databases scoped to your project or workflow. POST /v1/data_stores/{storeId}/records sets a key-value pair; GET retrieves it. Useful for storing workflow state, deduplication tracking, caching API responses, or maintaining counters. Free tier includes 100 operations per day; paid plans include 10,000+.
Can I use Pipedream for high-frequency workflows?
Pipedream is optimized for event-driven and scheduled workflows, not high-frequency streaming. For workflows triggered more than once per second, consider batching or using Pipedream as a coordinator that queues work to specialized systems. Scheduled workflows support cron expressions with minimum 1-minute intervals.
Can I limit what my agent is allowed to do with the Pipedream API?
Yes. Because Jentic One is self-hosted, your own rules decide which Pipedream operations and credentials the agent may use. Pipedream puts the workflow id and data-store id in the URL path (/v1/workflows/{workflowId}, /v1/data_stores/{storeId}/records), so a rule can pin the agent to a single workflow or data store. You also choose which operations it may call, so deploying a workflow or writing store records stays off-limits unless you add it, while your API token is injected at execution time and never enters the agent's prompt.
GET STARTED