learndash/delete-notification deletes a notification email. It requires confirm_title matching the current subject.
Trashing achieves the same effect reversibly.
Before you run it
Future sends stop immediately. Emails already sent are unaffected and no learner data is touched, which makes this one of the mildest destructive operations here — the loss is the notification’s own content and configuration. force=false trashes it, and a trashed notification does not send either, so trashing is usually what you want.
At a glance
| Ability | learndash/delete-notification |
| Toolset | LearnDash — toolset/learndash |
| Group | LearnDash › Notifications |
| Requires | AcrossAI Pro, plus LearnDash LMS active on the site |
| Capability | manage_options |
| Safety | Destructive — requires confirm_title. Future sends stop; no learner data is touched. |
| Repeatable | Not idempotent — each call changes the row set, so re-running is not a no-op |
| Ships in | AcrossAI Pro 0.9.16 and later |
How it works
A trashed notification does not send. So if the goal is to stop an email going out, trashing does it and keeps the content — which makes the permanent option rarely necessary.
What permanent deletion loses is the body and the configuration: the wording somebody wrote, the shortcodes they chose, the trigger and scope and delay they worked out.
On a site with a carefully built notification sequence that is real work, and there is no copy anywhere.
No learner data is affected. Emails already sent stay sent, and nothing about anybody’s progress or enrolment changes.
The silent consequence is on the receiving end: whoever was getting this email stops getting it, and nothing tells them. For an administrator notification about assignments needing marking, that means assignments quietly piling up.
Not idempotent.
Input
| Name | Type | Required | What it is |
|---|---|---|---|
notification_id | integer | Yes | The notification. |
confirm_title | string | Yes | Must exactly match the current title on the live record. |
force | boolean | No | True deletes permanently; false trashes and still stops sends. |
confirm | boolean | Yes — must be true | The irreversibility gate. Without it the call is refused before anything is touched. |
What comes back
| Name | Type | What it is |
|---|---|---|
notification_id | integer | The notification. |
success | boolean | Whether the call completed. |
message | string | A one-line summary of what happened, suitable for showing a human. |
error_code | string | Present only on failure — a stable machine-readable reason, such as a missing field, a wrong field type or an unmet confirmation. |
Example
Ask your assistant:
Stop sending that reminder email.
It resolves to one call:
{
"ability": "learndash/delete-notification",
"parameters": {
"notification_id": 950,
"confirm_title": "You have finished [course_title]"
}
}Worth knowing
- Trashing stops sends too, and keeps the content.
- No learner data is touched.
- Whoever was receiving it is not told it stopped.
- An admin notification stopping means work piling up unnoticed.
Related abilities
- LearnDash Manage Notification — unpublish it instead
- LearnDash Get Notification — copy the body first
Get the plugins:
AcrossAI Abilities Manager · AcrossAI MCP Manager
Browse the rest: Every ability, by category