Make (Integromat) integration

This integration runs on webhooks and the REST API, not a packaged connector: VGraple CRM posts signed events to a Make webhook trigger, and Make 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

Setup

1. In Make, create a scenario with a Custom webhook trigger and copy its URL.
2. In VGraple CRM go to Settings, then Webhooks, click Add Endpoint, paste the URL, tick the events and save; copy the whsec_ secret.
3. Click Test on the endpoint; Make receives a sample message.received and learns the structure.
4. Add a Crypto HMAC SHA-256 module and a filter that compares it with X-Signature-256.
5. For the reverse direction, create an API key under Settings, then API Keys, and add an HTTP module with the Bearer header calling /api/v1/....
6. Run once with a test contact, then schedule the scenario as immediate.

How the two directions work

VGraple CRM to Make. Under Settings, then Webhooks, add an endpoint with the Make 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.

Make to VGraple CRM. Create an API key under Settings, then API Keys (Owner only) and use an HTTP module in Make 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.

Cost and reliability notes

Make bills per operation, and a VGraple CRM event is one operation plus whatever modules follow, so a scenario that fires on every inbound message costs more than one that fires on lead.created; put the filter as early as possible. Scenarios set to immediate run within seconds of the webhook; scheduled scenarios batch events, which is fine for logging and wrong for notifications. Make's error handlers can route a failed API call (for example a template rejected for a closed window or a capped recipient) to a fallback path such as a note on the contact instead of silently dropping it.

Three recipes

• message.received (Filter: text contains "invoice") -> Make -> Google Drive search -> HTTP POST /api/v1/messages sends the invoice template with the document link.
• Shopify Watch Orders (Make module) -> HTTP POST /api/v1/contacts -> POST /api/v1/messages order_confirmed, with no Zapier tasks.
• lead.stage_changed (Won) -> Make -> Google Sheets add row -> Slack message for the daily wins log.

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 Make 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.