Connectors Overview
Connectors let you trigger QA flows and simulations automatically from external tools. Instead of manually running tests, connect your existing development workflow to Marketrix and let testing happen on its own.
Supported platforms
Section titled “Supported platforms”| Platform | Trigger |
|---|---|
| Timer | Run on a cron schedule — hourly, daily, weekly, monthly, or a custom expression |
| GitHub | Trigger on push or pull request events |
| Slack | Trigger via slash commands |
| Jira | Trigger on issue creation or updates |
| Teams | Receive webhook notifications |
How Connectors work
Section titled “How Connectors work”Each connector links an external platform to one or more scheduled tasks. A task defines:
- What to run — A QA Flow or Simulation.
- When to run — A schedule (for Timer connectors) or an event trigger (for platform connectors).
- Whether it’s active — Individual tasks can be enabled or disabled without deleting them.
When a trigger fires, Marketrix automatically starts the associated QA flow or simulation run. Results appear in your dashboard just like any manually initiated run.
Common use cases
Section titled “Common use cases”- Nightly regression testing — Use a Timer connector to run your full QA suite every night.
- PR validation — Use a GitHub connector to run QA flows on every pull request.
- On-demand testing — Use a Slack connector to let your team trigger tests with a slash command.
- Issue-driven testing — Use a Jira connector to automatically test workflows when related issues are created.
Task history
Section titled “Task history”Each connector tracks its execution history so you can see when tasks ran, whether they succeeded, and link to the full results.