Explore 4 workflow actions for Mailgun, including account permissions and operation limits.
3 read actions1 write action
WORKFLOW ACTIONS
What you can configure.
Choose an action in the workflow builder, connect an account, and map its inputs. These actions are available in the catalog; your account access and a successful test determine whether they work for your setup.
Get sending domain
Read
Read a domain's provider status and TLS setting without SMTP credentials.
Permissions and limits
Account permissions
API key with domain read access
Operation limits
Uses Mailgun's US API region. EU-region domains require a separate regional connection implementation. Connection verification and domain reads require an account API key with domain-read access; sending-only domain keys cannot currently complete NodeHub connection verification.
List delivery logs
Read
Read a domain-filtered page of accepted, delivered and failed email events from the current Logs API.
Permissions and limits
Account permissions
API key with account log read access
Operation limits
Uses Mailgun's US API region. EU-region domains require a separate regional connection implementation. Connection verification and domain reads require an account API key with domain-read access; sending-only domain keys cannot currently complete NodeHub connection verification.
Provider retention and plan permissions determine available history. Pass pagination.next as cursor to fetch another page; a single operation returns one bounded page.
Pagination: cursor. Check the result for additional pages; a single action may not return every record.
List sending domains
Read
Read a page of domain status summaries without exposing SMTP credentials.
Permissions and limits
Account permissions
API key with domain read access
Operation limits
Uses Mailgun's US API region. EU-region domains require a separate regional connection implementation. Connection verification and domain reads require an account API key with domain-read access; sending-only domain keys cannot currently complete NodeHub connection verification.
Pagination: offset. Check the result for additional pages; a single action may not return every record.
Send email
Write
Submit one email from a verified Mailgun domain and return the provider's queue receipt.
Permissions and limits
Account permissions
API key allowed to send from the selected domain
Operation limits
Uses Mailgun's US API region. EU-region domains require a separate regional connection implementation. Connection verification and domain reads require an account API key with domain-read access; sending-only domain keys cannot currently complete NodeHub connection verification.
The receipt confirms queuing, not delivery. Use List delivery logs to check provider events. Attachments and templates are not included. Dispatched sends are never automatically retried.
A repeated request may repeat the external action. Review the previous result before retrying a write.
SETUP
Start with a controlled test.
01Connect the intended account
Use the account and permissions required for your process. Review the connection check before configuring a workflow action.
02Review inputs and access
Select a listed operation and map its required inputs. Use test records and add a human approval before writes that need review.
03Confirm the result
Inspect step outputs and confirm the result in Mailgun. A saved workflow is not a completed provider action.
Messaging · CONNECTION
