PipedreamHQ/pipedream

[ACTION] Integrate Pipedream Connect with our Lovable App

Open

#17,393 opened on Jul 2, 2025

View on GitHub
 (1 comment) (0 reactions) (0 assignees)JavaScript (5,305 forks)batch import
actionenhancementgood first issuehelp wantedquestiontriaged

Repository metrics

Stars
 (7,438 stars)
PR merge metrics
 (Avg merge 9d 7h) (131 merged PRs in 30d)

Description

Description

We need to integrate Pipedream Connect with our Lovable App to allow users to securely connect and manage third-party services (e.g., Gmail) via managed OAuth.

Requirements:

Implement both Connect Token (popup/iframe) and Connect Link (redirect) authentication flows as per Pipedream Connect documentation.

Ensure backend securely generates Connect tokens and handles API calls using the correct Pipedream OAuth client credentials (Client ID, Client Secret, Project ID).

Store connection metadata in our database and handle connection status updates via webhooks.

Provide clear user feedback for successful and failed connections in the UI.

Follow security best practices for environment variable management and error handling.

References:

Pipedream Connect Overview

Managed Auth Quickstart

Example App (Next.js)

Acceptance Criteria:

Users can connect/disconnect their Gmail (and other supported) accounts through the Lovable App UI.

Connection status is accurately reflected and updated in the app.

All secrets and credentials are managed securely.

Errors are logged and surfaced for troubleshooting.

Contributor guide

Research direction
Review the Pipedream Connect documentation to understand the token and link flows. Implement backend endpoints for generating Connect tokens and handling webhooks. Integrate the frontend popup and redirect flows. Ensure secure storage of OAuth credentials and environment variables.
Tech stack
javascriptnodejs
Domain
full stackapi
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
JavaScriptOAuthwebhooks
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60