ActionMailgunUpdated May 2026

How do I query Mailgun event history?

Short answer: Drop the "Mailgun → Get Mailgun Events" action anywhere in your workflow, map the inputs from upstream nodes, and publish.

Use this action All 3 Mailgun actions

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 workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does Get Mailgun Events support batch operations?

Yes. Run Get Mailgun Events inside a Loop node to process arrays. Tiny Command handles Mailgun's rate limits automatically so you don't have to throttle manually.

More actions