On this page
Connecting Pabbly Connect to VGraple CRM works the same way Make does, through VGraple CRM's generic outbound webhook system as a trigger and the public REST API as an action target, using Pabbly Connect's own Webhook trigger step and its HTTP-capable action step rather than a dedicated pre-built app. This walkthrough covers both directions.
Before you start
- You need permission to manage webhooks in VGraple CRM, included in Owner and Admin roles by default.
- For pushing data into VGraple CRM, you also need an API key from Settings > API Keys, generated by the organisation owner.
- Have a Pabbly Connect account and a workflow ready to start; the Webhook trigger is one of Pabbly Connect's built-in trigger types, available without searching an app directory.
Steps: receiving VGraple CRM events in Pabbly Connect
- In Pabbly Connect, create a new workflow and choose Webhook as the trigger app. Pabbly Connect generates a unique webhook URL for this trigger.
Copy that URL.
In VGraple CRM, go to Settings > Webhooks and click Add Endpoint. Paste Pabbly Connect's webhook URL, add a description like "Pabbly Connect workflow," and choose the events you need (for example New Lead, Contact Opted Out, Broadcast Completed).
Copy the signing secret shown once, and store it where your Pabbly Connect workflow can reference it.
Trigger a test event in VGraple CRM (create a test contact, for example) so Pabbly Connect can capture a sample payload for mapping later steps.
Add a signature verification step. Use Pabbly Connect's Code action to compute an HMAC-SHA256 hash of the raw request body with your stored secret, and compare it to the
X-Signature-256header before continuing. See verifying webhook signatures for the exact algorithm in a form you can adapt.Add your next action steps. Route the verified event into any app Pabbly Connect supports, using the fields documented in the payload reference.
Steps: pushing data into VGraple CRM from Pabbly Connect
Add an HTTP/API Request action step at the point in your workflow where you want to reach VGraple CRM.
Set the URL to a VGraple CRM v1 endpoint, for example
https://crm.vgraple.co.in/api/v1/contacts, method POST.Add the header
Authorization: Bearer vgk_your_key_hereand a JSON body matching the endpoint's fields (see the REST API quickstart).
What you will see
VGraple CRM's endpoint list in Settings > Webhooks shows a delivery count that grows every time your workflow's trigger fires, and Pabbly Connect's task history shows each run with the payload received. An action step pushing data shows the API's response, for example a created lead's id, in Pabbly Connect's execution log.
Settings and options
| Setting or field | What it does | Default |
|---|---|---|
| Pabbly Connect Webhook URL | Where VGraple CRM sends events | Generated by Pabbly Connect's Webhook trigger |
| VGraple CRM endpoint | Subscribes the URL to chosen events | Created in Settings > Webhooks |
| Signing secret | Used inside Pabbly Connect to verify the payload | Shown once at endpoint creation |
| HTTP action Authorization header | Authenticates a workflow calling into VGraple CRM | Bearer vgk_..., your API key |
Troubleshooting
| Symptom | Likely cause | Fix |
|---|---|---|
| Pabbly Connect never receives anything | The endpoint URL was pasted incorrectly, or the workflow is not turned on | Recheck the URL in Settings > Webhooks against the one Pabbly Connect generated; confirm the workflow is active |
| The signature check inside the Code step always fails | The step is hashing a reformatted or re-serialised version of the body rather than the exact raw bytes received | Confirm the Code step has access to the raw payload text, not a value already parsed into an object, before hashing |
| VGraple CRM's endpoint shows deliveries as "failed" | Pabbly Connect's webhook URL returned a non-2xx status, often from an error partway through the workflow | Check Pabbly Connect's task history for the specific error and confirm the workflow completes and returns success quickly |
| An HTTP action call to the API returns 401 | The API key is missing, mistyped, or was rotated since the workflow was built | Recheck the Authorization header value against your current key in Settings > API Keys |
| Workflow works in testing but stops running live | Pabbly Connect's task limit for your plan was reached | Check Pabbly Connect's own usage dashboard; this is a Pabbly plan limit, not a VGraple CRM restriction |
Once this is working, see verifying webhook signatures for the full HMAC check, or using Make with webhooks if you use both platforms.