It works with what you already use.
Decisions reach the team where it already is, and the result comes back to the case.
Available today
Microsoft Teams
AvailableThe decision request arrives as a card in Teams. The answer counts as the decision on the case, with the channel recorded.
Electronic signature
AvailableThe agent prepares the document and opens "Send for signature?" with the preview. The document goes to the signers only after a person clicks Send.
Claude, through the CaseFy MCP server
AvailableConnect Claude to CaseFy with an OAuth login and work on cases with the same permissions as your user.
api.casefy.io/mcpWebhooks and API
AvailableThe Inbound webhook creates a case from another system, with a secret key and no duplicates. Outbound webhooks tell other systems what happened.
Case email
AvailableEvery case has its own address. Whatever arrives there stays on the case.
sup-2026-00006@casefy.emailAzure DevOps
AvailablePR and pipeline linked to the case; a merged PR as proof to leave the stage.
New Relic
AvailableThe agent queries New Relic with the connection's credential, and an alert opens a case through the webhook.
Microsoft 365
AvailableEmail, calendar and Teams in a single connection, with the team mailbox replies go out from.
Any MCP server
AvailableGoogle, Notion, HubSpot and others: the system's tools become the agent's tools.
Credentials never show in full.
Connection credentials are stored encrypted in CaseFy and only ever shown masked (••••1234), and you choose which agents use each one. Production secrets, such as a database password or a cloud key, never enter CaseFy: they stay on the machine where the agent runs, read from your company's vault.
••••1234Start with a process you already run.
Create an account, connect a company machine and put an agent on one stage. It does the work; you decide when the case moves on.
Free plan forever · No credit card