Use the supported ecommerce connection instead of treating every purchase as an anonymous webhook. Import selected historical contacts, orders and transactions, configure future synchronization and build workflows around submitted orders and verified payments while preserving WooCommerce order identity.
Connect the main HTTPS store URL without a trailing slash, authorize the store, select the historical records to import and the data to synchronize going forward. Then build workflows using Order Submitted or Payment Received with source filters and test paid, failed, cancelled, refunded and guest-checkout paths.
Confirm the production URL, admin access, record volume, matching rules and which system owns customer, order and fulfilment fields.
Start the ecommerce store connection, enter the canonical store URL and complete authorization with the intended production store.
Select contacts, orders and transactions needed for CRM history. Skipped historical types may require disconnecting and reconnecting to import later.
Enable the supported contact, order, transaction and workflow-trigger options required after the initial import.
Use Order Submitted and Payment Received with the WooCommerce source and product or status filters. Key actions to the external order or transaction ID.
Place controlled guest and known-customer orders, then test successful payment, failure, cancellation and refund behavior before broad activation.
Trigger
WooCommerce Payment Received with successful status
Actions
Result
A verified payment creates one reliable operational handoff.
Trigger
Order Submitted for selected product or category
Actions
Result
Customers receive the correct next steps for what they bought.
Trigger
Supported order history reaches a defined count or value
Actions
Result
Purchase history drives differentiated retention without duplicating first-order automation.
Use the main HTTPS URL without a trailing slash, confirm administrator access and check that authorization completed on the intended store.
Review the original import selection and status. Adding a skipped historical data type may require a controlled reconnect.
Guest checkout can create a contact, but ongoing synchronization may differ from a registered customer. Match by stable available identifiers and test the actual checkout configuration.
Filter Order Submitted or Payment Received by external-store source, sub-source, product and status.
Connectors, events, actions and usage charges can vary by plan, account and region. Verify the options shown in your account and test them before publishing.
No. Current official documentation describes a supported ecommerce connection for importing and synchronizing contacts, orders and transactions, plus order and payment workflow triggers.
Yes, selected historical contacts, orders and transactions can be imported during connection. Choose deliberately because skipped types may require reconnecting later.
Yes. Supported Order Submitted and Payment Received triggers can start source-filtered workflows.
Guest purchases may create contacts needed for the order, but future synchronization behavior can differ from registered customers.
Connect the event to an owner, next action and outcome, then test it before launch.
Discuss your integration.png){kind=logo}