The moment it happens

Post each BigCommerce order to Slack

Seconds after checkout, Slack shows the order number, customer and total.

Runs: The moment it happens
Apps: BigCommerce
AI: Not needed
Access: Orders read-only

Send this to your assistant

Create a ClickRuntime automation: when a new order is placed in my BigCommerce store, post the order number, customer name and order total to #orders in Slack.

Paste it into your assistant. It tells you what it will send or change before it runs live.

Add to ChatGPT Add to Claude

First time? Adding ClickRuntime to your assistant takes about two minutes.

Why use it

Why teams use this automation

A small BigCommerce store with two people in the warehouse and one on support has a familiar problem. New orders pile up in the BigCommerce control panel, and nobody notices a Saturday-morning rush until the carrier pickup is already gone. Owners refresh the Orders page between other jobs, and a high-value wholesale order can sit unseen for hours while the customer wonders if checkout worked.

Each time BigCommerce reports a new order, the webhook arrives carrying only the order ID. ClickRuntime then fetches the complete order from the BigCommerce API and posts a short summary to your Slack channel: the order number, the customer name and the order total. It runs when the event arrives, so the message lands within seconds of checkout rather than on a polling delay.

It suits stores where the people who pack boxes, answer customers or watch revenue live in Slack all day and should not need a BigCommerce login open to know a sale happened.

What you get out of it

Packing starts the minute a sale lands
Whoever handles fulfillment sees the order the moment it is placed, so same-day shipping cutoffs stop depending on someone remembering to refresh the Orders page. Orders placed just before a carrier pickup actually make it onto the truck.
Big orders never wait unnoticed
A large wholesale or bundle order appears in the channel with its total, so an owner can personally check stock and reply to the buyer within minutes. That early reply is often what turns a nervous first-time bulk buyer into a repeat customer.
Accurate details from the full order
The webhook only carries an ID, so the workflow fetches the whole order before posting. The number, customer and total in Slack match what BigCommerce actually holds, which avoids packing from a half-complete notification.
A shared pulse for a small team
Seeing orders scroll by in a channel tells everyone how the day is going without a dashboard meeting. Slow afternoons and sudden spikes are obvious to support and marketing as well as the warehouse.
Quicker answers to where is my order
Support staff can search the channel by customer name and find the order number right away. Replying to an early pre-shipment question takes seconds instead of a trip into the BigCommerce admin.

How it works

What happens, step by step

When a new order is placed in your BigCommerce store, BigCommerce tells ClickRuntime straight away.
ClickRuntime looks up the full order to get the customer and total.
A message goes to your #orders Slack channel with the order number, customer name and amount.

Before it runs live

Connect BigCommerce
Paste your automation's link into the other app's webhook settings

What you get

RunsThe moment it happens

Post each BigCommerce order to Slackjust nowSucceeded

Slack · #ordersNew order #10342: Dana Fox, USD 129.00

Build your own

Need it to work differently?

This template is a starting point. Copy the prompt and change it, or describe a different automation from scratch, with your own conditions, more apps or an AI step. Your assistant writes it, tests it and runs it on ClickRuntime.

Your own rules
Conditions, thresholds, filters and exceptions, written the way you'd explain them to a colleague.
Any number of apps
One automation can read from one app and update several others. Over 248 apps are ready, and anything with an API works too.
AI where it helps
Summaries, classification, extraction and drafts use ClickRuntime's built-in AI, with no extra key.
On a schedule or on each event
Runs as often as every 5 minutes, or the moment an app sends an event, and keeps track of what it already handled.

Changes you can ask for

Act only on the items that match your own rules, and skip the rest
Add an AI step, for example to summarize, sort or draft a reply
Add another app, for example also send it to Slack
Combine it with other BigCommerce steps into one automation

Under the hood

The code that runs this automation

This is the Python script that runs each time the automation starts. Your AI assistant writes it for you when you send the prompt, and you allow each step in your assistant. To change how the automation works, describe the change to your assistant and it updates the script for you. For every function it can use, see the script reference.

new_order_notification.pyexample

from clickruntime import on_event, credentials, http, notify

API = "https://api.bigcommerce.com/stores/your-store-hash"

@on_event
def handle(event):
    order_id = event.json["data"]["id"]
    order = http.get(f"{API}/v2/orders/{order_id}",
                     headers={"X-Auth-Token": credentials.secret("BIGCOMMERCE_TOKEN"), "Accept": "application/json"})
    order.raise_for_status()
    o = order.json()
    b = o["billing_address"]
    notify.slack(f"New order #{o['id']}: {b['first_name']} {b['last_name']}, "
                 f"{o['currency_code']} {float(o['total_inc_tax']):,.2f}", channel="#orders")
    return {"order": o["id"]}

FAQ

Common questions

Does the Slack message wait for BigCommerce to be polled?

No. BigCommerce sends a webhook when an order is created, and the run starts when that event arrives. There is no schedule involved, so the post typically appears within seconds of the customer completing checkout, subject to how quickly BigCommerce delivers the event.

Why does it fetch the order again after the webhook?

BigCommerce order webhooks contain the order ID and not the order details. To post a useful summary, the workflow calls the BigCommerce API with that ID and reads the customer and total from the full record, so what you see in Slack is current.

Can I post only orders above a certain total?

Yes. Because the total is read from the fetched order, a condition such as only posting orders over $500 can be added, or you can send big orders to a separate channel. Tell your AI assistant the threshold and review the change before it goes live.

What permissions does it need?

Orders read-only. Nothing else in your accounts is used.

Does it need AI?

No. It runs without AI, so it doesn't use your plan's AI allowance.

How many runs does it use?

One run for each event the app sends.

Can I change how it works?

Yes. Describe the change to your AI assistant, for example a different schedule, channel or filter. It updates the automation, tests it and tells you what changed.

Every 6 hours