datawebotExtraction guide
Plan WooCommerce product extraction
Choose between authorized merchant data and public observations.
01 / INPUTStore URL + required product fields
02 / YOUR WORKFLOWConfirm access → map variations
03 / OUTPUTProduct and variation field plan
Keep the right fields.
Workflow field map| Field / step | Input | Rule |
|---|---|---|
| Identity | Product ID + variation ID | Preserve parent-child relationships. |
| Price | Amount + store currency | Check variation-specific values. |
| Access | Merchant authorization or public source | Do not treat store-owner APIs as public access. |
Before you use the output
WooCommerce documents a merchant REST API. That is separate from datawebot's extraction API; the current reviewed extraction examples use Shopify storefronts. Another source requires review.
Check one record first.
Start with the smallest useful scope. Compare the returned record with its source, confirm variant identity and inspect missing fields before applying the mapping to a larger dataset.
Keep extraction warnings and the retrieval timestamp with downstream output. When a required field is missing, leave it unresolved or return to the source; do not fill it from an assumption.