Fixing Failed to Parse Body Input Error in Relevance AI Connection

💤 You've caught us outside of our support hours (9am-9pm EST), but don't worry - we'll be back in touch within 24 hours (often sooner!). If you haven't already, please include the URL of your table in the thread below so that we can help you as quickly as possible!

Share your input body and I will help you fix

https://api-<d7b62b>.stack.tryrelevance.com/latest/agents/trigger/ Muhammad S.

i mean screenshot of your http input

what is the http input?

The input you are adding to HTTP API Integration.

...

here!

Muhammad S.

your body is bad

its not JSON

so how do i change it?

Muhammad S.

This would be your body:

{"message":{"role":"user","content":"Hello"},"agent_id":agent_id}

you will need to replace the word Hello with prompt and agent_id with your actual agent_id

I tried but I thought that my prompt is inside of Relevance AI, no?

Still no luck - can someone please help from the Clay team? here's the table link: https://app.clay.com/workspaces/227991/tables/t_bqMkH8ofSvzc/views/gv_Kq3GiU2byQY3 (HTTP API column...)

Hey Tim! Thanks for reaching out. Happy to help. I made some changes to the body input and it looks like it's now returning an undefined error from the Header, specifically for Job Description (see screenshot below). For context, the initial error was related to an issue with the JSON structure. Can you check your API documentation and confirm what the header structure should be for "Job Description"? If you can also share your API documentation, I'm happy to help. https://downloads.intercomcdn.com/i/o/1174017781/9165f54194bd6fc26c19bc76/CleanShot+2024-09-09+at+17_05_13%402x.png?expires=1725900300&signature=bb3d4d0b231dce3ed520894f17f8d83999e80dd9ccecd785051c5e914b31979d&req=dSEgEsl%2FmoZXWPMW1HO4zZyG4B8cWozAzDzglRugAwWjKBfplZVC7g6WXO%2FX%0Ac1Py%0A

Daniela D. thanks! Here's the API docs: https://relevanceai.com/docs/agent/api/conversation. My API key and authorisation code are already in the table.

Any way we can huddle about this?

Hi Tim, thanks for reaching out. Sorry this issue is persisting! Looks like the issue is caused by the <agent_id> you input here. Please double check this value and update it as needed. Here's whereyou can retrieve your agent_id. I hope this was helpful. If there's anything else I can assist you with, please let me know!

We haven't heard back from you in a bit, so we're going to go ahead and close things out here - feel free to let us know if you still need something!