Post every new BigCommerce order to Slack and a Google Sheet

When a new order comes in on BigCommerce, run this workflow. Trigger on the BigCommerce webhook for order events (store/order/statusUpdated and/or store/order/created) so every incoming order fires the automation the moment BigCommerce publishes it. The webhook payload carries the order id — use that as the input to the fetch steps below.

Step 1: Use Get an Order on BigCommerce with the order id from the webhook payload to fetch the full order record (customer name, email, order total, currency, order status, timestamps, billing/shipping address).

Step 2: Use List Order Products on BigCommerce with the same order id to fetch the line items — product name, SKU, quantity, and unit price for each item.

Step 3: Format a deterministic new-order summary and use Send a Message on Slack to post it to a single fixed sales-orders channel. Use Slack mrkdwn formatting. Include, every time: customer name (from the order), order id, order total (formatted with the store's currency), a bullet list of items with quantity and unit price, and the order status. Same channel every run.

Step 4: Use Append Values on Google Sheets to append exactly one row to a fixed tab in a fixed spreadsheet. Columns in this order: order timestamp, order id, customer name, customer email, order status, order total, items summary (concatenate the line items as "SKU x quantity" pairs separated by semicolons), and the BigCommerce order URL. Use valueInputOption USER_ENTERED so the timestamp parses as a date and the total parses as a number.

Keep it deterministic. Same fields every time, same Slack channel, same spreadsheet and tab. Every order must be posted to Slack and appended to Google Sheets — do not skip either destination on any run. If either the Slack post or the Sheets append fails, surface the error and stop so the operator can investigate rather than silently missing a log entry.