Direct WooCommerce actions

Products, images and workflows.

Controlled release testing: direct cards are being verified before public launch. Existing starters and legacy actions stay available.

$9/month per store, including authorised team members. New direct actions have no Sitetrail monthly operation cap. Starters and legacy backend actions share the existing 10,000 monthly starter/legacy operations. Google, hosting and protective request limits still apply.

  1. Install or update Sitetrail Studio Bridge. Choose its WooCommerce section and connect the store as its account owner.
  2. Keep your existing WordPress subscription separate. Buying WooCommerce does not unlock WordPress, or vice versa.
  3. Confirm your Workspace administrator permits Send a webhook, including automatic execution where needed.
  4. Choose a Prepare WooCommerce card, your paired store, stable request reference and product fields.
  5. Add Google's Send a webhook: POST to the exact bridge endpoint shown by Prepare; paste that endpoint as a static URL. Map Prepared payload as the entire body.
  6. Add Read WooCommerce result and map the webhook response plus Prepare's request ID, store and action.

Before subscribing

Direct actions require a Google Workspace edition with Send a webhook, enabled by your administrator. Check that the step is available before subscribing. Site connected verifies pairing, rather than a complete tested workflow.

Images

Use accessible HTTPS JPEG, PNG or WebP addresses or image attachment IDs on this store. The store downloads files directly. Set a featured image, ordered gallery and separate variation images. Omitted image fields preserve existing media; clearing requires explicit controls. Private Drive files and raw binary uploads are not included.

Retries and errors

Reuse the same stable reference and inputs for a retry. A partial image failure saves progress. A non-success native webhook stops the flow before Read result and can show only a generic error. Check Recent WooCommerce request errors in the plugin and inspect the store. Do not invent a new reference for an uncertain write. A signed permission expires after five minutes; if a manual approval was delayed, rerun the whole flow with the same reference and inputs to obtain a fresh permission.

If an original image URL expires or must change, inspect the existing draft in WooCommerce Products first. Use an Update product action with that product ID and a new reference for the changed inputs; do not repeat Create product with a new reference.

Optional event starters

In the bridge’s WooCommerce permissions, enable Send WooCommerce events only when you need starters. New connections default off; existing paired stores retain event access. When enabled, the five native hooks send store records even without a listening flow, including events caused by direct writes. Turning this off pauses only this connector’s hooks; queued events may finish. Direct actions and WordPress are unchanged.

Data route

Direct action content and results travel between Google and your site. Sitetrail checks identity, payment, site and signed input hashes. Existing starters and legacy actions still pass store data through Sitetrail; direct writes can also emit those starter events.

Account and billing Legacy starter/action guide