A trigger subscribes to an event on a connected app such as a new email or a succeeded charge. You set it up once, and Maton delivers every matching event to the destinations you register.
The parts of a trigger
Source
The source is the app the events come from (eg. google-mail). See the list of supported sources.
Event type
The event type defines which event to watch for on the source (eg. email.received). See the Maton Events section of each app's reference page for supported event types.
Connection
The connection is the account the events come from. Required for every source except time.
Destinations
The destinations are HTTPS endpoints a trigger delivers matching events to. See Managing destinations for how to register and shape them.
Supported sources
| Name | ID | API Host |
|---|---|---|
| Calendly | calendly | api.calendly.com |
| GitHub | github | api.github.com |
| Gmail | google-mail | gmail.googleapis.com |
| HubSpot | hubspot | api.hubapi.com |
| Linear | linear | api.linear.app |
| Notion | notion | api.notion.com |
| Slack | slack | slack.com |
| Stripe | stripe | api.stripe.com |
| Time | time |
Common Questions
A connection is the stored credential for one app account. A trigger uses that connection to subscribe to events on the account and deliver them to your destinations. You create a connection once, then build any number of triggers on top of it.
No. Every event is stored per-trigger regardless of destinations, so you can poll them with the Events API. Destinations add push delivery on top — Maton POSTs each event to them as it fires.
Every source needs one except , which fires on a cron schedule and watches no external account. All other sources — GitHub, Gmail, Stripe, and the rest — subscribe through a connection's stored credentials.