Skip to main content
There is no Integrations area in FTS today, and none of the connectors below exist yet. There is no Integrations entry in Settings, no Jira, ServiceNow or Redmine connector, and no outgoing webhooks. Measured on 06.08.2026 (round 99) against the source: the words Integration, Jira, ServiceNow and Redmine do not occur anywhere in the application code, and the only webhook endpoints in the product are the incoming ones FTS uses itself for Stripe, Clerk and email delivery.Earlier versions of this page described setup steps, buttons, field mappings and payloads for all of them as if they were available. Two sections of this page — Email-to-Case and the rate limits — had already been corrected twice before; the connector sections beside them were missed both times (the dates are on those sections below). They are corrected here.What exists today for getting data in and out: the JSON export of your organisation under Settings → Data Export, and the filtered CSV export from the case list. Connectors and a read-only REST API are on our roadmap for Team and Enterprise — that is also what our FAQ says. If a specific tool decides your rollout, write to hello@ferrufino-tech-solutions.com and we will tell you where it stands instead of guessing.

​
Planned integrations

The tools below are the ones we are asked for most often. None of them is available today; they are listed so you can tell us which one matters, not so you can switch one on.
  • Jira Cloud — create a case from a labelled Jira issue
  • ServiceNow — sync incidents and problems to cases
  • Redmine — track selected projects
  • Outgoing webhooks — POST case events to a URL of your choice
  • Slack / Microsoft Teams — create cases from a chat command
  • Splunk / Elastic — alert- and log-driven case creation
Write to us to request your tool.

​
Email-to-Case

This does not exist yet. This section gave every workspace an address at inbox.ferrufino-tech-solutions.com to forward alerts to. That domain has no DNS record and no MX record, so mail sent to it does not bounce back to us — it never arrives anywhere. There is no inbound mail handling in the product (corrected 05.08.2026, measured rather than assumed). Until it exists, create the case in the app and attach the forwarded mail as evidence. If email intake is a requirement for your rollout, tell us at hello@ferrufino-tech-solutions.com and we will tell you where it stands.

​
Outgoing webhooks

These do not exist yet. This section described a Webhooks screen with a + New Webhook button, a target URL, selectable case.created / case.updated / case.reviewed events and a sample JSON payload. None of it is in the product: there is no screen to create one, no delivery, no retry, and no signing secret. Those event names and that payload shape were written in advance and were not marked as planned (corrected 06.08.2026). There is also no Integration Status view in workspace settings, and no integration auth scopes to check — earlier Best practices and Troubleshooting sections referred to both. They have been removed rather than reworded, because there is nothing yet for them to advise about. Until outgoing webhooks exist, the supported way to move case data into another system is the export: Settings → Data Export for the full JSON, or the CSV export from the case list.

​
What to do in the meantime

  • Keep your tagging consistent across FTS and your ticketing system. That costs nothing today and is what makes a future connector useful.
  • Use the export. The JSON export includes signed download links for every attachment and is the documented path for programmatic access right now.
  • Tell us which tool decides your rollout. We prioritise connectors by what paying customers actually block on, not by what is easiest to build.

Create your first case

Import legacy data

Contact support