Use an automation’s Send email action to email the member who triggers an event, such as joining your community. These are marketing emails and follow the member’s email preferences.
Who can do this: Owners and admins with permission to configure or send email. · Where: Web, Admin → Automations → Rules. · Plan: Requires automations and the email feature for your community; the editor shows availability and the shared monthly email allowance.
Check automated email availability
Email actions depend on the selected trigger, permissions, platform plan, and sending configuration. The action explains what is missing. Complete your sending settings before sending a test or running the rule; configuring content and previewing may still be available before then.
The recipient is the member who triggered the event. Email actions do not target community admins, an arbitrary mailing list, or event attendees as a group. Use the supported triggers shown in your editor. Sending respects marketing subscriptions and suppression lists, and includes a system unsubscribe footer.
Write an automated email
- Create or edit a rule and add Send email.
- Enter the subject and body. Follow the displayed character and content limits, and insert only variables offered by the editor.
- Optionally use Start from a template. Applying a template replaces the subject and body after confirmation; you can undo the replacement. Later template changes do not update this copied content.
- Review the sender, reply address, and available allowance. Save the rule, leaving it off while you check it.
Email actions run independently from the trigger time, not one after another. Entry conditions are checked when the event triggers. If the standard welcome email is also enabled, a new member may receive both emails; review that warning before enabling your rule.
Preview and test an automated email
Preview email renders the message using your administrator profile for personalized values. It sends nothing, and its unsubscribe link is only a placeholder. Regenerate the preview after editing.
Send test to my email sends only to your administrator email with a Test subject. It does not run other actions or use the monthly allowance. If the result is uncertain, Retry the same test keeps the original attempt and content; Send a new test starts another test using the current content. Follow any cooldown shown and inspect the test’s delivery status.
The rule’s ordinary Test rule remains a dry run and does not send real email. Use the email action’s administrator test to check an actual message.
Enable or manually run an email automation
After reviewing the email, save and enable the rule for future matching events. Run now runs the entire rule and sends real marketing email, so select a member and review every action first. Email rules require a selected member for a manual run; they cannot use an anonymous sample recipient.
Real sends use the shared monthly allowance and current sending eligibility. A member who has unsubscribed, lacks a usable address, or has a suppressed address may be skipped. Changing the rule or disabling it affects pending actions as explained in the automation guide.
Review automated email delivery and recovery
Open an execution log and inspect Email delivery. The rule’s run result and the email’s delivery result are separate. Accepted by email service; delivery unconfirmed means the email service accepted the message; it does not confirm delivery. The status can also show delivery, a bounce, complaint, suppression, cancellation, failure, or an uncertain result.
Refresh the log to check the latest result. Already accepted emails are not submitted again when rerunning. Recovery is available only when the service confirms that the delivery can be retried. Fix sending settings, allowance, or recipient issues first; an uncertain delivery result is not a reason to start another send blindly.
Related articles
Was this guide helpful?