BatchDialer and BotStar Integration

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

Connect BatchDialer and BotStar to automate communication 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 BatchDialer and BotStar

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

  • BatchDialer

    • Communication
    • 2 triggers
    • 6 searches
    • 5 actions

    Cloud predictive dialer for sales and collections teams with contacts and campaigns.[5]

  • BotStar

    • Communication
    • 1 trigger
    • 8 searches
    • 18 actions

    Chatbot builder for Messenger and web chat.[6]

How to connect BatchDialer to BotStar

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

How does the integration between BatchDialer and BotStar work in WEXTL?

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

BatchDialer triggersBotStar actions

BatchDialer modules

  • Add a Single Contact Creates one contact from a First Name, with optional Last Name, Address, mailing address fields, Email and Score. Add several entries under Phone Numbers to store each number the person can be dialed on.
  • Add Contacts Adds several contacts to BatchDialer in one request, each with its names, addresses, Email and up to five phone numbers. Use Campaign IDs to enrol them in campaigns, or Webhook URL to be notified when the import finishes.
  • Delete a Contact Deletes a contact from your BatchDialer account by Contact ID.
  • Get a Contact Looks up one contact by Contact ID. Returns its names, addresses, phone numbers, Score, campaign and list counts, and the date it was last touched.
  • Get a Transcription as HTML Fetches the transcript of one recorded call, using the Call ID, as ready-made HTML. The output is a single HTML value you can drop into an email or a page.
  • Get a Transcription as JSON Reads the transcript of a call by its Call ID. Returns structured entries, each with a Time, a Role for who spoke and the Text said.
  • List Contacts Returns contacts from your account as separate items. Narrow them with Date Added, Date Modified or Date Deleted, which keep only contacts changed between that moment and now, and use Limit to cap the count.
  • Make an API Call Runs a free-form request against the BatchDialer REST API using your saved credential.
  • Search Campaigns Finds campaigns and sorts them by Sort Field, ascending or descending per Sort Direction. Use Filter to match a Search keyword, Campaign Status, Agent, External ID or a Contacts Count Range, and set Limit to size the result.
  • Search Recent Calls Lists call records that match a Call Disposition, such as answered or no answer. Add Call Direction to see only inbound or outbound calls, Call Date to match one date, and Limit to set the number returned.
  • Update a Contact Changes fields on an existing contact, such as its Title, name, address, Email, Score or Comments. Pass the Contact ID of the contact to change, Phone Numbers for the phone records, and Custom Fields for your own data.
  • Watch Calls Polls BatchDialer for new call records, each one starting the workflow with its Call Disposition. Narrow the check with Call Direction, and use Limit to bound the calls handled in one check.
  • Watch Contacts Polls your account on a schedule for contacts that were added, modified or deleted, depending on Trigger on. Each match starts the workflow separately. Set Limit to cap how many contacts each check handles.

BotStar modules

  • Create a Bot Sets up a new chatbot in your BotStar account under a Name of your choice.
  • Create a Bot Attribute Defines an attribute on a bot with a Data Type and an optional starting Value. Add Language Values for a separate value per language.
  • Create a CMS Entity Opens a content table in the CMS of your bot, and can seed it with columns. Add Fields to start with some already defined.
  • Create a CMS Item Saves a new row in a CMS entity. Use Field Values to fill its columns and Status to set the state.
  • Create a Custom User Attribute Registers an extra profile field for bot users, with an Attribute Name and a Type.
  • Create CMS Entity Fields Appends new columns to an existing CMS entity. Every entry of Fields has a unique name, a name and a data type.
  • Delete a Bot Attribute Deletes an attribute from a bot, in the draft only or in the draft and live version.
  • Delete a CMS Entity Removes a CMS entity, with all the items stored in it.
  • Delete a CMS Item Removes one record from a CMS entity of a bot.
  • Delete CMS Entity Fields Deletes several columns of a CMS entity at once.
  • Get a Bot Fetches one bot with its Bot ID, Name and Team Name.
  • Get a Bot User Looks up a person who talked to a bot, by the User ID shown in the bot conversation. The profile has Email, Birthday, Channel, Locale and Timezone.
  • Get a CMS Entity Pulls the definition of a CMS entity, meaning its Name and the Fields it holds.
  • Get a CMS Item Shows a single CMS row with its Name, Status and Entity ID, as stored in one entity of a bot.
  • List Bot Attributes Gathers the attributes defined on a bot, each with a Description, Value and Data Type. Use Limit to cap the count.
  • List Bots Collects the bots in your account, up to Limit. Each has a Bot ID and a Team Name.
  • List CMS Entities Enumerates CMS entities for a bot along with their Fields, up to Limit.
  • List CMS Items Retrieves the records stored in a CMS entity. Narrow them down by Name or Status, and use Limit for the count.
  • Make an API Call Makes an authorized free-form request to the BotStar REST API with your saved credential.
  • Publish a Bot Sends the current draft of a bot live for your audience.
  • Send a Message Delivers a Messenger message written as JSON in the BotStar message format. Add a Message Tag to reach someone outside the 24 hour window.
  • Update a Bot Attribute Modifies the Description or Value on a bot attribute. Use Value Type to say how the value is sent.
  • Update a Bot User Revises the stored profile of a user: First Name, Last Name, Email, Gender or Birthday. Use Custom Attributes to write your own attribute values as JSON.
  • Update a CMS Entity Changes the Name of an existing CMS entity within a bot.
  • Update a CMS Item Rewrites a CMS row with a changed Name, Status or Field Values.
  • Update CMS Entity Fields Alters existing columns of a CMS entity, with each item of Fields naming the unique name of the column to change.
  • Watch Events (Instant) Starts the workflow the moment BotStar sends an event, with its Event Type, Tag Name and User ID.

Explore alternative integrations

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

Automate BatchDialer and BotStar on WEXTL®

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

Cancel anytime.

Frequently asked questions

Common questions about connecting BatchDialer and BotStar.

How do I connect BatchDialer and BotStar?

Connect your BatchDialer and BotStar 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 BatchDialer and BotStar?

Example: when the "Watch Calls" trigger in BatchDialer fires, WEXTL can "Create a Bot" in BotStar. BatchDialer has 2 triggers (including Watch Calls and Watch Contacts). BotStar has 26 actions (including Create a Bot, Create a Bot Attribute, and Create a CMS Entity). Add filters and transforms between steps when you need them.[1]

Can BatchDialer trigger actions in BotStar, and BotStar in BatchDialer?

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 BatchDialer and BotStar?

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

Does BatchDialer integrate with BotStar in real time?

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

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

References

List of sources used to gather information about the BatchDialer and BotStar integration.

  1. BatchDialer and BotStar integration source code, module specs and credentials implementation.
  2. Our BatchDialer and BotStar integration documentation, structured input and output parameters, scopes, and authentication methods.
  3. Official vendor API documentation for BatchDialer and BotStar, 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. BatchDialer integration information
  6. BotStar integration information
  7. WEXTL® Scheduling
  8. WEXTL® Pricing and Trial
  9. WEXTL® Apps Library

How we write our apps documentation

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

Explore BatchDialer and BotStar, or get started