WhatsApp webhooks: connect group commands to your CRM, ERP or API
In 9bot, integration works from the inside out: when someone uses a command in the group, such as /quote or /order, 9bot makes an outbound HTTP call (GET, POST or PUT) to your CRM, ERP or API endpoint. 9bot does not offer a URL to receive webhooks from other systems. This differs from the Meta Cloud API webhook, which pushes message events to your server.
How it works in practice
What is a WhatsApp webhook
Short answer: a webhook is an automatic HTTP call made when an event happens. WhatsApp has two models: the inbound Meta Cloud API webhook, which notifies your server about received messages, and the outbound call triggered by a command, which is the 9bot model for groups.
| Aspect | Cloud API webhook (Meta) | Command with API in 9bot |
|---|---|---|
| Direction | Inbound: Meta calls your server | Outbound: 9bot calls your system |
| Trigger | Account message events | Command sent in the group |
| Methods | POST to your endpoint | GET, POST or PUT |
| Receiving URL at the provider | You register your URL with Meta | 9bot has no inbound URL |
How a group command triggers a GET, POST or PUT call
Create the command
In the 9bot dashboard open Commands and click New command. Set the trigger, which must start with a period, exclamation mark or slash.
Choose the API type
Under Response type select API and enter the endpoint and method: GET to read, POST to create, PUT to update.
Use it in the group
When an authorized member sends the command, 9bot calls your system.
Monitor
Check the execution in the dashboard logs and adjust the command if needed.
The custom commands guide shows the creation screen step by step. For multi step flows, the integration action is also available inside a 9bot workflow.
Use cases: CRM, orders, tickets and automation
| Command | Method | System | Result |
|---|---|---|---|
| /quote | POST | CRM | Creates a lead with the customer request |
| /order 1234 | GET | ERP or ecommerce | Looks up the order status |
| /ticket | POST | Help desk | Opens a support ticket |
| /stock product | GET | ERP | Checks availability |
| /update 1234 | PUT | CRM | Moves a deal to a new stage |
| /report | POST | n8n or Make | Triggers an automation scenario |
Platforms such as n8n and Make usually expose an inbound URL for each scenario. In that case the 9bot command calls that URL and the platform routes the data to your other systems.
If the group also takes orders from resellers, see how to organize WhatsApp ordering with commands and logging in your system.
Payload example
The example below is illustrative. Fields and endpoint depend on your API contract.
POST https://api.yourcompany.com/leads
Content-Type: application/json
{
"command": "/quote",
"group": "Wholesale Customers",
"text": "20 boxes of product X"
}For status lookups, a GET with the order number in the URL is usually enough. To update an existing record, use PUT.
Security best practices for outbound webhooks
- Always HTTPS: never point commands to endpoints without TLS.
- Dedicated endpoint: create a route just for 9bot, with minimal permissions in the CRM or ERP.
- Validate in your API: treat incoming text as untrusted input and check format and size.
- Who can use it: restrict sensitive commands to admins and the right groups.
- Idempotency and logs: avoid duplicate records and keep an audit trail in your system.
Read also
Frequently asked questions
Does 9bot receive webhooks from other systems?
How is this different from the official API webhook?
Do I need to code to integrate with my CRM?
Which HTTP methods are supported?
How much does it cost?
Turn group commands into data in your CRM
326 customers worldwide use 9bot to run WhatsApp groups. Try it for 7 days or talk to a specialist to map the integrations your operation needs.
