ChatBotKit and Sonix Integration

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

Connect ChatBotKit and Sonix to automate ai workflows. Trigger events from one app, run actions in the other and use AI to make smart decisions. Integrate apps in 3 simple steps - no code required.

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

Learn about ChatBotKit and Sonix

Detailed info you need to know about ChatBotKit and Sonix 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]

  • Sonix

    • AI
    • 6 searches
    • 6 actions

    Automated transcription and translation for audio and video content.[6]

How to connect ChatBotKit to Sonix

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

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

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

Sonix modules

  • Create a New Media Uploads an audio or video file to Sonix for transcription in a Language. Use File URL for files over 100MB, or Transcript Text to align an existing transcript instead of transcribing.
  • Create a Translation Requests a translation of a transcribed recording into another Language. Run Get a Translation Status to follow its progress.
  • Delete a Media Removes a recording from your Sonix account.
  • Get a JSON Transcript Pulls the finished transcript of a completed recording in structured JSON form, with the Name of the recording alongside it.
  • Get a Media Status Looks up one recording and reports its Status, Language, Created at, Public URL and Custom Data.
  • Get a Text Transcript Returns the transcript of a finished recording as text, looked up by its Media ID.
  • Get a Translation Retrieves the translated transcript of a recording. Use Language to choose which translation to read, and only completed recordings are offered.
  • Get a Translation Status Looks up the Status of the translation of a recording into one Language, using its Media ID.
  • Make an API Call Runs a free-form request against the Sonix REST API using your saved credential.
  • Search Media Finds recordings in your Sonix account. Use Search to match by name, Status to keep completed, transcribing, aligning or failed ones, and Limit to cap how many are returned.
  • Submit Multitrack Media Submits a recording with several audio tracks for transcription, with Multitrack turned on. Use Speaker Labels for a JSON array of speaker names and Keywords to hint at words the engine should expect.
  • Update a Media Changes a recording in Sonix. Set Name to rename it, Custom Label to label it, or Folder ID to put it in another folder.

Explore alternative integrations

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

Automate ChatBotKit and Sonix on WEXTL®

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

Cancel anytime.

Frequently asked questions

Common questions about connecting ChatBotKit and Sonix.

How do I connect ChatBotKit and Sonix?

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

Example: when the "Watch Event Logs" trigger in ChatBotKit fires, WEXTL can "Create a New Media" in Sonix. ChatBotKit has 4 triggers (including Watch Event Logs, Watch New Contacts, and Watch New Conversations). Sonix has 12 actions (including Create a New Media, Create a Translation, and Delete a Media). Add filters and transforms between steps when you need them.[1]

Can ChatBotKit trigger actions in Sonix, and Sonix 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 Sonix?

No. ChatBotKit-to-Sonix 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 Sonix in real time?

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

You can build your ChatBotKit + Sonix 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 Sonix integration.

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

Explore ChatBotKit and Sonix, or get started