--- title: "Connect Docparser to Stedi - APIANT.ai" description: "When \"Parsed Document Data Available\" fires in Docparser, your agent runs \"Add event destination\" in Stedi." canonical: "https://apiant.ai/connect/docparser-to-stedi" --- # Connect Docparser to Stedi When **Parsed Document Data Available** fires in [Docparser](https://apiant.ai/connections/docparser), your agent runs **Add event destination** in [Stedi](https://apiant.ai/connections/stedi). Describe the whole flow and it is built, tested on every scenario and kept running. Docparser **2** triggers Docparser **2** actions Stedi **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 Docparser and Stedi 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 Docparser can start in Stedi - When **Parsed Document Data Available** in Docparser then **Add event destination** in Stedi - When **Parsed Table Row Available** in Docparser then **Update event destination** in Stedi 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 Docparser and Stedi ## Triggers and actions 2 triggers · 11 actions - Trigger **Parsed Document Data Available** Triggers whenever a new Document is processed and parsed data is available. - Trigger **Parsed Table Row Available** Triggers whenever a new Document is processed and parsed table rows are available. - Action **Fetch Document From URL** Fetches a new document from a publicly accessible URL and imports it into Docparser to begin parsing. (To receive the parsing results, you'll need a separate Zap listening for the "New Parsed Data Available" Trigger). - Action **Upload Document** Uploads a new document to Docparser which will immediately begin parsing after reception. (To receive the parsing results, you'll need a separate Zap listening for the "New Parsed Data Available" Trigger). - Action **Add event destination** Create a new event destination for receiving Stedi webhook events. - Action **Check eligibility** Runs a real-time eligibility and benefits check (X12 270/271) against a payer for a patient and returns the payer's coverage and benefits response. - Action **Delete event destination** Permanently deletes a Stedi event destination so it stops receiving events. This cannot be undone; to pause delivery instead, update the destination's status to DISABLED. - Action **Find payers by criteria** Searches the Stedi Payer Network for payers matching a name, payer ID or alias, optionally filtered by supported transaction types, coverage types, operating states and insurance programs. Returns matching payers ranked by relevance. - Action **Get event destination** Retrieve an event destination by id. - Action **Get payer** Retrieve a single payer record by id. - Action **List event destinations** Lists the event destinations configured in your Stedi account, optionally filtered by status or event type. - Action **List payers** Lists every payer Stedi supports, with payer IDs, aliases, supported transactions and enrollment requirements. - Action **Update event destination** Updates an existing Stedi event destination's name, URL, subscribed event types, description, status or concurrency limit. Fields left blank are not changed. ## Each app on its own - [ **Docparser** Docparser converts your PDF documents into structured and easy-to-handle data.](https://apiant.ai/connections/docparser) - [ **Stedi** API-based healthcare clearinghouse for eligibility checks, claims submission, claim status, and remittance...](https://apiant.ai/connections/stedi) Reviews ## What our customers say ## More from Docparser - [ **Docparser to Prismix** Real-time uptime for 77 AI APIs (OpenAI, Anthropic, Cursor, Gemini) — free JSON endpoint, no auth required](https://apiant.ai/connect/docparser-to-prismix) - [ **Docparser to HubSpot** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/docparser-to-hubspot) - [ **Docparser to Salesforce** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/docparser-to-salesforce) - [ **Docparser to Slack** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/docparser-to-slack) - [ **Docparser to Google Sheets** Google Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.](https://apiant.ai/connect/docparser-to-google-sheets) - [ **Docparser to Gmail** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/docparser-to-gmail) ## More into Stedi - [ **HubSpot to Stedi** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-stedi) - [ **Salesforce to Stedi** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/salesforce-to-stedi) - [ **Slack to Stedi** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/slack-to-stedi) - [ **Google Sheets to Stedi** Google Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.](https://apiant.ai/connect/google-sheets-to-stedi) - [ **Gmail to Stedi** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/gmail-to-stedi) - [ **Google Calendar to Stedi** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/google-calendar-to-stedi) Questions ## Docparser and Stedi, answered ### ### What can start an automation from Docparser? Any of Docparser's 2 triggers in the catalog, including Parsed Document Data Available and Parsed Table Row Available. Describe the moment in plain language and your agent picks the right one. ### ### What can your agent do in Stedi when something happens in Docparser? Any of Stedi's 9 actions, including Update event destination, Add event destination, Check eligibility and Find payers by criteria. Your agent maps the data both ways and tests every scenario before it ships. ### ### Can it also run from Stedi to Docparser? Stedi has no triggers in the catalog today, so automations start in Docparser. If you need the other direction, ask: your agent reads Stedi's API documentation and adds it. ### ### Do I have to build a connector for Docparser or Stedi? 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 Docparser and Stedi 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.