Connectors
A Connector links a platform to Marketrix. A connected Connector 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 Workflows page in the dashboard. Each provider card links to its own page, where you manage that provider’s triggers and actions.
What each Connector contributes
Section titled “What each Connector contributes”Connecting a provider and getting workflow capability from it are two different things. This table is the honest version:
| Connector | Triggers | Actions | Notes |
|---|---|---|---|
| GitHub | Pull request, Workflow run | Comment on PR, Create issue | The most complete integration. |
| Slack | — | Send message, Post thread reply | No trigger form; Slack starts work through the /marketrix slash command instead. |
| Timer | Timer tick | — | Built in, nothing to authenticate. |
| Teams | None | None | Connects, but contributes nothing to a workflow yet. |
| Jira | None | None | Connects, but contributes nothing to a workflow yet. |
| MCP | None | None | A separate surface — exposes Marketrix as tools to AI assistants. |
Every workflow can also use the two built-in Marketrix actions — Run QA Flow and Run Simulation — regardless of which Connectors you have linked.
Connecting a provider
Section titled “Connecting a provider”- Open the Workflows page.
- Pick a provider card — GitHub, Slack, Teams, or Jira.
- Authenticate the account. GitHub uses Authenticate with GitHub; the others use Connect.
Once connected, the provider’s card shows it as connected and its page lists its triggers and actions. You can disconnect a provider at any time from its page — existing triggers and actions for that provider stop working when you do. GitHub can also refresh its data to re-fetch the latest repositories from the connected account.
Timer and MCP are built in and need no authentication.
GitHub
Section titled “GitHub”The GitHub page manages the triggers and actions for your connected account:
- Triggers — Pull request and Workflow run, each scoped to a repository with an optional branch filter. See Triggers.
- Actions — Comment on PR and Create issue.
Because a GitHub trigger is the natural start of a QA cycle, the one built-in workflow template — GitHub PR → QA Check — pairs a pull-request trigger with Run QA Flow.
Slack contributes actions to workflows — Send message and Post thread reply — and it has its own command surface. Instead of a trigger table, the Slack page lists the capabilities of the /marketrix slash command along with a log of every command your workspace has run, its detected intent, and whether it completed or failed.
| Command | What it does |
|---|---|
/marketrix qa 5 |
Run a QA Flow by id |
/marketrix simulate 1 test checkout |
Start a Simulation on an Application |
/marketrix search how does pricing work |
Search Knowledge with AI |
/marketrix workflow Nightly QA |
Run a Workflow by name |
/marketrix send #general hello |
Send a message to a Slack channel |
/marketrix create channel project-x |
Create a Slack channel |
/marketrix help |
List every available command |
The Timer Connector creates scheduled triggers that fire on a cron schedule — hourly, daily, weekly, monthly, or a custom cron expression. Use one to run a workflow on a regular cadence, such as a nightly QA pass. Timer supplies triggers only; pair it with a Marketrix, GitHub, or Slack action.
MCP is not a workflow Connector — it takes no part in triggers or actions. It exposes Marketrix itself as a set of AI-callable tools over the Model Context Protocol, so an AI assistant can work with your Applications directly.
Activate MCP from its page to get a server URL, an ID, and an API key. Tools are grouped by area — Simulations, QA, Knowledge, Workflows, and Application context — and each one can be switched on or off individually. You can regenerate the API key at any time, which immediately breaks existing integrations, or deactivate MCP to revoke access entirely.