Connect WooCommerce to Convor with REST API keys, signed webhooks, order context, and a manual widget script embed.
The WooCommerce integration connects a store to Convor with WooCommerce REST API keys and signed webhooks. Operators can test the saved API credentials, receive supported webhook events, and fetch recent orders for customer context.
In WordPress Admin, open WooCommerce, then Settings, then Advanced, then REST API. Click Add Key, name it Convor Integration, choose the user who owns the key, and set permissions to Read. Generate the key and copy both values.
Consumer Key: ck_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Consumer Secret: cs_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxConvor stores both values encrypted and only returns masked values in the dashboard.
In WooCommerce, open Settings, then Advanced, then Webhooks. Create one active webhook per topic you want to send to Convor, or create the topics required by your workflow. Use:
https://your-convor-domain.com/api/woocommerce/webhookwebhookSecret value saved in ConvorWooCommerce signs webhook payloads with X-WC-Webhook-Signature. Convor verifies the HMAC before acknowledging the event.
In Convor, open Integrations → WooCommerce. Enter:
storeUrl: the WooCommerce store root, for example https://yoursite.comconsumerKey: the REST API consumer key beginning with ck_consumerSecret: the REST API consumer secret beginning with cs_webhookSecret: the shared webhook signing secrettopics: one or more supported webhook topics{
"integration": "woocommerce",
"storeUrl": "https://yoursite.com",
"consumerKey": "ck_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx",
"consumerSecret": "cs_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx",
"webhookSecret": "shared-webhook-secret",
"topics": ["order.created", "order.updated"]
}After the first save, all secrets are masked. When editing the store URL or topics, leave the credential fields blank to keep the saved encrypted values. Enter fresh values only when rotating credentials.
| Topic | Description | Status |
|---|---|---|
| order.created | A new order is placed in your store | Supported |
| order.updated | An order status or details change | Supported |
| order.deleted | An order is deleted | Supported |
| customer.created | A customer account is created | Supported |
| customer.updated | Customer details change | Supported |
| product.updated | Product details change | Supported |
Use Test Connection after saving. Convor verifies the saved WooCommerce credentials against the store API. Disconnecting removes the saved WooCommerce configuration from Convor. Revoke or delete the REST API keys and webhooks in WooCommerce when you retire the connection.
| Feature | Description | Status |
|---|---|---|
| REST API connection test | Verifies saved WooCommerce consumer key and secret | Supported |
| Signed webhooks | Verifies WooCommerce HMAC signatures before processing events | Supported |
| Recent orders | Fetches recent order context for operators | Supported |
| Topic selection | Stores the webhook topics Convor should accept for the org | Supported |
| Cleanup | Deletes saved Convor-side WooCommerce configuration | Supported |
Credential scope
WooCommerce REST API keys need Read permission at minimum. If order context is unavailable, confirm the key is active and belongs to a user who can read orders.
/wp-json/; verify the key begins with ck_ and the secret begins with cs_.Ostatnia aktualizacja: 10 sie 2026
Czy ta strona była pomocna?