Triggers
A Trigger is what starts an automation. It listens for an event from a connected provider — or fires on a schedule — and kicks off the Workflow wired to it.
Trigger types
Section titled “Trigger types”Each trigger belongs to one of the six providers:
| Provider | Fires on | |----------|----------| | GitHub | Repository events such as pushes and pull requests | | Slack | Slash commands run in your workspace | | Teams | Commands and message actions in Microsoft Teams | | Jira | Project and issue events | | Timer | A cron schedule you define | | MCP | An AI assistant invoking the trigger as a tool |
Creating a trigger
Section titled “Creating a trigger”- Open the Automations page and select a provider.
- Add a trigger and give it a name.
- Configure its source — for example, the repository and event for GitHub, the slash command for Slack, or the cron schedule for Timer.
For platform providers (GitHub, Slack, Teams, Jira), Marketrix can auto-install the trigger’s configuration on the connected provider so the external side is wired up for you. Each trigger has a unique webhook so the provider can notify Marketrix when the event occurs.
Triggers can be enabled or disabled at any time without deleting them.
Trigger run history
Section titled “Trigger run history”Each trigger keeps a history of when it fired. From a provider’s page you can view all recent trigger runs, and open an individual trigger to see its run detail — including the event, related repository or workflow, status (passed, failed, or unknown), timestamp, and a link to the external run where available.
Common use cases
Section titled “Common use cases”- PR validation — A GitHub trigger runs a workflow on every pull request.
- On-demand runs — A Slack slash command lets your team start a workflow without leaving chat.
- Scheduled runs — A Timer trigger runs a workflow on a nightly or weekly cadence.
- Issue-driven runs — A Jira trigger starts a workflow when a related issue is created or updated.