BotStar and Tidio Integration
Connect BotStar and Tidio 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
How to connect BotStar to Tidio
Set up your BotStar and Tidio integration in 3 simple steps[2]. No coding required. Up to 10 minutes setup.
STEP 1
Connect BotStar and Tidio
Save credentials in WEXTL once. We store them encrypted and reuse the authorization across every workflow[3]. No coding or API skills required.
STEP 2
Build a workflow
Paste selected BotStar and Tidio nodes onto the canvas[4], or describe what you want and WEXTL wires the flow together with AI Builder.
STEP 3
Map your data
Choose which fields need to sync between BotStar and Tidio. Use filters or a JS custom code step in between. Everything is on the canvas.
How does the integration between BotStar and Tidio work in WEXTL?
WEXTL exposes actions and triggers for BotStar and Tidio 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.
BotStar triggersTidio actions
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.
Tidio modules
- Create a Contact Adds a contact to Tidio under the Distinct ID it has in your own system. Use Email, Phone, First Name and Last Name for the profile, and Email Consent to mark Subscribed or Unsubscribed. Returns only the Contact ID.
- Create a Ticket as Contact Opens a support ticket on behalf of a contact, from their Contact Email, a Subject and the first Message Content. Set Assigned Department ID to route it, otherwise the General department gets it. Returns the Ticket ID.
- Create Multiple Contacts Imports a batch of contacts into Tidio in one request. Every entry of the Contacts List needs a Distinct ID, and may add an Email, Phone or Properties.
- Delete a Contact Deletes a single contact that is stored in your Tidio account.
- Delete a Ticket Removes a support ticket from Tidio.
- Get a Contact Loads one contact with its Distinct ID, First name, Last name, Email, Phone, Language, Country, City and Properties. Email consent and the Created at date are included too.
- Get a Ticket Reads one ticket and returns its Subject, Status, Priority, Contact email, Link, Assigned operator ID and Assigned department ID.
- List Departments Shows the departments in Tidio with the ID and Name of each. Use Limit to cap how many are returned.
- List Operators Retrieves the operators on your Tidio account, with their Name, Email, Role, Active flag and Last seen time. Use Limit to restrict the result count.
- List Tickets Lists tickets from Tidio, each with its Subject, Status, Priority and Contact email, plus the Assigned operator ID. Use Limit when you only need the first few.
- Make an API Call Makes an authorized free-form request to the Tidio REST API with your saved credential.
- Reply to a Ticket Adds a reply to an existing ticket with the Content you write. Set Author Type to Contact or Operator to say who replied, and Message Type to Public or Internal to control its visibility. Returns the ID of the new message.
- Search Contact Messages Reads the conversation history of one contact. Each Message comes with who wrote it (Author type and Author ID) and when it was sent (Created at). Use Limit to stop after a set number of messages.
- Search Contacts Finds contacts in Tidio and returns each with its Distinct ID, names, Email and Phone. Use Email to narrow the search to one address, and Limit to set the most results.
- Update a Contact Changes the details of a contact: Distinct ID, Email, Phone, First Name, Last Name, Email Consent or Properties.
- Update a Ticket Moves a ticket to a new Status (Open, Pending or Solved) and Priority (Low, Normal or Urgent). Use Assigned to hand it to a Department or an Operator.
- Update Multiple Contacts Applies changes to many contacts in a single request, using a Contacts List with one entry per contact. Use it for bulk edits when Update a Contact would take one call per person.
- Watch Contacts Checks Tidio on a schedule and runs the workflow once for each newly added contact. Use Limit to decide how many contacts a single cycle works through.
- Watch Events Runs the instant a Tidio webhook arrives for an event. Each run holds the contact involved, with its ID, Email, Phone, First name, Last name, Distinct ID and Properties.
- Watch Tickets Polls Tidio and triggers once per ticket that is new since the previous poll. Use Limit to set how many tickets a cycle handles.
Explore alternative integrations
There are other apps[9] supported by WEXTL that can be paired with BotStar and Tidio integrations. Pick any from the list below if the current combination isn't the one you need.
Frequently asked questions
Common questions about connecting BotStar and Tidio.
References
List of sources used to gather information about the BotStar and Tidio integration.
- BotStar and Tidio integration source code, module specs and credentials implementation.
- Our BotStar and Tidio integration documentation, structured input and output parameters, scopes, and authentication methods.
- Official vendor API documentation for BotStar and Tidio, used to verify field meanings, authentication flows, and anything our own specs don't fully capture.
- WEXTL® visual workflow builder, anonymized data from our technical support team.
- BotStar integration information
- Tidio integration information
- WEXTL® Scheduling
- WEXTL® Pricing and Trial
- WEXTL® Apps Library
How we write our apps documentation
Explore how WEXTL® crafted BotStar and Tidio integration page documentation. Used sources, the role of AI, and how the team validates the result.

