Autocalls AI and BotStar Integration

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

Connect Autocalls AI 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 Autocalls AI and BotStar

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

  • Autocalls AI

    • Communication
    • 3 triggers
    • 2 searches
    • 7 actions

    AI phone agents for outbound and inbound calling, lead qualification, and follow-ups.[5]

  • BotStar

    • Communication
    • 1 trigger
    • 8 searches
    • 18 actions

    Chatbot builder for Messenger and web chat.[6]

How to connect Autocalls AI to BotStar

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

How does the integration between Autocalls AI and BotStar work in WEXTL?

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

Autocalls AI triggersBotStar actions

Autocalls AI modules

  • Create a Lead Puts a lead into an Autocalls AI campaign, reached at its Phone Number in E.164 format. Attach Variables, add Secondary Contacts, or turn on Allow Duplicate to let one number into a campaign twice.
  • Delete a Call Deletes a call record from your Autocalls AI account. Treat it as final.
  • Delete a Lead Removes a lead from Autocalls AI. Treat this as final.
  • List Leads Reads every lead with its Status, Phone number and Secondary contacts. Set Limit to stop after a given number of leads.
  • Make a Phone Call Has an assistant place an outbound call to a customer at their Phone Number. Pass Variables with the call, and add a Customer Name and Email if you have them. Output includes the Message and Data.
  • Make an API Call Sends a free-form request to the Autocalls AI REST API, signed with your saved credential.
  • Search Calls Finds calls by Status, Type (inbound, outbound or web), Phone Number, Assistant ID or Campaign ID. Use Date From and Date To to set a period. Each call comes with its Transcript, Duration, Total cost and Recording URL.
  • Send an SMS Sends a text message from one of your SMS-capable numbers, using From for the ID of the number and To for the recipient. Keep Body to 300 characters at most.
  • Update a Lead Edits an existing lead. Use Phone Number to change the number, Campaign ID to move it to another campaign, Status to set Created, Completed or Reached Max Retries, and Variables for its variable values.
  • Watch Calls Detects new calls with a scheduled check and fires once for each. Pass Status, Type or Assistant ID to react only to matching calls, and Limit to size each run.
  • Watch Inbound Events Starts the workflow the moment an assistant receives an inbound event, through a webhook from Autocalls AI.
  • Watch Leads Notices newly created leads during a timed check and fires for each, bringing its Campaign ID and Status. Reduce Limit to handle fewer leads per run.

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

Automate Autocalls AI and BotStar on WEXTL®

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

Cancel anytime.

Frequently asked questions

Common questions about connecting Autocalls AI and BotStar.

How do I connect Autocalls AI and BotStar?

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

Example: when the "Watch Calls" trigger in Autocalls AI fires, WEXTL can "Create a Bot" in BotStar. Autocalls AI has 3 triggers (including Watch Calls, Watch Inbound Events, and Watch Leads). 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 Autocalls AI trigger actions in BotStar, and BotStar in Autocalls AI?

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 Autocalls AI and BotStar?

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

Does Autocalls AI integrate with BotStar in real time?

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

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

References

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

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

Explore Autocalls AI and BotStar, or get started