Fetch Events Page
mailgun.fetch_events_page
ActionEmailconnection required
Calls the Mailgun API with the connection's credentials.
Follow a paging cursor from a previous events page and return the next page of the same query.
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
1 field, 1 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 |
|---|---|---|---|---|---|
page_url The next_page_url (or paging.next) from an earlier Mailgun events step. Must be an https URL on api.mailgun.net or api.eu.mailgun.net. | string | Yes | — | — | https://api.mailgun.net/v3/mg.acme.com/events/W3siYSI6ICJiIn1d |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"page_url": "https://api.mailgun.net/v3/mg.acme.com/events/W3siYSI6ICJiIn1d"
}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
- The URL must point at api.mailgun.net or api.eu.mailgun.net over HTTPS.
See Fetch Events Page 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.