--- title: "Connect incident.io to Qdrant - APIANT.ai" description: "When \"New Incident\" fires in incident.io, your agent runs \"Add collection\" in Qdrant." canonical: "https://apiant.ai/connect/incident-io-to-qdrant" --- # Connect incident.io to Qdrant When **New Incident** fires in [incident.io](https://apiant.ai/connections/incident-io), your agent runs **Add collection** in [Qdrant](https://apiant.ai/connections/qdrant). Describe the whole flow and it is built, tested on every scenario and kept running. incident.io **1** trigger incident.io **10** actions Qdrant **15** 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 Qdrant 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 Qdrant - When **New Incident** in incident.io then **Add collection** in Qdrant - When **New Incident** in incident.io then **Add payload index** in Qdrant 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 Qdrant ## Triggers and actions 1 trigger · 25 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 collection** Creates a new Qdrant collection with the given name and vector configuration. - Action **Add payload index** Creates a payload index on a field of a Qdrant collection so that filters on that field run fast. - Action **Add points** Adds points (vectors with optional payloads) to a Qdrant collection, overwriting any existing point with the same id. - Action **Add snapshot** Creates a new snapshot of a Qdrant collection and returns the snapshot's name, size and checksum. - Action **Count points** Returns the number of points in a Qdrant collection, optionally only those matching a payload filter. - Action **Delete collection** Deletes a Qdrant collection and all of the points and data stored in it. - Action **Delete points** Deletes points from a Qdrant collection, either by a list of point ids or by every point matching a filter. - Action **Find points by vector** Returns the points in a collection whose vectors are closest to the vector you supply, ranked by similarity score, with their payloads. - Action **Get collection** Returns the details of a Qdrant collection: its status, point and vector counts, segment count, configuration and payload index schema. - Action **Get point** Returns a single point from a Qdrant collection, including its payload and vector. - Action **List collections** Returns the names of all collections in your Qdrant cluster. - Action **List points** Returns the points stored in a Qdrant collection, optionally narrowed by a payload filter and ordered by a payload field. - Action **List snapshots** Returns every snapshot stored for a Qdrant collection, with each snapshot's file name, creation time, size and checksum. - Action **Update collection** Updates the settings of an existing Qdrant collection, such as its vector, index, optimizer, quantization, strict-mode or metadata parameters. - Action **Update point payload** Sets payload values on points in a Qdrant collection, chosen by point ids or a filter. Keys you supply are added or overwritten; other existing payload keys are kept. ## 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) - [ **Qdrant** Vector database and search engine for similarity search, RAG, recommendations, and AI agent retrieval at...](https://apiant.ai/connections/qdrant) 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 Qdrant - [ **HubSpot to Qdrant** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-qdrant) - [ **Salesforce to Qdrant** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/salesforce-to-qdrant) - [ **Slack to Qdrant** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/slack-to-qdrant) - [ **Google Sheets to Qdrant** Google Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.](https://apiant.ai/connect/google-sheets-to-qdrant) - [ **Gmail to Qdrant** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/gmail-to-qdrant) - [ **Google Calendar to Qdrant** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/google-calendar-to-qdrant) Questions ## incident.io and Qdrant, 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 Qdrant when something happens in incident.io? Any of Qdrant's 15 actions, including Update collection, Update point payload, Add collection and Add payload index. Your agent maps the data both ways and tests every scenario before it ships. ### ### Can it also run from Qdrant to incident.io? Qdrant has no triggers in the catalog today, so automations start in incident.io. If you need the other direction, ask: your agent reads Qdrant's API documentation and adds it. ### ### Do I have to build a connector for incident.io or Qdrant? 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 Qdrant 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.