Connect WooCommerce to WhatsApp CRM

On this page

Before you start
Steps: WooCommerce to WhatsApp via Zapier (recommended)
Alternative: without Zapier, using Make or Pabbly Connect
What you will see
Settings and options
Troubleshooting

VGraple CRM has no native WooCommerce plugin; the honest, working route is Zapier's own WooCommerce trigger app feeding into VGraple CRM's Send Template Message or Create Lead action, since WooCommerce's built-in webhook settings have no field for the Authorization header VGraple CRM's API needs. This walkthrough covers that route, and the Make/Pabbly Connect alternative.

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 or shipping updates; see creating your first template.
You need admin access to your WordPress site to install and connect Zapier's WooCommerce app, or to configure Make's or Pabbly Connect's WooCommerce connector.

Steps: WooCommerce to WhatsApp via Zapier (recommended)

Create a new Zap and choose WooCommerce as the trigger app. Pick an event, most often New Order or Order Status Changed, and connect your WooCommerce store, which needs your site's URL and API credentials that Zapier's connection flow generates for you.

API keys in VGraple CRM with prefix, creation date and last use

Test the trigger to pull a sample order, giving you real field names (order number, total, billing phone, order status) for mapping.
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 built for this purpose, with variables for whatever order details you want to include.
Map the "To" field to the order's billing phone number, and map body variables to the matching WooCommerce fields.
Test the action, then turn the Zap on.

Alternative: without Zapier, using Make or Pabbly Connect

Use Make's or Pabbly Connect's own WooCommerce module as your trigger, or, if your WooCommerce version and connector combination does not support it directly, call WooCommerce's own REST API from an HTTP module to poll recent orders.
Add an HTTP action step calling VGraple CRM's REST API directly. POST to https://crm.vgraple.co.in/api/v1/messages with Authorization: Bearer vgk_your_key_here and a body containing to, template and variables. See the REST API quickstart.

What you will see

Once live, an order reaching the event you chose (a new order, or an order moving to a specific status) sends the mapped WhatsApp template within moments, landing in VGraple CRM's inbox on that customer's conversation, creating a contact automatically if the phone number is new.

Settings and options

Setting or field	What it does	Default
WooCommerce trigger event	Which order event starts the Zap or workflow	Chosen when building it (New Order, Order Status Changed)
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 order's billing phone
Body variable mapping	Which order details fill the template's placeholders	Mapped manually per Zap or workflow

Troubleshooting

Symptom	Likely cause	Fix
WooCommerce's built-in webhook does not authenticate against VGraple CRM	Native WooCommerce webhooks have no field for a custom Authorization header	Use Zapier's, Make's, or Pabbly Connect's WooCommerce connector instead, which handles authentication for you
No WhatsApp message sends even though the trigger fired	The order's billing 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 with wrong or blank variables	The mapped values do not line up with the template's `{{1}}`, `{{2}}` order	Recheck the variable mapping against the exact order the template body expects
"No approved template named..." error in 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
Message sends multiple times for one order	The trigger event fires more than once (for example the order changes status several times, each wired to the same action)	Pick a single, specific status transition as the trigger, or add a Filter step limiting it to one status

Example

A D2C store on WooCommerce sends a shipping-update template the moment an order's status changes to "Completed," mapping the order number and a tracking note into the template body, replacing a manual WhatsApp message the founder used to send by hand.

Once this is working, see Shopify order events to WhatsApp if you also run a Shopify store, or connecting Zapier for the full trigger and action reference.

Frequently asked questions

Is there a native WooCommerce plugin for VGraple CRM?

No. There is no VGraple CRM plugin in the WordPress plugin directory and no direct WooCommerce connection. The working route is Zapier's own WooCommerce trigger app feeding into VGraple CRM's Send Template Message or Create Lead action.

Can I use WooCommerce's own built-in webhooks (Settings > Advanced > Webhooks) directly?

Not on their own. WooCommerce's native webhook feature lets you set a secret for WooCommerce's own signature, but has no field to add a custom Authorization header, so it cannot authenticate directly against VGraple CRM's API without an intermediate step like Zapier, Make or Pabbly Connect.

What WooCommerce events can trigger a WhatsApp message?

Whatever Zapier's WooCommerce app exposes as triggers, typically New Order and Order Status Changed among others; pick the one matching when you actually want the message sent, for example when an order is marked "completed" rather than the moment it is placed.

Does the customer need to already exist as a VGraple CRM contact?

No. Sending a template creates a new contact automatically if the phone number is not already saved, the same behaviour any template send produces, whether it came from WooCommerce, a manual send, or any other integration.

Can I include the order number and total in the message?

Yes, provided your approved template has variables for them. Map the WooCommerce order's number, total and any other field you want into the template's body variables in the same order the template's placeholders expect.

What if I use Make or Pabbly Connect instead of Zapier?

The same pattern works there using Make's or Pabbly Connect's own WooCommerce module (or, if unavailable for your version, WooCommerce's REST API called from an HTTP module) as the trigger, and an HTTP action step calling VGraple CRM's REST API directly with your API key.

WooCommerce to WhatsApp