Issue when hosting n8n on Heroku with domain

Describe the problem/error/question

Hi everyone!
I have two major issues with my n8n account that seems to be due to the same reason :

  1. I have set-up a Lemlist trigger but it doesn’t work (whereas it does when I use n8n cloud or install n8n locally). After investigating, it seems that the webhook generated by n8n (my-website.herokuapp.com/etc.) is not the same than the URL generated by Heroku when I created my app (Heroku automatically added 12 characters after “my-website” = my-website-9aacd26bbc60.heroku.com)

  2. I try to send the information to BigQueery, but here again I have the issue when setting up the OAuth when redirecting after connection because the redirect URL generated by n8n is not the same than my domain (my-website.heroku.com (image 1) vs my-website-9aacd26bbc60.heroku.com (image 2)). In this example, the URL order is even different before the random characters.

I have checked on Heroku help center and it seems that since 2023 they automatically add the 12 characters by default (cf image 3). It doesn’t explained however why my URL changed (image 1 & 2) So how can I handle this in n8n?

Thanks a lot for your help!

What is the error message (if any)?

Heroku after callback with Google OAuth : There’s nothing here, yet.

Please share your workflow

Information on your n8n setup

  • **n8n version:1.50.2
  • **Running n8n via (Docker, npm, n8n cloud, desktop app):Heroku
  • **Operating system:MacOS



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:

Hi @AhCH

Thanks for posting here and welcome to the community! :tada:

Have you set the heroku URL in your WEBHOOK_URL variable?

You can read more about environment variables here:

1 Like

Hi @ria, thanks a lot for your answer!
Finally I decided to do it with DigitalOcean and it worked perfectly :slight_smile:

Best,
Arnaud

1 Like

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