Pipedream Glossary
Below you’ll find a glossary of Pipedream-specific terms. We use these in the product, docs, and other content, so if you’re seeing a term for the first time, you’ll probably find it below.
All terms that aren’t in this doc hold their standard technical meaning. If you see a term missing, please reach out.
0-9 | A | B | C | D | E | F | G | H | I | J | K | L | M | N | O | P | Q | R | S | T | U | V | W-Z
A directory available to the workflow’s execution environment for storing files. Files stored in
0 - 9
2FA
Short for two-factor authentication.A
Account
Synonym for connected account.Action
Actions are reusable code steps, written as Pipedream components.Advanced plan
Pipedream’s plan for individuals and teams running production workflows. See the pricing page for more details.Auto-retry
A workflow setting that lets you automatically retry an execution from the failed step when it encounters an error.B
Bash runtime
Pipedream’s internal code in the execution environment responsible for running Bash code.Basic plan
Pipedream’s plan for individuals who need higher limits and the option to scale usage. See the pricing page for more details.Bi-directional GitHub sync
When you configure GitHub Sync, you can make changes in Pipedream and push them to GitHub, or make changes locally, push to GitHub, and deploy to Pipedream. Since changes can be made in each system and communicated to the other, the sync is bi-directional.Branch
Short for Git branch. When using Pipedream GitHub Sync, you can sync a GitHub repository to a Pipedream project and manage changes to code in a branch.Builder
The Pipedream UI where you build, edit, and test workflows.Business plan
Pipedream’s plan for teams with security, compliance, and support needs. See the pricing page for more details.C
Changelog
Synonym for project changelog.Code step
Steps that let users run custom code in a workflow.Cold start
A cold start refers to the delay between the invocation of workflow and the execution of the workflow code. Cold starts happen when Pipedream spins up a new execution environment to handle incoming events.Commit
Short for Git commit. When using Pipedream GitHub Sync, you commit changes to a branch before deploying the workflow to production.Component
Components are Node.js modules that run on Pipedream’s serverless infrastructure. Sources and actions are two types of components. See the component API for more details.Component API
The programming interface for creating components in Pipedream.Component guidelines
Guidelines applied to components submitted to the Pipedream component registry.Component registry
The public registry of components available to Pipedream users, available on GitHub.Concurrency
A workflow setting that lets users configure the number of concurrent workers available to process events.Connected account
A specific account or credentials used to connect to a Pipedream integration. If both you and your team member have an account with OpenAI, for example, you would connect each account as a distinct connected account. See the docs for more details.Connected account access control
You can restrict access to connected accounts to specific individuals or share with the entire workspace. See the docs for more details.Credit
Pipedream charges one credit per 30 seconds of compute time at 256MB megabytes of memory (the default) per workflow execution. Credits are also charged for dedicated workers. See the docs for more details.Custom domain
By default, HTTP endpoints are served from the*.m.pipedream.net domain. You can configure a custom domain if you want to host that endpoint on your own domain.
Custom source
An event source that you create using custom code, or by modifying a registry source.D
Data retention
A workflow setting that allows you to configure how long Pipedream stores event data and logs associated with executions. See the docs for more details.Dedicated workers
Workers that remain available to process events, even when the workflow is not running. This can help reduce cold starts and improve performance for workflows that require low latency. See the docs for more details.Deduper
Event sources can receive duplicate requests tied to the same event. Pipedream’s infrastructure supports deduplication to ensure that only unique events are emitted by a source.Delay
A built-in service that lets you pause a workflow for a specified amount of time. You can delay workflows using pre-built actions, or delay in code.Destination
Destinations are built-in services that abstract the delivery and connection logic required to send events to services like Amazon S3, or targets like HTTP and email.Domain
Synonum for custom domain.Data store
Data stores are Pipedream’s built-in key-value store.Deploy key
When you configure GitHub Sync, you can use a deploy key to authenticate Pipedream with your GitHub repository. See the docs for more details.E
Editor
The built-in code editor in the builder.Email trigger
A workflow trigger that listens for incoming email. This trigger exposes a workflow-specific email address that you can use to send email to the workflow.Emit
Event sources, workflow triggers, and even workflows themselves can emit events that trigger other listeners. Since sources have a built-in deduper, not all requests are emitted as events.Emitter
A resource that emits events. Emitters can be event sources, workflow triggers, or even workflows themselves.Error notification
When a workflow execution encounters an error, Pipedream sends an error notification to the configured error listeners.Environment variable
Pipedream supports two types of environment variables:- Project variables, available within a specific project
- Workspace variables, available across all projects in a workspace
Event
Events are emitted by sources and consumed by workflows. Events can be triggered by a variety of sources, including HTTP requests, cron schedules, and third-party APIs. Events can be passed to actions, which can process the event data and perform a variety of operations, including making HTTP requests, sending emails, and interacting with third-party APIs.Event context
Metadata about a workflow execution, including the timestamp of the event, the event ID, and more. Exposed insteps.trigger.context.
Event data
The content of the event, exposed insteps.trigger.event.
Event history
A log of all workflow events and executions, available in the event inspector or the global event history UI.Event queue
When using built-in concurrency or throttling controls, events are queued in a workflow-specific queue and processed by available workers.Event source
Components that watch for events from a third-party data source, emitting those events to listeners.Execution
When a workflow is triggered by an event, the running instance of the workflow on that event is called an execution.Execution environment
The virtual machine and internal Pipedream platform code that runs a workflow execution. An instance of an execution environment is called a worker.Execution rate controls
The workflow setting that allows users to configure the number of executions a workflow can process per unit time. Also known as throttling. See the docs for more details.Export
Depending on the context, export can function as a noun or verb:- Noun: A synonym for step export
- Verb: The act of exporting data from a step using Pipedream primitives like
$.exportorreturn.
Expression
In programming, expressions are code that resolve to a value. In Pipedream, you can use expressions within props forms to reference prior steps or compute custom values at runtime.External credentials
Connected accounts are accounts that users link directly in Pipedream. External credentials are credentials that users store in their own database or service, and reference in Pipedream at runtime. See the docs for more details.F
File store
File stores are filesystems scoped to projects. Any files stored in the file store are available to all workflows in the project.Filter
Built-in actions that let you continue or stop a workflow based on a condition.Folder
Within projects, you can organize workflows into folders.Free plan
Pipedream’s free plan. See the limits docs for more details.G
Global search
PressCtrl + K or Cmd + K to open the global search bar in the Pipedream UI.
GitHub Sync
When enabled on a project, GitHub Sync syncs the project’s workflow code with a GitHub repository. See the docs for more details.Golang runtime
Pipedream’s internal code in the execution environment responsible for running Go code.H
Helper functions
Built-in actions that convert data types, format dates, and more.Hooks
Hooks are functions executed as a part of the event source lifecycle. They can be used to perform setup tasks before the source is deployed, or teardown tasks after the source is destroyed.HTTP endpoint
The URL tied to a workflow HTTP trigger or HTTP-triggered event source.HTTP trigger
A workflow trigger that listens for incoming HTTP requests. This trigger exposes a unique URL that you can use to send HTTP requests to the workflow.I
Inspector
The Pipedream UI that displays a specific workflow’s event history. See the docs for more details.Integrations
When Pipedream adds a new third-party service to our marketplace of apps, we often have to handle details of the OAuth process and authentication, and build sources and actions for the API. These details are abstracted from the user, and the app configuration is referred to as an integration.J
K
Key-based account
A connected account that uses static credentials, like API keys.L
Listener
A resource that listens for events emitted by emitters. Listeners can be workflows, event sources, webhook URLs, and more.Logs
Standard output and error logs generated by steps during a workflow execution. Logs are available as a part of the step execution details in the event inspector or the global event history UI.M
Merge
When you configure GitHub Sync, you can merge changes from a branch into the production branch of your GitHub repository, deploying those changes to Pipedream.N
Node.js runtime
Pipedream’s internal code in the execution environment responsible for running Node.js code.O
Organization
Synonym for workspaces.OAuth account
A connected account that uses OAuth to authenticate with a third-party service.P
Premium apps
Pipedream’s built-in integrations that require a paid plan to use. See the pricing page for more details and the full list of premium apps.Project
A container for workflows, secrets, and other resources in Pipedream. Projects can be synced with a GitHub repository using GitHub Sync. See the docs for more details.Project-based access control
You can restrict access to projects to specific individuals or share with the entire workspace. See the docs for more details.Project changelog
When using Pipedream GitHub Sync, the changelog shows the history of changes made to a project.Project file
A file stored in a file store.Project secret
Users can add both standard project variables and secrets to a project. The values of secrets are encrypted and cannot be read from the UI once added.Project settings
Configure GitHub Sync and other project-specific configuration in a project’s settings.Project variable
Project-specific environment variables, available to all workflows in a project.Props
Props allow you to pass input to components.Python runtime
Pipedream’s internal code in the execution environment responsible for running Python code.Object explorer
The builder UI that allows you to search objects exported from prior steps. See the docs for more details.Q
R
Registry
Synonym for component registry.Registry source
An event source available in the component registry. Registry sources are reviewed and approved by Pipedream.S
Schedule trigger
A workflow trigger that runs on a schedule. This trigger exposes a cron-like syntax that you can use to schedule the workflow.Single sign-on (SSO)
Users can configure SSO to authenticate with Pipedream using their identity provider.Source
Synonym for event source.Step
Steps are the building blocks used to create workflows. Steps can be triggers, actions, or code steps.Step export
JSON-serializable data returned from steps, available in future steps of a workflow. See the docs for more details.Step notes
Step notes are Markdown notes you can add to a step to document its purpose.Subscription
A connection between a listener and an emitter that allows the listener to receive events from the emitter.Suspend
Workflow executions are suspended when you delay or use functions like$.flow.suspend to pause the workflow.
T
Throttling
Synonym for execution rate controls.Timeout
All workflows have a default timeout. You can configure a custom timeout in the workflow settings./tmp directory
A directory available to the workflow’s execution environment for storing files. Files stored in /tmp are only guaranteed to be available for the duration of the workflow execution, and are not accessible across workers.