Overview

​

What are Components?

Components are Node.js modules that run on Pipedream’s serverless infrastructure. They can use Pipedream managed auth for 3,000+ apps (for both OAuth and key-based APIs) and use most npm packages with no npm install or package.json required. Components are the actions and triggers you run through Pipedream Connect and MCP. Explore curated components for popular apps in Pipedream’s Marketplace and GitHub repo, or author and share your own.

​

Component Types

Pipedream supports two types of components — sources and actions.

​

Sources

Sources (also called triggers) must be deployed, and they run as independent resources on Pipedream. They listen for events in a third-party app or on a schedule, then emit an event for you to consume. Capabilities

• Accept user input on deploy via props
• Trigger on HTTP requests, timers, cron schedules, or manually
• Emit events that can be inspected and consumed in your own app by webhook or API
• Store and retrieve state using the built-in key-value store
• Use any of Pipedream’s built-in deduping strategies
• Deploy via Pipedream’s UI, CLI or API

Example The New Files (Instant) source for Google Drive is a prebuilt component in Pipedream’s registry that can be deployed in seconds and emits an event every time a new file is added to the user’s Google Drive, and can also be configured to watch for changes to a specific folder within that drive. Each new event that is emitted can be delivered to your app.

​

Actions

Actions are components you invoke on demand: you pass a configuration, Pipedream runs the action, and you get the result back. Unlike sources, actions don’t run on their own. Capabilities

• Accept user input via props
• May return JSON serializable data

Example The Add Single Row action for Google Sheets is a prebuilt component in Pipedream’s registry. You can configure and run it in seconds to send data to Google Sheets, without having to learn the Google Sheets API.

​

Using Components

You run components through Connect:

• Actions: run an action on behalf of one of your users with the Connect API or SDKs
• Triggers: deploy a source for one of your users and receive each event by webhook
• MCP: expose components to your AI agent as tools with Pipedream MCP
• CLI: deploy and inspect sources in your own workspace with the CLI

​

Using private components

Private components published from the CLI belong to your workspace and are available alongside the public registry components in every Connect API. To make a private action available in Connect, publish it with the --connect-environment flag and reference it with the ~/ prefix. See Using custom tools for the full walkthrough. Private sources deployed from your workspace via the CLI create a new source with the prop configuration you specified. You can also deploy new instances of a source from the Components dashboard. To deploy a new instance of a source, click the menu on the right hand side and select Create source.

​

Developing Components

Develop components locally using your preferred code editor (and maintain your code in your own GitHub repo) and deploy or publish using Pipedream’s CLI.

• Sources may be deployed directly from local code, or published to your account and instantiated via Pipedream’s UI
• Actions may only be published — published actions are available to run through Connect and MCP

Published components are only available to your own account by default. If published to a team account, the component (source or action) may be discovered and selected by any member of the team.

​

Prerequisites

• A free Pipedream account
• A free GitHub account
• Basic proficiency with Node.js or JavaScript
• Pipedream CLI

Finally, the target app must be integrated with Pipedream. You can explore all apps supported by Pipedream in the marketplace. If your app is not listed, please create a GitHub issue to request it and reach out to our team to let us know that you’re blocked on source or action development.

​

Quickstart Guides

• Sources
• Actions

​

Component API Reference

After getting familiar with source/action development using the quickstart guides, check out the Component API Reference and examples on GitHub to learn more.

​

Managing Privately Published Components

Components published to your workspace are available in the Components section of the dashboard. Your private components published from the CLI are listed here.

​

Unpublishing Privately Published Components

To unpublish components belonging to your workspace, open the menu on the right hand side of the component details and select Unpublish Component. A prompt will open to confirm the action, click Confirm to unpublish your action.

​

Sharing Components

Contribute to the Pipedream community by publishing and sharing new components, and contributing to the maintenance of existing components.

​

Verified Components

Pipedream maintains a source-available registry of components (sources and actions) that have been curated for the community. Registered components are verified by Pipedream through the GitHub PR process and:

• Can be trusted by end users
• Follow consistent patterns for usability
• Are supported by Pipedream if issues arise

Registered components also appear in the Pipedream marketplace and are available to run through Connect and MCP.

​

Community Components

Developers may create, deploy and share components that do not conform to these guidelines, but they will not be eligible to be listed in the curated registry (e.g., they may be hosted in a GitHub repo). If you develop a component that does not adhere to these guidelines, but you believe there is value to the broader community, please reach out in our community forum.