# Pipedream Registry

When developing workflows with pre-built actions and triggers, under the hood you're using components from the Pipedream Registry Github Repository (opens new window).

Components contributed to the Pipedream Registry Github Repository (opens new window) are published to the Pipedream marketplace (opens new window) and are listed in the Pipedream UI when building workflows.

What is a component?

If you haven't yet, we recommend starting with our Component Development Quickstart Guides for sources and actions to learn how to build components and privately publish them to your account.

# Registry Components Structure

All Pipedream registry components live in this GitHub repo (opens new window) under the components (opens new window) 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 (opens new window) within the registry:

├── README.md
├── actions
│   ├── get-record
│   │   └── get-record.mjs
├── airtable.app.mjs
├── node_modules
│   ├── ...here be dragons
├── package.json
└── sources
    └── new-records
        └── new-records.mjs

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.

The repository is missing the app directory I'd like to add components for

You can request to have new apps integrated into Pipedream.

Once the Pipedream team integrates the app, we'll create a directory for the app in the components (opens new window) directory of the GitHub repo.

# 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 (opens new window).
  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 (opens new window).
  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 (opens new window) in Slack or on Discourse (opens new window).

Not sure what to build?

Need inspiration? Check out sources (opens new window) and actions (opens new window) requested by the community!

# Reference Components

The following components arfor developing sources and actions for Pipedream's registry.

# Reference Sources

Name App Type
New Card (opens new window) Trello Webhook
New or Modified Files (opens new window) Google Drive Webhook + Polling
New Submission (opens new window) Jotform Webhook (with no unique hook ID)

# Reference Actions

Name App
Add Multiple Rows (opens new window) Google Sheets
Send Message (opens new window) Discord
Append Text (opens new window) Google Docs
GET request (opens new window) HTTP