Flag high-value and first-time BigCommerce orders for sales

When BigCommerce sends an order webhook (any store/order/* event carrying an order ID), run this workflow to decide whether the order is worth a human touch and, if so, route it to sales.

First, pull the full context of the order. Use BigCommerce Get an Order with the ID from the webhook payload to load totals, currency, customer ID, and status. Then use BigCommerce List Order Products to load the line items on the order (product names, quantities, prices). Use BigCommerce Get a Customer with the customer ID from the order to load the buyer's email, first name, last name, and any stored company or notes. Finally use BigCommerce Get a Count of Orders scoped to that customer ID: if the count is 1 (this order), the buyer is a new customer; if it is greater than 1, they are returning.

Decide whether this order is worth flagging. Flag the order if either the order total is at or above the configurable value threshold (default: 250 in the store's default currency, exposed to the runner as a tunable input) or the buyer is a new customer (Get a Count of Orders returned 1). If neither is true, exit silently. Do not post to Slack and do not touch HubSpot. Cheap repeat orders should not create noise.

If the order is flagged, first upsert the buyer into HubSpot using Batch Upsert Contacts matched on email. Write email, firstname, and lastname from the BigCommerce customer. Include a lifetime spend property that folds this order's total into any prior lifetime value already on the contact, and a last purchased products property containing a short comma-separated list of the product names from this order. Add a short note that this contact was flagged as a sales opportunity by BigCommerce order [order number].

Then post a Slack message using Send a Message to the configured sales channel. Keep it pitch-ready and under five short lines. Open by naming the buyer and whether they are new or returning. Follow with what they bought and the order total. Close with a line explaining why this order stands out (crossed the value threshold, first-time buyer, notable product mix, unusually large basket). The summary should read like something a rep can act on without opening BigCommerce.

Inputs to expose to the runner: the order value threshold (default 250, treated in the store's default currency), the Slack channel that should receive summaries, and the HubSpot properties to write beyond the required email and name (lifetime spend, last purchased products, tags). Never post about orders that fail both bars. Silence is the correct behavior for small repeat orders, and the whole point of the workflow is to surface only the ones worth a real sales touch.