Mark MarchandFounder of Seawalker Tech. Helps associations streamline Nimble AMS operations and deliver outstanding membership and event experiences.
Do not index
You set up Community Hub, configured your order confirmation email template, and everything looks great. Then you generate a test order and... nothing.
No confirmation emails. No error messages. Just silence.
If you've been there, you're not alone. Email deliverability issues in Nimble AMS Community Hub are one of the more common support requests I see.
Here's what I do to track down the problem every time.
Check Your Package Settings
Open your Nimble AMS package settings and look at the
Email Confirmation Template field.If your org uses a custom Classic Email Template, it will be listed here. If it’s a picklist that reads
Default or is a blank text field, it will use the OOTB Nimble AMS Order Confirmation Classic email template. Verify that this field points to the right template.Review the Template
Make sure the email template can actually render. This sounds obvious, but I've seen it trip up experienced admins more than once.
Try generating the template using its NUTPLX (NUTPL Extensions) wrapper. For order confirmations, that means going to an actual order record and clicking the
Order Confirmation* action/button. If the template throws an error here, it'll never send automatically either.If the template can't render in context, no amount of configuration changes elsewhere will fix it.
The Chatter Email Settings Gotcha
This one can catch admins off guard.
Despite the name,
Chatter Email Settings don’t just control Chatter notifications. It also controls emails triggered by Nimble Create — including order confirmation emails. If Allow Emails is set to FALSE, your confirmation emails simply won't send. No error, no log entry, just nothing.Guest User Permissions
If your emails are triggered by actions from guest users (which is common for public-facing event registrations or membership applications), there's an additional layer of complexity.
Guest users need specific permissions to send Visualforce emails. Without them, you'll often see an "invalid cross reference id" error buried in your flow error emails. The fix involves configuring Classic Email Template permissions correctly for the guest user profile.
Wrapping Up
Email deliverability in Nimble AMS Community Hub isn't necessarily complicated, but the failure points are relatively numerous and the failure modes are silent — the system doesn't tell you why an email didn't send, it just... doesn't send it.
The areas I've outlined above are just a few of the places things can go sideways, and the interactions between them are where it gets really tricky.
If you're running into email issues and can't track down the root cause, reach out to us. We've debugged this enough times that we can usually pinpoint and fix the problem in a single call.
Written by
Mark Marchand
Founder of Seawalker Tech. Helps associations streamline Nimble AMS operations and deliver outstanding membership and event experiences.