--- title: "Connect Docparser to SigningHub - APIANT.ai" description: "When \"Parsed Document Data Available\" fires in Docparser, your agent runs \"Add Document\" in SigningHub." canonical: "https://apiant.ai/connect/docparser-to-signinghub" --- # Connect Docparser to SigningHub When **Parsed Document Data Available** fires in [Docparser](https://apiant.ai/connections/docparser), your agent runs **Add Document** in [SigningHub](https://apiant.ai/connections/signinghub). Describe the whole flow and it is built, tested on every scenario and kept running. Docparser **2** triggers Docparser **2** actions SigningHub **11** 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 SigningHub 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 SigningHub - When **Parsed Document Data Available** in Docparser then **Add Document** in SigningHub - When **Parsed Table Row Available** in Docparser then **Add User** in SigningHub 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 SigningHub ## Triggers and actions 2 triggers · 13 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 Digital Signature** Adds a digital signature field to a document in a SigningHub package and assigns it to a recipient in the workflow. - Action **Add Document** Uploads a document file into an existing SigningHub document package. - Action **Add Electronic Signature** Adds an electronic signature field to a document in a package, assigned to a recipient in the workflow. - Action **Add Recipient to Workflow** Adds a signer or other recipient to a document package's workflow. - Action **Add User** Registers a new user in your SigningHub enterprise account, optionally with a password, role and profile details. - Action **Create Integration URL** Generates an encrypted SigningHub link that opens a shared document package so a user can view and sign it from your application. - Action **Create Package** Creates a new document package in SigningHub to hold documents and recipients for a signing workflow. - Action **Download Package** Downloads a document package as a Base64-encoded file: a PDF for a single-document package, or a zip of all its documents. - Action **Get Document Fields** Returns the fields on a document in a SigningHub package: signature, initials, in-person, text, checkbox, radio, dropdown, listbox, QR code, attachment and comment fields. - Action **Get Package** Returns the details of a SigningHub document package: its name, owner, status and the documents it contains. - Action **Share Document for Signing** Shares a prepared document package with its signers and starts the signing workflow. ## Each app on its own - [ **Docparser** Docparser converts your PDF documents into structured and easy-to-handle data.](https://apiant.ai/connections/docparser) - [ **SigningHub** SigningHub is an e-signature service with a powerful workflow engine that boosts team productivity by...](https://apiant.ai/connections/signinghub) 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](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 SigningHub - [ **HubSpot to SigningHub** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-signinghub) - [ **Salesforce to SigningHub** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/salesforce-to-signinghub) - [ **Slack to SigningHub** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/slack-to-signinghub) - [ **Google Sheets to SigningHub** Google Sheets](https://apiant.ai/connect/google-sheets-to-signinghub) - [ **Gmail to SigningHub** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/gmail-to-signinghub) - [ **Google Calendar to SigningHub** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/google-calendar-to-signinghub) Questions ## Docparser and SigningHub, 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 SigningHub when something happens in Docparser? Any of SigningHub's 11 actions, including Create Integration URL, Create Package, Add Digital Signature and Add Document. Your agent maps the data both ways and tests every scenario before it ships. ### ### Can it also run from SigningHub to Docparser? SigningHub has no triggers in the catalog today, so automations start in Docparser. If you need the other direction, ask: your agent reads SigningHub's API documentation and adds it. ### ### Do I have to build a connector for Docparser or SigningHub? 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 SigningHub 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.