BotStar Zapier integrationAutomate BotStar with Zapier.
The BotStar Zapier integration is all about listening: 5 triggers, every one of them instant, and no action or search. Your chatbot tells Zapier when a visitor asks for a human, reaches a checkpoint, gets a tag or subscribes, and another app takes it from there.
Verified Trustpilot reviews · AI, automation & growth agency
What the BotStar Zapier integration gives you
Zapier connects your apps so an event in one starts work in another, without anyone copying data across. BotStar plays only one role here: it is where things start. Five chatbot events can each launch an automation, and the work itself (alert, record, follow-up) happens in the other apps of your Zap.
Three results that are worth setting up, each built on a real trigger:
No visitor left waiting for a person. New Request for Human Takeover fires the moment someone in the chat asks to talk to an operator, so a message can reach whoever is on duty in your team tool.
Leads that land where sales work. New Checkpoint Record fires when a conversation reaches a checkpoint you defined, such as the step where a visitor leaves an email, and the record can be passed to your CRM.
Segments that follow the chat. New Tag on User and New Subscriber report who was tagged and who opted in to broadcasts, ready for your email tool or a spreadsheet.
What Zapier does not do for BotStar: it cannot write anything back into the bot. There is no action and no search, so a Zap can neither tag a user, nor send a chat message, nor look up a past conversation. If you also want to see how BotStar behaves on Make, read the BotStar Make integration page.
The Zapier words behind this page
Seven terms, one plain line each, and you can read the rest without a dictionary.
- Zap
- The automation you build on Zapier: one trigger, then one or more actions that run every time that trigger event happens.
- Trigger
- The event in an app that starts the Zap. Once the Zap is on, Zapier waits for it, here something happening in your BotStar bot.
- Action
- What the Zap does once it starts. BotStar has none on Zapier, so the action always belongs to another app of your Zap.
- Task
- The unit Zapier bills: one action that completes successfully. Your plan is a monthly number of tasks, not of Zaps.
- Polling vs instant
- A polling trigger is checked on a timer. An instant one is reported by the app as it happens. All five BotStar triggers are instant.
- Filter
- A step that lets the Zap carry on only when what arrived meets your condition, and stops it there otherwise.
- Multi-step Zap
- Any Zap with more than one trigger and one action. A filter or a second action makes it one, and it then needs a paid plan.
What a BotStar Zap costs
BotStar is not a premium app, so the free Zapier plan can use it. Billing is in tasks.
- Free plan100 tasks a month
- Free plan ZapsUnlimited, two steps each
- BotStar triggers5, all instant on every plan
A BotStar trigger never costs a task, and neither does waiting for chat events. What you pay for is the action that follows in the other app: one task each time it succeeds, nothing when it fails. On the free plan, a BotStar trigger plus one action in another app is a two-step Zap and stays free. Add a filter or a second action, and it becomes a multi-step Zap that needs a paid plan. All five triggers are instant, so the interval grid never slows them down.
Connect BotStar to Zapier in three steps
- 01
Go to Apps
In your Zapier account, open Apps and click + Add connection. A connection is your BotStar account linked to Zapier once, then reused by every Zap that listens to your bots.
- 02
Find BotStar
Search for BotStar in the dialog, pick it and click Add connection. You need an existing BotStar account with at least one bot; Zapier links to it but never creates anything.
- 03
Sign in and allow access
Sign in to BotStar in the tab that opens and grant Zapier access to the account. Pick the account that owns the bot you want to listen to, since every trigger reads from it.
First Zap: alert your team when a visitor asks for a person
GoalWhen someone in the chatbot asks to speak to a human, your support team gets a message in its chat tool right away.
- 01
Build: pick the BotStar trigger
Create a Zap, choose BotStar as the app and New Request for Human Takeover as the event, then select the BotStar connection you added before.
- 02
Test with a real request
Run the trigger test. Zapier brings back the three most recent takeover requests of the account, so you can see what a request carries before mapping anything.
- 03
Add the alert
Add your team chat tool as the action and choose the step that sends a message. Map the visitor details from the BotStar step into the message, so the operator knows who is waiting.
- 04
Add the ticket, if you need one
The third card, a ticket in your help desk, is optional. It makes the Zap multi-step and needs a paid plan; without it, the alert alone runs on the free plan.
- 05
Test, then Publish
Test the action, check the message arrived, then click Publish. The Zap is on and reacts to the next visitor who asks for a human.
BotStar triggers on Zapier
5 events start a Zap when something happens in BotStar, and 5 of them are instant: the app calls Zapier straight away, whatever your plan.
New Request for Human Takeover
Instant triggerIn Zapier“Triggers when a user request to contact human operator.”
Starts your Zap when a visitor in the chatbot asks to be put through to a human operator, which is the moment the bot stops being enough.
New Checkpoint Record
Instant triggerIn Zapier“Triggers when a new checkpoint record is created.”
Fires when a conversation creates a new record at one of your checkpoints, those named stages you set in the bot to group what visitors left behind.
Updated User Attribute
Instant triggerIn Zapier“Triggers when a specified User Attributes has been added or updated to audience.”
Runs when the user attribute you chose is added to someone in your audience, and again every time that attribute changes later.
New Subscriber
Instant triggerIn Zapier“Triggers when a user subscribes to receive broadcast messages.”
Goes off when a user subscribes to receive your broadcast messages in BotStar, the bulk messages the bot sends to everyone who opted in.
New Tag on User
Instant triggerIn Zapier“Triggers when a new tag is added to a user.”
Kicks off when a new tag is added to a user, using the tag name you pick, so your bot segments can travel to other apps.
When a BotStar Zap breaks
Zapier documents no BotStar-specific error or rate limit. What goes wrong comes from the general rules of Zaps.
Four cases to know before you switch a Zap on. If a run fails and the reason is not clear, the Zapier troubleshooting page is a good next step, and the Zapier training covers the basics in more depth.
Past conversations are not replayed
A Zap only reacts to what happens after it is published. Earlier takeovers, tags and subscribers are never picked up; moving that history is a separate job.Duplicates from attribute updates
Updated User Attribute fires on every change. A Zap that creates a contact each time will end up with several copies of the same person.A sudden flood held back
When a trigger suddenly returns a huge batch, after a bulk import for instance, Zapier's flood protection can hold the runs back instead of letting them through.A failed action is free
If the action in the other app fails, no task is counted. Fix the mapping in the other app before the next visitor event arrives.
Need help automating BotStar with Zapier?
A person reads every message.
