The moment it happens

Turn alerts from other tools into tickets

Anything posted to your link becomes a Freshdesk ticket with a subject and description.

Runs: The moment it happens
Apps: Freshdesk
AI: Not needed
Access: write

Send this to your assistant

Create a ClickRuntime automation: give me a link; whenever our uptime monitor posts to it, create a Freshdesk ticket from ops@acme.com with the alert title as subject and the details as the description.

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

Monitoring tools, payment providers, forms and internal scripts all raise problems that someone needs to handle, but each one reports them in a different place: an email, a Slack message, a dashboard. Support teams that live in Freshdesk end up copying details from those alerts into tickets by hand, or worse, the alert is seen by one person and forgotten. An error that should have been a ticket never gets an owner, a due date or a record.

When another tool sends a webhook, ClickRuntime parses the payload and creates a Freshdesk ticket with the requester's email, a subject and a description built from the data it received. The ticket appears in your queue immediately, assigned and tracked like any other.

It is useful for teams that want a single queue for work coming from many systems.

What you get out of it

Give every alert an owner
A ticket has an assignee, a status and a due date. A failed payment alert becomes a task that cannot be quietly forgotten in a chat scroll. Accountability follows automatically.
Work from one queue
Agents handle problems from many tools in Freshdesk instead of watching several inboxes. Prioritizing is simpler when everything is in one list. Triage is faster and nothing is missed. Fewer tools to watch.
Keep a record for later review
Tickets stay in Freshdesk with their history. When a similar error happens again, you can search for how it was handled last time. Past solutions save time on repeat incidents and are easy to find.
Remove copy-and-paste work
Creating tickets by hand from alert text is slow and error-prone. Automated creation passes the exact details, such as order numbers and error messages, without typos. Accuracy matters when an order number decides the fix.
Connect any tool that can send a webhook
Many apps can call a webhook but none have a Freshdesk integration. One flow covers monitoring, forms and scripts without custom code in each. New tools can be added later in the same way.

How it works

What happens, step by step

When another tool, such as an uptime monitor, sends an alert to your ClickRuntime link, the automation runs straight away.
It takes the alert's title as the ticket subject and its details or message as the description.
It creates an open, high-priority Freshdesk ticket from ops@acme.com, ready for your team to pick up.

Before it runs live

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

What you get

RunsThe moment it happens

Turn alerts from other tools into ticketsjust nowSucceeded

Freshdesk · New ticket#5840 "api.acme.com is down (HTTP 503)" from ops@acme.com · High

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

create_ticket_from_webhook.pyexample

from clickruntime import on_event, credentials, http

DOMAIN = "acme"

@on_event
def handle(event):
    alert = event.json
    key = credentials.secret("FRESHDESK_API_KEY")
    resp = http.post(f"https://{DOMAIN}.freshdesk.com/api/v2/tickets", auth=(key, "X"), json={
        "email": "ops@acme.com",
        "subject": alert.get("title", "Uptime alert"),
        "description": alert.get("details") or alert.get("message", ""),
        "status": 2,
        "priority": 3,
    })
    resp.raise_for_status()
    return {"ticket_id": resp.json()["id"]}

FAQ

Common questions

What does the webhook need to contain?

At minimum a requester email, a subject and a description. Other fields, such as priority, tags or group, can be set from the payload or fixed in the flow, and missing optional data is filled with defaults.

Will it create duplicate tickets for repeated alerts?

It can, if the same alert fires repeatedly. To avoid it, the flow can check for an open ticket with the same subject first, or use an identifier from the payload to add a note instead.

Which Freshdesk plan do I need?

Creating tickets through the API is available on Freshdesk plans that include API access. You supply an API key from your agent profile, which is stored as a secret and used only to create tickets.

What permissions does it need?

write. 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 for each event the app sends.

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