On this page
Connecting Make to VGraple CRM does not use a dedicated app, it uses Make's built-in Custom Webhook module to receive signed events from VGraple CRM's outbound webhook system, and an HTTP module to call the REST API when you need to push data the other way. 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, to create the endpoint that points at Make.
- For pushing data into VGraple CRM, you also need an API key, generated by the organisation owner.
- Have a Make account with a scenario ready to build; the Custom Webhook module is one of Make's core, always-available modules, not a separate app to search for.
Steps: receiving VGraple CRM events in Make
- In Make, start a new scenario and add a Custom Webhook module as the trigger. Click Add, name the webhook, and Make generates a unique receiving URL.
Copy that URL. This is what VGraple CRM will POST signed payloads to.
In VGraple CRM, go to Settings > Webhooks and click Add Endpoint. Paste Make's webhook URL, add a description like "Make scenario," and choose the events you want (for example New Lead, New Contact, Broadcast Completed).
Copy the signing secret shown once. Store it somewhere you can reference from Make, since you will use it to verify incoming payloads.
Back in Make, run the scenario once to capture a sample payload. Trigger the matching event in VGraple CRM (create a test contact, for example) so Make can "listen" for a real payload and learn its structure for the next modules.
Add a signature verification step. Before acting on the payload, compute an HMAC-SHA256 hash of the raw body with your stored secret (Make's built-in functions or a short custom function can do this) and compare it to the
X-Signature-256header. See verifying webhook signatures for the exact algorithm.Add your next modules. Route the verified event into whatever Make supports, a Google Sheets row, a Slack message, an email, a database write, using the fields documented in the payload reference.
Steps: pushing data into VGraple CRM from Make
Add an HTTP module (Make an API Key Auth Request, or a raw HTTP request module) as a step in any scenario.
Set the URL to a VGraple CRM v1 endpoint, for example
https://crm.vgraple.co.in/api/v1/leads, method POST.Add the header
Authorization: Bearer vgk_your_key_hereand a JSON body matching the endpoint's expected fields (see the REST API quickstart).
What you will see
Once both sides are configured, VGraple CRM's endpoint list in Settings > Webhooks shows a delivery count that increases every time your scenario fires, and Make's scenario history shows each execution with the payload it received. An HTTP module pushing data shows a response body from VGraple CRM's API, for example a created contact's id, in Make's execution log.
Settings and options
| Setting or field | What it does | Default |
|---|---|---|
| Make Custom Webhook URL | Where VGraple CRM sends events | Generated by Make when you add the module |
| VGraple CRM endpoint | Subscribes Make's URL to chosen events | Created in Settings > Webhooks |
| Signing secret | Used inside Make to verify the payload | Shown once at endpoint creation |
| HTTP module Authorization header | Authenticates a Make scenario calling into VGraple CRM | Bearer vgk_..., your API key |
Troubleshooting
| Symptom | Likely cause | Fix |
|---|---|---|
| Make never receives anything | The endpoint URL was pasted incorrectly in VGraple CRM, or the scenario is turned off in Make | Recheck the endpoint's URL in Settings > Webhooks against Make's Custom Webhook URL; confirm the scenario is active, not just saved |
| Make receives the payload but your signature check always fails | Make's HTTP-in module may re-serialise the body before your hashing step runs | Use Make's raw body capture where available, or verify against the exact bytes Make received, not a reformatted version |
| VGraple CRM's endpoint shows deliveries as "failed" | Make's webhook URL returned a non-2xx status, often because the scenario errored partway through | Check Make's scenario execution history for the error, and confirm the scenario returns a success response quickly |
| An HTTP module call to the API returns 401 | The API key is missing, mistyped, or was rotated since the scenario was built | Recheck the Authorization header value against your current key in Settings > API Keys |
| Everything works but stops after a while | Make's operation limit for your plan was reached, or the scenario was paused | Check Make's own usage dashboard; this is a Make plan limit, not a VGraple CRM restriction |
Once this is working, see verifying webhook signatures for the exact HMAC check, and Pabbly Connect with webhooks if you use both tools or are comparing them.