FixControl works on top of the systems you already use and replaces none of them. This page says, per system, what FixControl can do with it — because "connected" does not yet say what happens. The steps to connect are in the Admin guide.
What a connection can do
| Capability | Meaning |
|---|---|
| Bring in work | New reports become work in FixControl (an inbox conversation or an issue). |
| Read | FixControl uses information from the system as context, for example earlier tickets. |
| Reply | A reply to a customer goes out through this system. |
| Notify | FixControl posts progress or notifications in the system. |
| Approve | You can decide an approval from the system. |
| Code | FixControl reads the repository and delivers changes as pull requests. |
| Status back | A status change in the system comes back into FixControl. |
Overview
| System | What FixControl does with it | Default / condition |
|---|---|---|
| E-mail (forwarding, Microsoft 365 / Outlook, Gmail) | Bring work into the Inbox, reply from the mailbox. | Replying is off per mailbox. Gmail only where FixControl offers it; forwarding where FixControl has set it up. |
| Slack | Report work (issue after confirmation), ask about tickets, approve, post progress. | Approving needs an elevated, linked account. |
| Microsoft Teams | Report work, ask about tickets, approve. | No progress updates yet; a few cards fewer than in Slack. |
| Website chat | A widget on your own site: answers questions from knowledge you make public and, where configured, creates a request or issue. | Answers only from public knowledge; requires a list of allowed websites. |
| GitHub | Code: read the repository, open pull requests; merge status back. | A pull request only after approval; auto-deliver per project, off by default. |
| GitLab | Code: open merge requests; merge status back through the CI/CD webhook. | Self-hosted GitLab through an access token. |
| Bitbucket (Cloud and Server) | Code: open pull requests; status back for Bitbucket Cloud. | Bitbucket Server through your FixControl contact. |
| Freshdesk | Create and link tickets, read earlier tickets, status back, and where switched on, replies and progress notes. | New tickets do not become issues by themselves. Writing back is off by default; a customer reply always after approval. |
| Odoo Helpdesk | Same role as Freshdesk. | Same. |
| TOPdesk | Same role as Freshdesk, with incidents. | Same. |
| Jira Software | Create and link issues, read earlier issues, status back through a webhook you set up, and (when switched on per project) turn new Jira tickets into issues through that webhook. | No customer-visible replies. |
| Jira Service Management | As Jira Software, plus customer replies. | Customer replies off by default, always after approval. |
| Linear | Create and link issues, post comments. | No status back. |
| AFAS Profit, Visma Raet Youforce (HR) | Read-only, for HR questions. | Set up per project. See HR governance. |
| Google Cloud | Read-only: Cloud Logging and Error Reporting as context on bugs. | Off by default; FixControl enables it for your workspace. See Google Cloud. |
| PostgreSQL (database connector) | Read-only, as context on bugs. | Off by default. See Database connector. |
| Argo Rollouts, CI/CD approvals (GitHub Actions, GitLab CI, Jenkins), Kubernetes through the FC Agent | Approving a deployment your own pipeline has already paused. | Off by default; CI/CD approvals are a pilot. See DevOps & CI/CD. |
| Azure DevOps, Vercel, Terraform Cloud | Follow pipeline and deployment events. | Preview. |
| Outbound webhooks | Send FixControl events to your own systems. | See Webhooks. |
| Public API | Your own systems create issues and read issues and patches. | See Public API. |
Not available: WhatsApp and SAML single sign-on are on the roadmap and not available yet. A generic incoming webhook to open work does not exist yet; use the public API for that. There is no wiki connector; you fill the knowledge base by adding documents or reading in a website.
How work comes in
- E-mail lands in the Inbox. There you turn it into an issue, or let FixControl do that per mailbox automatically.
- Slack and Teams: the bot proposes an issue; it is created after confirmation.
- Support software (Freshdesk, Odoo, TOPdesk, Jira, Linear): FixControl creates tickets from an issue and follows their status. A new ticket in those systems does not become an issue by itself, except in Jira when Import new Jira tickets as issues is switched on for the project's Jira link. In Slack or Teams you can import an existing Jira or Freshdesk ticket by hand.
- Your own systems create issues through the public API.
Visibility and failures
Each connection's status is shown per capability under Settings → Channels — never as one blanket "connected". A mailbox that can receive but not send shows exactly that. Every write to an external system is queued, retried and, if it keeps failing, shown on the connection and on the work that was waiting for it, and reported to admins.
What FixControl is not
Not a CRM, billing system or general automation platform. To react to a FixControl event in another system, use an outbound webhook. To use information from another system at triage time, put it in the Knowledge base.
See also: Communication channels · Connecting e-mail · Issue trackers · GitHub