Pipedream Registry

When developing workflows with pre-built actions and triggers, under the hood you’re using components from the Pipedream Registry Github Repository.

Components contributed to the Pipedream Registry Github Repository are published to the Pipedream marketplace and are listed in the Pipedream UI when building workflows.

Registry Components Structure

All Pipedream registry components live in this GitHub repo under the components directory.

Every integrated app on Pipedream has a corresponding directory that defines the actions and sources available for that app. Below is a simplified version of the Airtable app directory within the registry:

In the example above, the components/airtable/actions/get-record/get-record.mjs component is published as the Get Record action under the Airtable app within the workflow builder in Pipedream.

Contribution Process

Anyone from the community can build sources and actions for integrated apps.

To submit new components or update existing components:

1. Fork the public Pipedream Registry Github Repository.
2. Create a new component within the corresponding app’s directory within the components directory (if applicable).
3. Create a PR for the Pipedream team to review.
4. Address any feedback provided by Pipedream based on the best practice Component Guidelines & Patterns.
5. Once the review is complete and approved, Pipedream will merge the PR to the master branch
6. The component will be available for use within workflows for all Pipedream developers! 🎉

Component Development Discussion

Join the discussion with other Pipedream component developers at the #contribute channel in Slack or on Discourse.

Reference Components

The following components are references for developing sources and actions for Pipedream’s registry.

Reference Sources

Reference Actions