PipedreamHQ/pipedream

[COMPONENTS] Migrate Copper components to use access token instead of API Keys

Open

#20814 opened on May 7, 2026

View on GitHub
 (0 comments) (0 reactions) (1 assignee)JavaScript (7,438 stars) (5,305 forks)batch import
actionenhancementgood first issuehelp wantedtrigger / source

Description

Is there a specific app this action is for? Copper https://pipedream.com/apps/copper

Please provide a link to the relevant API docs for the specific service / operation. https://developer.copper.com/index.html

Additional context Copper supports the OAuth 2.0 authentication method and the Pipedream app for Copper has been migrated to use it. Need to update Copper app file so that the the access token is used to access the API endpoints required by components. The $auth variable now features the oauth_access_token property for the access token.

Contributor guide

Tech stack
javascriptnodejs
Domain
authenticationapi
Issue type
refactor
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.
active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
JavaScriptNode.jsOAuthPipedream components
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50
Research direction
Examine the Copper app component in the Pipedream repository, likely located in components/copper/. Update the authentication logic to use the oauth access token property from $auth instead of the api key. Ensure that all API endpoints currently using the API key are switched to use the access token in the Authorization header as per the Copper OAuth docs.