--- title: "Connect Sorry to Elastic Cloud - APIANT.ai" description: "When \"New notice\" fires in Sorry, your agent runs \"Add Elasticsearch project\" in Elastic Cloud." canonical: "https://apiant.ai/connect/sorry-to-elastic-cloud" --- # Connect Sorry to Elastic Cloud When **New notice** fires in [Sorry](https://apiant.ai/connections/sorry), your agent runs **Add Elasticsearch project** in [Elastic Cloud](https://apiant.ai/connections/elastic-cloud). Describe the whole flow and it is built, tested on every scenario and kept running. Sorry **1** trigger Sorry **16** actions Elastic Cloud **9** actions What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it. ## What do you want Sorry and Elastic Cloud 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 Sorry can start in Elastic Cloud - When **New notice** in Sorry then **Add Elasticsearch project** in Elastic Cloud - When **New notice** in Sorry then **Get Elasticsearch project** in Elastic Cloud 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 Sorry and Elastic Cloud ## Triggers and actions 1 trigger · 25 actions - 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. - Action **Add API key** Creates a new Elastic Cloud API key and returns it, including the secret key value, which is shown only once. - Action **Add Elasticsearch project** Creates an Elastic Cloud Serverless Elasticsearch project and returns its id, endpoints and access credentials. - Action **Delete API key** Deletes (invalidates) an Elastic Cloud API key. - Action **Delete Elasticsearch project** Schedules deletion of an Elastic Cloud Serverless Elasticsearch project. - Action **Get deployment** Returns a deployment's details, including its name, alias, health and Elasticsearch, Kibana and other resources. - Action **Get Elasticsearch project** Returns the details of one Elasticsearch serverless project, including its name, region, endpoints, cloud ID and tags. - Action **List API keys** Returns the metadata for the Elastic Cloud API keys your account is allowed to see. - Action **List Elasticsearch projects** Returns the Elasticsearch Serverless projects in your Elastic Cloud organization, optionally filtered by traffic filter or linked project. - Action **List regions** Returns the cloud provider regions where Elastic Cloud Serverless projects can be created. ## Each app on its own - [ **Sorry** Status page and incident communication platform for notifying customers about downtime.](https://apiant.ai/connections/sorry) - [ **Elastic Cloud** Managed Elasticsearch platform for full-text and vector search, log/metrics observability, and security...](https://apiant.ai/connections/elastic-cloud) Reviews ## What our customers say ## More from Sorry - [ **Sorry to Stripe** Stripe is a payment processing platform for online businesses.](https://apiant.ai/connect/sorry-to-stripe) - [ **Sorry to Trello** Trello is a visual collaboration tool that organizes projects into boards, lists, and cards.](https://apiant.ai/connect/sorry-to-trello) - [ **Sorry to Zoom** Zoom unifies cloud video conferencing, simple online meetings, group messaging, and a software-based...](https://apiant.ai/connect/sorry-to-zoom) - [ **Sorry to Twilio** Cloud communications platform for sending SMS/MMS messages, making and managing voice calls, and looking up...](https://apiant.ai/connect/sorry-to-twilio) - [ **Sorry to Typeform** Build and publish online forms, surveys, and quizzes with Typeform.](https://apiant.ai/connect/sorry-to-typeform) - [ **Sorry to Webflow** Webflow is a professional website builder and CMS for designing, building, and launching responsive...](https://apiant.ai/connect/sorry-to-webflow) ## More into Elastic Cloud - [ **HubSpot to Elastic Cloud** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-elastic-cloud) - [ **Salesforce to Elastic Cloud** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/salesforce-to-elastic-cloud) - [ **Slack to Elastic Cloud** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/slack-to-elastic-cloud) - [ **Google Sheets to Elastic Cloud** Google Sheets](https://apiant.ai/connect/google-sheets-to-elastic-cloud) - [ **Gmail to Elastic Cloud** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/gmail-to-elastic-cloud) - [ **Google Calendar to Elastic Cloud** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/google-calendar-to-elastic-cloud) Questions ## Sorry and Elastic Cloud, answered ### ### What can start an automation from Sorry? Any of Sorry's 1 trigger in the catalog, including New notice. Describe the moment in plain language and your agent picks the right one. ### ### What can your agent do in Elastic Cloud when something happens in Sorry? Any of Elastic Cloud's 9 actions, including Add API key, Add Elasticsearch project, Get deployment and Get Elasticsearch project. Your agent maps the data both ways and tests every scenario before it ships. ### ### Can it also run from Elastic Cloud to Sorry? Elastic Cloud has no triggers in the catalog today, so automations start in Sorry. If you need the other direction, ask: your agent reads Elastic Cloud's API documentation and adds it. ### ### Do I have to build a connector for Sorry or Elastic Cloud? 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 Sorry and Elastic Cloud 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.