--- title: "Connect incident.io to Parallel Web Systems - APIANT.ai" description: "When \"New Incident\" fires in incident.io, your agent runs \"Add FindAll run\" in Parallel Web Systems." canonical: "https://apiant.ai/connect/incident-io-to-parallel-web-systems" --- # Connect incident.io to Parallel Web Systems When **New Incident** fires in [incident.io](https://apiant.ai/connections/incident-io), your agent runs **Add FindAll run** in [Parallel Web Systems](https://apiant.ai/connections/parallel-web-systems). Describe the whole flow and it is built, tested on every scenario and kept running. incident.io **1** trigger incident.io **10** actions Parallel Web Systems **13** actions What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it. ## What do you want incident.io and Parallel Web Systems 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 incident.io can start in Parallel Web Systems - When **New Incident** in incident.io then **Add FindAll run** in Parallel Web Systems - When **New Incident** in incident.io then **Add monitor** in Parallel Web Systems 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 incident.io and Parallel Web Systems ## Triggers and actions 1 trigger · 23 actions - Trigger **New Incident** Triggers when a new incident is declared in incident.io, optionally limited to a status, severity, incident type or mode. - Action **Add follow-up** Creates a follow-up on an incident, with an optional description, assignee, team, category, priority and labels. - Action **Add incident update** Shares an update on an incident: a message, a move to a new status, a new severity, or any combination. - Action **Create Incident** Creates a new incident in incident.io, optionally setting its severity, type, status, roles, timestamps and custom fields. - Action **Find Users On-Call** Finds the users on-call for a schedule over a window of time (or right now), returning each effective shift with its user after overrides are applied. - Action **Get incident** Returns a single incident, including its status, severity, role assignments, timestamps and custom field values. - Action **Get Schedule** Returns a single on-call schedule, including its rotations, time zone and current shifts. - Action **List actions** Returns the actions recorded on incidents in your incident.io organisation, optionally filtered by incident, incident mode, or created/updated date. - Action **List schedules** Returns every on-call schedule configured in your incident.io account, including its rotations and who is currently on shift. - Action **List severities** Returns every incident severity configured for your incident.io organisation. - Action **List users** Returns the users in your incident.io account, optionally filtered by email address or Slack user ID. - Action **Add FindAll run** Starts a Parallel FindAll run that searches the web for every entity matching your objective and match conditions. The run starts queued; retrieve its status and results with the FindAll run id it returns. - Action **Add monitor** Creates a Parallel monitor that watches a web search query, or the output of an existing task run, for material changes on a schedule. The monitor runs once right away and then on the chosen frequency. - Action **Cancel monitor** Permanently stops a monitor from running. Cancellation cannot be undone; cancelling an already-cancelled monitor changes nothing. - Action **Create Async Web Enrichment** Starts an asynchronous web research/enrichment task run in Parallel. Returns immediately with the run in status 'queued'; fetch the result later with the run id. - Action **Extract web content** Extracts relevant excerpts (and optionally full content) as markdown from up to 20 web URLs. - Action **Fetch Results for Async Runs** Retrieves the result of a Parallel task run (created asynchronously) by its run ID, waiting until the run completes or the timeout elapses. - Action **Find entities by objective** Returns up to the chosen number of people or companies, ranked, that match a natural-language description of the entities you want. - Action **Get FindAll run** Retrieve a FindAll run's status, candidate metrics, generator and metadata. - Action **Get FindAll run result** Retrieve a snapshot of a FindAll run's result: run status and metrics plus every candidate evaluated so far with its match status, output and citations. - Action **Get monitor** Retrieves a monitor by its ID, including its type, status, frequency, query settings, webhook configuration and, for snapshot monitors, the latest output. - Action **List monitors** List monitors in the Parallel account, newest first, optionally filtered by type and status. - Action **Search web** Searches the web with Parallel and returns ranked results with relevant excerpts. - Action **Update monitor** Updates an existing Parallel monitor's frequency, processor, webhook, metadata, query or source settings. Only the fields you fill in are changed. ## Each app on its own - [ **incident.io** incident.io is an incident management platform, designed for your entire organisation.](https://apiant.ai/connections/incident-io) - [ **Parallel Web Systems** Parallel Web Systems is a web search platform that enables AI agents to find, extract, and enrich...](https://apiant.ai/connections/parallel-web-systems) Reviews ## What our customers say ## More from incident.io - [ **incident.io to Salesforce** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/incident-io-to-salesforce) - [ **incident.io to Slack** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/incident-io-to-slack) - [ **incident.io to Mailchimp** Mailchimp marketing automation and email platform.](https://apiant.ai/connect/incident-io-to-mailchimp) - [ **incident.io to Stripe** Stripe is a payment processing platform for online businesses.](https://apiant.ai/connect/incident-io-to-stripe) - [ **incident.io to Shopify** Shopify is a commerce platform for online stores and retail point-of-sale.](https://apiant.ai/connect/incident-io-to-shopify) - [ **incident.io to QuickBooks Online** QuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...](https://apiant.ai/connect/incident-io-to-quickbooks-online) ## More into Parallel Web Systems - [ **Salesforce to Parallel Web Systems** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/salesforce-to-parallel-web-systems) - [ **monday.com to Parallel Web Systems** monday.com helps you move projects forward fast, letting everyone know what's been done on a task—and what...](https://apiant.ai/connect/monday-com-to-parallel-web-systems) - [ **HubSpot to Parallel Web Systems** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-parallel-web-systems) - [ **Slack to Parallel Web Systems** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/slack-to-parallel-web-systems) - [ **Google Sheets to Parallel Web Systems** Google Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.](https://apiant.ai/connect/google-sheets-to-parallel-web-systems) - [ **Gmail to Parallel Web Systems** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/gmail-to-parallel-web-systems) Questions ## incident.io and Parallel Web Systems, answered ### ### What can start an automation from incident.io? Any of incident.io's 1 trigger in the catalog, including New Incident. Describe the moment in plain language and your agent picks the right one. ### ### What can your agent do in Parallel Web Systems when something happens in incident.io? Any of Parallel Web Systems's 13 actions, including Create Async Web Enrichment, Update monitor, Add FindAll run and Add monitor. Your agent maps the data both ways and tests every scenario before it ships. ### ### Can it also run from Parallel Web Systems to incident.io? Parallel Web Systems has no triggers in the catalog today, so automations start in incident.io. If you need the other direction, ask: your agent reads Parallel Web Systems's API documentation and adds it. ### ### Do I have to build a connector for incident.io or Parallel Web Systems? 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 incident.io and Parallel Web Systems 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.