Connectors
A Connector links an external platform to Marketrix. Once connected, a provider can supply Triggers (events that start a workflow) and actions (steps a Workflow can run), so your testing and operations plug into the tools your team already uses.
Connectors are managed from the Automations page in the dashboard.
Supported providers
Section titled “Supported providers”| Provider | What it offers |
|---|---|
| GitHub | Triggers for repository events and pull requests; actions for issues, PRs, and workflows |
| Slack | Slash-command triggers and workspace message actions |
| Teams | Microsoft Teams command triggers and message actions |
| Jira | Triggers for project events; actions for issues |
| Timer | Scheduled triggers that fire on a cron schedule — no account to connect |
| MCP | Exposes automation triggers as AI-callable tools via Model Context Protocol |
GitHub, Slack, Teams, and Jira require connecting an external account. Timer and MCP are built in and need no authentication.
Connecting a provider
Section titled “Connecting a provider”- Open the Automations page.
- Pick a provider card (GitHub, Slack, Teams, or Jira).
- Authenticate the account. For GitHub, use Authenticate with GitHub; the other providers use Connect.
Once connected, the provider’s card shows it as connected, and you can add triggers and actions for it. You can disconnect a provider at any time from its page, or refresh its data to re-fetch the latest details from the connected account.
Triggers and actions
Section titled “Triggers and actions”Each connected provider exposes two kinds of capabilities:
- Triggers — Events that start a workflow (for example, a GitHub push or a Slack slash command). See Triggers for details.
- Actions — Steps a workflow can run on that provider (for example, posting a Slack message, or creating a Jira issue).
Open a provider’s page to view, add, enable, or disable its triggers and actions. Each provider page also shows a history of recent trigger runs.
The MCP provider
Section titled “The MCP provider”The MCP provider exposes your automation triggers as AI-callable tools over the Model Context Protocol. Activate MCP to get an endpoint and API key that AI assistants can use to invoke your triggers as tools. Individual tools can be toggled on or off, and the API key can be regenerated.
The Timer provider
Section titled “The Timer provider”The Timer provider creates scheduled triggers that fire on a cron schedule. Use Timer triggers to run workflows on a regular cadence — for example, a nightly QA pass. See Triggers for how to configure a schedule.