FluentSMTP
FluentSMTP handles outgoing email for your WordPress site. Connect it to Advanced Form Integration (AFI) and every email your site sends, or fails to send, can trigger an automation. You can keep a delivery log in Google Sheets, send failed delivery alerts to a webhook or messaging tool, or record bounce prone recipients in your CRM.
What You’ll Need
- The FluentSMTP plugin installed, active, and configured with a mail connection
- Advanced Form Integration (free version is enough for this trigger)
- An account on the receiving platform, such as Google Sheets
How to Create the Integration
- Go to AFI > Add New.
- AFI fills in a default Integration Title. Rename it to something recognizable, such as “Failed Emails to Google Sheets”.
- In the Trigger section, select FluentSMTP from the Form Provider dropdown. FluentSMTP must be active on your site or the provider will not appear.
- In the Form/Task Name dropdown, choose the event: Email sent successfully (FluentSMTP) or Email delivery failed (FluentSMTP).
- Under Action, select your receiver platform and connect your account.
- Map the email fields to the receiver fields. For a failure log you would typically map Email Subject, Recipients, Error Message, and Event Timestamp.
- Click Save Integration.
- Send a test email from your site and check the receiver.
Available Events
- Email sent successfully (FluentSMTP): fires every time an email is delivered successfully through the site while FluentSMTP is active.
- Email delivery failed (FluentSMTP): fires when FluentSMTP fails to deliver an email and no fallback connection succeeds. This is the final failure, not a temporary retry.
Be careful with the success event on busy sites. It fires for every outgoing email, including order notifications and password resets, so the volume can be high.
Fields You Can Send
Email sent successfully
| Field | Description |
|---|---|
| Status | Always sent for this event |
| Email Subject | Subject line of the email |
| Email Body | Full message body |
| Recipients | Recipient addresses as a readable, comma separated list |
| Recipients (raw) | Recipient data as JSON |
| Headers (JSON) | Email headers as JSON |
| Attachments (JSON) | Attachment list as JSON |
| Event Timestamp | Date and time the email was sent |
Email delivery failed
| Field | Description |
|---|---|
| Status | Failure status reported by FluentSMTP |
| Email Subject | Subject line of the email |
| Email Body | Full message body |
| Recipients | Recipient addresses as a readable, comma separated list |
| Recipients (raw) | Recipient data as JSON |
| From Address | Sender address |
| Error Message | Human readable error extracted from the mailer response |
| Mailer Response (JSON) | Raw mailer response as JSON |
| Extra Data (JSON) | Extra logged data as JSON |
| Headers (JSON) | Email headers as JSON |
| Attachments (JSON) | Attachment list as JSON |
| FluentSMTP Log ID | ID of the entry in the FluentSMTP email log |
| Timestamp | Date and time of the failure |
Alert Only on Order Emails
If you only care about failed WooCommerce order emails, use conditional logic:
- Create an integration on the Email delivery failed (FluentSMTP) event.
- Enable Conditional Logic.
- Set the condition to: Email Subject contains order.
- Save the integration.
Now only failures whose subject mentions an order reach your alert channel.
Troubleshooting
FluentSMTP is not in the dropdown
Confirm the FluentSMTP plugin is active. AFI checks for FluentSMTP at runtime and skips the trigger entirely when the plugin is missing.
The integration is not firing
Check AFI > Log after sending a test email. If nothing appears, confirm FluentSMTP is actually handling your mail: open Settings > FluentSMTP and send a test from its Email Test tab. Also remember that the failure event only fires after all fallback connections have failed.
Too many entries on the success event
The success event fires for every email the site sends. Add conditional logic on Email Subject or Recipients to narrow it down, or switch to the failure event if you only need problem reports.
Error Message arrives blank
AFI extracts the error from the mailer response when FluentSMTP provides one. Some mailers return sparse responses. Map Mailer Response (JSON) as well to capture the raw data.