Pipedream serves as a platform for developers focused on system integration.

Pipedream furnishes a complimentary, managed environment for linking diverse applications and engineering reactive automation sequences. With access to over a thousand pre-integrated applications, users can rapidly employ pre-built modules to dispatch notifications to Slack, append records to Google Sheets, and similar functions. Furthermore, any custom logic can be executed using Node.js, Python, Golang, or Bash scripts. Pipedream maintains SOC 2 compliance certification and can furnish the corresponding Type 2 report upon formal request (please direct inquiries to support@pipedream.com).

This repository encompasses:

The source code for all standardized integration components
The evolving product roadmap
The comprehensive Pipedream documentation artifacts
Additional source artifacts pertaining to the Pipedream ecosystem.

This README outlines the principal capabilities of the platform and guidance for initial setup.

For assistance, kindly visit https://pipedream.com/support.

Core Capabilities

Automation Sequences - These sequences execute orchestrated tasks. They comprise a series of stages—either utilizing pre-validated actions or custom scripting in Node.js, Python, Golang, or Bash—initiated by a specific stimulus (e.g., an HTTP invocation, a scheduled trigger, or the arrival of a new Google Sheets entry, among others).
Event Triggers - These initiate the automation sequences. They broadcast data emissions from platforms such as GitHub, Slack, Airtable, RSS feeds, and a larger catalog. When you require an automation to react to an occurrence within any external service, you employ an event trigger.
Operations - These are pre-coded steps enabling execution of typical tasks across Pipedream's extensive library of over 1,000 integrated APIs. For instance, operations allow you to dispatch electronic mail, append data to a Google Sheet record, and much more.
Bespoke Scripting - Custom logic frequently necessitates tailored expressions. Scripting provides the optimal medium for this, thus Pipedream permits the execution of any Node.js, Python, Golang, or Bash code. You retain the ability to incorporate any library from the respective language's package repositories, interface with any connected Pipedream application, and so forth. Pipedream embodies "low-code" efficacy: leverage standardized components for routine tasks, but switch to custom coding when specific requirements arise.
Data Delivery Targets - Asynchronously transmit emitted events to prevalent endpoints such as Amazon S3, Snowflake, generic HTTP endpoints, or electronic mail services.
Complimentary Tier - No monetary cost for individual developers (consult usage constraints)

Illustrative Demonstration

Select the visual element below to view a concise demonstration hosted on YouTube.

Automation Sequences

Sequences are linear arrangements of stages initiated by an external trigger (such as an HTTP request receipt or a new data entry in a Google Sheet). You can rapidly architect intricate automation flows by linking these steps and connecting to any of the 1,000+ supported external systems.

Consult our sequence quickstart guide to commence development.

Event Stimuli

Event Triggers actively monitor for fresh data feeds originating from services like GitHub, Slack, Airtable, RSS, and others. When a stimulus detects a relevant occurrence, it broadcasts an event, thereby activating all linked automation sequences.

You may also ingest events broadcast by these triggers via Pipedream's REST API or a private, instantaneous SSE stream.

If a standard trigger does not cover your specific need, you possess the capability to construct your own. The following code snippet illustrates the most rudimentary event trigger: it establishes an HTTP listener accessible via an endpoint, logging the request's contents upon activation:

export default {
  name: "http-listener",
  version: "0.0.1",
  props: {
    http: "$.interface.http",
  },
  run(event) {
    console.log(event); // The 'event' object contains request details like method, payload, etc.
  },
};

The implementation code for all default triggers resides within the components directory. Should you identify a defect or wish to contribute enhancements, please review our contribution methodology.

Operations

Operations are discrete, pre-written code blocks integrated into a sequence to execute standardized routines across Pipedream's expansive catalogue of over 500 API integrations. Examples include sending messages, updating spreadsheet rows, and numerous others.

You are empowered to author your own operations, which can be reused across multiple automation sequences. Furthermore, you may elect to publish these operations to the wider Pipedream collective, making them accessible for general utilization.

Below is an example operation that accepts a name parameter as input and outputs it to the sequence logs:

export default {
  name: "Operation Demonstration",
  description: "A simple demonstration of an operation",
  key: "operation_demo",
  version: "0.0.1",
  type: "action",
  props: {
    name: {
      type: "string",
      label: "Input Name",
    },
  },
  async run() {
    return `Greetings ${this.name}!`;
  },
};

You can locate the source code for all included operations within the components folder. For reporting issues or suggesting feature additions, refer to our contribution standards.

Custom Scripting

Many integration scenarios necessitate specialized programmatic logic. Scripting is frequently the clearest path for implementing this logic; consequently, Pipedream facilitates the execution of custom code within an automation sequence via:

Dependencies from the respective language package managers can be incorporated simply by declaring the imports directly within the script. Pipedream automatically handles the parsing and acquisition of the required assets.

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

# Python implementation example
import pandas as pd

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

You also have the option to interface with any Pipedream-configured application within custom code blocks. For instance, you can establish a connection to your Slack workspace and broadcast a message to a channel:

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

export default defineComponent({
  props: {
    // Defines a connection handle 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 from Pipedream!",
      channel: "#general",
    });
  },
});

Delivery Targets

Delivery Targets, similar to operations, abstract the complexities of connection management, data batching, and transmission protocols necessary for sending events to endpoints like Amazon S3 or adhering to HTTP or email protocols.

For example, routing data to an Amazon S3 repository is as straightforward as invoking $send.s3():

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

Pipedream furnishes support for the subsequent delivery destinations:

Contributors

Our sincere gratitude to every individual who has contributed to the Pipedream source code base. Your efforts are highly valued!

Cost Structure

Pipedream features a robust complimentary tier. You can execute triggers and automation sequences without charge, subject to the prescribed operational constraints of this tier. Should these usage thresholds be exceeded, upgrading to one of our subscribed service plans is an option.

Operational Constraints

The Pipedream infrastructure imposes certain execution duration and volume limitations on both triggers and automation sequences. Detailed specifications of these restrictions can be reviewed in our official documentation.

Detected Issue? Proposing an Enhancement?

Before submitting a new issue report, please perform a search across all existing reported issues or contact our support personnel to ascertain if a similar inquiry is already documented.

If a matching entry is found, we encourage you to register your support via a reaction or elaborate on your specific implementation context in a comment.

If no prior report exists and you must create one, kindly utilize the provided issue templates.

Security Posture

Information regarding our platform's security protocols and data privacy standards is available at this location.

If you suspect a security vulnerability or have questions pertaining to product security, please direct your correspondence to our dedicated security team at security@pipedream.com.