Overcoming Challenges: Sending JSON in Make.com

Have you ever tried to send a JSON to a certification tool like Accredible using Make.com and encountered errors? You're not alone. This is a common issue that many users face. But don't worry, we've got a solution for you.

The Problem

Everything works perfectly in Postman, but when you try to send data using the HTTP make request Module in Make.com, you keep getting a 500 error. You can receive data from Accredible, but sending data seems to be the problem.

When you send an invalid token, you get a 401 HTTP token Access denied. When you send no body, you get a 422 Can not create credential without recipient data. When you send a wrong JSON, you also get a 500 error.

The Solution

The solution to this problem is to include the access token properly. You can do this by using the format 'Bearer {token}' or 'Token token = {token}'. However, even after changing it to 'Bearer {token}', you might still get the 500 error.

Troubleshooting Tips

If you're still facing issues, try using a JSON formatter/beautify tool to fix the spacing and all. The spacing before and after the colons : and commas , makes more of a difference than having it on multiple lines. Postman prettifies the JSON by default to fix spacing, but Make.com doesn’t.

Conclusion

In conclusion, sending a JSON to a certification tool like Accredible using Make.com can be a bit tricky. But with the right access token and proper JSON formatting, you can overcome this challenge. Remember, if you're still facing issues, don't hesitate to reach out for help. There's always a solution to every problem.

You do have further questions?

Ask your question via E-Mail: Richard@make-app.de
Book a paid Support & Consulting Session
New Make.com user? Sign up through this Affiliate Link to receive 10.000 operations for FREE.