Connection method: Email MFA forwarding
Washington Gas requires email-based MFA verification when a login is detected from a new device or IP address. Since Nectar logs in from its own servers, the portal will send a verification code even if you don’t see an MFA prompt when logging in yourself.Why you might not see an MFA prompt. Washington Gas only triggers MFA from unfamiliar
devices. When you log in from your own computer, you may not be prompted — but when Nectar logs
in from its servers, the portal requires verification. This is expected behavior.
Setup
Start a new connection or reconnect
From Data Input > Connections, click New connection and select Washington Gas, or click Reconnect on a connection showing MFA Token Expired.
Enter your credentials
Provide your Washington Gas username and password — the same credentials you use at my.washingtongas.com/portal.
Choose MFA forwarding type
- Managed forwarding (recommended): Nectar provides a unique email. Update your Washington Gas account to send verification codes to this address.
- Customer-inbox forwarding: Keep your existing email and add a forwarding rule that sends Washington Gas verification emails to Nectar.
Set up email forwarding
For managed forwarding: Log in to Washington Gas > account settings > update the email on file to the Nectar-provided address.For customer-inbox forwarding: Create a forwarding rule in your email client for messages from Washington Gas containing verification codes.
Tips
- Triggering the first code: After you set up forwarding in Nectar, the system triggers a login attempt which causes Washington Gas to send a verification code. If you’ve set up your forwarding rule in your email client, make sure the rule is active before this step.
- Login from Nectar’s IP: Don’t be confused if you can log into Washington Gas without MFA on your device — Nectar connects from a different IP, which triggers the verification step.
Troubleshooting
| Issue | Solution |
|---|---|
| ”MFA Required” but I don’t see MFA when I log in | This is normal — MFA only triggers from new devices/IPs. Nectar needs forwarding set up to handle the code when it logs in from its servers. |
| Forwarding set up but still shows “MFA Token Expired” | Verify your forwarding rule is active and the destination address matches exactly what Nectar provided. |
| Codes arriving but connection fails | Check that your email forwarding isn’t adding extra text or modifying the message body. Some email clients add signatures or formatting that can interfere. |