mailerpress/add-contact-note attaches an internal note to a contact record.
Notes are staff-only and never visible to the contact.
At a glance
| Ability | mailerpress/add-contact-note |
| Toolset | MailerPress — toolset/mailerpress |
| Group | MailerPress › Contacts |
| Requires | AcrossAI Pro, plus MailerPress active on the site |
| Capability | manage_options |
| Safety | Writes data |
| 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
The useful pattern is recording the why behind a change. A contact moved between lists, unsubscribed by request, or excluded from a campaign has a reason, and the record otherwise holds only the outcome.
That matters most for the decisions somebody might reverse. A contact re-subscribed because they asked looks identical to one re-subscribed by mistake, and a note is the only difference.
Notes are internal but not private in any strong sense — they live in the database and appear in an export of the contact record, which is worth remembering under a data-subject access request.
So write them as though the contact might read them, because under the right circumstances they can.
Not idempotent — each call adds another note.
Input
| Name | Type | Required | What it is |
|---|---|---|---|
contact_id | integer | Yes | The contact. |
note | string | Yes | The note text. |
What comes back
| Name | Type | What it is |
|---|---|---|
note_id | integer | The note created. |
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:
Note that this contact asked to be moved to the monthly list.
It resolves to one call:
{
"ability": "mailerpress/add-contact-note",
"parameters": {
"contact_id": 118,
"note": "Asked to move from weekly to monthly — email 12 Sept."
}
}Worth knowing
- Never visible to the contact in the normal course of things.
- Appears in an export of the record, so a subject access request surfaces it.
- The right place for the reason behind a reversible change.
- Not idempotent.
Related abilities
- MailerPress Update Contact — the change the note explains
- MailerPress Get Contact Activity — what they did
Get the plugins:
AcrossAI Abilities Manager · AcrossAI MCP Manager
Browse the rest: Every ability, by category