Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

Mailgun

Email delivery service for sending, receiving, and tracking emails

CategoryMarketing
Authenticationcustom
Version0.1.0
Published scopes0 published scopes
Last updatedSeptember 19, 2026

Overview

Connect Mailgun with Flows360

Email delivery service for sending, receiving, and tracking emails

Use the Mailgun connector to include its declared actions and events in Flows360 workflows without duplicating the integration logic inside each consuming system. This pinned connector version currently exposes 9 actions and 8 triggers.

Available actions

  • Send Email
  • Validate Email
  • Add Mailing List Member
  • Get Events
  • Get Domain Stats
  • List Bounces
  • Delete Bounces (Bulk)
  • Get Domain Health
  • Plus 1 additional declared action.

Available triggers

  • New Bounce Event
  • New Complaint Event
  • New Delivery Event
  • New Failed Delivery Event
  • New Open Event
  • New Click Event
  • Plus 2 additional declared triggers.

The capability list above is generated from the exact reviewed connector package so the public description stays aligned with the version Flows360 operates.

Technical guide

Technical reference

Package identity

  • Connector: Mailgun
  • Package: @activepieces/piece-mailgun@0.1.0
  • Exact artifact digest: sha256:44f2a2cca1246ff8cd506bd63e7654fc235ef07b2c4861514bae05a1152a35eb
  • Runtime: Activepieces-compatible deterministic worker
  • Source: the exact reviewed Activepieces source

Authentication

CUSTOM AUTH. Connection values are tenant-specific and remain in the consuming Studio instance; CDK stores definitions and field metadata, not customer credential values.

Action contracts

  • Send Email (send_email), Send an email using your Mailgun domain Classification: read.
  • Validate Email (validate_email), Validate an email address using Mailgun validation service. Requires a Mailgun account with email validation enabled. Classification: read.
  • Add Mailing List Member (add_mailing_list_member), Add a new member to a Mailgun mailing list Classification: read.
  • Get Events (get_events), Retrieve email events from your Mailgun domain (deliveries, failures, opens, clicks, etc.). Useful for monitoring and alerting. Classification: read.
  • Get Domain Stats (get_domain_stats), Retrieve aggregated email statistics for a Mailgun domain (delivered, failed, opened, etc.). Useful for monitoring delivery health and detecting anomalies. Classification: read.
  • List Bounces (list_bounces), Retrieve the list of bounced email addresses for a Mailgun domain. Useful for cleanup after delivery issues or spam attacks. Classification: read.
  • Delete Bounces (Bulk) (delete_bounces_bulk), Remove bounced addresses from the Mailgun suppression list, either all at once for a domain or a single address. Classification: read.
  • Get Domain Health (get_domain_health), Fetch the health of a Mailgun domain: current state, whether it has been disabled, and DNS verification status for sending and receiving records. Classification: read.
  • Custom API Call (custom_api_call), Make a custom API call to a specific endpoint Classification: read.

Trigger contracts

  • New Bounce Event, webhook.
  • New Complaint Event, webhook.
  • New Delivery Event, webhook.
  • New Failed Delivery Event, webhook.
  • New Open Event, webhook.
  • New Click Event, webhook.
  • New Unsubscribe Event, webhook.
  • Bulk Bounce Threshold Exceeded, polling.

Verification

Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Capability summary

Authenticationcustom
Supported objects17
Supported actionsNot published
Triggers8

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • API Key Required · protected credential
  • Region Required

Supported objects

ObjectReadWriteNotes
Send Email Yes No Send an email using your Mailgun domain
Validate Email Yes No Validate an email address using Mailgun validation service. Requires a Mailgun account with email validation enabled.
Add Mailing List Member Yes No Add a new member to a Mailgun mailing list
Get Events Yes No Retrieve email events from your Mailgun domain (deliveries, failures, opens, clicks, etc.). Useful for monitoring and alerting.
Get Domain Stats Yes No Retrieve aggregated email statistics for a Mailgun domain (delivered, failed, opened, etc.). Useful for monitoring delivery health and detecting anomalies.
List Bounces Yes No Retrieve the list of bounced email addresses for a Mailgun domain. Useful for cleanup after delivery issues or spam attacks.
Delete Bounces (Bulk) Yes No Remove bounced addresses from the Mailgun suppression list, either all at once for a domain or a single address.
Get Domain Health Yes No Fetch the health of a Mailgun domain: current state, whether it has been disabled, and DNS verification status for sending and receiving records.
Custom API Call Yes No Make a custom API call to a specific endpoint
New Bounce Event Yes No webhook trigger declared by the pinned package.
New Complaint Event Yes No webhook trigger declared by the pinned package.
New Delivery Event Yes No webhook trigger declared by the pinned package.
New Failed Delivery Event Yes No webhook trigger declared by the pinned package.
New Open Event Yes No webhook trigger declared by the pinned package.
New Click Event Yes No webhook trigger declared by the pinned package.
New Unsubscribe Event Yes No webhook trigger declared by the pinned package.
Bulk Bounce Threshold Exceeded Yes No polling trigger declared by the pinned package.

Triggers

New Bounce Event · Webhook

Triggers when an email permanently fails to deliver (hard bounce) in Mailgun

Inputs

  • domain · string
New Complaint Event · Webhook

Triggers when a recipient reports an email as spam in Mailgun

Inputs

  • domain · string
New Delivery Event · Webhook

Triggers when an email is successfully delivered in Mailgun

Inputs

  • domain · string
New Failed Delivery Event · Webhook

Triggers when an email temporarily fails to deliver in Mailgun (will be retried)

Inputs

  • domain · string
New Open Event · Webhook

Triggers when a recipient opens an email in Mailgun

Inputs

  • domain · string
New Click Event · Webhook

Triggers when a recipient clicks a tracked link in an email in Mailgun

Inputs

  • domain · string
New Unsubscribe Event · Webhook

Triggers when a recipient unsubscribes from emails in Mailgun

Inputs

  • domain · string
Bulk Bounce Threshold Exceeded · Poll

Triggers once when too many emails bounce within a set time period. Useful for catching spam attacks or deliverability problems early.

Inputs

  • domain · string
  • threshold · number
  • window_minutes · number
  • severity · string

Setup

Setup

  1. Add the Mailgun connector to the workflow in the target Flows360 Studio instance.
  2. Create or select the tenant-specific connection required by the connector. Connection secrets remain in the Studio connection boundary and are not copied into CDK documentation.
  3. Provide the connection fields declared by the pinned package:
  • API Key (api_key), required; stored as a sensitive connection value.
  • Region (region), required.
  1. Select the required action or trigger and complete its declared input fields. Required and optional inputs are defined by the exact package schema.
  2. Test the workflow in the appropriate environment before enabling production scheduling or event delivery.

Limitations

Limitations and operational notes

  • This content describes @activepieces/piece-mailgun@0.1.0; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 9 actions and 8 triggers declared by this pinned package are represented here.
  • Tenant credentials and connection values are not stored in the public connector record.
  • Provider-side permissions, account entitlements, quotas and rate limits remain subject to the connected provider account and are not inferred when the package does not declare them.
  • Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Troubleshooting

Why canu2019t the connector authenticate?

Check the tenant connection in Studio and confirm every required Mailgun connection field is present. Re-authorise OAuth-based connections if the provider token or consent has expired. Do not place credential values in CDK content or logs.

Why is an action or trigger unavailable?

Confirm that the workflow is using @activepieces/piece-mailgun@0.1.0 and compare the requested capability with the declared action and trigger list for this version. A capability that is not declared by the pinned package should not be presented as supported.

What should I check after a provider-side change?

Revalidate authentication, required fields, action/trigger behaviour and provider documentation before publishing refreshed connector content or moving a new package version into production.

github.com