Pipedream is a platform for running hosted, backend components.

Pipedream components are reusable Node.js modules that run code on specific events: HTTP requests, timers, and more. Components are free to run and simple to learn. Here's a component that spins up a hosted HTTP server on deploy and logs inbound HTTP requests:

module.exports = {
  name: "http",
  version: "0.0.1",
  props: {
    http: "$.interface.http"
  },
  run(event) {
    console.log(event); // event contains the method, payload, etc.
  }
};

Components come with a built-in key-value store, an interface for passing input via props, and more. You deploy and manage components using Pipedream's REST API or CLI.

Components can emit events, which can be retrieved programmatically via CLI, API or SSE. Components that emit events can be used as event sources. Event Sources collect data from any service and make it available via Pipedream's REST or SSE APIs: they can turn any API into an event stream, or turn any event stream into an API. For example, you can use event sources to create a REST API from an RSS feed. You can also trigger Pipedream workflows on these events.

Usage

Install the Pipedream CLI:

curl https://cli.pipedream.com/install | sh

Then deploy a component from the registry:

pd deploy   # prompts you to select a component and pass required options

The simplest event source is an HTTP Source. Start there or review the docs to learn more.

Docs

• Component API
• Event Sources
• HTTP Event Sources Quickstart
• REST API Reference
• SSE Reference
• CLI Reference
• Workflows

Pricing

Pipedream is currently free, subject to the limits noted below. Paid tiers for higher volumes are coming soon.

If you exceed any of these limits, please reach out.

Limits

Components are subject to the limits of the Pipedream platform in all cases but one: workflows are limited to 60 seconds per invocation, but components can run for up to 300 seconds per invocation.

Other key limits include:

• 30 minutes of component runtime per UTC day
• 192MB of available memory and 512 MB of disk on /tmp during the execution of your code.

Getting Support

You can get help on our public Slack or reach out to our team directly with any questions or feedback. We'd love to hear from you!

Found a Bug? Have a Feature to suggest?

Any bugs or feature requests for specific components can be raised in this repo as new Github issues or pull requests.

Pipedream also operates a roadmap to solicit feature requests for the Pipedream platform at large (the pipedream.com UI, workflows, the CLI, etc).

You can always reach out to our team - we're happy to discuss feedback or help fix a bug.