ActionMailgunUpdated September 2026

How do I query Mailgun event history?

Short answer: You can get mailgun events in Mailgun by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Mailgun Get Mailgun Events action to a workflow, map its 2 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

Get Mailgun Events in Mailgun — start free All 3 Mailgun actions

Get Mailgun Events in Mailgun — start free

Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

Field	Type	Required	Description
Event Type event	options	Optional	Event Type. Options: All events, Delivered, Opened, Clicked, Bounced, Unsubscribed, Complained (spam)
Limit limit	number	Optional	Limit. e.g. "25"

Sample request

{
  "event": "{{trigger.event}}",
  "limit": "25"
}

Returns

{
  "items": [
    {
      "event": "delivered",
      "message": {
        "headers": {
          "subject": "Hello"
        }
      },
      "recipient": "user@example.com",
      "timestamp": 1712835600
    }
  ]
}

Use these fields in downstream nodes for routing, logging, or error handling.

Triggered by

Apps that pair well as the trigger for Get Mailgun Events.

Any of these apps can fire this action as part of a workflow.

Google Sheets → Mailgun

2 Google Sheets triggers

HubSpot → Mailgun

18 HubSpot triggers

FAQ

Questions about Get Mailgun Events.

What does the Get Mailgun Events action do in Mailgun?

Paginated event log (delivered, opened, clicked, bounced, failed, complained) with filters by date, message-id, recipient. For "did this email actually deliver?" forensics or bulk-export to warehouse.

What inputs does Get Mailgun Events require?

Get Mailgun Events has no required inputs. Sensible defaults are applied if you leave fields blank.

Can I use dynamic inputs from earlier workflow nodes?

Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.

What happens if Mailgun returns an error?

The run history shows the failed step with its input and the error message Mailgun returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.

Does Get Mailgun Events support batch operations?

Run Get Mailgun Events inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within Mailgun's rate limits.

More actions

Other Mailgun actions.

Action

Mailgun Send Email

Sends transactional or bulk email with HTML/text body, attachments, per-recipient variables for batched personalised sends. The standard hook for "external event → transactional email" patterns.

Action

Mailgun Validate Email

SMTP-handshake + DNS + Mailgun-heuristic validation. Returns deliverable/undeliverable/risky/unknown. Useful for in-flow validation before adding to sequences.

Get Mailgun Events in Mailgun — start free