Gmail to Mailjet, Netflix codes forwarded instantly
That “Netflix sign-in code” email always arrives at the wrong time. You’re away from your phone, someone’s waiting, and you end up digging through Gmail like it’s a scavenger hunt.
This Gmail Mailjet forwarding setup is a lifesaver for busy parents managing family accounts, small teams sharing a company subscription, and agency owners who just want the code to land where it needs to. No more texting screenshots. No more “did it come through?”
You’ll set up an automation that watches your Gmail for Netflix emails, then forwards them through Mailjet to a pre-approved list. Here’s what it does, what you need, and how it behaves in the real world.
How This Automation Works
Here’s the complete workflow you’ll be setting up:
n8n Workflow Template: Gmail to Mailjet, Netflix codes forwarded instantly
flowchart LR
subgraph sg0["Gmail Inbox Watcher Flow"]
direction LR
n0@{ icon: "mdi:play-circle", form: "rounded", label: "Gmail Inbox Watcher", pos: "b", h: 48 }
n1@{ icon: "mdi:swap-vertical", form: "rounded", label: "Assign Recipient List", pos: "b", h: 48 }
n2@{ icon: "mdi:swap-vertical", form: "rounded", label: "Expand Recipient Rows", pos: "b", h: 48 }
n3["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/mailjet.svg' width='40' height='40' /></div><br/>Mailjet Dispatch Email"]
n0 --> n1
n1 --> n2
n2 --> n3
end
%% Styling
classDef trigger fill:#e8f5e9,stroke:#388e3c,stroke-width:2px
classDef ai fill:#e3f2fd,stroke:#1976d2,stroke-width:2px
classDef aiModel fill:#e8eaf6,stroke:#3f51b5,stroke-width:2px
classDef decision fill:#fff8e1,stroke:#f9a825,stroke-width:2px
classDef database fill:#fce4ec,stroke:#c2185b,stroke-width:2px
classDef api fill:#fff3e0,stroke:#e65100,stroke-width:2px
classDef code fill:#f3e5f5,stroke:#7b1fa2,stroke-width:2px
classDef disabled stroke-dasharray: 5 5,opacity: 0.5
class n0 trigger
classDef customIcon fill:none,stroke:none
class n3 customIcon
Why This Matters: Netflix Codes Get Lost in the Shuffle
Netflix login codes are time-sensitive, and they always show up when someone is already stuck on the sign-in screen. If the code lands in one person’s Gmail, everyone else is suddenly blocked until that person finds it, copies it, and forwards it. Sounds small. In practice, it’s constant friction: missed notifications, spam/promotions tabs, and threads that get buried under real work emails. It also creates awkward “Can you send it again?” follow-ups that waste attention and slow everyone down.
It adds up fast. Here’s where it breaks down most often.
- You end up searching Gmail for “Netflix” while someone waits, then the code has already expired.
- Forwarding manually is inconsistent because people forget, get distracted, or simply don’t see the email in time.
- Group chats turn into a messy workaround, with screenshots and partial codes that create more confusion than clarity.
- Sharing passwords feels “done,” until Netflix forces verification and the whole system falls apart again.
What You’ll Build: Automatic Netflix Email Forwarding from Gmail
This workflow watches your Gmail inbox for new messages from Netflix, checking every minute. When a matching email arrives (including temporary login codes), it immediately prepares a clean recipient list you control inside n8n. Then it sends the email out through Mailjet to each approved recipient, one-by-one, so everyone gets the exact same message without you lifting a finger. The result is simple: Netflix emails stop being “owned” by one person’s inbox and become instantly available to the people you trust.
The workflow starts with a Gmail trigger that scans for new Netflix emails. Next, it assigns your recipient list and expands it into individual sends. Finally, Mailjet dispatches the forwarded message to each recipient reliably, without you copying content or managing threads.
What You’re Building
| What Gets Automated | What You’ll Achieve |
|---|---|
|
|
Expected Results
Say your household sends Netflix codes to 4 people. Manually, the “owner” of the inbox typically spends about 5 minutes finding the email, copying the code, and forwarding or texting it (and another few minutes when someone misses it). That’s easily 20 minutes of back-and-forth every time Netflix asks to verify. With this workflow, Gmail checks every minute, Mailjet forwards automatically, and the only “work” is adding or removing recipients, which takes maybe 1 minute when it changes.
Before You Start
- n8n instance (try n8n Cloud free)
- Self-hosting option if you prefer (Hostinger works well)
- Gmail as the inbox that receives Netflix emails.
- Mailjet to send forwarded emails to recipients.
- A verified sender address inside Mailjet (ideally a custom domain email).
Skill level: Beginner. You’ll connect Gmail and Mailjet, then paste a list of recipient emails into one node.
Want someone to build this for you? Talk to an automation expert (free 15-minute consultation).
Step by Step
Gmail watches for Netflix messages. The workflow runs on a schedule and scans your inbox every minute for new emails from Netflix. When it sees one, it pulls the email content into the workflow so it can be forwarded.
Your approved recipients are applied. In the “Assign Recipient List” step, you maintain a simple array of email addresses. This is the guardrail: only the people you add here get Netflix emails.
The list is expanded into individual sends. The workflow splits the array into separate recipient rows. That keeps sending predictable, and it plays nicely with email providers that expect one recipient (or small groups) per message.
Mailjet forwards the email. Mailjet sends the Netflix email out to each recipient. Because it’s handled by an email provider, delivery is typically faster and more consistent than manual forwarding from a phone.
You can easily modify the recipient list to add family members, remove old addresses, or route certain Netflix emails differently. See the full implementation guide below for customization options.
Step-by-Step Implementation Guide
Step 1: Configure the Gmail Trigger
Set up the workflow to watch your Gmail inbox for matching messages.
- Add the Gmail Inbox Watcher node as your trigger.
- Credential Required: Connect your gmailOAuth2 credentials.
- Set Sender filter to
netflix.com. - Enable Include Spam & Trash to
true. - Set Poll Times to
everyMinute.
Step 2: Connect Recipient Data
Define the list of recipients who will receive forwarded emails.
- Add the Assign Recipient List node after Gmail Inbox Watcher.
- In Fields, add recipients as an array and set the value to
['[YOUR_EMAIL]','[YOUR_EMAIL]','[YOUR_EMAIL]'].
Use real recipient addresses in the array so the split step can generate individual outgoing messages.
Step 3: Set Up Recipient Expansion
Split the recipients array into individual items so each email is sent separately.
- Add Expand Recipient Rows after Assign Recipient List.
- Set Field To Split Out to
recipients. - Set Include to
allOtherFields. - In Options, set Destination Field Name to
recipient.
Step 4: Configure the Mailjet Output
Send the forwarded content to each recipient using Mailjet.
- Add Mailjet Dispatch Email after Expand Recipient Rows.
- Credential Required: Connect your mailjetEmailApi credentials.
- Set HTML to
={{ $json.html }}and Text to={{ $json.text }}. - Set Subject to
={{ $json.subject }}. - Set To Email to
={{ $json.recipient }}. - Set From Email to
[YOUR_EMAIL].
⚠️ Common Pitfall: If the incoming Gmail data does not contain html, text, or subject, the outgoing email may be blank. Verify the Gmail message fields during testing.
Step 5: Test and Activate Your Workflow
Verify the end-to-end flow and enable the automation.
- Click Execute Workflow and send a test email from
netflix.com(or adjust the filter to match your test sender). - Confirm that Expand Recipient Rows produces one item per recipient with a
recipientfield. - Check Mailjet logs to confirm Mailjet Dispatch Email sent one email per recipient.
- When the test passes, toggle the workflow to Active for production use.
Troubleshooting Tips
- Gmail credentials can expire or lose permissions. If nothing triggers, check your n8n Gmail credential status and confirm the Gmail account is still connected.
- Mailjet will not let you use a Gmail address as the sender in many setups. Verify your sender identity inside Mailjet first (a custom domain address is the easiest path).
- If the recipients array is empty or has a typo, the Split/Send sequence can behave strangely. Double-check the “Assign Recipient List” node for commas, quotes, and valid email formats.
Quick Answers
About 20 minutes if your Gmail and Mailjet accounts are ready.
No. You’ll connect accounts and paste your recipient list into a single node.
Yes. n8n has a free self-hosted option and a free trial on n8n Cloud. Cloud plans start at $20/month for higher volume. You’ll also need to factor in Mailjet sending costs (often just a few dollars a month for low volume).
Two options: n8n Cloud (managed, easiest setup) or self-hosting on a VPS. For self-hosting, Hostinger VPS is affordable and handles n8n well. Self-hosting gives you unlimited executions but requires basic server management.
Yes, and it’s straightforward. You can filter for other senders (like Netflix + billing emails) by adjusting the Gmail trigger query, and you can swap the recipient array in the “Assign Recipient List” node to route messages to different groups. Some people maintain separate workflows per service (Netflix, Hulu, Disney+) so the right household members get only what they need. You can also change the Mailjet sender and subject formatting to make the emails easier to spot.
Most of the time it’s sender verification or permissions. Confirm your Mailjet API key is correct in n8n, then check that your sender address is validated in Mailjet (Gmail addresses are often rejected). If you recently changed your Mailjet plan or settings, recheck limits and account status, because Mailjet may block sending until those are resolved.
For Netflix emails, plenty.
Often, yes, especially if you want control and predictable costs. n8n is comfortable with multi-step logic (like splitting a recipient array into individual sends) without pushing you into higher tiers. You can also self-host, which means you’re not paying per task the same way. Zapier or Make can still be a fine choice for a simple “forward to one address” setup, but this workflow is built to handle a proper approved list. If you want a second opinion, Talk to an automation expert.
Once this is live, Netflix codes stop being a bottleneck. The workflow handles the repetitive part, so you can get on with your evening.
Need Help Setting This Up?
Our automation experts can build and customize this workflow for your specific needs. Free 15-minute consultation—no commitment required.
