Home/ Integrations/Generic REST
Generic REST WhatsApp integration
Deliver any BotPulsar event to your own REST endpoint when no named connector fits.
No connector catalogue covers every internal system. The Generic REST connector delivers BotPulsar events to any endpoint you control, which together with the versioned REST API and signed webhooks means an in-house system is never blocked on a vendor building a named integration first.
What the Generic REST connector supports
Capabilities
- Deliver events over REST
What you'll need to connect
base_url
What teams build with it
Push WhatsApp events into an internal ERP or in-house CRM.
Feed a data warehouse ingestion endpoint directly.
Prototype an integration before deciding whether it warrants a dedicated connector.
Generic REST integration: common questions
What can I connect with the Generic REST connector?
Any system that can expose an HTTP endpoint. Events are delivered to the base URL you configure.
Is this different from BotPulsar's webhooks?
They overlap. Signed outgoing webhooks and the versioned REST API cover most custom integration needs; the Generic REST connector fits the same delivery into the connector framework alongside named integrations.
Do I need a developer to use the Generic REST connector?
Yes, unlike the no-code automation connectors, this delivers events straight to an endpoint you build, so someone needs to build and maintain that receiving endpoint.
What plan includes REST API and webhook access?
REST API access with scoped API keys and signed outgoing webhooks is available from the Growth plan (₹999/month) upward.
Are the events sent securely?
Outgoing events are delivered as signed webhooks, so your endpoint can verify a payload actually came from BotPulsar before acting on it.
Should I use Generic REST or one of the no-code tools like Zapier?
If your team doesn't want to write code, Zapier, Make, n8n or Pabbly Connect cover most cases as no-code options; Generic REST is for when you're building your own receiving endpoint directly.