--- title: "Connect Parseur and Sorry - APIANT.ai" description: "When \"New Document Export Failed\" fires in Parseur, your agent runs \"Update status page\" in Sorry, or \"New notice\" in Sorry to \"Create Document\" in Parseur." canonical: "https://apiant.ai/connect/parseur-to-sorry" --- # Connect Parseur and Sorry When **New Document Export Failed** fires in [Parseur](https://apiant.ai/connections/parseur), your agent runs **Update status page** in [Sorry](https://apiant.ai/connections/sorry), or **New notice** in Sorry to **Create Document** in Parseur. Describe the whole flow and it is built, tested on every scenario and kept running. Parseur **6** triggers Parseur **10** 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 Parseur 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 Parseur and Sorry can do together ### From Parseur to Sorry - When **New Document Export Failed** in Parseur then **Update status page** in Sorry - When **New Document Not Processed** in Parseur then **Add component** in Sorry ### From Sorry to Parseur - When **New notice** in Sorry then **Create Document** in Parseur - When **New notice** in Sorry then **Create Document From File** in Parseur 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 Parseur and Sorry ## Triggers and actions 7 triggers · 26 actions - Trigger **New Document Export Failed** Triggered when Parseur fails to export a document to its destination. - Trigger **New Document Not Processed** Triggered when Parseur receives a document it cannot extract data from, so you can follow it up. - Trigger **New Document Processed** Triggered when Parseur finishes extracting data from a document, with the extracted fields. - Trigger **New Document Processed (With List Items)** Triggered when Parseur finishes extracting data from a document, including any table or list fields it found (line items, rows). - Trigger **New Mailbox** Triggers when a new mailbox is created in your Parseur account. Returns the mailbox's name, email prefix, AI engine and document counts. - Trigger **New Table Field Processed** Triggers once for every row of a table or list field when Parseur finishes processing a document. Returns the row's values along with the document and mailbox it came from. - Action **Create Document** Sends text or HTML content to a Parseur mailbox as a new document, so Parseur can extract its data. Returns the new document's ID. - Action **Create Document From File** Uploads a file (PDF, DOCX, image and so on) to a Parseur mailbox as a new document, so Parseur can extract its data. Returns the new document's ID. - Action **Delete Document** Deletes a document from Parseur by its ID. - Action **Delete Mailbox** Deletes a Parseur mailbox and everything in it. This cannot be undone. - Action **Get Document** Returns one document from Parseur by its ID, including its processing status and the data Parseur extracted from it. - Action **Get Mailbox** Returns one Parseur mailbox by its ID, with its email address, document counts and settings. - Action **List Documents** Returns the documents in Parseur, optionally narrowed to one mailbox or one processing status. - Action **List Mailboxes** Returns the mailboxes in your Parseur account, with the email address to send documents to and how many documents each holds. - Action **Reprocess Document** Sends an existing document back through parsing, for example after you update its template. Returns the document's ID, name and processing status. - Action **Update Mailbox** Updates a Parseur mailbox's settings. Only the values you supply are changed — anything you leave blank keeps its current setting. - 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 - [ **Parseur** Send documents such as emails, PDFs and spreadsheets to your custom Parseur mailbox and extract any data.](https://apiant.ai/connections/parseur) - [ **Sorry** Status page and incident communication platform for notifying customers about downtime.](https://apiant.ai/connections/sorry) Reviews ## What our customers say ## More from Parseur - [ **Parseur to Salesforce** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/parseur-to-salesforce) - [ **Parseur to Slack** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/parseur-to-slack) - [ **Parseur to Stripe** Stripe is a payment processing platform for online businesses.](https://apiant.ai/connect/parseur-to-stripe) - [ **Parseur to Shopify** Shopify is a commerce platform for online stores and retail point-of-sale.](https://apiant.ai/connect/parseur-to-shopify) - [ **Parseur to QuickBooks Online** QuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...](https://apiant.ai/connect/parseur-to-quickbooks-online) - [ **Parseur to Pipedrive** Pipedrive is a sales CRM and pipeline management tool.](https://apiant.ai/connect/parseur-to-pipedrive) ## 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](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 ## Parseur and Sorry, answered ### ### What can start an automation from Parseur? Any of Parseur's 6 triggers in the catalog, including New Document Export Failed, New Document Not Processed, New Document Processed and New Document Processed (With List Items). Describe the moment in plain language and your agent picks the right one. ### ### What can your agent do in Sorry when something happens in Parseur? 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 Parseur? Yes. When something happens in Sorry, your agent can act in Parseur too. This page covers both directions: Sorry's triggers and Parseur's actions are listed here as well. ### ### Do I have to build a connector for Parseur 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 Parseur 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.