What are Event Sources?

Event sources turn any API into an event stream. They can also turn any event stream into an API.

Event sources run on Pipedream's infrastructure and collect data from services like Github, Stripe, the bitcoin blockchain, RSS feeds, and more. They emit new events produced by the service, which you can inspect in the UI or consume using batch or real-time APIs.

Pipedream Event Sources are in preview, and we'd love your feedback on how you'd like to use them, and what we can improve. Please reach out on Slack or raise an issue on our Github roadmap with any questions or suggestions.

Since this is a preview release, the documentation below, the REST API, and the CLI are subject to change based on feedback.

Consuming events from sources

You can view the events for a source in the sources UI, under the EVENTS section of that source.

You can also consume events programmatically from a source in one of three ways:

Example: HTTP source

The simplest event source is an HTTP source.

When you create an HTTP source:

  • You get a unique HTTP endpoint that you can send any HTTP request to.
  • You can view the details of any HTTP request sent to your endpoint: its payload, headers, and more.
  • You can delete the source and its associated events once you're done.

HTTP sources are essentially request bins that can be managed via API.

HTTP sources are a good example of how you can turn an event stream into an API: the HTTP requests are the event stream, generated from your application, client browsers, webhooks, etc. Then, you can retrieve HTTP requests via Pipedream's REST API, or stream them directly to other apps using the SSE interface.

Create your first HTTP source

See the Github quickstart to get started.

Limits

Event sources are subject to the same limits as Pipedream workflows.

Still have questions?

Please reach out if this doc didn't answer your question. We're happy to help!