The no-reply sender rule
A specific SendGrid behavior worth remembering: SendGrid will not deliver an email where the From address equals the To address. It silently drops the send with no error in the automation run history.
This bites the “Send a notification email to the studio when a new lead arrives” flow.
The scenario
Section titled “The scenario”A new-lead automation typically:
- Sends a confirmation email to the lead (
To: lead@example.com). - Sends a notification email to the studio so staff are alerted (
To: studio@studio-example.com).
The natural choice for the second email’s From address is the studio’s own email — same address — because that’s the address customers typically have set up. But that means SendGrid sees From: studio@studio-example.com and To: studio@studio-example.com and drops it.
The rule
Section titled “The rule”For any internal-recipient email (sent to the studio itself), set the From address to a different address on the same domain. By convention: noreply@<studio-domain>.
For external-recipient emails (sent to leads, prospects, customers), use the regular info@ or studio email — it’s the natural reply-to.
| Recipient | Sender (From) |
|---|---|
| Lead / customer | info@studio-example.com (or whatever the studio’s main inbox is) |
| Studio itself | noreply@studio-example.com |
Configuring both senders in SendGrid
Section titled “Configuring both senders in SendGrid”In Settings → Sender Authentication → Single Sender Verification (or via the Domain Authentication flow), add both addresses:
info@<domain>— for outgoing customer mail.noreply@<domain>— for internal-recipient mail.
Both must be added in SendGrid before they can be registered on the RocketLead integration (the integration’s setup wizard reads from SendGrid’s verified-sender list — see API key + scopes for the registration step). The RocketLead integration stores them as a flat list (integrationData.emails); you can register additional senders if the studio uses more (e.g. sales@, support@).
What this looks like in RocketLead
Section titled “What this looks like in RocketLead”When configuring a Send Email node in an automation:
- The “From” field is a dropdown of senders configured for the SendGrid integration.
- For a notification-to-studio email, pick
noreply@<domain>. - For a confirmation-to-lead email, pick
info@<domain>(or equivalent).
The default templates ship with the right From already picked for each node — only customize if the studio uses different conventions.
Why SendGrid does this
Section titled “Why SendGrid does this”Silently dropping same-sender-as-recipient is SendGrid’s anti-abuse measure. The reasoning: legitimate mail almost never has the sender and recipient identical, and the pattern is common in spam-loop or backscatter attacks.
The user-facing symptom is “the new-lead notification email I expected to receive never arrived” with no error trail. The fix is always the same: change the From to noreply@.
Customer asks “Why noreply?”
Section titled “Customer asks “Why noreply?””Sometimes a customer pushes back: “Why is your platform sending email from noreply@? Customers might reply to it, and I want those replies to come back to me.”
Two responses:
- The
noreply@address is only used for internal-recipient emails — not customer-facing ones. Lead confirmations and reminders still go from the regularinfo@address. - There’s planned support for inbound email — RocketLead would receive replies to any address on the customer’s domain and thread them back to the lead’s record. Once that ships, even
noreply@becomes a viable reply target. Until then, the rule stands.
What’s next
Section titled “What’s next”- API key + scopes — how the SendGrid setup is wired back into RocketLead via the API key.
- Forms — last setup step.