Daily

Start the day with yesterday's ticket numbers

One morning email with tickets created and resolved yesterday, and what is still open by priority.

Runs: Daily
Apps: Freshdesk
AI: Not needed
Access: read

Send this to your assistant

Create a ClickRuntime automation: every weekday at 7:30am, email me how many Freshdesk tickets were created and resolved yesterday, and the open count split by Urgent, High, Medium and Low.

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 support lead wants the same few numbers every morning: how many tickets came in yesterday, how many were resolved, and how many are open now. In Freshdesk, getting them means building filters or opening reports, and on a busy day nobody does. Without the numbers, backlogs grow for several days before anybody says the queue looks long, and staffing decisions are made on hunches. Hunches rarely survive a busy Monday.

Each morning, ClickRuntime searches Freshdesk for tickets created yesterday, tickets resolved yesterday and tickets still open, and emails you the three counts. It is a short note that you can read in ten seconds before the team meeting. The numbers arrive without anyone building a report.

Support leads and founders who run their own support will find it a useful daily pulse.

What you get out of it

See backlog growth early
If created tickets outnumber resolved ones for three days, the open count climbs. A morning email makes that obvious before customers complain about slow replies. Acting early is much cheaper.
Plan staffing with real numbers
Daily counts show which days are busy. You can schedule extra hours on Mondays or after launches instead of guessing. Better coverage means shorter waits. Plan around the pattern, not the surprise.
Run a better standup
Opening the meeting with yesterday's numbers saves the team from debating how things feel. The conversation moves to what to do about the queue. Meetings get shorter and more useful.
Measure the effect of changes
After a new help article or product fix, you can see whether created tickets fall. Daily figures show the impact within days instead of at quarter end. Cause and effect become visible.
Report upward without extra work
Managers asking how support is doing can be answered with a line from the email. A running record of daily numbers makes monthly reports quick to prepare. Over time you build a record that supports requests for budget.

How it works

What happens, step by step

Every morning ClickRuntime counts the Freshdesk tickets created yesterday and the ones resolved yesterday.
It also counts how many tickets are still open at each priority: urgent, high, medium and low.
You get one email with those numbers, with the created and resolved totals in the subject line.

Before it runs live

Connect Freshdesk

What you get

RunsDaily

Start the day with yesterday's ticket numberstoday, 9:00Succeeded

Email · Freshdesk daily summaryCreated: 42 · Resolved: 37 Open: Urgent 2, High 9, Medium 31, Low 14

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 Freshdesk 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_ticket_summary.pyexample

from datetime import date, timedelta
from clickruntime import on_trigger, credentials, http, notify

DOMAIN = "acme"

@on_trigger
def run(event):
    key = credentials.secret("FRESHDESK_API_KEY")
    def count(query):
        r = http.get(f"https://{DOMAIN}.freshdesk.com/api/v2/search/tickets",
                     params={"query": f'"{query}"'}, auth=(key, "X"))
        r.raise_for_status()
        return r.json()["total"]
    y = (date.today() - timedelta(days=1)).isoformat()
    created = count(f"created_at:'{y}'")
    resolved = count(f"status:4 AND updated_at:'{y}'")
    open_by = {name: count(f"status:2 AND priority:{p}")
               for p, name in ((4, "Urgent"), (3, "High"), (2, "Medium"), (1, "Low"))}
    notify.email_me(f"Freshdesk {y}: {created} created, {resolved} resolved",
                    f"Created: {created}\nResolved: {resolved}\nOpen: " +
                    ", ".join(f"{k} {v}" for k, v in open_by.items()))
    return {"created": created, "resolved": resolved, **open_by}

FAQ

Common questions

How does it define resolved yesterday?

It counts tickets whose status is Resolved and which were updated yesterday, which is the closest match Freshdesk's search provides. Tickets closed straight away without a Resolved step are counted by their closed status. Closed counts differ slightly from resolved. Choose the definition that matches your reports.

Can I split the counts by group or agent?

Yes. Add a group or agent filter, or ask for a table with a row per group. The same searches run for each, so a team lead can see their own numbers. A single table keeps it readable.

Will weekends show zeros?

Yes, if no tickets arrive. You can skip the email on weekends or send it on weekdays only. Many teams keep a Monday version that sums Saturday and Sunday to avoid an empty message. Weekday-only sending is common.

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 (daily). 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.

On a schedule