PipedreamHQ/pipedream

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

Closed

#20,814 opened on May 7, 2026

View on GitHubContributor guide
 (0 comments) (0 reactions) (1 assignee)JavaScript (5,305 forks)batch import
actionenhancementgood first issuehelp wantedtrigger / source

Repository metrics

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

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

Research direction
Update the Copper app file to use the oauth access token property from $auth for API calls instead of API keys. Ensure all components using Copper authenticate with OAuth.
Tech stack
javascript
Domain
api
Issue type
Refactor
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
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
JavaScriptOAuth
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70