Hello n8n Community,
I’m encountering a persistent 401 error (“The provided API key is invalid”) when using the Creatomate API within an n8n workflow hosted on Google Cloud Services with my custom domain. Despite generating and verifying a new API key, ensuring the domain is correctly configured in both n8n and Creatomate, and confirming that my Google Cloud setup (including necessary APIs and credentials) is not interfering, the issue remains unresolved. The “Merge - Creatomate” node in my workflow sends a POST request to https://api.creatomate.com/v1/renders with a valid JSON body (including template_id and modifications), but the authorization fails with a 401 status code. I’ve tried setting the API key as a Bearer token in the Authorization header via the “Specify Headers” option, yet the error persists. I’m using the latest n8n version and have cleared executions, but no luck. Could anyone suggest what might be wrong with my node configuration or headers? I’d be happy to share my node setup or logs if needed.
Thanks in advance for your help!
hello @mopatirhys, welcome to the 
community!
I’d like to share my HTTP node. I’ve worked with Creatomate in the past and thought this might help with your issue.
Basically, I send the API key in the header like this:
Feel free to test this node setup and let me know if it’s still not working.
hello @mohamed3nan i tried that setup but the error still remains
Are you sure there are no extra spaces or characters when you paste the API Key?