Integrations & Agent API
Plug OpsQI into your team's toolchain.
Git connections, signed webhooks, an API for coding agents and a link catalogue.
The problem
Data gets copied between tools.
Code lives in one place, tasks in another, documents in a third. Without connections, every status change is moved by hand.
AI in this module
Open to agents, but controlled.
- Coding agents are authorised in the browser via the CLI; tokens expire and can be revoked
- What an agent can do is limited to its owner's permissions: create/update tasks, status, comments, time logs, files
- Task events flow to your own systems via signed webhooks
What you can do
Git connections
GitHub, GitLab, Bitbucket; OAuth or a personal access token, with your own server URL.
Repository tracking
Track all or selected repositories; link a repo to a project or have one created.
Connection health
Healthy / warning / broken checked hourly; automatic or manual webhooks, secret rotation.
Outbound webhooks
Task status changed, task assigned, comment added; HMAC-SHA256 signatures and retries.
Agent API tokens
Valid 90 days by default (365 max); status, last use and revocation.
Link catalogue
Attach Jira, Confluence, Figma, Slack, Notion, Trello and other links to projects, tasks or threads with tags.
Who uses it and how
CTO
Manages webhooks and integration settings.
Developer
Connects a coding agent to OpsQI; the agent updates tasks.
Department Manager
Curates the project link catalogue.
Frequently asked
Is there live sync with Jira or Slack?
No. Jira, Slack and similar tools are attached as references in the link catalogue; live integration is via Git providers, webhooks and the Agent API.
Can an agent do anything?
No. An agent's rights are the intersection of the allowed actions and its token owner's permissions.
See it with your own data.
Open a free workspace, or let's schedule a demo with your team.