Completion Notifications (Email, Slack, Chatwork)
Get notified when an article is finished or when generation fails
No need to keep checking the admin screen
When automatic generation is running, you have no way to notice when an article is done. Setting up notifications for completions and failures under "Settings > Notifications" makes day-to-day operation much easier.
When you're notified
| Item | Setting key | Details |
|---|---|---|
| When generation completes | nt_on_done | Notifies you when an article is finished |
| When held by quality review | nt_on_held | Notifies you when an article falls below the passing line and is held |
| When generation fails | nt_on_failed | Notifies you when generation ends in an error |
| Include manual runs too | nt_manual_too | Whether to also notify for articles you triggered by hand |
When running fully automated, the worst outcome is generation sitting broken for days without you noticing. We recommend enabling at least nt_on_failed.
Where notifications go
| Item | Setting key |
|---|---|
| Use email notifications | nt_email_enabled |
| Recipient | nt_email_to |
Leave the recipient blank and notifications go to the WordPress admin email address.
When email doesn't arrive (SMTP settings)
By default, email is sent directly from the server's PHP. It's convenient, but this method has a weakness: since there's no way to verify the sender is genuine, receiving services like Gmail can silently discard it. The server considers the message "sent," so no error appears. You're left with mail that was sent but never arrived.
Press "Send test" and Sorabun shows you which method actually sent it (PHP's mail() function, or SMTP) along with the sender address. If it shows "PHP's mail() function" and mail still isn't arriving, this is where SMTP settings come in.
| Item | Setting key |
|---|---|
| Send via SMTP | nt_smtp_enabled |
| Server hostname | nt_smtp_host |
| Port number | nt_smtp_port |
| Encryption | nt_smtp_secure |
| Username | nt_smtp_user |
| Password | nt_smtp_pass |
| Sender address | nt_smtp_from |
| Sender name | nt_smtp_from_name |
Sending through your email service's SMTP authenticates the message as coming from that service, so receiving servers trust it and deliver it.
| Service | Server hostname | Port | Encryption |
|---|---|---|---|
| Gmail | smtp.gmail.com | 587 | TLS |
| Outlook | smtp-mail.outlook.com | 587 | TLS |
| SendGrid | smtp.sendgrid.net | 587 | TLS |
If the sender address doesn't match the SMTP account, most services will refuse to send the message at all. If you're using Gmail, your normal login password won't work. Issue an "app password" from your Google account and use that instead.
The password is stored encrypted and used only when sending mail. Save your settings, then try "Send test."
Slack
| Item | Setting key |
|---|---|
| Use Slack notifications | nt_slack_enabled |
| Webhook URL | nt_slack_webhook |
Create a Slack Incoming Webhook and paste its URL here.
Chatwork
| Item | Setting key |
|---|---|
| Use Chatwork notifications | nt_chatwork_enabled |
| API token | nt_chatwork_token |
| Room ID | nt_chatwork_room |
The room ID is the number after rid at the end of the Chatwork room URL.
When notifications don't arrive
- Email: First press "Send test" to check which method is being used. If it shows "PHP's mail() function," the SMTP settings above resolve it in most cases. Also check your spam folder.
- Slack / Chatwork: Check whether your webhook URL or token has expired. Nothing will send if the server is blocking outbound connections.