On this page
VGraple CRM has no native Shopify app; the honest, working route is Zapier's own Shopify trigger app feeding into VGraple CRM's Send Template Message or Create Lead action, since Shopify's built-in webhooks cannot carry the authentication header VGraple CRM's API needs. This walkthrough covers that route, and the Make/Pabbly Connect alternative for teams already using one of those instead of Zapier.
Before you start
- You need an API key if you plan to call VGraple CRM's REST API directly from Make or Pabbly Connect; a pure Zapier route only needs a connected Zapier app using an API key behind the scenes.
- You need at least one approved WhatsApp template for order confirmations, shipping updates, or whatever message you plan to send; see creating your first template.
- You need a Shopify account with permission to install Zapier's Shopify app, or to configure Make's or Pabbly Connect's own Shopify connector.
Steps: Shopify to WhatsApp via Zapier (recommended)
- Create a new Zap and choose Shopify as the trigger app. Pick an event, for example New Order, New Paid Order, or Order Fulfilled, and connect your Shopify store if this is your first Shopify Zap.
Test the trigger to pull a sample order, which gives you real field names (order number, total price, customer phone, line items) to map in the next step.
Add VGraple CRM as the action app and choose Send Template Message. Connect with an API key if this is your first VGraple CRM Zap.
Pick your approved template from the dynamic dropdown. Choose one built for this exact purpose, an order confirmation or a shipping update, with variables for whatever order details you want to include.
Map the "To" field to the Shopify order's customer phone number, and map any template body variables to the matching Shopify fields (order number, total, tracking link).
Test the action, checking that the message renders correctly against the sample order, then turn the Zap on.
Alternative: without Zapier, using Make or Pabbly Connect
Use Make's or Pabbly Connect's own Shopify module as your trigger (both support Shopify natively as a first-class app), instead of a generic webhook.
Add an HTTP action step calling VGraple CRM's REST API directly. POST to
https://crm.vgraple.co.in/api/v1/messageswithAuthorization: Bearer vgk_your_key_hereand a body containingto,templateandvariablesmapped from the Shopify order. See the REST API quickstart for the exact request shape.
What you will see
Once live, a new Shopify order (or whichever event you chose) sends the mapped WhatsApp template within moments, appearing in VGraple CRM's inbox as an outbound message on that customer's conversation, automatically creating a contact if the phone number is new.
Settings and options
| Setting or field | What it does | Default |
|---|---|---|
| Shopify trigger event | Which Shopify order event starts the Zap or workflow | Chosen when building it (New Order, Order Fulfilled, etc.) |
| Send Template Message action | Sends the mapped WhatsApp template to the order's customer | Requires an approved template |
| To field mapping | Which phone number the message goes to | Mapped from the Shopify order's customer phone |
| Body variable mapping | Which order details fill the template's {{1}}, {{2}} placeholders | Mapped manually per Zap or workflow |
Troubleshooting
| Symptom | Likely cause | Fix |
|---|---|---|
| Shopify's own Notifications webhook does not seem to work with VGraple CRM | Shopify's built-in webhook feature cannot attach the Authorization header VGraple CRM's API requires | Use Zapier's, Make's, or Pabbly Connect's Shopify app instead, which handles authentication for you |
| No WhatsApp message sends even though the Zap ran | The order's customer phone field was empty, or is not a valid WhatsApp-reachable number | Add a Filter step requiring a non-empty phone field before the Send Template Message action |
| The message sends but variables are blank or wrong | The template's variable order does not match the order Zapier mapped values in | Recheck that each mapped value lines up with the exact {{1}}, {{2}} order the template body uses |
| "No approved template named..." error in the Zap's run history | The chosen template is no longer approved, or was renamed after the Zap was built | Reselect a currently approved template in the action step's dropdown |
| Duplicate order confirmation messages | The Shopify trigger event fires more than once for the same order (for example both New Order and New Paid Order are wired to the same action) | Use only one Shopify trigger event per action, or add a Filter step to prevent overlap |
Example
A D2C store sends an order confirmation template the moment Shopify marks an order as paid, mapping the order number and total into the template body, so a customer gets a WhatsApp confirmation before they have even closed the checkout tab.
Once this is working, see WooCommerce to WhatsApp if you also run a WordPress storefront, or connecting Zapier for the full trigger and action reference.