DocsBot and Parseur Integration

Demonstration of how apps are integrated in WEXTL workflow builder[4]

Keep DocsBot and Parseur matched by integrating their events and actions. When ai events happen in DocsBot, update the Parseur automatically - without any line of code in visual workflow builder.

  • 3-day trial
  • Cancel anytime
  • Up to 10 minutes quick set up
  • GDPR
  • Data Encryption
  • 2FA
  • Local Data Region

Learn about DocsBot and Parseur

Detailed info you need to know about DocsBot and Parseur integrations in WEXTL. Explore which modules apps support and how you connect them.

  • DocsBot

    • AI
    • 1 trigger
    • 24 searches
    • 32 actions

    AI support chatbots trained on your documents.[5]

  • Parseur

    • AI
    • 2 triggers
    • 10 searches
    • 16 actions

    Document processing that extracts data from emails and PDFs.[6]

How to connect DocsBot to Parseur

Set up your DocsBot and Parseur integration in 3 simple steps[2]. No coding required. Up to 10 minutes setup.

How does the integration between DocsBot and Parseur work in WEXTL?

WEXTL exposes actions and triggers for DocsBot and Parseur that help you connect apps and automate repetitive tasks[1]. A trigger is an event that happens, and an action is a step that performs when the event has occurred.

DocsBot triggersParseur actions

DocsBot modules

  • Watch Events (Instant) Starts the workflow right away through a DocsBot webhook when a bot event happens. Each run gets the Event, Team ID and Bot ID.
  • Ask a Question Sends a one-off Question to a bot. You get the Answer with its Sources, and the History of a previous answer keeps follow-ups in context.
  • Cancel a Research Job Cancels a research job of a bot and reports the Job ID that was cancelled.
  • Capture a Lead Records contact details against a bot conversation, even when the conversation does not exist yet. Add Email, Name, Phone and Company, or More Details for anything else.
  • Chat with a Bot Talks to a bot using a Question. Keep the same Conversation ID to continue a thread, or leave it empty to start a new one and read the new ID from the result.
  • Continue a Research Job Resumes a research job that asked for clarification, using your Answers to its questions. Use Model or Web Search to override those settings for this job.
  • Create a Bot Starts a DocsBot bot called Name. Use Copy From Bot to start from an existing bot, Privacy to set who can use it and Model to choose the AI model.
  • Create a Conversation Ticket Generates a support ticket from a conversation and returns its Subject and Message. Only chat agent conversations on the Standard plan and above work.
  • Create a Document Source Uploads a File of up to 2 GB for the bot to index. DocsBot requires a Title for documents. Turn on Advanced Document Parsing for layout-aware reading.
  • Create a Source Indexes a sitemap, YouTube video, RSS feed or similar source for a bot, depending on its Type. Use Refresh Interval to re-index it on a schedule and Tags to organise it.
  • Create a Team Opens a new DocsBot team. Leave Name empty and DocsBot picks a default.
  • Create a Webhook Subscribes a Target URL to the chosen Events, so DocsBot sends a call there when they fire. Set Expires At to give the webhook an end date.
  • Delete a Bot Deletes a bot from DocsBot, and the action cannot be undone.
  • Delete a Conversation Removes one conversation of a bot. Needs edit permission on the bot.
  • Delete a Lead Removes a lead recorded by a bot.
  • Delete a Question Clears the content of a question. It is a soft delete, so the row stays in the list.
  • Delete a Source Queues a source for removal from a bot. Removal takes a few minutes, so answers may still show it for a while.
  • Delete a Webhook Deletes a webhook that was registered for a bot.
  • Escalate a Conversation Marks a conversation as escalated and fires the conversation.escalated webhook.
  • Export Leads Builds an export of the leads captured between Created From and Created To. The result is a URL.
  • Fetch a Source Document Reads one indexed file by File ID, taken from a Search Bot Sources result, and returns its Title, Page and Content.
  • Get a Bot Fetches one bot with its Name, Privacy and Question Count.
  • Get a Bot Image Upload URL Prepares an image upload for a bot and returns an Upload URL plus the Cdn URL the file will have. Give the File Name with its extension.
  • Get a Bot Report Reads the monthly report for a bot, taking the latest one unless Month is set. Also lists the Available Reports.
  • Get a Conversation Pulls one conversation with its Summary, Sentiment and Topic.
  • Get a Research Job Checks a research job for its Status and, once finished, its Response.
  • Get a Source Looks up one source with its Type, Page Count and Chunk Count.
  • Get a Team Fetches a team and its Roles, Status and Question Count.
  • Get a Webhook Pulls a webhook with its Target URL, Events and Expiration Date.
  • Get Bot Statistics Shows Resolution Rate, Deflection Rate and Time Saved for a bot. Use Last Days for a recent window or give From and To for exact dates.
  • Get Source Tag Counts Counts how many sources carry each tag. Reports Untagged and the Total as well.
  • Invite a Team Member Emails an invitation to join a team to the Invite Email address. Use Role to decide what the invited user can do.
  • List Bots Browses the bots in a team. Use Search to match a name or description, and Privacy, Sort By and Order to refine the result.
  • List Conversations Collects conversations held with a bot, giving the Title, Summary and Sentiment of each. Use Limit to read fewer.
  • List Leads Returns leads of a bot. Use Created From and Created To to keep a date range, and Limit to stop after a set count.
  • List Questions Lists questions asked of a bot. Filter by Rating, Escalated, Could Answer or an IP Hash, and narrow the dates with Created From and Created To.
  • List Research Jobs Shows the research jobs started on a bot, along with their Status and Question.
  • List Sources Gets the knowledge sources attached to a bot, optionally only those with certain Tags. Each comes with its Type and Page Count.
  • List Team Members Shows who belongs to a team, with the Display Name, Email and Role of each member.
  • List Teams Finds the teams you belong to, each with its Roles and Status.
  • List Webhooks Returns webhooks registered on a bot, with the Target URL and Status of each.
  • Make an API Call Sends a free-form request to the DocsBot REST API, signed with your saved credential.
  • Rate an Answer Records a Rating on a logged answer, using the ID of its question.
  • Remove a Team Member Removes someone from a team, or revokes a pending invite by Invite Email.
  • Respond to an Invite Answers a team invite by its Invite ID with Accept, Deny or Retry. DocsBot has no list of invites, so copy the ID from the invitation. Use Role to set what the new member can do when accepting.
  • Retry a Source Starts indexing again for a source that failed to index.
  • Search Bot Sources Runs a natural-language Query over the indexed passages of a bot. Use Top K to limit the passages returned and Alpha to balance keyword against semantic matching.
  • Send a Test Webhook Delivery Fires a sample delivery of the chosen Event to check your receiver.
  • Start a Research Job Begins a research job on a Question. Switch on Web Search, Code Interpreter or Search Documents to widen what it may use.
  • Summarize a Conversation Writes a Title, Summary and Sentiment for a conversation. Only chat agent conversations are supported.

Parseur modules

  • Copy a Document to a Mailbox Duplicates a document so the Target Mailbox gets its own copy. Read the Document ID off List Documents.
  • Copy a Mailbox Makes a duplicate of an existing Parseur mailbox.
  • Copy a Template Copies a template to another mailbox. Use the Template ID shown by List Templates, and send the copy to the Target Mailbox.
  • Create a Custom Download Defines a named download for a mailbox that covers either the whole mailbox or one table field. Use Fields to choose what a Mailbox download contains, and Table Field for a Table Field download.
  • Create a Mailbox Creates a Parseur mailbox. Start from a ready-made Mailbox Type, choose an AI Engine, and use Retention Days to set how long Parseur holds documents. Skip Name and Parseur picks one.
  • Delete a Custom Download Removes a mailbox custom download. Parseur refuses when the download is still in use.
  • Delete a Document Deletes a document from Parseur. This cannot be undone.
  • Delete a Mailbox Deletes the selected mailbox from Parseur, and it cannot be recovered afterwards.
  • Delete a Template Removes one template from a mailbox. This cannot be undone.
  • Get a Document Fetches one document by Document ID, which Watch Documents also provides. The result shows the File Name, Status and Template ID. A hex ID from an upload may not be accepted.
  • Get a Mailbox Shows one mailbox with its AI Engine, Document Count and Documents Per Status.
  • Get a Mailbox Schema Lists the fields that a mailbox extracts, as Type and Fields.
  • Get a Template Looks up a template by the Template ID that List Templates shows, giving its Name, Engine, Status and Document Count.
  • Get the Bootstrap Config Reads the general settings of Parseur, including the Choices and Mappings it accepts, the Maximum Field Lengths and the Email Domain.
  • Get the Document Logs Reads the log entries of one document, with the Created time, Code and Template Name of each. Use Search to keep entries matching a text, and Limit for the number to read.
  • List Custom Downloads Lists mailbox custom downloads by Name and Type, plus the links to each CSV and XLS file. Use Limit to set how many are returned.
  • List Documents Lists documents in a mailbox by Status, Received After or Received Before. Use Search to match part of a document name, and Include Extracted Data to add the parsed data. Parseur serves them 100 at a time.
  • List Mailboxes Retrieves the mailboxes in your Parseur account. Use Search for a name, and Sort By to order by Document count or Template count.
  • List Templates Shows the templates in a mailbox with Template ID, Name, Engine, Status and Last Activity. Pick a Limit to restrict the list.
  • Make an API Call Calls the Parseur REST API directly with a free-form request under your saved credential.
  • Reprocess a Document Runs a document through Parseur again. Its webhooks are sent again with the same document ID.
  • Skip a Document Marks a document as skipped and returns the updated document.
  • Update a Custom Download Edits a custom download on a mailbox. Use Name to rename it, Fields and Type to change what it covers, and Clear Fields to empty values when moving from Table Field to Mailbox.
  • Update a Mailbox Edits a mailbox through its Name, AI Engine, Retention Days or Sender Allow List Mode, and others. Use Clear Fields to empty a setting, since a blank field leaves it unchanged. Mailbox fields cannot be changed here.
  • Upload a Document Submits a File and its File Name to a mailbox. Parseur processes the file after this call returns, and Custom Values attach extra data to the extracted result.
  • Upload an Email or Text Submits email content or plain text to a mailbox through its Mailbox Address, with a Subject and From. Use HTML Body or Plain Text Body for the content, and note the HTML Body takes priority when both are filled.
  • Watch Documents Checks a mailbox on a schedule for documents with the Status you watch, such as Processed or Process failed. Use Limit to cap how many the first check returns.
  • Watch Events (Instant) Receives Parseur webhook events as they happen, each with its Document ID and Sender Name.

Explore alternative integrations

There are other apps[9] supported by WEXTL that can be paired with DocsBot and Parseur integrations. Pick any from the list below if the current combination isn't the one you need.

Automate DocsBot and Parseur on WEXTL®

Claim your 3-day trial to build DocsBot with Parseur integration and access every WEXTL® feature.

Cancel anytime.

Frequently asked questions

Common questions about connecting DocsBot and Parseur.

How do I connect DocsBot and Parseur?

Connect your DocsBot and Parseur accounts once, pick a trigger in one app and an action in the other, then map the fields so data flows automatically between them.[3]

What can I automate between DocsBot and Parseur?

Example: when the "Watch Events (Instant)" trigger in DocsBot fires, WEXTL can "Copy a Document to a Mailbox" in Parseur. DocsBot has 1 trigger (including Watch Events (Instant)). Parseur has 26 actions (including Copy a Document to a Mailbox, Copy a Mailbox, and Copy a Template). Add filters and transforms between steps when you need them.[1]

Can DocsBot trigger actions in Parseur, and Parseur in DocsBot?

Yes. The integration works in both directions. Use the triggers of each app to start a workflow and the actions of the other app to update it.[2]

Do I need to write code to integrate DocsBot and Parseur?

No. DocsBot-to-Parseur automations are built visually on the canvas. You can optionally add custom JavaScript with Functions when you need advanced logic.[4]

Does DocsBot integrate with Parseur in real time?

Yes. Trigger-based automations start the moment DocsBot (or Parseur) fires a new event. Webhook-backed apps run within seconds, and polling-only apps re-check on a schedule you control.[7]

How long does it take to set up a DocsBot + Parseur integration?

A first automation typically takes 5–10 minutes: connect the credential of each app once, drop a trigger + action onto the canvas, map the fields, and turn the workflow on.

Do I need a paid plan to connect DocsBot with Parseur?

You can build your DocsBot + Parseur automation on a 3-day trial with every feature unlocked. Cancel anytime.[8]

References

List of sources used to gather information about the DocsBot and Parseur integration.

  1. DocsBot and Parseur integration source code, module specs and credentials implementation.
  2. Our DocsBot and Parseur integration documentation, structured input and output parameters, scopes, and authentication methods.
  3. Official vendor API documentation for DocsBot and Parseur, used to verify field meanings, authentication flows, and anything our own specs don't fully capture.
  4. WEXTL® visual workflow builder, anonymized data from our technical support team.
  5. DocsBot integration information
  6. Parseur integration information
  7. WEXTL® Scheduling
  8. WEXTL® Pricing and Trial
  9. WEXTL® Apps Library

How we write our apps documentation

Explore how WEXTL® crafted DocsBot and Parseur integration page documentation. Used sources, the role of AI, and how the team validates the result.

Explore DocsBot and Parseur, or get started