Overview

The Pipedream API connector enables your Leena AI Agents to integrate with thousands of third-party SaaS applications through a single unified gateway, eliminating the need to build and maintain individual connectors for every downstream tool in your enterprise stack.

Pipedream is an integration platform that provides managed authentication, credential storage, and a library of pre-built actions for 2,500+ applications including Slack, Gmail, Google Sheets, Salesforce, HubSpot, Jira, GitHub, Notion, and more. The Pipedream API connector allows Leena AI to dynamically discover, configure, and execute actions on any supported Pipedream app, giving your AI Agents broad reach across the enterprise without multiple bespoke integrations.

The full list of apps and connectors available through Pipedream can be viewed here: https://pipedream.com/apps

Each Pipedream API connection in Leena AI is scoped to a single Pipedream app (for example, slack or google_sheets). To enable automation across multiple downstream apps, configure one Pipedream API connection per target app. Credentials, auth flows, and token refresh for each downstream app are managed entirely by Pipedream.

API Details

Leena AI integrates with Pipedream via the Pipedream Connect REST API.

Documentation link: https://pipedream.com/docs/connect/api-ref

Setup

The Pipedream API connector uses OAuth 2.0 authentication with the client credentials grant type. Two OAuth modes are supported:

• Admin OAuth: A single workspace-level credential is used for all end users. Recommended for internal automations where actions run under a central service identity.
• User OAuth: Each end user authorises their own downstream account (for example, their own Gmail or Salesforce). Recommended for employee-facing workflows where actions must run under the individual user's permissions.

Prerequisites

Before setting up the Pipedream API connector, ensure you have:

• Administrator access to your Pipedream workspace
• Ability to create projects in the Pipedream workspace
• Ability to create OAuth clients in the workspace API settings
• Access to your Leena AI workspace with connector management permissions

Get credentials

Here is how to create a Pipedream project and OAuth client:

1. Log in to your Pipedream workspace at https://pipedream.com as a workspace admin
2. Create a Project:
   1. Click Projects in the top left of the Pipedream dashboard
   2. Create a new project (or select an existing one)
   3. Copy the Project ID from the project URL (starts with proj_, for example proj_ABC123)
3. Create an OAuth Client:
   1. Navigate to your workspace's API settings
   2. Click New OAuth Client
   3. Enter a descriptive name (for example, "Leena AI Integration") and click Create
   4. Copy the Client Secret (it is displayed only once during creation)
   5. Click Close
   6. Copy the Client ID from the OAuth clients list
4. Identify the App Slug:
   1. Decide which downstream Pipedream app this connection will target (for example, Slack, Gmail, HubSpot)
   2. Note its name slug from the app's page on Pipedream (for example, slack, gmail, hubspot)

Add connection

Here is how to add a connection on Leena AI:

1. Log in to your Leena AI workspace
2. Navigate to Settings > Integrations
3. Search for "Pipedream API" and select it from the list to add a new connector
4. Start configuring the connector
   1. Auth Type: The credential type used to connect to Pipedream
   2. OAuth Type: Choose how end-user authorisation is handled:
      • Admin OAuth: A single set of workspace credentials is used across all users
      • User OAuth: Each end user authorises their own downstream account
   3. App Name: The slug of the Pipedream app this connection will target (for example, slack, google_sheets, hubspot). Search and select from the list of Pipedream apps.
   4. Environment: The Pipedream project environment:
      • Development: For testing and non-production scenarios
      • Production: For live production workloads
   5. Client ID: The OAuth client ID from your Pipedream workspace
   6. Client Secret: The OAuth client secret from your Pipedream workspace
   7. Project ID: The Pipedream project ID (for example, proj_ABC123)
   8. Webhook URI: The callback URL used by Pipedream to post events (auto-generated by Leena AI)
5. Save the configuration
   1. Click Connect to validate the credentials and establish the connection
   2. For User OAuth connections, each end user will be prompted to authorise their own downstream account the first time an action runs on their behalf
   3. Once validated, the connection will be saved and the available actions for the selected app will be dynamically loaded

Actions

Unlike static connectors, the Pipedream API connector exposes actions dynamically based on the Pipedream app selected during connection setup. When the connection is saved, Leena AI fetches the list of supported actions for that app from Pipedream, along with the configurable parameters for each action. Leena AI then auto-generates the input form for each action so your builders can use them in workflows without additional configuration.

For example:

• A connection configured with App Name = slack exposes Slack actions such as sending messages, creating channels, and updating user status
• A connection configured with App Name = google_sheets exposes Google Sheets actions such as adding rows, updating cells, and creating worksheets
• A connection configured with App Name = hubspot exposes HubSpot actions such as creating contacts, updating deals, and adding notes

To view the full list of apps and their supported actions, refer to the Pipedream app catalog at https://pipedream.com/apps.

Common Use Cases

The Pipedream API connector can be leveraged by Leena AI Orchestrator/Agent to automate a wide range of cross-system workflows. Here are some common use cases:

• IT Service Management: Create, update, and close tickets in Jira, ServiceNow, Zendesk, or Freshservice based on employee queries
• HR Automation: Push onboarding tasks to Asana, Monday, or ClickUp; sync employee data with HCM systems
• Communication Workflows: Send notifications to Slack, Microsoft Teams, or Gmail when specific events occur in other systems
• CRM Updates: Create contacts, deals, or notes in Salesforce or HubSpot from employee-submitted information
• Document Management: Create or update files in Google Drive, Notion, Confluence, or SharePoint
• Data Capture: Append rows to Google Sheets, Airtable, or databases for auditing and reporting

Action Structure

Every dynamically-loaded action follows a common structure when configured in Leena AI:

Input Parameters

The input parameters for each action are defined by the selected Pipedream app and are fetched at runtime. Leena AI renders these as a form, with mandatory and optional fields derived from the Pipedream action's configurable properties.

Mandatory

Optional

Response

Upon successful execution, the action returns the response payload from the downstream Pipedream app, which typically includes:

• Resource ID of the created, updated, or retrieved entity
• URL to the resource (where applicable)
• Execution status and timestamp
• Full response object from the downstream API

Best Practices

• One connection per app: Configure a separate Pipedream API connection for each downstream app your agents need to interact with
• Choose OAuth mode carefully: Use Admin OAuth for system-level automations and centralised auditing; use User OAuth when the action must respect individual user permissions and data access scopes
• Separate environments: Use the Development environment for testing new workflows, and Production for live deployments to ensure isolation of credentials and logs
• Rotate secrets regularly: Rotate your Pipedream OAuth client secret periodically and update the connection in Leena AI to maintain security posture
• Least privilege: When creating downstream OAuth apps (for example, a Google Cloud OAuth client for Gmail actions), grant only the scopes required for your workflows
• Monitor usage: Track action executions in both Leena AI logs and the Pipedream project dashboard to maintain observability across the integration chain