PipedreamHQ/pipedream

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

Open

#20,814 建立於 2026年5月7日

在 GitHub 查看
 (0 留言) (0 反應) (1 負責人)JavaScript (7,438 star) (5,305 fork)batch import
actionenhancementgood first issuehelp wantedtrigger / source

描述

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.

貢獻者指南

技術棧
javascriptnodejs
領域
authenticationapi
議題類型
refactor
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
1-2 days
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
active
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
JavaScriptNode.jsOAuthPipedream components
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
50
研究方向
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.