Error using api request action for Productboard

Hi @SD Admin 

For us to have more info, post these:

• screenshots showing how your Zap step is configured in EDIT mode so we can see the field mappings
• link to the app API endpoint documentation you referenced to configure the API request in the Zap step

Hi @SD Admin! 👋 

Were you since able to get this sorted on your own? If you did, we’d love it if you could share some details on how you solved it so others in the Community can give that a try too! 🙏

And if not, we’re happy to help further! API Requests use the authentication details for the connected account so there’s no need to add any authorization headers to the set up of the request. 

Looking at the screenshot you sent it appears you might be trying to use ProdcutBoard’s Retrieve company endpoint, is that right? If so, it could be the lack of a company ID in the URL that’s causing an issue as they’re expecting to have the ID included at the end:

Hope that helps to get you pointed in the right direction if you’re still stuck. Would love to hear how you’re getting on so please keep us updated on how things are going on this!

Hello,

I am having the same problem where the API Request (beta) action is not working rather I add an authentication header or not.
 

I am getting this error:

Response Data Message: Bad token; invalid JSON

When I try the same call using curl on my laptop, it works:

curl --location --request GET https://api.productboard.com/products  --header 'X-Version: 1' --header 'Authorization: Bearer <my token>'
{"data":[{"id":"5f64c….}

Also note that the native Create feature action works just fine.

I believe this API Request (beta) action is broken. Could you fix it please :) ?
Thanks!

Thanks so much for reaching out here @gitguardian! 🙂

Hmm, if the same set up is working on a Custom Action, as well as when you do a curl request, then you could well right about something being broken with the API Request for Productboard. I’d recommend reaching out directly to our Support team to flag these “Bad token; invalid JSON” errors. They’ll be able to dig into the error logs for your Zap to confirm whether it is broken and if it is, they’ll open up a bug report so it can be investigated further and fixed.

Please do keep us in the loop on how you get on with them, keen to ensure this gets sorted! 

@SD Admin - given the above, it might be worth rebuilding it as a Custom Action in case that gets rid of the error for you as well. Can you give that a try and let us know if that works as hoped? 🤞

Hi, ​@SamB! 

I’m having the same issue. It seems that the API request (Beta) is not working properly for ProductBoard. Even if I try the most straightforward thing (I.E. retrieve list of components), it will return the same error mentioned above. 

The "create feature” action does work, but that’s about it. The API Request (beta) and custom actions authentication are not working. 

I have tried adding with and without including version, playing around with the quotes  “ ‘ “, but nothing.  

Thanks!