mailerpress/get-workflow-logs returns a paginated per-job execution log for one workflow.
The status filter accepts only FAILED or COMPLETED.
At a glance
| Ability | mailerpress/get-workflow-logs |
| Toolset | MailerPress — toolset/mailerpress |
| Group | MailerPress › Workflows |
| Requires | AcrossAI Pro, plus MailerPress 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 restriction reflects how MailerPress displays them: EXITED jobs are normalised to FAILED internally for display, so filtering to FAILED returns both genuine failures and deliberate exits.
Which means a long list of “failed” jobs may be a workflow working exactly as designed, with a condition routing most contacts out.
mailerpress/get-workflow-stats counts them separately, so reading the stats alongside the logs is how you tell which you are looking at.
The per-job detail is what identifies a specific contact’s path through the automation — useful when somebody reports receiving the wrong email from a workflow, or nothing at all.
Post-run diagnostics rather than monitoring: the logs exist after jobs run, and a workflow that never triggers has no logs to read.
Input
| Name | Type | Required | What it is |
|---|---|---|---|
id | integer | Yes | The workflow. |
status | string | No | FAILED or COMPLETED. |
per_page | integer | No | Rows per page. |
What comes back
| Name | Type | What it is |
|---|---|---|
logs | array | Per-job execution records. |
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:
Why did that automation fail for some people?
It resolves to one call:
{
"ability": "mailerpress/get-workflow-logs",
"parameters": {
"id": 21,
"status": "FAILED"
}
}Worth knowing
- EXITED is normalised to FAILED for display, so the filter returns both.
- A long FAILED list can be a workflow working as designed.
- Read the stats alongside to tell them apart.
- No logs at all means the workflow never triggered.
Related abilities
- MailerPress Get Workflow Stats — exits counted separately
- MailerPress Retry Failed Workflow Jobs — act on the failures
Get the plugins:
AcrossAI Abilities Manager · AcrossAI MCP Manager
Browse the rest: Every ability, by category