On this page
This integration runs on webhooks and the REST API, not a packaged connector: VGraple CRM posts signed events to a Pabbly Connect webhook trigger, and Pabbly Connect calls VGraple CRM's REST API with an API key to create contacts and leads or send approved templates. It is the lowest-cost route for high volumes and the most flexible, because you shape every payload.
What syncs
| Data | Direction | Timing |
|---|---|---|
| Any VGraple CRM event | VGraple CRM to Pabbly | Instant, retried |
| Contact upsert, lead creation, template send | Pabbly to VGraple CRM | Immediate via REST API |
| Indian payment gateway and form events | Pabbly to VGraple CRM | Per Pabbly trigger |
Setup
- In Pabbly Connect, create a workflow with the Webhook trigger and copy the URL.
- In VGraple CRM, Settings, then Webhooks, Add Endpoint, paste the URL, tick events, save.
- Click Test so Pabbly captures a sample payload and maps its fields.
- Create an API key under Settings, then API Keys, and add an API by Pabbly action with the Bearer header for calls to
/api/v1/.... - Test with your own number, then enable the workflow.
How the two directions work
VGraple CRM to Pabbly Connect. Under Settings, then Webhooks, add an endpoint with the Pabbly Connect webhook URL and tick the events you need (message.received, message.sent, contact.created, contact.opted_out, lead.created, lead.stage_changed, broadcast.completed, conversation.assigned, conversation.resolved, conversation.reopened, form.submitted; the four broadcast lifecycle events are subscribed through POST /api/v1/hooks). Every delivery is a JSON POST signed with HMAC-SHA256 in the X-Signature-256 header using the endpoint's whsec_ secret, retried on failure and logged with the response.
Pabbly Connect to VGraple CRM. Create an API key under Settings, then API Keys (Owner only) and use an HTTP module in Pabbly Connect with Authorization: Bearer <key> against https://crm.vgraple.co.in/api/v1: POST /contacts upserts by phone, POST /leads creates a lead in a pipeline, POST /messages sends an approved template by name and language with variables, GET /templates and GET /pipelines list what you can use. Errors come back as JSON with a code and a plain message, including Meta's code on a template send.
When Pabbly is the right middle layer
Pabbly Connect makes sense for businesses already on it for Indian tools (Razorpay, Instamojo, Zoho, Google Workspace, Indian email and SMS providers) who want WhatsApp added to those workflows without buying another automation subscription. The webhook route gives it every VGraple CRM event, and API by Pabbly gives it every REST action. For workflows that move sensitive data, add a verification step on your own server or use Make or n8n, which can check the HMAC signature natively; for ordinary notifications an unguessable webhook URL is the accepted practice.
A worked example
A coaching institute captures enquiries on a WordPress form, takes fees through Razorpay and keeps students in Zoho. Three Pabbly workflows cover it: the form webhook creates the contact and lead in VGraple CRM and sends the acknowledgement template; Razorpay's payment captured trigger sends the fee receipt template and tags the contact as enrolled; VGraple CRM's lead.stage_changed event updates the Zoho lead status. None of it needs code, and the monthly task count stays inside a small Pabbly plan.
Three recipes
- form.submitted -> Pabbly -> Google Sheets row -> API by Pabbly POST /api/v1/messages with a utility acknowledgement.
- Razorpay Payment Captured (Pabbly trigger) -> POST /api/v1/contacts -> POST /api/v1/messages payment_received.
- lead.created -> Pabbly -> Zoho CRM create lead for teams that keep Zoho as the sales system.
Limits and gotchas
- Only approved templates can be sent through the API; consent, messaging limits, the US marketing pause and delivery protection apply as in the app.
- Webhook endpoints must be public HTTPS; verify the signature before trusting a payload, and deduplicate on the event ID because retries can arrive after a slow success.
- API keys are Owner-only secrets with a rolling limit of 600 requests per hour per key.
- Phone numbers must be in international format without spaces or a leading zero.
- Payloads contain customer personal data; keep Pabbly Connect scenarios and their logs inside your data protection scope.
The webhooks guide, the payload reference, the signature guide and the REST API quickstart have the exact fields and code.