--- title: "Connect DoiT and Sorry - APIANT.ai" description: "When \"New Alert Notification\" fires in DoiT, your agent runs \"Update status page\" in Sorry, or \"New notice\" in Sorry to \"Add support ticket\" in DoiT." canonical: "https://apiant.ai/connect/doit-to-sorry" --- # Connect DoiT and Sorry When **New Alert Notification** fires in [DoiT](https://apiant.ai/connections/doit), your agent runs **Update status page** in [Sorry](https://apiant.ai/connections/sorry), or **New notice** in Sorry to **Add support ticket** in DoiT. Describe the whole flow and it is built, tested on every scenario and kept running. DoiT **7** triggers DoiT **27** actions Sorry **1** trigger Sorry **16** actions What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it. ## What do you want DoiT and Sorry 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 DoiT and Sorry can do together ### From DoiT to Sorry - When **New Alert Notification** in DoiT then **Update status page** in Sorry - When **New Cloud Incident** in DoiT then **Add component** in Sorry ### From Sorry to DoiT - When **New notice** in Sorry then **Add support ticket** in DoiT - When **New notice** in Sorry then **Add comment** in DoiT 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 DoiT and Sorry ## Triggers and actions 8 triggers · 43 actions - Trigger **Budget Threshold Surpassed** Triggered when a budget's current spend passes one of its alert thresholds. Fires once per threshold in each budget period. - Trigger **New Alert Notification** Triggers when a DoiT cost alert sends a notification (its last-alerted time advances). - Trigger **New Cloud Incident** Triggered when a new cloud incident is reported for Google Cloud, Amazon Web Services or Microsoft Azure. - Trigger **New Cost Anomaly** Triggers when DoiT detects a new cloud cost anomaly, newest first, optionally narrowed by service, billing account, platform or severity. - Trigger **New Invoice** Triggered when a new invoice is created in your DoiT organization. - Trigger **New Service** Triggers when a new cloud service (support product) becomes available in DoiT, optionally for one platform. - Trigger **New Service (For Doers)** Triggers when a new support product (service) becomes available in DoiT, optionally limited to one cloud platform. - Action **Add alert** Creates a cost or usage alert in DoiT Cloud Analytics that notifies email or Slack recipients when a metric crosses the threshold you set. - Action **Add allocation** Creates a new DoiT allocation, either a single allocation defined by one rule or a group allocation made of several rules. - Action **Add annotation** Creates a new annotation on a date in DoiT Cloud Analytics, optionally linked to reports and labels. - Action **Add budget** Creates a new DoiT budget that tracks cloud spend for the selected scope against a fixed or recurring amount. - Action **Add comment** Adds a comment to an existing DoiT support request and returns the new comment. - Action **Add label** Creates a new label in DoiT Cloud Analytics with a name and color, ready to assign to reports, budgets and other objects. - Action **Add support ticket** Creates a new DoiT support request and returns its id, status and a link to view it in the DoiT console. - Action **Delete alert** Deletes an alert from your DoiT account. - Action **Get alert** Returns a Cloud Analytics alert by its ID, including its name, recipients, timestamps and evaluation configuration. - Action **Get anomaly** Returns one cost anomaly, including its cost impact, severity, affected service, contributing SKUs and resources, and review status. - Action **Get budget** Returns a budget's configuration and its current and forecasted utilization. An error occurs if the budget is not found. - Action **Get invoice** Returns the full details of an invoice by its invoice number, including status, amounts, due date and line items. A cancelled invoice or credit memo is returned with status CANCELED. - Action **List alerts** Returns the alerts your DoiT account has access to, optionally filtered by owner or name and sorted. - Action **List allocations** Returns the cost allocations your DoiT account has access to, optionally filtered by type, owner, name or folder. - Action **List annotations** Returns the Cloud Analytics annotations your DoiT account has access to, with their content, date, associated reports and labels. - Action **List anomalies** Returns the cloud cost anomalies DoiT detected, optionally filtered by time window, service, billing account, platform or severity. - Action **List assets** Returns the customer's assets in DoiT, such as Google Cloud billing accounts, Workspace subscriptions and AWS accounts, optionally filtered by a filter expression. - Action **List budgets** Returns the budgets your DoiT account can access, each with its amount, utilization and risk status. - Action **List CloudFlows** Returns the CloudFlows in the DoiT account, with each flow's name, published state, trigger type and last run status. - Action **List invoices** Returns the current and historical invoices for your organization, newest first, optionally filtered by platform, due date, status or creation time. - Action **List labels** Returns the Cloud Analytics labels your DoiT account can access, optionally filtered by name or type and sorted. - Action **List reports** Returns the Cloud Analytics reports your DoiT account can access, newest first, with optional filtering by name, owner, type, folder or creation time. - Action **Query Cloud Analytics** Runs a one-off Cloud Analytics query with the configuration you supply and returns the result columns and rows, without saving a report. - Action **Run CloudFlow** Starts a run of a published CloudFlow and returns the new run, which begins in pending status. - Action **Run Report** Runs a saved Cloud Analytics report and returns its results: the column schema and the result rows, plus the report's name, owner and labels. - Action **Update alert** Updates an existing DoiT alert's name, threshold settings or notification recipients. Only the values you fill in are changed. - Action **Update budget** Updates an existing DoiT budget. Only the values you supply are changed; everything else on the budget is kept. - Trigger **New notice** Triggers when a new notice (incident, maintenance or general announcement) is created on the selected Sorry status page. - Action **Add component** Creates a new component on a Sorry status page, optionally nested under a parent component. - Action **Add notice** Creates a new incident, maintenance or general notice on a Sorry status page, optionally linking affected components and publishing it to subscribers. - Action **Add notice update** Posts a new update on an existing notice on a Sorry status page, optionally publishing it to your configured integrations. - Action **Add subscriber** Adds an email or SMS subscriber to a status page, optionally limited to specific components, so they receive status notices. - Action **Delete notice** Deletes a notice (incident, maintenance or general) from a Sorry status page. - Action **Delete subscriber** Permanently removes a subscriber from a status page. - Action **Get notice** Returns a single notice from a status page, including its type, state, subject, synopsis and link. - Action **Get status page** Returns a single Sorry status page with its name, state, timezone, support details and notification settings, optionally including related brand, components, notices and more. - Action **List components** Returns all components (the services or infrastructure elements) shown on a Sorry status page, with their current state. - Action **List notices** Returns the notices (incidents, maintenance and general notices) posted on a Sorry status page, optionally filtered by type, state, subject or creation date. - Action **List notice updates** Returns all updates posted on a notice on one of your Sorry status pages, optionally filtered by creation date or content. - Action **List status pages** Returns all status pages in your Sorry account, optionally filtered by name or creation date. - Action **List subscribers** Returns the subscribers on a status page, optionally only those who receive notices for a specific component. - Action **Update component** Updates a component on a Sorry status page, such as its name, description, position or parent component. - Action **Update notice** Updates an existing notice on a Sorry status page — change its subject or state, add a comment, set affected components or reschedule planned maintenance. - Action **Update status page** Updates a status page's settings, such as its name, timezone, support contact details, search visibility and language. ## Each app on its own - [ **DoiT** DoiT ensures your cloud spend generates value for your business and eliminates wasted time for your teams.](https://apiant.ai/connections/doit) - [ **Sorry** Status page and incident communication platform for notifying customers about downtime.](https://apiant.ai/connections/sorry) Reviews ## What our customers say ## More from DoiT - [ **DoiT to HubSpot** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/doit-to-hubspot) - [ **DoiT to Salesforce** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/doit-to-salesforce) - [ **DoiT to Slack** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/doit-to-slack) - [ **DoiT to Google Sheets** Google Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.](https://apiant.ai/connect/doit-to-google-sheets) - [ **DoiT to Gmail** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/doit-to-gmail) - [ **DoiT to Google Calendar** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/doit-to-google-calendar) ## More into Sorry - [ **HubSpot to Sorry** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-sorry) - [ **Salesforce to Sorry** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/salesforce-to-sorry) - [ **Slack to Sorry** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/slack-to-sorry) - [ **Google Sheets to Sorry** Google Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.](https://apiant.ai/connect/google-sheets-to-sorry) - [ **Gmail to Sorry** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/gmail-to-sorry) - [ **Google Calendar to Sorry** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/google-calendar-to-sorry) Questions ## DoiT and Sorry, answered ### ### What can start an automation from DoiT? Any of DoiT's 7 triggers in the catalog, including New Alert Notification, New Cloud Incident, New Cost Anomaly and New Invoice. Describe the moment in plain language and your agent picks the right one. ### ### What can your agent do in Sorry when something happens in DoiT? Any of Sorry's 16 actions, including Update component, Update notice, Update status page and Add component. Your agent maps the data both ways and tests every scenario before it ships. ### ### Can it also run from Sorry to DoiT? Yes. When something happens in Sorry, your agent can act in DoiT too. This page covers both directions: Sorry's triggers and DoiT's actions are listed here as well. ### ### Do I have to build a connector for DoiT or Sorry? 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 DoiT and Sorry 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.