Skip to main content
FTS integrates with industry-standard tools to streamline case capture. Connect your ticketing system, incident platform, or workflow tool.

​
Available integrations

​
Jira Cloud

Create FTS cases automatically when Jira issues are marked with a specific label (e.g., ops-incident). Setup:
  1. Go to Integrations → Jira
  2. Click Connect
  3. Authorize FTS to access your Jira workspace
  4. Select which Jira projects to monitor
  5. Choose the trigger label (default: ops-incident)
New Jira issues with this label will spawn a case in FTS with:
  • Title: Jira issue key + summary (e.g., “OPS-2847: Database replication lag”)
  • Body: Jira description + linked issue URL
  • Attachment: Jira attachments auto-imported
Use Jira automations to assign labels on issue creation—FTS will capture the case immediately.

​
ServiceNow

Sync incidents and problems to FTS cases in real-time. Setup:
  1. Integrations → ServiceNow
  2. Enter your ServiceNow instance URL
  3. Provide API credentials (OAuth recommended)
  4. Select incident tables to monitor (incident, problem, change_request)
Cases are created with ServiceNow field mapping:
  • FTS title ← ServiceNow short_description
  • FTS body ← ServiceNow description + notes
  • FTS tags ← ServiceNow impact + urgency (e.g., impact-1, urgency-2)

​
Redmine

Connect your Redmine project to FTS for unified case management. Setup:
  1. Integrations → Redmine
  2. Enter your Redmine URL and API key
  3. Select which projects to track
  4. Choose issue status triggers (e.g., only “In Progress” issues)

​
Email-to-Case

Forward incident reports, alerts, or customer emails to FTS. Setup:
  1. Integrations → Email-to-Case
  2. Copy your unique FTS email address: your-workspace@inbox.ferrufino-tech-solutions.com
  3. Set up email forwarding in your alert tool or email client
Example: Configure your monitoring platform (Datadog, PagerDuty, etc.) to email this address. Each email becomes a case.
Email headers and attachments are included. Remove sensitive data from forwarded emails or use email templates.

​
Webhooks

For custom integrations, use FTS webhooks. To create a webhook:
  1. Integrations → Webhooks
  2. Click + New Webhook
  3. Enter a name and target URL
  4. Select events: case.created, case.updated, case.reviewed
  5. Save
FTS will POST JSON to your URL when events occur: 
{
  "event": "case.created",
  "workspace_id": "ws_abc123",
  "case": {
    "id": "case_xyz",
    "title": "Connector burn failure",
    "tags": ["connector", "hardware"],
    "created_by": "user_foo"
  },
  "timestamp": "2026-04-10T14:32:00Z"
}

​
Future integrations

We’re working on:
  • Slack: Create cases via /case command
  • Microsoft Teams: Similar bot integration
  • Splunk: Alert-to-case automation
  • Elastic: Log-driven case creation
  • Custom HTTP: Generic webhook receiver
Join our community to request your tool.

​
Best practices

  • Label consistently: Use a standard label/tag across all tools so FTS receives clean, searchable data.
  • Test first: Create a test issue in your ticketing system and verify the case appears in FTS.
  • Monitor syncs: Check Integration Status in workspace settings to see sync health and last run time.
  • Avoid loops: Don’t configure FTS to create cases from a tool that FTS writes back to—this causes infinite loops.
All integrations respect your workspace’s member roles. Cases created via integration inherit “Admin” ownership; normal member review workflows still apply.

​
Troubleshooting

“Authorization failed”: Check that your API credentials are valid and have the correct permissions. “No cases created”: Verify the trigger condition (label, status, etc.) matches your test issue. “Attachments missing”: Some tools require additional permissions. Check your integration’s auth scope. See Troubleshooting for more help.

Create your first case

Import legacy data

Contact support