Emails are not arriving

If verification, invitation, order or alert emails never show up, check the address, the spam folder, who the recipients are and the email step in your flow.

Last updated: September 30, 2026

On this page

Check the address and the recipient
Check the spam folder and your filters
If an invitation never arrives
If an automation's email never arrives
Other known issues and limits

You sent an invitation and the other person never got it; or password resets, order confirmations and connection alerts simply never arrive. Email is the only channel that leaves the panel, and there are several stops along the way: the address, the recipient rule, the spam filter and the corporate mail server. This guide checks those stops in order.

💡 Tip: In-app notifications work separately. If the bell icon at the top shows the notification but no email arrives, the problem is delivery rather than sending — which is exactly what this guide is for.

You may be seeing one of these situations:

An invitation email never arrives.
Verification or password reset emails never arrive.
Order and payment emails never arrive.

An email sent by an automation never arrives.

A concrete example: a business owner invites their new accountant to the team and the invitation never arrives. The address is spelled correctly and the invite is sitting under Pending invitations. The accountant uses a corporate address and their company's mail server quarantines automated mail from outside. Once it is released from quarantine, the invitation opens.

Resending does not help in cases like this; the email was already sent. What helps is fixing the filter on the recipient's side, or having the person sign in to the panel with that address — if they have an account, the invitation is already waiting there.

Check the address and the recipient

First make sure the email is being sent to the right place.

Open My user settings › Profile and read the address in the Email field. System emails go there.
If the address is wrong you cannot change it yourself; the screen says to contact support to change your email.
The billing email is separate. Order and invoice documents follow the Billing email under Plan and invoices › Billing details.
For invitations, check the address on Portfolio settings › Team › Pending invitations.
Connection-drop and permission-expiry alerts go only to the portfolio's owner and admins. If you are an agent or an editor, those emails are never sent to you.

Check the spam folder and your filters

An email can be sent and still not land in the inbox.

Look in the Spam / Junk folder.
On Gmail, also check the Promotions and Social tabs.
When you find it, mark it as not spam and add the sender to your contacts.
On a corporate address, ask your IT team to allowlist the sender domain.
If your mailbox is full, new mail is refused; free up space.
If you use forwarding rules, make sure a rule is not moving the email into another folder.

If an invitation never arrives

Invitations have rules of their own.

Open Portfolio settings › Team.
Find the invitation under Pending invitations and check its expiry date.
If it has expired, remove it with Cancel and send a new one.
Make sure the person signs in with that email. Opening the invite while signed in as someone else shows a message naming the invited address.
If they already have a user account on that address, the invitation is waiting in the panel the moment they sign in; they can accept it even without finding the email.
If you are told the portfolio's team limit is full, the invitation was never sent.

If an automation's email never arrives

The Send email step in a flow takes a separate route and records its own reasons.

Open the run under Automations › the automation › Logs.
Find the event saying the email was sent, or that it could not be sent.
Read the reason:
- "No valid recipient address." If the step is set to The contact's email and the contact card has no email, nothing can be sent. Add an information-collection step earlier in the flow to ask for it.
- "The email could not be sent." Delivery failed; check the address and its spelling.
- "Email cannot be sent in this environment." You see this in test runs; publish the flow and try it with a real message.
If the step uses A specific address, make sure multiple addresses are separated by commas and each one is spelled correctly.
If it uses The team (portfolio members), the email goes to the portfolio's members; confirm that list on the Team screen.

Other known issues and limits

Not every notification goes to everyone. Connection alerts go to owners and admins; plan and payment emails go to the user who owns the plan.
Emails are sent in the recipient's own language. If the person has no preferred language, the platform's default is used.
A connection-drop notification is sent once per incident. No second email goes out for the same drop, and only events from the last 7 days are covered.
Connections you cut yourself are never announced. That is deliberate; your own action does not come back to you as an email.
The low-credit warning goes only to the plan owner; see my AI credits have run out.
Bulk emails carry an unsubscribe link. If you unsubscribed earlier, you will not receive that list again.
In-app notifications are independent of email. The list behind the bell icon at the top shows the same events, so you can follow urgent alerts there even when email is delayed.

If you have followed every step and the problem continues, contact our Support team.

Was this article helpful?