On a schedule

Get a morning count of open Front conversations

Each morning you see how many conversations are open and unassigned in every inbox.

Runs: On a schedule
Apps: Front
AI: Not needed
Access: read

Send this to your assistant

Create a ClickRuntime automation: every weekday at 8am, email me the number of open and unassigned Front conversations in each inbox.

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

If a team shares inboxes in Front, nobody sees the whole picture unless someone goes and looks. One inbox has 12 unassigned conversations, another has 3 open and a long queue was archived by mistake, but the support manager only learns this when a customer escalates. Weekend backlog is especially easy to miss until Monday afternoon.

Each morning on the schedule you set, conversations are counted by status for every inbox and the results are emailed in one table: open, unassigned and archived. The unassigned count is the one to watch, since those conversations belong to no one yet.

It works well for support managers, agency account leads and founders who share an inbox with a part-time helper and want one line to tell them whether to worry. Anyone can read it in seconds.

What you get out of it

Unassigned work is surfaced early
The number of conversations that nobody owns is listed each morning, so the manager can hand them out before the first customer asks why nobody replied. That helps ensure every customer has a named person responsible for the reply, not just a shared inbox.
Comparing inboxes shows imbalance
Seeing counts per inbox makes it clear when Sales Enquiries is calm and Support is drowning, which supports moving a teammate for the day with a reason. Moving one person for a day is easier to justify with a table to point at.
Archived counts catch mistakes
A sudden jump in archived conversations can signal a bulk action that was run by accident or a rule that is closing things too aggressively. Catching it the next morning is far better than discovering missing conversations a week later.
Weekend backlog is visible by Monday
The report that arrives on Monday morning shows what accumulated since Friday, so the week starts by clearing a known quantity rather than discovering it. The first hour of Monday then goes to the backlog rather than to counting it.
A simple record of inbox health
Saved emails form a day-by-day history of queue size that you can scroll back through when reviewing a busy season or justifying a new hire. Over a quarter this shows seasonal patterns clearly.

How it works

What happens, step by step

Every morning, ClickRuntime counts the conversations in each of your Front inboxes.
It notes how many are open and how many have no one assigned.
You get one email with a line per inbox, like "Support: 42 open, 7 unassigned".

Before it runs live

Connect Front

What you get

RunsOn a schedule

Get a morning count of open Front conversationstoday, 9:00Succeeded

Email · Front inboxesSupport: 42 open, 7 unassigned Billing: 9 open, 0 unassigned

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

Run it at a different time, more or less often, or only on weekdays
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 Front 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_inbox_report.pyexample

from clickruntime import on_trigger, credentials, http, notify

API = "https://api2.frontapp.com"

@on_trigger
def run(event):
    headers = {"Authorization": f"Bearer {credentials.secret('FRONT_API_TOKEN')}"}
    lines = []
    for inbox in http.get(f"{API}/inboxes", headers=headers).json()["_results"]:
        counts = {}
        for label, q in (("open", "is:open"), ("unassigned", "is:open is:unassigned")):
            resp = http.get(f"{API}/conversations/search/{q} inbox:{inbox['id']}", headers=headers, params={"limit": 1})
            counts[label] = resp.json()["_total"]
        lines.append(f"{inbox['name']}: {counts['open']} open, {counts['unassigned']} unassigned")
    notify.email_me("Front inboxes this morning", "\n".join(lines))
    return {"inboxes": len(lines)}

FAQ

Common questions

What is the difference between open and unassigned in the report?

Open conversations are still active in the inbox, whether or not someone is working them. Unassigned ones are open conversations with no teammate assigned. The unassigned number is usually the more urgent figure. Watch unassigned first, because those need an owner today.

Can the report cover only some of my inboxes?

Yes. You choose which Front inboxes are counted, so a private or low-volume inbox can be left out. Only the inboxes you list appear as rows in the email. Add or remove inboxes whenever your team structure changes.

Can it go to Slack instead of email?

It can. The same table can be posted to a Slack channel, or sent to both places. Your AI assistant can rewrite the final step and show you the new version to approve. Either route works equally well for the same data.

What permissions does it need?

read. 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 runs (on a schedule). Checks that find nothing to do 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.

Daily