Collects as they arrive, acts daily

Get an evening count of new sign-ups per event

A single 6pm email lists how many people registered today for each event.

Runs: Collects as they arrive, acts daily
Apps: Luma
AI: Not needed
Access: calendar API key

Send this to your assistant

Create a ClickRuntime automation: collect Luma registrations through the day and at 6pm email me how many new guests each event got.

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

Hosts running several Luma events at once, a weekly meetup, a workshop series and a conference, cannot watch each registration page. Opening every event each day to see who signed up is tiresome, and a notification for each guest is far too much. Meanwhile the numbers that matter, how many registered for Thursday's workshop since yesterday, stay out of sight until the week of the event.

ClickRuntime collects every guest registration as it arrives. At 6 p.m. it groups the day's sign-ups by event, emails you one digest with the names and counts per event and then clears its collection, so tomorrow's digest only has new registrations.

Event managers and community leads use it to track momentum without being interrupted. The digest is designed to be read in under a minute. It keeps the whole picture of your events in one place, so nothing falls between the cracks while you are busy preparing for the next gathering.

What you get out of it

You see momentum for each event
A digest that shows 12 registrations for one event and 2 for another tells you where to focus promotion. It beats discovering a weak turnout in the last week. That insight arrives early enough to act on.
One email replaces constant checking
Instead of logging in several times a day, you read one summary at the end of it. The time saved is small each day and large over a season of events.
Promotion is adjusted in time
If a campaign did not produce registrations today, you know by evening and can try a different channel tomorrow. Waiting until the weekly review wastes valuable days. That clarity helps you plan effort and not only react.
Names are visible for preparation
Seeing who registered lets hosts prepare name badges, seating or personal greetings in advance. It improves the experience of guests who feel recognized. It also prevents wasted time wondering about the system.
Quiet days are stated, not hidden
When nobody registered for an event, the digest says so rather than omitting it. That is useful information, and it prevents confusion about whether the automation ran. That helps you plan promotion and venue size for next time.

How it works

What happens, step by step

Each time someone registers for a Luma event, ClickRuntime notes which event they signed up for.
At 6pm it counts the day's registrations for each event.
You get one email with the total for the day and a count per event, or a note saying there were none.
The tally is then cleared so tomorrow starts from zero.

Before it runs live

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

What you get

RunsCollects as they arrive, acts daily

Get an evening count of new sign-ups per eventtoday, 9:00Succeeded

Email · Luma registrationsLuma: 14 new guests today Acme Founders Breakfast: 9 · Northwind Demo Night: 5

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 Luma 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.

daily_registrations_digest.pyexample

from collections import Counter
from clickruntime import on_event, on_trigger, state, notify

@on_event
def handle(event):
    body = event.json or {}
    if body.get("type") == "guest.registered":
        names = state.get("today") or []
        names.append(body["data"]["event"]["name"])
        state.set("today", names)
    return {"ok": True}

@on_trigger
def run(event):  # 6pm daily
    names = state.get("today") or []
    counts = Counter(names)
    notify.email_me(f"Luma: {len(names)} new guests today",
                    "\n".join(f"{ev}: {n}" for ev, n in counts.most_common()) or "No new registrations today.")
    state.delete("today")
    return {"guests": len(names)}

FAQ

Common questions

Why is the digest at 6 p.m.?

It is a default that catches the day's registrations before people leave work. You can choose any time, such as 8 a.m. to cover the previous day. The day's boundary is whichever time you set, and everything collected since the last digest is included. You can ask for the counts to be listed first.

What happens to registrations that arrive while the digest is being sent?

They are kept for the next digest. Collection and sending are separate, and the stored list is only cleared of the registrations that were included in the email, so a guest who registers at the wrong moment is not lost.

Does it include cancellations?

This version covers new registrations only. Cancellations are a different Luma event and can be added to the same email as a separate section, so you see net movement per event rather than only gains.

What permissions does it need?

calendar API key. 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 each time it checks. Checks that find nothing new and stop right away aren't counted.

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.

The moment it happens