See the CLI installation docs to learn how to install the CLI for your OS / architecture.
pd to see a list of all commands with basic usage info, or run
pd help <command> to display help docs for a specific command.
We've also documented each command below, with usage examples for each.
Everywhere you can refer to a specific component as an argument, you can use the component's ID or its name slug. For example, to retrieve details about a specific source using
pd describe, you can use either of the following commands:
> pd describe dc_abc123
> pd describe http
Searching for sources matching http
Deletes an event source. Run:
pd delete <source-id-or-name>
pd list so to display a list of your event sources.
Deploy an event source from local or remote code.
pd deploy, without any arguments, brings up an interactive menu asking you select a source. This list of sources is retrieved from the registry of public sources published to Github.
When you select a source, we'll deploy it and start listening for new events.
You can also deploy a specific source via the source's
key (defined in the component file for the source):
pd deploy http-new-requests
or author a component locally and deploy that local file:
pd deploy http.js
Display the details for a source: its id, name, and other configuration details:
pd describe SOURCE_ID_OR_NAME
pd dev allows you to interactively develop a source from a local file.
pd dev will link your local file with the deployed component and watch your local file for changes. When you save changes to your local file, your component will automatically be updated on Pipedream.
pd dev FILE_OR_NAME
If you quit
pd dev and want to link the same deployed source to your local file, you can pass the deployed component ID using the
pd dev --dc SOURCE_ID FILE_OR_NAME
Returns historical events sent to a source, and streams emitted events directly to the CLI.
pd events SOURCE_ID
pd events prints (up to) the last 10 events sent to your source.
pd events -n 100 SOURCE_ID_OR_NAME
pd events -n N retrieves the last
N events sent to your source. We store the last 100 events sent to a source, so you can retrieve a max of 100 events using this command.
pd events -f SOURCE_ID_OR_NAME
pd events -f connects to the SSE stream tied to your source and displays events as the source produces them.
pd events -n N -f SOURCE_ID_OR_NAME
You can combine the
-f options to list historical events and follow the source for new events.
Displays help for any command. Run
pd help events,
pd help describe, etc.
Generate new app and component files from templates.
Creates a directory and an app file from a template
# Creates google_calendar/ directory and google_calendar.mjs file
pd init app google_calendar
Creates a new directory and a component action from a template.
# Creates add-new-event/ directory and add-new-event.mjs file
pd init action add-new-event
Creates a new directory and an event source from a template.
# Creates cancelled-event/ directory and cancelled_event.mjs file
pd init source cancelled-event
For example, running:
pd init source cancelled-event --db --http --timer
will include the following props in your new event source:
Lists Pipedream sources running in your account. Running
pd list without any arguments prompts you to select the type of resource you'd like to list.
You can also list specific resource types directly:
pd list components
pd list streams
streams have shorter aliases, too:
pd list so
pd list st
Log in to Pipedream CLI and persist API key locally. See Logging into the CLI for more information.
Unsets the local API key tied to your account.
pd logout without any arguments removes the default API key from your config file.
You can remove the API key for a specific profile by running:
pd logout -p PROFILE
Event sources produce logs that can be useful for troubleshooting issues with that source.
pd logs displays logs for a source.
pd logs <source-id-or-name> connects to the SSE logs stream tied to your source, displaying new logs as the source produces them.
Any errors thrown by the source will also appear here.
To publish an action, use the
pd publish command.
pd publish <filename>
pd publish my-action.js
Sign up for Pipedream via the CLI and persist your API key locally. See the docs on Signing up for Pipedream via the CLI for more information.
Unpublish a component you've published to your account. If you publish a source or action that you no longer need, you can unpublish it by component
pd unpublish component <component-key>
Updates the code, props, or metadata for an event source.
If you deployed a source from Github, for example, someone might publish an update to that source, and you may want to run the updated code.
pd update SOURCE_ID_OR_NAME \
You can change the name of a source:
pd update SOURCE_ID_OR_NAME --name NEW_NAME
You can deactivate a source if you want to stop it from running:
pd update SOURCE_ID_OR_NAME --deactivate
or activate a source you previously deactivated:
pd update SOURCE_ID_OR_NAME --activate
Profiles allow you to work with multiple, named Pipedream accounts via the CLI.
When you login to the CLI, the CLI writes the API key for that account to your config file, in the
api_key = abc123
You can set API keys for other, named profiles, too. Run
pd login -p <profile>
<profile> can be any string of shell-safe characters that you'd like to use to identify this new profile. The CLI opens up a browser asking you to login to your target Pipedream account, then writes the API key to a section of the config file under this profile:
api_key = def456
You can also run
pd signup -p <profile> if you'd like to sign up for a new Pipedream account via the CLI and set a named profile for that account.
If you're working with resources in an workspace, you'll need to add an
org_id to your profile.
- Retrieve your workspaces's ID
- Open up your Pipedream config file and create a new profile with the following information:
api_key = <API Key from user settings>
org_id = <Workspace ID from workspace settings>
When using the CLI, pass
--profile <profile_name> when running any command. For example, if you named your profile
workspace, you'd run this command to publish a component:
pd publish file.js --profile workspace
You can set a profile on any
pd command by setting the
--profile flag. For example, to list the sources in a specific account, run:
pd list sources --profile PROFILE
To get the current version of the
pd CLI, run
The CLI is configured to check for new versions automatically. This ensures you're always running the most up-to-date version.
pd config file contains your Pipedream API keys (tied to your default account, or other profiles) and other configuration used by the CLI.
XDG_CONFIG_HOME env var is set, the config file will be found in
Otherwise, it will be found in
If you'd like to opt-out of CLI analytics, set the
PD_CLI_DO_NOT_TRACK environment variable to