--- title: "Connect ilert to Fergus - APIANT.ai" description: "When \"New or Updated Incident\" fires in ilert, your agent runs \"Add Contact\" in Fergus." canonical: "https://apiant.ai/connect/ilert-to-fergus" --- # Connect ilert to Fergus When **New or Updated Incident** fires in [ilert](https://apiant.ai/connections/ilert), your agent runs **Add Contact** in [Fergus](https://apiant.ai/connections/fergus). Describe the whole flow and it is built, tested on every scenario and kept running. ilert **1** trigger ilert **12** actions Fergus **31** actions What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it. ## What do you want ilert and Fergus to do together? Give your AI client this address. `https://mcp.apiant.ai` One connection does both: ask your client to act in an app once, or have it build an automation that keeps running. Any client that takes a remote MCP server. Nothing to install. Create your free account, then sign in once in your browser. ### Set it up in your client ### Claude Code Run this in the directory you want to work in. `claude mcp add --transport http -s project apiant-ai https://mcp.apiant.ai` Start Claude Code there, approve the server, and sign in in the browser page it opens. [Claude Code guide (opens in a new tab)](https://apiant.ai/docs/mcp/claude-code) ### Claude, web and desktop Open Customize, then Connectors, then Add custom connector, and paste the address. On Team and Enterprise an owner adds it first. [Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp) ### Cursor Add the address to your MCP configuration as a server URL. Cursor signs you in in your browser. [Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp) ### Zed Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server. [Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp) ### Codex and the ChatGPT desktop app Open Settings, then MCP servers, then Add server, and choose Streamable HTTP. From the terminal, Codex takes the address with its own add command and then signs you in. [Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp) ### Any other MCP client Paste the address where the client asks for a remote MCP server URL, and name the server apiant-ai where it lets you. APIANT's skills reach the client over the same connection. [Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp) Example flows ## What ilert can start in Fergus - When **New or Updated Incident** in ilert then **Add Contact** in Fergus - When **New or Updated Incident** in ilert then **Add Task** in Fergus Starting points drawn from the triggers and actions in the catalog today. Describe the flow you need, at any depth, and your agent builds it and tests every scenario before it ships. Everything your agent can do with ilert and Fergus ## Triggers and actions 1 trigger · 43 actions - Trigger **New or Updated Incident** Triggers when an incident (alert) on the chosen ilert alert source is created or changes: assigned, escalated, accepted, raised, commented on, resolved, or a responder is added or removed. - Action **Accept Incident** Accepts a pending ilert alert (formerly called an incident) on behalf of the connected user, stopping its escalation, and returns the updated alert. - Action **Add Alert** Creates an alert in ilert on the chosen alert source, which then escalates according to the source's escalation policy (or a policy or responders you specify). - Action **Add maintenance window** Creates a maintenance window in ilert that suppresses alerts for the chosen alert sources and services between a start and end time. - Action **Create Incident** Creates a new incident in ilert, optionally marking affected services and adding responders. Depending on the affected services, subscribers may be notified. - Action **Find User on Call** Finds the user currently on call for an on-call schedule, along with the start and end of their current shift. Returns found=false when nobody is on call. - Action **Get alert** Returns a single ilert alert by its id, including its summary, status, priority, alert source, escalation policy and responders. - Action **Get incident** Returns a single ilert incident by its id, including its status, severity, affected services and responders. - Action **Get maintenance window** Fetches a maintenance window by ID. An error occurs if the maintenance window is not found. - Action **List Alert Sources** Returns all alert sources in your ilert account, including each source's integration type, integration key, status and escalation policy. - Action **List incidents** Returns the incidents in your ilert account, optionally filtered by status, affected service, severity and declaration date. - Action **List users** Returns the users in your ilert account, with their name, email, role and contact settings. - Action **Resolve Incident** Resolves an ilert alert (formerly called an incident), closing it and stopping further escalation. - Action **Add Calendar Event** Creates a new calendar event/booking. - Action **Add Contact** Creates a new contact. - Action **Add Note** Creates a new note against a record. - Action **Add Quote** Creates a new draft quote on a Fergus job. Supported for jobs whose job type is Quote or Estimate. - Action **Add Task** Creates a new task in Fergus, optionally linked to a job and assigned to employees. - Action **Archive Site** Archives a site in Fergus. The site can later be restored. - Action **Create Customer** Creates a new customer. - Action **Create Job** Creates a job in Fergus — an active job, a draft job, or a variation of an existing job. - Action **Create Site** Creates a new site. - Action **Delete Customer** Deletes a Fergus customer by ID. - Action **Edit Draft Job** Updates a draft job in Fergus. Only draft jobs can be edited; leave a field blank to keep its current value. - Action **Finalize Draft Job** Finalises a draft job in Fergus, turning it into an active job. - Action **Find All Quotes** Returns up to 100 quotes from across all jobs that match the specified status and date criteria. - Action **Find Customer** Returns the customers whose name, or main or billing contact's name, email or phone, contains the search text. - Action **Find Site** Finds sites by name, city, postal code, or free-text search. Returns the first page of matches (up to 10). - Action **Get Calendar Event** Returns a single Fergus calendar event by its ID, including title, start/end times, event type, assigned user, linked job/job phase and recurrence details. - Action **Get Contact** Returns a single Fergus contact (customer or site contact) by its ID, including name, position, company and contact items. - Action **Get Customer by ID** Returns a Fergus customer by its ID. - Action **Get Customer Invoice** Retrieves a customer invoice by ID. - Action **Get Job by ID** Retrieves a specific job using its unique ID. - Action **Get Quotes for Job** Returns all quotes for a Fergus job, optionally filtered by status. - Action **Get Site by ID** Retrieves a specific site using its unique ID. - Action **List Contacts** Lists contacts, with optional filtering. - Action **List Customer Invoices** Lists customer invoices, with optional filtering. - Action **List Notes** Returns the notes (with their replies) attached to a Fergus record. - Action **List Tasks** Lists the company's tasks, optionally filtered by status, assigned employee, job, due date range or overdue state. - Action **Update Contact** Updates an existing customer contact or site contact in Fergus. - Action **Update Customer** Updates an existing customer's details. - Action **Update Quote** Updates a draft quote on a Quote or Estimate job in Fergus: title, description and its sections with line items. - Action **Update Site** Updates an existing site's details. - Action **Update Task** Updates a task's description, due date, or assigned employees in Fergus. The job a task is linked to cannot be changed. ## Each app on its own - [ **ilert** ilert is a platform for alerting, on-call management, and status pages.](https://apiant.ai/connections/ilert) - [ **Fergus** Fergus is a job management software for plumbers, electricians and other trades.](https://apiant.ai/connections/fergus) Reviews ## What our customers say ## More from ilert - [ **ilert to Salesforce** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/ilert-to-salesforce) - [ **ilert to Slack** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/ilert-to-slack) - [ **ilert to Mailchimp** Mailchimp marketing automation and email platform.](https://apiant.ai/connect/ilert-to-mailchimp) - [ **ilert to Stripe** Stripe is a payment processing platform for online businesses.](https://apiant.ai/connect/ilert-to-stripe) - [ **ilert to Shopify** Shopify is a commerce platform for online stores and retail point-of-sale.](https://apiant.ai/connect/ilert-to-shopify) - [ **ilert to QuickBooks Online** QuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...](https://apiant.ai/connect/ilert-to-quickbooks-online) ## More into Fergus - [ **Outlook to Fergus** Outlook is Microsoft's email and calendaring platform integrating contacts and scheduling, enabling users to...](https://apiant.ai/connect/outlook-to-fergus) - [ **HubSpot to Fergus** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-fergus) - [ **Salesforce to Fergus** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/salesforce-to-fergus) - [ **Slack to Fergus** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/slack-to-fergus) - [ **Google Sheets to Fergus** Google Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.](https://apiant.ai/connect/google-sheets-to-fergus) - [ **Gmail to Fergus** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/gmail-to-fergus) Questions ## ilert and Fergus, answered ### ### What can start an automation from ilert? Any of ilert's 1 trigger in the catalog, including New or Updated Incident. Describe the moment in plain language and your agent picks the right one. ### ### What can your agent do in Fergus when something happens in ilert? Any of Fergus's 31 actions, including Create Customer, Create Job, Create Site and Update Contact. Your agent maps the data both ways and tests every scenario before it ships. ### ### Can it also run from Fergus to ilert? Fergus has no triggers in the catalog today, so automations start in ilert. If you need the other direction, ask: your agent reads Fergus's API documentation and adds it. ### ### Do I have to build a connector for ilert or Fergus? No. Both are in the catalog with their triggers and actions. You describe the automation; your agent builds it, tests every scenario and keeps it running. ### ### Can my AI client use ilert and Fergus without building an automation? Yes. With your AI client connected to APIANT, ask it to do something in either app once and it runs that action on the spot. Ask for an automation and your agent builds it, tests every scenario and keeps it running. One connection covers both. ### ### What happens when something fails? Your agent works that out for you. It plans the failure paths along with the happy path, then tests every scenario before it ships. ### ### Is there a free plan? Yes. Every plan includes the agent, including free, and building from your own AI client spends no assistant credits.