How we built a Fin Task for Incident Management
This Fin Task was designed to help customers quickly understand whether an issue they’re experiencing is related to a known incident, without needing to contact support directly. The goal was to make it feel fast, human, and reassuring while surfacing relevant technical information from our infrastructure. 🌍 Step 1: Detect the Customer’s Hosting Region We start by detecting the customer’s data hosting region , which is stored as a company-level attribute in Intercom. This attribute is critical — it allows the task to tailor its response and status checks to where the customer's workspace is hosted. Regions we support include: US Europe Australia If the region attribute is missing or unrecognized , the task defaults to US , and clearly explains this fallback behavior in the customer message (without speculating or misleading). 🔌 Step 2: Query the Incidents API via Region-Specific Data Connectors For each supported region, we’ve set up a dedicated Fin Data Connector that calls our inte