Trigger a specific automation directly
Fire one named automation directly (the pre-v1 path the Zapier app and
HubSpot workflows use). Prefer POST /api/v1/events for new integrations —
it binds by event type instead of hardcoding an automation id and reports
richer outcomes. The target automation is named in ?id= and must belong
to the key’s org. Idempotent on deal_id (a repeat short-circuits before
geocoding). Field extraction is tolerant of HubSpot/Zapier mappings, so
properties.* aliases and flat fields both work.
Authorizations
Organization-scoped Mailr API key. Header: Authorization: Bearer ak_….
Query Parameters
The automation id to trigger.
Body
Highly tolerant of CRM/Zapier field shapes. address may be given flat or
as properties.address (also deal_address/install_address). Name may
be customer_first_name/customer_last_name, customer_name, or CRM
properties.dealname/contact_name. deal_id may be properties.hs_object_id
or objectId.
Echo-loop guard. Map this from the Mailr New Lead trigger when applicable.
Response
Queued (or already queued — idempotent: true). queue_id is
Mailr's internal id for the queued campaign job. attribution is
present only for deal_won automations that attributed revenue.
Automation name (omitted on the deal_id idempotent short-circuit).
Mailr's internal id for the queued campaign job.
True when this was a replay of an already-queued deal_id.
The geocoded/formatted address (omitted on the idempotent short-circuit).
Present only for deal_won automations that attributed revenue.