FireHydrant
Enable your AI agent to surface active incidents to customers and let CoPilot create incidents, add notes, and page the on-call team via FireHydrant.
5 min read
Updated February 2026
Overview
The FireHydrant integration connects ChatSpark to your FireHydrant account. Read actions are available in the customer-facing AI agent widget so customers can check incident status. Write actions are available to CoPilot only.
Your support team can create incidents, add notes, and page the on-call team directly from CoPilot during an active incident.
Available Actions
| Action | Description | Use |
|---|---|---|
| Get Active Incidents | List active FireHydrant incidents | Customer-facing |
| Get Incident Details | Get details on a specific incident | Customer-facing |
| Create Incident | Declare a new incident | CoPilot |
| Add Incident Note | Add a note to an open incident | CoPilot |
| Page On-Call | Send a page to the on-call team | CoPilot |
Prerequisites
Before setting up the FireHydrant integration, you'll need:
- A FireHydrant account
- At least one team configured in FireHydrant
- Admin access to generate API keys
Setup Instructions
Step 1: Generate an API Key
- Log in to FireHydrant at app.firehydrant.io
- Go to Organization Settings and select API Keys
- Click New API Key and give it a name
- Copy the key
Step 2: Enable in ChatSpark
- In ChatSpark, go to AI Actions
- Find FireHydrant in the Library and click Enable
- Enter your API Key
- Click Save
Configuration Fields
| Field | Description | Example |
|---|---|---|
| API Key | Your FireHydrant API key | xxx |
Testing Your Integration
Test customer-facing actions in your AI agent widget:
- “Is there an active incident?”
- “What is the status of incident inc-abc?”
Test CoPilot actions in the CoPilot browser extension:
- “Create a new FireHydrant incident for the payment service”
- “Add a note to incident inc-abc”
- “Page the engineering team”
Troubleshooting
Unauthorized
Check that the API key is still active. You can verify this in your FireHydrant Organization Settings under API Keys.
Incident not found
Confirm the incident ID is correct. FireHydrant incident IDs use the format inc-xxxxxxxx.
Cannot page on-call
Make sure on-call schedules are configured in FireHydrant and the target team ID is valid.