Connecting N8N with Bling through their API

Hello, recently I was trying to connect n8n with a API form Bling (it’s used to save data about store products, payment, shipment, etc). And Bling is now using it’s V3 version of it’s API, which requeries to use oauth2. I put all the credentials asked on n8n that I could find, client_id, client_secret and a authorization_URL that it seems to be working, but when I give authorization I received the following error: “Something went wrong, try again later!”

After reading Bling documentation, I saw that the example they use is for supported extensions on their stores, so my theory is that there is something wrong on the redirect_url from n8n.

Can anyone tell me if Bling is compatible or not with Bling? Or what I could be doing wrong?

Edit.: Okay, it’s possible this error screen is irrelevant, as all I need is a code from the url so I can get the access_token, which I did, the issue is. When I put the access code on the n8n header in a http request. It keeps saying I need a access code to log in, as if I didn’t one.

image

  • I tried it this way and putting the Bearer where Authorization is.

image

  • n8n version: 1.64.3
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • **Running n8n vian: 8n cloud
  • Operating system: Windows

It looks like your topic is missing some important information. Could you provide the following if applicable.

  • n8n version:
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app):
  • Operating system:

Hey @braia_ia , you mentioned you created credentials for Bling API. Do you happen to use both at the same time now - the node built-in authentication and the header authentication?

Hello, I’m afraid it has been a long time and I no longer remember what was done, I also no longer have this specific workflow anymore, my apologies.

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.