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
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
A user invited to a workspace. Members can create projects, workflows, and other resources in the workspace, but cannot manage billing or administer the workspace.
When you use GitHub Sync, Pipedream serializes the workflow configuration to a YAML file. Optionally, if your workflow contains custom code, Pipedream serializes the code to a separate file.
Workflows are the primary resource in Pipedream. They process events from triggers and run steps to perform actions like making HTTP requests, sending emails, and more.Troubleshooting
