We run several client automations on n8n hosted on Railway. It's quick to set up, it's cheap, and backups are easy. But one thing cost us an afternoon: our email nodes kept timing out, with no useful error.

The reason is that, when we hit it, Railway blocked outbound SMTP on its lower plans, so any workflow that sends mail through an SMTP server simply couldn't connect. Moving up one plan didn't fix it either, because SMTP was only open on a higher tier. Check Railway's current plan rules, since these change.

It's like renting an office where the post room is locked unless you're on the premium lease: everything else works fine, but your letters never leave the building.

The fix: send email over HTTPS instead of SMTP

  1. Sign up with a transactional email service that has an HTTP API (we used Resend).
  2. Verify your sending domain by adding the DNS records it gives you.
  3. In n8n, replace the Send Email (SMTP) node with an HTTP Request node: POST to the provider's send endpoint, with the API key in a header credential and the from, to, subject and HTML in the JSON body.
  4. Send one test and check it lands in the inbox, not in spam.

Port 443 is always open, so this works on any plan.

Two more things worth knowing on Railway

  • The trial runs on a small credit, and when it runs out, everything stops, including your scheduled workflows. Put the plan on a card before a client depends on it.
  • Keep n8n's database on a volume or a managed Postgres, not inside the container, or a redeploy can wipe your workflows.

I run Arwahyn AI, an AI automation agency in Dhaka.