Issues in the Retool Agents App

💬 Agents
1

  1. My goal:
    I am following the Retool Agents lab but have encountered several issues in the process. Please see if you can advise the required steps.

  2. Issue:

(a) Unable to connect to the resources of AWS Lambda – Call Transcripts via https://9z1qea8sjk.execute-api.us-east-2.amazonaws.com/openapi.json. A firewall error has been returned.

(b) Unable to build custom tool for connecting to Linear
I have successfully add the Linear resource to the App. However when I try to run the workflow, it return the error of "Bearer OAUTH2_TOKEN is not a legal HTTP header value"

  1. Steps I've taken to troubleshoot:
    I have tried to read different API documentation but unable to resolve the issues.

  2. Additional info: (Cloud or Self-hosted, Screenshots)
    Cloud Instance.

2 Likes
3

Hi @jaydenip,

Apologies for the issue. Let me see if I can help troubleshoot.

(A) Have you been able to connect with this AWS resource in the app outside of the Agent tool? Can you share a screen recording of the creation of this tool and the error message?

(B) That is very odd that the Linear resource is connecting in the app but that the agent is somehow not able to pass the auth token when making the request :thinking: I would also love to see a screen recording of the tool creation and error.

We may need to have you hop into our office hours to do further testing and to debug.

4

Hi @jaydenip,

I believe that for (B) since the workflow is being run by the agent and not a human, that the agent is not able to auth in using OAuth2 as that security protocol requires a human to be involved in authing in successfully so that Bearer OAUTH2_TOKEN can be assigned to the returned token's value from the auth flow.

As the error message would indicate that the filler variable is being passed as is and not being replaced with a token since automated workflows can't auth in. The way around this would be to remove OAuth from that linear resource.

My hunch is that for issue (A) there may be some configurations for the AWS firewall that is preventing the Agent from using the Lambda.

5

Hi @jaydenip,

Just wanted to circle back and check if you are still facing both issues A and B. I was curious if you had gotten a chance to test out the resource without OAuth and if you had found any firewall settings that were preventing the requests from reaching the Lambda.