The moment it happens

Turn app errors into Asana tasks

Each new error becomes a task with a likely cause and a suggested fix, and repeats of the same error are skipped.

Runs: The moment it happens
Apps: Asana
AI: Yes, uses the built-in AI allowance
Access: read+write

Send this to your assistant

Create a ClickRuntime automation: give me a link my apps can send errors to. For each new error, explain the likely cause and fix, and create a task in my Bugs project in Asana. Skip errors that already have a task.

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

When a production error fires, the first fifteen minutes often go to the same routine: someone copies the stack trace into a chat, a colleague asks whether it has happened before, and a third person opens Asana to create a ticket. Duplicate reports arrive from every monitoring tool, so one flaky endpoint produces forty tickets in an hour. Real incidents are hard to pick out from noise, and tickets contain only a pasted blob.

Point your error reporter, log alert or app at your ClickRuntime link. For each report, ClickRuntime checks whether the same error has been seen before and skips duplicates. For new ones, the built-in AI analyzes the message and trace, proposes a likely cause and a suggested fix, and ClickRuntime creates an Asana task containing all three.

Small engineering teams without a dedicated on-call tooling stack use it as a simple triage layer.

What you get out of it

Duplicates no longer flood the board
A noisy error that repeats forty times produces one task. Engineers see a clean list of distinct problems, so real incidents stand out from repeated noise. Real incidents stay visible.
Tickets start with a hypothesis
Instead of a raw trace, the task opens with a likely cause and a suggested fix. The engineer who picks it up begins by checking an idea, which can cut the first hour of diagnosis.
Nothing is lost between tools
Errors from a mobile app, a backend and a cron job all end up in the same Asana project. You do not need to watch three dashboards to know what is broken.
Junior developers get guidance
A plain-language explanation of what a stack trace means helps less experienced team members take on bugs confidently, without waiting for a senior engineer to translate. Fewer people wait on senior help.
Bug history becomes searchable
Every error is a dated task with its analysis. When something returns, a quick Asana search shows when it first appeared and what was tried last time. You avoid repeating old fixes.

How it works

What happens, step by step

When your app or error tracker reports an error to ClickRuntime, the automation starts straight away.
It skips errors it has already turned into tasks, so one bug does not create a pile of duplicates.
AI reads the error and writes a likely cause and a suggested fix.
A task is created in your Asana Bugs project with the error and the AI's analysis.

Before it runs live

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

What you get

RunsThe moment it happens

Turn app errors into Asana tasksjust nowSucceeded

Asana · Bugs[billing-api] KeyError: 'currency' Likely cause: Acme invoices created before the currency field existed. Fix: default to account currency.

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
Change what the AI looks for, or how it writes the result
Add another app, for example also send it to Slack
Combine it with other Asana 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.

turn_error_reports_into_tasks_with_ai_analysis.pyexample

import hashlib
from clickruntime import on_event, http, credentials, ai, state

BUGS_PROJECT = "BUGS_PROJECT_GID"

def asana(method, path, body=None, **params):
    r = http.request(method, f"https://app.asana.com/api/1.0{path}", params=params,
                     json={"data": body} if body else None,
                     headers={"Authorization": f"Bearer {credentials.secret('ASANA_TOKEN')}"})
    r.raise_for_status()
    return r.json().get("data")

@on_event
def handle(event):
    err = event.json or {}
    message = str(err.get("message", ""))[:500]
    key = hashlib.sha1(f"{err.get('service')}:{message}".encode()).hexdigest()
    if state.get(f"err:{key}"):
        return {"created": False, "reason": "already has a task"}
    analysis = ai.generate(
        f"Service: {err.get('service')}\nError: {message}\nStack:\n{str(err.get('stack', ''))[:2000]}",
        system="Explain the likely cause and a fix in under 120 words.", max_output_tokens=250).text
    task = asana("POST", "/tasks", {"name": f"[{err.get('service')}] {message[:120]}",
                                    "notes": analysis, "projects": [BUGS_PROJECT]})
    state.set(f"err:{key}", task["gid"])
    return {"task": task["permalink_url"]}

FAQ

Common questions

How does it decide an error is a duplicate?

It builds a fingerprint from details such as the error message and the top lines of the stack trace, and keeps those fingerprints in memory. A report with a known fingerprint is skipped, while one with a new fingerprint creates a task.

Is the AI's suggested fix reliable?

Treat it as a starting point, not a verdict. The analysis reads only the error text you send, not your codebase, so it can point toward likely causes but cannot confirm them. The task still needs an engineer's judgment before any change is made.

Which tools can send reports to the link?

Anything that can make an HTTP request: Sentry-style alerts, a logging service webhook, a try/catch in your own code or a scheduled script. As long as the report carries an error message, ClickRuntime can read it and create the task.

What permissions does it need?

read+write. Nothing else in your accounts is used.

Does it need AI?

Yes. It uses ClickRuntime's built-in AI, so you don't need an OpenAI or Anthropic key. Every plan includes a monthly 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.

The moment it happensAI