The moment it happens
Post new orders and sign-ups to Slack
When something happens in your shop, app or form, the details land in the right channel straight away.
- Runs
- The moment it happens
- Apps
- Slack
- AI
- Not needed
- Access
- chat:write
Send this to your assistant
Create a ClickRuntime automation: give me a link my shop can send new orders to. Post every order over $100 to #sales with the customer, total and a link to the order.
First time? Adding ClickRuntime to your assistant takes about two minutes.
Why use it
Why teams use this automation
A new order, a form submission, a tagged release, a failed payment: each of these happens in a different tool, and each tool has its own notification settings that go to a different person's email. The founder sees the order, the developer sees the release, and the support lead finds out about the payment problem from a customer. The team has no single place where things that happen in the business are visible as they occur.
When a connected app sends an event as JSON to ClickRuntime, it applies the filter you set, such as order amount, urgency or a label, formats the fields into a readable message and posts it to a channel like #alerts through the Slack API. Events that do not pass the filter are ignored, so the channel carries only what deserves attention.
Small teams often use it as an activity feed for the business, and larger ones use it to route urgent events to a dedicated channel.
What you get out of it
The team sees one live feed
Orders, releases and sign-ups appear next to team conversation. People notice a spike or a stall the moment it happens, instead of discovering it in a weekly report that arrives after the chance to react has gone.
Important events are separated from noise
A filter on amount, urgency or label keeps routine events out and puts only significant ones in front of people, so alerts continue to be read rather than muted after a week.
Anything with a webhook can connect
Many tools can send an event to a URL. This avoids waiting for a ready-made Slack integration for each one, and also covers homemade internal systems that no marketplace app supports and that no vendor will ever build for.
Faster reactions to customers
A form submission posted in a channel gets claimed by whoever is online. Replies go out in minutes, which affects conversion on inquiries and goodwill on complaints, and nothing waits in one person's mailbox.
Fewer scattered notification emails
Each person stops receiving separate emails from five apps. The events that matter are in a channel, and the rest are left behind in the source systems, where anyone who wants them can still find them.
How it works
What happens, step by step
When your shop or app reports a new event, such as an order being placed, ClickRuntime receives it straight away.
It checks the event against your filter, for example skipping orders under $100.
Events that pass become a short message with the order number, amount, customer email and a link.
The message is posted to your Slack channel, such as #sales, within seconds.
Before it runs live
- Connect Slack, then invite the app to the channel (type /invite @ClickRuntime there)
- Paste your automation's link into the other app's webhook settings
What you get
Build your own
Need it to work differently?
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 Google Sheets
- Combine it with other Slack steps into one automation
Under the hood
The code that runs this automation
from clickruntime import on_event, notify, log
MIN_TOTAL = 100
@on_event
def handle(event):
order = event.json
total = float(order.get("total_price", 0))
if total < MIN_TOTAL:
log.info("skipped small order", {"id": order.get("id"), "total": total})
return {"posted": False}
customer = (order.get("customer") or {}).get("email", "unknown customer")
notify.slack(
f"New order {order.get('name')}: ${total:,.2f} from {customer}\n{order.get('order_status_url', '')}",
channel="#sales",
)
return {"posted": True, "total": total}FAQ
Common questions
Which apps can send events to it?
Can I change the filter later?
What does the posted message contain?
Can I post only deals over $10,000?
What permissions does it need?
Does it need AI?
How many runs does it use?
Can I change how it works?
Related
You might also like
Get error alerts with a plain-English explanation
When one of your jobs or systems fails, #ops gets the error and a one-line guess at the cause, without the same error twice in an hour.
See how it worksSend your best leads to sales straight away
Every contact form message is scored, and the promising ones reach #sales while they're still warm.
See how it worksKnow the moment your website goes down
Your team hears in Slack when the site stops responding or slows down, and again when it's back.
See how it worksKeep exploring
Set up “Post new orders and sign-ups to Slack” from your assistant
Copy the prompt above, or connect your assistant first. Free plan, no credit card.