List Events
mailgun.list_events
ActionEmailconnection required
Calls the Mailgun API with the connection's credentials.
Query the domain's event log — accepted, delivered, opened, failed and the rest — and return one page plus the cursor for the next.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- Username & password
- Providers
- Mailgun
- Secret shape
- the private API key: {"username": "api", "password": "…"}, or {"api_key": "…"}, or the raw key
- Config it needs
- domain, region, from_email, base_url
- Resolved by
- config.connection_id, else node.connection_id
Configuration
8 fields, none required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.
| Field | Type | Required | Default | Constraints | Example |
|---|---|---|---|---|---|
event Event type to filter on, e.g. 'delivered' or 'failed'. | string | No | — | one of "accepted", "rejected", "delivered", "failed", "opened", "clicked", "unsubscribed", "complained", "stored" | — |
recipient Only return events for this recipient address. | string | No | — | — | — |
tags Only return events carrying this tag. | string | No | — | — | — |
begin Start of the time range, in epoch seconds or RFC-2822. | string | No | — | — | — |
end End of the time range, in epoch seconds or RFC-2822. | string | No | — | — | — |
ascending Set to 'yes' to walk the log oldest-first instead of newest-first. | string | No | — | one of "yes", "no" | — |
limit Maximum events to return in this page. Mailgun caps the value at 300. | number | No | 100 | 1–300 | — |
domain Sending domain for this call; overrides the domain on the connection. | string | No | — | — | — |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"limit": 100
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
items The event records on this page, newest first by default. | array | — |
count How many events this page returned. | number | — |
paging Mailgun's next/previous cursor URLs for this query. | object | — |
next_page_url The paging.next URL — feed it to Mailgun: Fetch Events Page to continue. | string | — |
{
"count": 0,
"items": [],
"next_page_url": "",
"paging": {}
}Notes
- Mailgun always returns a paging.next URL; the log is exhausted when a page comes back with no items.
See List Events run in a workflow.
In a technical demo we add the Mailgun connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.