# Connect Parseur to Instatus When **New Document Export Failed** fires in [Parseur](https://apiant.ai/connections/parseur), your agent runs **Add component** in [Instatus](https://apiant.ai/connections/instatus). Describe the whole flow and it is built, tested on every scenario and kept running. Parseur **6** triggers Parseur **10** actions Instatus **14** 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 Instatus to do together? Give your AI client this address. `https://mcp.apiant.ai` 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 can start in Instatus - When **New Document Export Failed** in Parseur then **Add component** in Instatus - When **New Document Not Processed** in Parseur then **Add incident update** in Instatus 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 Instatus ## Triggers and actions 6 triggers · 24 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. - Action **Add component** Creates a new component on an Instatus status page and returns the created component. - Action **Add incident update** Posts a new update to an existing incident on an Instatus status page, optionally changing the incident status and affected component statuses. - Action **Add maintenance** Schedules a new maintenance on an Instatus status page, with its affected components, timing and subscriber notification options. - Action **Add subscriber** Adds a subscriber (by email or phone) to a status page, subscribed to all components or to specific ones. - Action **Create Incident** Creates a new incident on an Instatus status page, optionally marking affected components and notifying subscribers. - Action **Delete incident** Deletes an incident from an Instatus status page. - Action **Get component** Returns one component on an Instatus status page, including its name, current status, description and group. - Action **Get incident** Returns a single incident on a status page, including its updates, affected components and the teammate who created it. - Action **Get maintenance** Returns one scheduled maintenance on a status page, including its updates and affected components. - Action **List components** Returns the components on an Instatus status page, with each component's name, status and group. - Action **List maintenances** Returns the scheduled, in-progress and completed maintenances on an Instatus status page. - Action **List status pages** Returns the status pages in your Instatus account, including each page's id, name, subdomain and current status. - Action **List subscribers** Returns the subscribers of an Instatus status page, optionally filtered by email/phone search or subscription status. - Action **Update component** Updates a component on an Instatus status page, such as its name, description, status, order or group. ## 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) - [ **Instatus** Instatus is a tool to monitor services, manage incidents with your team, and share real-time status with...](https://apiant.ai/connections/instatus) 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 Instatus - [ **HubSpot to Instatus** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-instatus) - [ **Salesforce to Instatus** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/salesforce-to-instatus) - [ **Slack to Instatus** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/slack-to-instatus) - [ **Google Sheets to Instatus** Google Sheets](https://apiant.ai/connect/google-sheets-to-instatus) - [ **Gmail to Instatus** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/gmail-to-instatus) - [ **Google Calendar to Instatus** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/google-calendar-to-instatus) Questions ## Parseur and Instatus, 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 Instatus when something happens in Parseur? Any of Instatus's 14 actions, including Create Incident, Update component, Add component and Add incident update. Your agent maps the data both ways and tests every scenario before it ships. ### ### Can it also run from Instatus to Parseur? Instatus has no triggers in the catalog today, so automations start in Parseur. If you need the other direction, ask: your agent reads Instatus's API documentation and adds it. ### ### Do I have to build a connector for Parseur or Instatus? 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. ### ### 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.