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). 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.

Connecting a provider

1. Open the Workflows page.
2. Pick a provider card — GitHub or Slack.
3. Authenticate the account. GitHub uses Authenticate with GitHub; Slack uses 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.

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	None	Built in, nothing to authenticate.
Teams	None	None	Not available — cannot be connected.
Jira	None	None	Not available — cannot be connected.
MCP	None	None	A separate surface — exposes Marketrix as tools to AI assistants.

Note

Teams and Jira cannot be connected today. No Marketrix environment carries OAuth credentials for either one, so Connect fails. They also supply no trigger and no action, so nothing is lost by waiting — don’t build a plan around a Jira issue event or a Teams message action.

Every workflow can also use the two built-in Marketrix actions — Run QA Flow and Run Simulation — regardless of which Connectors you have linked.

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.

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

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. It also logs 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

Anything that doesn’t match one of these patterns is answered conversationally instead — you can type the request in your own words and Marketrix works out what you meant.

Note

Usage here is charged only for measured inference cost. See Billing and Credits.

Timer

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

MCP is a Connector that supplies no triggers or actions to workflows — it’s a separate surface that 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 into five categories — 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.

Tip

Pair a Timer trigger for regular cadence with a GitHub pull-request trigger — together they catch issues both on a schedule and before code ships.

Next steps

TriggersCreate a GitHub or Timer trigger and watch it fire.

Creating WorkflowsWire a trigger to actions on the canvas.