HeroBot Zapier integrationAutomate HeroBot with Zapier.
The HeroBot Zapier integration gives you 0 triggers, 1 action and 0 searches. One move, done well: another app spots an event, and HeroBot sends a single message to a phone number. It runs on Zapier's free plan, no upgrade needed.
Verified Trustpilot reviews · AI, automation & growth agency
What the HeroBot Zapier integration actually does
Connecting HeroBot to Zapier lets any of your other apps hand it a phone number and a line of text, and HeroBot sends that message for you. That's the whole deal: one outgoing message per run, triggered by something that happened somewhere else. No copy-pasting numbers from a spreadsheet into a messaging tool.
Three jobs fit that shape well. A booking confirmation: someone books a slot in your calendar tool, and Send Message texts them the date while it's still fresh in their mind. An order update: a new sale in your shop goes straight out as a short message to the buyer's phone. A form acknowledgment: a prospect fills in a contact form, and they get a text saying the request arrived, before they've even closed the page in their head.
Now the honest part. HeroBot describes itself as a chatbot platform for messaging, campaigns and feedback collection. Through Zapier, though, you only get the sending half. There is no trigger, so a reply from a customer can't start anything. There is no search either, so a Zap (the automation you build, one starting event followed by the steps it runs) can't look up a past conversation in HeroBot. Campaigns and feedback flows stay inside HeroBot itself.
So the Zap always begins in another tool, and HeroBot sits at the end of the chain. If you want to see how the same app looks on the other big platform, the HeroBot Make integration page covers it, and the Make vs Zapier comparison helps you weigh the two on your own criteria.
Zapier words, in plain English
Seven terms come back on this page. Here they are once, so the rest reads easily.
- Zap
- An automation on Zapier: one starting event, then one or more steps that run every single time that event happens.
- Trigger
- The event in an app that kicks the Zap off. Once the Zap is on, Zapier sits and waits for it. HeroBot offers none.
- Action
- What the Zap does once it has started: the step that sends, writes or moves something. Send Message is HeroBot's only one.
- Task
- The unit Zapier bills you for: one action completed successfully. Your plan's allowance is simply a count of those.
- Polling vs instant trigger
- Polling: Zapier checks the app on a timer for new items. Instant: the app calls Zapier the moment the event happens.
- Filter
- A step that lets the Zap continue only when the incoming data meets a condition you set, and stops it quietly otherwise.
- Connection
- Your HeroBot account, linked to Zapier once and then reused by every step in every Zap that sends through HeroBot.
What a HeroBot message costs you in Zapier
HeroBot isn't a premium app, so it works on the free plan. The bill is counted in tasks, not in messages.
- Premium appNo, available on the free plan
- Free plan100 tasks a month, two-step Zaps only
- One message sentOne task
- Failed sendNot counted
Each message that goes out successfully counts as one task. A send that fails doesn't count. The trigger in the other app never costs anything, however often Zapier checks it. The free plan gives you 100 tasks a month and Zaps of exactly two steps: one trigger, one action. Add a filter (say, to text only some bookings) and the Zap becomes multi-step, which needs a paid plan. How fast it runs depends on the starting app: an instant trigger fires at once on any plan, a polling one follows the grid below.
Connect HeroBot to Zapier in three steps
- 01
Open your apps list
In your Zapier account, go to the Apps page and click + Add connection. A dialog opens with a search box. Type HeroBot and pick it from the results. You'll need an existing HeroBot account first.
- 02
Add the connection
Click Add connection. A new tab opens on HeroBot's side, where you sign in with the account that should send the messages. Use the account your team actually sends from, not a personal test login.
- 03
Grant access
Approve the access request so Zapier can send messages on that account's behalf. The connection then appears in your list, and every Zap that sends through HeroBot reuses it without asking again.
Your first Zap: text every new Calendly booking
GoalA guest books a call in Calendly and receives a confirmation text from HeroBot, but only for the event types you pick.
- 01
Build the start
Create a Zap and pick Calendly as the app that starts it, with Invitee Created as the event. Connect your Calendly account when asked, so Zapier can see new bookings.
- 02
Test the trigger
Run the test. Zapier brings back the three most recent bookings from the connected account. Pick a real one, and note which value tells your event types apart.
- 03
Add the filter
From the plus icon, add a Filter step. Choose the value you noted, a text rule, and the event type to keep. This step makes the Zap multi-step, so a paid plan is needed.
- 04
Add Send Message
Add HeroBot with Send Message. Map the guest's phone answer into Receiver's Number, then write the Message, mixing your own words with the booking date from Calendly.
- 05
Test, then publish
Test the action and check that the text really arrived on a phone you own. If it looks right, click Publish to switch the Zap on.
The HeroBot action
HeroBot gives you 1 action. For each one: what it does for you, when to reach for it, and what to watch out for.
Send Message
ActionIn Zapier“Send a single message”
HeroBot sends one text to one phone number, using whatever your earlier steps carried: a name, a date, an order reference. Two fields are required, the receiver's number and the message itself.
When a HeroBot Zap goes wrong
Zapier links no help article to HeroBot, so the known failure points come from how Zaps behave in general.
With a single sending action, the classic traps are about timing and volume rather than settings. Four cases cover most of what you'll hit. For a step-by-step method, the Zapier troubleshooting guide goes further.
Past bookings never get a text
A Zap only reacts to what happens after you switch it on. Contacts already sitting in the other app won't receive anything; reaching them is a separate job.A bulk import sends nothing at first
If the starting app suddenly returns a huge batch, after an import or a migration, Zapier's flood protection can hold those items back instead of firing them all.Messages that loop
A Zap that writes into the place its own trigger watches sets itself off again and again. Keep the starting app and the place you log sends separate.The same person texted twice
On a polling trigger, Zapier remembers what it has already seen, so one item won't start the Zap twice. Duplicates usually mean duplicate records upstream.
Need help automating HeroBot with Zapier?
A person reads every message.
