Every 15 minutes
Hear who enters a key segment
New members of a segment such as 'At risk' are posted to Slack so someone can follow up.
- Runs
- Every 15 minutes
- Apps
- Klaviyo
- AI
- Not needed
- Access
- read (segments, profiles)
Send this to your assistant
Create a ClickRuntime automation: every 15 minutes, check my Klaviyo 'At risk' segment and post anyone new to #retention in Slack.
First time? Adding ClickRuntime to your assistant takes about two minutes.
Why use it
Why teams use this automation
Segments in Klaviyo describe moments that matter: customers who have spent over $1,000, subscribers who viewed a product three times without buying, people who just reached a loyalty tier. Membership changes on its own as behavior changes, and no one is told. A high-value customer might join the VIP segment on Monday and wait two weeks for the personal outreach that the program promised.
Every fifteen minutes, ClickRuntime lists the profiles currently in the segment you choose, compares them with the IDs it stored last time and treats the difference as new members. Each new member is posted to Slack, and the stored list is updated so the same person is not announced again.
Account managers and customer experience teams use it to make outreach feel timely and personal. No export or manual comparison is involved at any point.
What you get out of it
Timely outreach to valuable customers
A thank-you or a personal offer sent shortly after someone reaches a top spending tier feels earned. Sent three weeks later, it feels like an afterthought from a mailing list.
Interest signals are acted on
A segment of people who viewed a product repeatedly shows intent. Notifying a human lets someone reach out, answer a question or offer help while the shopper is still considering.
Segment definitions get tested in practice
Seeing who actually enters the segment tells you whether its rules are right. If strange profiles keep appearing, you can fix the conditions before a campaign targets them. That is cheaper than discovering the mistake after a big send.
Hand-offs between teams are quicker
When a profile enters a segment that sales or support cares about, the right person sees it without a request. That cuts the lag created by emailing around lists. Nobody has to chase a list through email first.
No recurring manual comparison
Without this, someone would export the segment each week and compare it to the previous one by hand. A stored list and a diff replace that and cannot be forgotten.
How it works
What happens, step by step
Every 15 minutes ClickRuntime gets everyone currently in a Klaviyo segment you care about, such as "At risk".
It compares them with the members it saw last time and keeps only the people who are new to the segment.
The new members are posted to your #retention Slack channel with their name and email, so someone can follow up.
Before it runs live
- Connect Klaviyo
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 Slack
- Combine it with other Klaviyo steps into one automation
Under the hood
The code that runs this automation
from clickruntime import on_trigger, credentials, http, state, notify, report_fetched
API = "https://a.klaviyo.com/api"
AT_RISK_SEGMENT_ID = "Rk7Sgm"
def klaviyo():
return {"Authorization": f"Klaviyo-API-Key {credentials.secret('KLAVIYO_API_KEY')}",
"revision": "2024-10-15", "accept": "application/vnd.api+json", "content-type": "application/vnd.api+json"}
@on_trigger
def run(event):
h, url, members = klaviyo(), f"{API}/segments/{AT_RISK_SEGMENT_ID}/profiles", []
while url:
page = http.get(url, headers=h, params={"fields[profile]": "email,first_name", "page[size]": 100}).json()
members += page["data"]
url = page["links"].get("next")
known = state.get("members")
new = [p for p in members if known is not None and p["id"] not in set(known)]
report_fetched(len(new))
state.set("members", [p["id"] for p in members])
if not new:
return {"summary": "Nothing new"}
notify.slack("New in At risk:\n" + "\n".join(f"• {p['attributes'].get('first_name') or ''} {p['attributes']['email']}"
for p in new), channel="#retention")
return {"posted": len(new)}FAQ
Common questions
How does it tell who is new in the segment?
What if someone leaves the segment and rejoins?
Is there a size limit for the segment?
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
Post new VIP list members to Slack
Within 15 minutes of joining your VIP list, each person appears in Slack with name and email.
See how it worksPost big orders to Slack
Orders above your threshold show up in Slack with the customer and amount.
See how it worksTell the team when a campaign goes out
Within the hour, Slack shows the name and audience of every campaign Klaviyo sent.
See how it worksKeep exploring
Set up “Hear who enters a key segment” from your assistant
Copy the prompt above, or connect your assistant first. Free plan, no credit card.
