Converla

WooCommerce & commerce setup

Commerce integrations let agents and automations talk about real orders and products — not guess. This guide focuses on WooCommerce, which Converla connects through a guided authorization flow.

Store owners & ecommerce ops

Before you start

  • A WooCommerce store you administer (HTTPS) and permission to authorize REST access.
  • A Converla brand workspace with commerce features available on your plan.
  • WhatsApp or another channel connected if you want order conversations in the inbox.

How to

Open commerce / WooCommerce in Converla

In admin Integrations or Commerce settings, choose WooCommerce for the active brand. Use the in-product connect flow rather than pasting random API keys from old plugins.

Authorize the store safely

Complete the Converla authorization steps for your store URL. Approve access only from an admin account you trust. Credentials stay scoped to the brand workspace.

Confirm connection health

After connect, run the product’s connection test or status check. Fix URL mismatches (www vs non-www), SSL issues, or revoked keys before inviting agents to rely on order data.

Sync and use order context in conversations

Once healthy, agents can reference order-related context while chatting on WhatsApp or other channels. Keep replies factual based on store data — never invent tracking numbers.

Optional: automation presets

Where available, enable order-confirmation or similar presets so customers get timely WhatsApp updates. Review templates and consent requirements before broadcasting.

Tips that save time

One brand ↔ one store mapping

Keep each Converla brand tied to the store it serves. Mixing stores in one workspace creates confusing order lookups for agents.

Rotate keys through Converla

If WooCommerce rejects credentials, reconnect with the official flow instead of hand-editing secrets in multiple places.

Examples

Agent reply pattern

Confirm the order ID the customer mentioned, check status in Converla’s commerce context, then reply with status and next step (shipped, pending payment, or refund in progress) — without pasting raw API dumps.

Troubleshooting

Authorization fails or returns unauthorized.

Confirm the store URL is exact (including https), that REST API is not blocked by a security plugin, and that you completed Converla’s reconnect flow after any key revoke.

Orders do not appear for agents.

Verify the integration status is healthy and that you are searching the correct customer identifiers. Sync may need a moment after first connect — retest with a recent order.

Shopify or Salla instead of WooCommerce?

Use the matching commerce connector in Converla when available for your plan. Do not force WooCommerce credentials into another platform’s store.

Frequently asked questions

Is WooCommerce the only commerce option?

Converla’s marketing and product surfaces also reference other commerce platforms. Use the connector that matches your store; this guide covers the WooCommerce path specifically.

Do I need developers to connect WooCommerce?

Usually no. Store admins can complete the guided authorization. Developers are only needed if a host firewall or custom security layer blocks REST access.

Does commerce replace the knowledge base?

No. Commerce supplies order and catalog context; the knowledge base covers policies and FAQs. Most teams use both.