learndash/get-notification fetches a single notification: its subject, its raw email body, the trigger that fires it, the recipient, the scope and the send delay.
The body is returned unrendered.
At a glance
| Ability | learndash/get-notification |
| Toolset | LearnDash — toolset/learndash |
| Group | LearnDash › Notifications |
| Requires | AcrossAI Pro, plus LearnDash LMS active on the site |
| Capability | manage_options |
| Safety | Read-only — changes nothing |
| Repeatable | Idempotent — running it twice leaves the same result |
| Ships in | AcrossAI Pro 0.9.16 and later |
How it works
That is deliberate. LearnDash merge shortcodes — [user_login], [course_title], [quiz_title] and the rest — are the mechanism that personalises the email, and rendering them here would replace them with values from no particular context.
Worse, an edit written against a rendered body would strip the shortcodes, producing an email that greets every learner by the name of whoever the read happened to resolve.
So the body comes back raw, shortcodes intact, ready to be edited and written back.
The recipient setting decides who gets it, which is frequently not the learner — admin notifications and group-leader notifications use the same system.
The delay and its unit turn an immediate email into a scheduled one, and a notification with a delay is easy to test wrongly because it does not arrive when you expect.
Input
| Name | Type | Required | What it is |
|---|---|---|---|
notification_id | integer | Yes | The notification. |
What comes back
| Name | Type | What it is |
|---|---|---|
notification | object | Subject, raw body, trigger, recipient, scope and delay. |
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:
What does our course completion email say?
It resolves to one call:
{
"ability": "learndash/get-notification",
"parameters": {
"notification_id": 950
}
}Worth knowing
- The body is raw so the merge shortcodes survive editing.
- Editing a rendered body would strip the personalisation.
- The recipient is often an admin or group leader, not the learner.
- A delayed notification does not arrive when you test it.
Related abilities
- LearnDash Manage Notification — edit it
- LearnDash List Notifications — the whole set
Get the plugins:
AcrossAI Abilities Manager · AcrossAI MCP Manager
Browse the rest: Every ability, by category