Pipedream functions as a specialized integration platform tailored for software developers.

Pipedream furnishes a complimentary, managed environment for orchestrating application connectivity and constructing reactive, event-driven architectures. The platform boasts a catalog exceeding 1,000 pre-integrated applications, enabling rapid deployment of standard tasks like dispatching notifications to Slack or appending records to Google Sheets. Furthermore, developers retain the ability to execute bespoke logic using Node.js, Python, Golang, or Bash code. Pipedream adheres to SOC 2 compliance standards and furnishes the requisite Type 2 report upon official request via support@pipedream.com.

This repository encapsulates:

The source code for all reusable integration primitives
The public evolution blueprint for the product
The comprehensive documentation set for Pipedream
And ancillary source materials pertaining to the Pipedream ecosystem.

This document elucidates the core functionalities of the platform and guides initial setup.

For operational assistance, please navigate to https://pipedream.com/support.

Core Capabilities

Execution Flows - Flows govern the automation process. They comprise a series of stages—either leveraging established actions or custom code modules (Node.js, Python, Golang, or Bash)—initiated by a discrete event (e.g., an HTTP invocation, a scheduled timer, or a new data entry in Google Sheets, among others).
Initiation Triggers - Triggers are the mechanisms that launch flows. They emit data derived from external services like GitHub, Slack, Airtable, RSS feeds, and many others. When you configure a flow to execute upon an event within a third-party service, you are utilizing an initiation trigger.
Pre-built Operations - Operations are standardized code segments designed for common tasks across Pipedream's ecosystem of over 1,000 integrated APIs. Examples include sending electronic mail or inserting a record into a spreadsheet, as detailed in the applications directory.
Custom Scripting - Complex integration requirements frequently necessitate bespoke logic. Pipedream facilitates the execution of arbitrary code written in Node.js, Python, Golang, or Bash. Users can integrate external libraries from the respective language package repositories and interact with any Pipedream-authenticated application. Pipedream embodies "low-code" principles effectively: utilizing standardized modules for routine functions while permitting granular custom scripting when necessary.
Data Offloading - Destinations manage the asynchronous transfer of emitted events to designated endpoints, such as Amazon S3 storage, Snowflake data warehousing, generic HTTP endpoints, or email services.
Cost Structure - The service offers a perpetually free tier for individual practitioners (subject to documented usage constraints).

Operational Demonstration

Consult the image below for a concise video demonstration hosted on YouTube.

Execution Flows

Flows represent sequential chains of operational stages activated by an originating event (like an HTTP receipt or a new Google Sheet entry). These flows allow for the rapid construction of intricate automation sequences interfacing with over 1,000 supported applications.

Refer to our flow quickstart guide to commence development.

Initiation Triggers

Initiation Triggers actively monitor external systems such as GitHub, Slack, Airtable, or RSS feeds for novel data events (and many more). Upon detecting an event, the trigger dispatches it, initiating any linked execution flows.

You can alternatively consume emitted events via Pipedream's standard REST interface or through a private, live SSE feed.

If a requirement lacks a native trigger, developers can construct custom ones. The simplest instantiation involves an HTTP listener: it exposes an endpoint ready to receive requests and logs the incoming data upon invocation:

export default {
  name: "http",
  version: "0.0.1",
  props: {
    http: "$.interface.http",
  },
  run(event) {
    console.log(event); // event contains the method, payload, etc.
  },
};

The source code for all provided triggers resides within the components repository section. For bug reports or feature submissions, please consult our documentation on contribution standards.

Pre-built Operations

Operations are modular snippets of code facilitating common tasks across Pipedream's extensive library of over 500 API integrations. Illustrative examples include sending communications or updating database tables, as detailed in the application catalog.

You possess the capability to author your own operations for internal reuse across flows, or elect to publish them to the broader Pipedream community.

Below is an example operation that accepts a name parameter and outputs it to the flow's execution log:

export default {
  name: "Action Demo",
  description: "This is a demo action",
  key: "action_demo",
  version: "0.0.1",
  type: "action",
  props: {
    name: {
      type: "string",
      label: "Name",
    },
  },
  async run() {
    return `hello ${this.name}!`;
  },
};

You can review the source code for all standard operations in the components folder. For contribution guidance or issue reporting, refer to the contribution protocols.

Custom Scripting

Implementing complex integration logic often necessitates writing custom code. Pipedream permits running user-defined code within an execution flow utilizing these runtimes:

Dependency management is streamlined: declare imports directly within the code, and Pipedream will automatically resolve and fetch the required packages from the respective language registries.

// Node.js
import axios from "axios";

# Python
import pandas as pd

// Go
import (
    "fmt"
    pd "github.com/PipedreamHQ/pipedream-go"
)

Furthermore, custom code steps can seamlessly interface with authenticated Pipedream applications. For instance, integrating a Slack connection to post a message:

import { WebClient } from "@slack/web-api";

export default defineComponent({
  props: {
    // Establishes a connection named "slack" linked to the Slack application.
    slack: {
      type: "app",
      app: "slack",
    },
  },
  async run({ steps, $ }) {
    const web = new WebClient(this.slack.$auth.oauth_access_token);

    return await web.chat.postMessage({
      text: "Hello, world!",
      channel: "#general",
    });
  },
});

Data Offloading

Data Offloading Targets, similar to operations, abstract the complexities of connection handling, data serialization, and reliable transmission to external targets like Amazon S3 or HTTP receivers.

Sending data to an S3 bucket, for instance, is accomplished via a concise function call: $send.s3():

$send.s3({
  bucket: "your-bucket-here",
  prefix: "your-prefix/",
  payload: event.body,
});

Pipedream natively supports the following offloading pathways:

Contributors Acknowledged

Our sincere gratitude extends to every individual who has contributed to the Pipedream source code. Your involvement is highly valued!

Pricing Structure

Pipedream features a robust complimentary tier. Sources and flows can operate without charge up to the defined operational thresholds. Exceeding these constraints prompts users to select one of our subscription plans.

Operational Constraints

The Pipedream platform enforces specific execution ceilings for both sources and flows. Detailed documentation regarding these limitations is available in our official guides.

Encountered an Anomaly or Possess an Enhancement Suggestion?

Prior to submitting a new issue, please investigate existing reported issues or contact our support team to ascertain if the matter has already been raised.

If a duplicate exists, kindly engage by adding a reaction or providing supplementary context regarding your specific integration scenario.

If no corresponding issue is found, please utilize the standardized issue templates when creating a new report.

Security Posture

Information concerning our platform's security protocols and data governance can be reviewed at this location.

Should you wish to report a potential vulnerability or security concern, or if you have inquiries regarding product security, please direct correspondence to our dedicated security team at security@pipedream.com.