Home/ Integrations/Zapier
Zapier WhatsApp integration
Trigger a Zap from a BotPulsar event, or call into BotPulsar from a Zap.
Zapier is the fastest way to connect WhatsApp to a tool BotPulsar does not ship a named connector for. Events are delivered to a Zap webhook with a configurable event type, so you can route different BotPulsar events to different Zaps rather than filtering everything inside one.
What the Zapier connector supports
Capabilities
- Deliver events over REST
What you'll need to connect
base_urlworkflow_idevent_type
What teams build with it
Add every new WhatsApp contact to a tool that has no direct connector.
Post a notification to Slack or email when a high-value conversation starts.
Write conversation outcomes into a project or ticketing tool through an existing Zap.
Zapier integration: common questions
Do I need a developer to use the Zapier integration?
No. The connector delivers events to a Zap webhook URL, and the rest of the automation is built in Zapier's own visual editor.
Can I send different events to different Zaps?
Yes, event type is a configuration field, so separate BotPulsar events can be routed to separate Zaps.
What plan do I need for the Zapier integration?
Delivering events to Zapier uses the same REST and webhook infrastructure available from the Growth plan (₹999/month) upward.
How is this different from using BotPulsar's REST API directly?
Zapier is a no-code option — you connect BotPulsar's Zap trigger and build the rest visually — while the REST API is for teams that want to write their own integration code.
Can I filter which conversations trigger a Zap?
Yes, by routing specific event types to specific Zaps using the configured event type field, rather than sending every BotPulsar event to one Zap.
Does BotPulsar support triggering Zaps and being triggered by them?
Yes, a Zap can call back into BotPulsar the same way it calls other apps, so the connection works as both a trigger and an action.