ChatBotKit and Parseur Integration

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

Build ai workflows between ChatBotKit and Parseur on a visual canvas. Set up data fields sync between apps once and let data flow when events come automatically. Integration will work without code and your team will see the workflow inside WEXTL® builder.

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

Learn about ChatBotKit and Parseur

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

  • ChatBotKit

    • AI
    • 4 triggers
    • 60 searches
    • 85 actions

    Build and run AI agents: chat with bots, manage datasets, skillsets, contacts and tasks, and watch new conversations in ChatBotKit.[5]

  • Parseur

    • AI
    • 2 triggers
    • 10 searches
    • 16 actions

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

How to connect ChatBotKit to Parseur

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

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

WEXTL exposes actions and triggers for ChatBotKit 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.

ChatBotKit triggersParseur actions

ChatBotKit modules

  • Answer Questions About a State Asks a model to answer a list of Questions about a State you describe. Returns the Answers and Usage.
  • Attach a File to a Dataset Links an existing file to a dataset. Use Type to say how the file is attached.
  • Cancel a Task Stops a task from running on its schedule. Returns the task Id.
  • Cancel a Task Execution Aborts a task run that is still in progress and returns its Id and Task Id.
  • Compact a Conversation Summarizes the history of a stored conversation and returns the summary Text with Usage.
  • Compact Messages into a Summary Summarizes the Messages you send without saving a conversation. Use Bot, Model, Dataset or Skillset to set the configuration it runs with, and read back the Text and Usage.
  • Complete a Chat Runs a chat from a list of Messages and replies once, without keeping a conversation. Choose who answers with Bot or Model, not both, and give it abilities and knowledge with Skillset or Dataset. Returns Text, Usage and End.
  • Continue a Chat in the Background Queues the next turn of a stored conversation without waiting for the answer. Leave Text empty to continue from the existing conversation state and use Channel Id to deduplicate dispatch requests. Returns the Channel Id.
  • Create a Blueprint Adds a blueprint, a container that groups bots, datasets and other resources. Use Visibility to set who can see it and Contact to tie it to a contact.
  • Create a Bot Builds a chatbot. Set how it answers with Model, Backstory, Dataset and Skillset, and who can see it with Visibility. Returns the new bot Id.
  • Create a Bot Session Opens a session for a bot and returns the Token, Conversation Id and Expires At. Use Session Length (seconds) to set the maximum time the session is open and Messages to include starting messages in the conversation.
  • Create a Chat Completion Calls an OpenAI-compatible chat completion for the chosen Model and Messages. Tune it with Temperature, Max Tokens or Extra Settings (JSON). Returns the Choices and Usage.
  • Create a Contact Saves a contact that bots and conversations can be tied to. Fill Name, Email, Phone or Fingerprint to identify it, and Nickname or Preferences for details.
  • Create a Conversation Starts a conversation tied to a Bot, Contact, Task Id or Space Id, optionally seeded with Messages. Returns the Id with the Messages.
  • Create a Conversation Message Adds a message of a given Type and Text to a conversation. Use Entities (JSON) to attach known entities. To get a reply, use Send a Message and Get a Reply.
  • Create a Conversation Session Issues a session token tied to one conversation. Use Session Length (seconds) to set its lifetime and read the Token and Expires At from the result.
  • Create a Dataset Adds a dataset, the store that bots search. Tune matching with Reranker, Search Minimum Score and Search Max Records.
  • Create a Dataset Record Stores a piece of Text in a dataset, with its Source and Meta, so bots can find it later.
  • Create a File Registers an empty file record to receive content later through Upload a File. Use Visibility to control who can see it.
  • Create a Memory Stores a fact in a memory for a Contact or Bot. Use Expires At to delete it automatically at a set time.
  • Create a Secret Stores a secret that skillset abilities can use. Use Kind to make it Shared or Personal, Type for how it authenticates, Value for the secret itself and Config for extra settings.
  • Create a Skillset Adds a skillset, a collection of abilities that bots can call. Fill it with Create a Skillset Ability. Use State to enable or disable it and Visibility to set who can see it.
  • Create a Skillset Ability Defines a new skillset ability. Use Instruction to describe it, Linked Secret Id, Linked File Id, Linked Bot Id or Linked Space Id to connect the resource it uses, and Linked Computer Id when it runs shell commands.
  • Create a Space Adds a storage space for files. Give it an Alias and Name, and link it to a Blueprint or Contact.
  • Create a Task Defines an autonomous job for a Bot. Add a Schedule and Timezone to run it on a clock, and cap it with Max Iterations, Max Time or Max Calls.
  • Create a Trigger Integration Builds an integration that triggers a bot. Use Schedule to set an interval, cron expression or ISO date, Timezone to evaluate it in, and turn on Authenticate to require authentication.
  • Create a User Adds a sub-account user with an Email, Name and Image. Use Limits (JSON) to set limits on the user.
  • Create a User Session Issues a session token that acts as one of your users. Returns the Token and Expires At. Pass Config (JSON) for extra settings.
  • Create an Extract Integration Sets up an integration that extracts structured data from conversations. Use Schema to define what to extract and Request to send the result to a webhook. Link it to a Bot, Blueprint or Model.
  • Delete a Blueprint Removes a blueprint. Turn on Delete Resources to remove what it holds too.
  • Delete a Bot Removes a chatbot from your ChatBotKit account.
  • Delete a Contact Deletes a contact record from your account.
  • Delete a Conversation Removes a conversation from your ChatBotKit history.
  • Delete a Conversation Message Deletes one message from the chat history of a conversation.
  • Delete a Dataset Removes a dataset from ChatBotKit and returns its Id.
  • Delete a Dataset Record Clears one entry inside a dataset.
  • Delete a File Deletes a file from your ChatBotKit file storage.
  • Delete a Memory Removes one remembered note from your account.
  • Delete a Secret Deletes a stored credential secret from your account.
  • Delete a Skillset Removes a skillset, the group of abilities that bots call.
  • Delete a Skillset Ability Deletes one ability that bots can call.
  • Delete a Space Removes a storage space from ChatBotKit.
  • Delete a Space File Deletes the file or folder at a Path in a space. Turn on Recursive to remove folders with their contents.
  • Delete a Task Deletes a scheduled task from the account.
  • Delete a Trigger Integration Removes an integration that starts bots by schedule or outside call.
  • Delete a User Deletes a sub-account user from your ChatBotKit account.
  • Delete an Extract Integration Removes an extraction integration from ChatBotKit.
  • Detach a File from a Dataset Unlinks a file from its dataset. Turn on Delete Records to remove the records that came from the file too.
  • Download a File Downloads the content of a stored file and returns it as File with its File Name and Content Type.
  • Download a Space File Reads one file at a Path inside a space and returns it as File with its File Name and Content Type.

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 ChatBotKit and Parseur integrations. Pick any from the list below if the current combination isn't the one you need.

Automate ChatBotKit and Parseur on WEXTL®

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

Cancel anytime.

Frequently asked questions

Common questions about connecting ChatBotKit and Parseur.

How do I connect ChatBotKit and Parseur?

Connect your ChatBotKit 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 ChatBotKit and Parseur?

Example: when the "Watch Event Logs" trigger in ChatBotKit fires, WEXTL can "Copy a Document to a Mailbox" in Parseur. ChatBotKit has 4 triggers (including Watch Event Logs, Watch New Contacts, and Watch New Conversations). 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 ChatBotKit trigger actions in Parseur, and Parseur in ChatBotKit?

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 ChatBotKit and Parseur?

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

Does ChatBotKit integrate with Parseur in real time?

Yes. Trigger-based automations start the moment ChatBotKit (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 ChatBotKit + 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 ChatBotKit with Parseur?

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

References

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

  1. ChatBotKit and Parseur integration source code, module specs and credentials implementation.
  2. Our ChatBotKit and Parseur integration documentation, structured input and output parameters, scopes, and authentication methods.
  3. Official vendor API documentation for ChatBotKit 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. ChatBotKit 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 ChatBotKit and Parseur integration page documentation. Used sources, the role of AI, and how the team validates the result.

Explore ChatBotKit and Parseur, or get started