Per-pair page

Connect HubSpot to Mailgun in two minutes.

Real-time triggers from HubSpot, ready-made actions in Mailgun. Filter, transform, and route without writing a line of code.

Connect HubSpot and Mailgun See reverse direction

Trigger app

HubSpot as the trigger

Workflows fire when something happens in HubSpot.

See all 18 triggers →

Action app

Mailgun as the action

Workflows do something in Mailgun, instantly.

Both directions

Pick the way that fits your stack.

Pair pages are mirrored. Each direction gets its own dedicated page.

HubSpot → Mailgun

When something happens in HubSpot, do it in Mailgun.

18 HubSpot triggers wired to 3 Mailgun actions. Most-used pairing: New Company → Get Mailgun Events.

Mailgun → HubSpot

Or fire it the other way around.

0 Mailgun triggers wired to 23 HubSpot actions downstream.

Use any trigger in the catalog as the upstream.

See Mailgun → HubSpot →

Popular pairings

Common HubSpot → Mailgun workflows.

Pick a pairing to set it up in two minutes. Each one is a fully editable recipe.

Showing 9 of 54 combinations

When new company in HubSpot, get mailgun events in Mailgun.

Fires when a new company is created in HubSpot. Use to enrich the company with firmographic data, mirror to your data warehouse, or run account-matching against parent records.

When new company in HubSpot, mailgun send email in Mailgun.

Fires when a new company is created in HubSpot. Use to enrich the company with firmographic data, mirror to your data warehouse, or run account-matching against parent records.

When new company in HubSpot, mailgun validate email in Mailgun.

Fires when a new company is created in HubSpot. Use to enrich the company with firmographic data, mirror to your data warehouse, or run account-matching against parent records.

When company deleted in HubSpot, get mailgun events in Mailgun.

Fires when a company is deleted in HubSpot. Useful for audit logs or for tearing down related records in other systems.

When company deleted in HubSpot, mailgun send email in Mailgun.

Fires when a company is deleted in HubSpot. Useful for audit logs or for tearing down related records in other systems.

When company deleted in HubSpot, mailgun validate email in Mailgun.

Fires when a company is deleted in HubSpot. Useful for audit logs or for tearing down related records in other systems.

When company property changed in HubSpot, get mailgun events in Mailgun.

Fires when a specific company property changes in HubSpot. Use a property filter to react only on changes you care about (e.g. lifecycle stage).

When company property changed in HubSpot, mailgun send email in Mailgun.

Fires when a specific company property changes in HubSpot. Use a property filter to react only on changes you care about (e.g. lifecycle stage).

When company property changed in HubSpot, mailgun validate email in Mailgun.

Fires when a specific company property changes in HubSpot. Use a property filter to react only on changes you care about (e.g. lifecycle stage).

How it works

Connect HubSpot and Mailgun in five steps.

No code, no glue, no half-day setup. Each step is one click.

1
Connect
Authorize HubSpot and Mailgun
Open Tiny Command, authorize HubSpot and Mailgun once each. Both connections are available to every workflow on your account.
2
Trigger
Pick a HubSpot trigger
Drop the HubSpot → New Company trigger onto the canvas. Tiny Command auto-registers the webhook.
POST /v1/webhooks/hubspot.trigger-company-created
3
Transform
Add a filter or AI step
Optionally add a Filter node ("subject contains URGENT") or an AI step ("classify intent") between trigger and action.
4
Action
Add the Mailgun action
Drop the Mailgun → Get Mailgun Events action below it. Map fields from the HubSpot payload into the Mailgun inputs.
mailgun.get-events
5
Publish
Publish and forget
Hit Publish. Tiny Command runs it in production from second one. Watch the run-log fill up.

FAQ

Questions about HubSpot + Mailgun.

How long does it take to connect HubSpot and Mailgun on Tiny Command?

Under two minutes. Authorize HubSpot and Mailgun once each, drop the HubSpot trigger and Mailgun action onto a workflow canvas, map a couple of fields, and publish. No code, no glue.

Is the HubSpot ↔ Mailgun integration real-time?

Yes. Both HubSpot and Mailgun expose webhooks, so events from one fire workflows in the other within seconds rather than on a polling interval.

Can I filter or transform data between HubSpot and Mailgun?

Yes. Add a Filter node to only pass through matching events, a Switch node to branch by value, or an AI / Code node to transform payloads before they hit Mailgun.

What HubSpot events can trigger a Mailgun workflow?

Any of the 18 HubSpot triggers, including "New Company". Each fires in real time when the matching event happens in HubSpot.

Do I need a paid plan to use HubSpot with Mailgun?

No. There's a free tier that covers most HubSpot+Mailgun use cases without a credit card. Paid plans unlock higher run volumes and team features when you outgrow it.

What if I want Mailgun → HubSpot instead?

Build it the same way, in reverse. There's a dedicated /integrations/mailgun/with/hubspot page with the reverse-direction triggers and actions.

Other apps that pair well with HubSpot.

HubSpot + Gmail

HubSpot + Slack

Communication

HubSpot + Google Sheets

Spreadsheets & Databases

Spreadsheets & Databases

Wire HubSpot to Mailgun in 2 minutes.

Free tier available. No credit card. No onboarding call.

Try for free Request a demo

Connect HubSpot to Mailgun in two minutes.

Pick the way that fits your stack.

When something happens in HubSpot, do it in Mailgun.

Or fire it the other way around.

Common HubSpot → Mailgun workflows.

Connect HubSpot and Mailgun in five steps.

Questions about HubSpot + Mailgun.

Other apps that pair well with HubSpot.

Wire HubSpot to Mailgun in 2 minutes.

Be the first to know what's next.