Hi everyone, I'm trying to build my first workflow in Relevance AI that uses our own internal API. The goal is to enrich customer data from our HubSpot forms with some additional scoring from our custom system.
I've set up a "Custom Tool" and configured the endpoint URL, method (POST), and headers. I'm pretty sure my request body formatting is correct, as I've tested the same call in Postman and it works fine. The problem is authentication. Our API uses a Bearer token, which I've added to the Authorization header in the tool configuration.
Despite this, the workflow step consistently fails with a 401 error. I've double-checked that the token is correct and hasn't expired. Is there something specific about how Relevance AI handles headers or makes the outbound call that I might be missing?
For context, in other platforms I've used (like Make or Zapier), there's sometimes a dedicated auth section for OAuth or API keys, rather than just a headers field. Do I need to format the token differently within the Relevance AI custom tool? Maybe as `Bearer {my_token}` in a single field, or is there a secret manager I should use instead of putting it directly in the header configuration?
Any guidance from someone who's successfully connected a private API would be really appreciated. I'm excited to get this working, as it seems like a powerful way to bridge our tools.