Skip to content
Marketrix Docs

Automations Overview

Automations connect your existing tools to Marketrix and let work happen on its own. Wire up an event in one tool, run a sequence of steps, and have the results delivered where your team already works — no manual kickoff required.

Everything lives on the Automations page in the dashboard, organized into three building blocks:

  • Connectors — Integrations with external platforms (GitHub, Slack, Teams, Jira) plus the built-in Timer and MCP providers.
  • Triggers — The events or schedules that start an automation, such as a repository push, a Slack slash command, or a cron schedule.
  • Workflows — Visual sequences that wire a trigger to one or more steps, with optional conditions between them.

How the pieces fit together

Section titled “How the pieces fit together”
  1. Connect a provider — Authenticate GitHub, Slack, Teams, or Jira so Marketrix can listen for their events and act on your behalf. Timer and MCP need no external account.
  2. Define a trigger — Choose what starts the automation: a platform event, a slash command, or a schedule.
  3. Build a workflow — Drag the trigger and one or more steps onto the canvas, connect them, and optionally add conditions that branch the flow.
  4. Let it run — When the trigger fires, the workflow runs each step in order. You can also run any workflow on demand with Run Now.

What you can build

Section titled “What you can build”
Connectors Connect GitHub, Slack, Teams, Jira, Timer, and MCP.
Triggers Start automations from events or on a schedule.
Workflows Wire triggers to steps with a visual builder.

Run history

Section titled “Run history”

Every workflow keeps a history of its runs. Each run records its status, when it started and finished, how long it took, and a per-step breakdown so you can see exactly which step succeeded, failed, or was skipped — and inspect each step’s output. Triggers keep their own run history too, so you can confirm an event actually fired.