This topic was automatically generated from Slack. You can find the original thread here.
Hey @U03EGTE5WC8, I’m currently trying to use the Connect Proxy to make an authenticated request to Asana but getting a 401 unauthorised for a custom tool that I want to implement. I’ve verified that the authentication for the account works with existing Pipedream components (e.g. asana-create-project ), was wondering if this is a problem with the Bearer token being passed in incorrectly or somehow mismanaging the token.
Here’s the full output ```
Error: Status code: 401
Body: {
“errors”: [
{
“message”: “Not Authorized”,
“help”: “For more information on API status codes and how to handle them, read the docs on errors: Errors”
}
]
}
❯ Proxy. node_modules/.pnpm/@pipedream+sdk@2.2.0/node_modules/@pipedream/sdk/dist/esm/api/resources/proxy/client/Client.mjs:91:31
❯ fulfilled node_modules/.pnpm/@pipedream+sdk@2.2.0/node_modules/@pipedream/sdk/dist/esm/api/resources/proxy/client/Client.mjs:5:58