n8n is an open-source workflow automation tool. When a workflow registers accounts or verifies emails, the missing piece is receiving the OTP.

The Problem with Gmail in n8n

Most n8n users try to connect Gmail via OAuth and poll for new messages. That runs into Gmail's rate limits on IMAP connections, and a shared inbox mixes test and production emails. You also cannot isolate OTPs per workflow run, so workflows running at the same time collide.

A Better Approach: Lumbox API in n8n

Lumbox gives each workflow run its own inbox address. Here is the pattern:

  1. HTTP Node (POST): Call POST /v1/inboxes to create a temporary inbox like run-abc123@lumbox.com.
  2. Use the address: Fill in your signup form with that inbox address.
  3. HTTP Node (GET): Call GET /v1/inboxes/{id}/otp?timeout=60. This long-polls for up to 60 seconds and returns the code the moment it arrives.
  4. Done: Use the OTP in the next step. Delete the inbox if you want cleanup.

n8n HTTP Request Node Config

For the OTP wait node, set the method to GET, the URL to your Lumbox endpoint, and add your API key as an X-API-Key header. The node will wait until the response arrives. No polling loop, no sleep nodes, no custom code.

Parallel Runs

Because each workflow run creates its own inbox, you can run hundreds of workflows in parallel without OTP collisions. Each run gets exactly one inbox and exactly one OTP.

Get Started

Create a free account at lumbox.com, grab an API key, and add the HTTP nodes described above. You will have a working OTP workflow in under 10 minutes.