The moment it happens

Log app errors as monday.com items

Errors from your systems land on a board as items with the message, source and time, ready to assign.

Runs: The moment it happens
Apps: monday.com
AI: Not needed
Access: read+write

Send this to your assistant

Create a ClickRuntime automation: give me a link my apps can send errors to, and add each one as an item on my monday.com Errors board with the message, the app it came from and the time.

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

Errors from a small product usually live in three places: a cron job that emails a stack trace, a payment webhook that returned 500, and a Slack channel nobody scrolls. Each one gets noticed by whoever happens to see it, and nobody records who is fixing it. A failed invoice sync found on Tuesday is still unassigned on Friday, and the same error is reported by three people because there is no shared list.

When one of your systems posts an error to the link ClickRuntime provides, it creates an item on a monday.com board right away. The item carries the error message, the source system and the time it happened, so a person can be assigned, a status set, and the item discussed in updates like any other piece of work.

Teams often point several services at one link, so a single board becomes the log of everything that went wrong.

What you get out of it

Every failure has an owner and a status
An error turned into a board item can be assigned, moved to In progress and closed. The Friday question of whether anyone looked at that sync failure has an answer you can read on the board.
Duplicate reports stop circulating
When all errors land in one list, a teammate searching the board sees the item already exists. The three people who each noticed the failing webhook add a comment instead of three separate messages.
Patterns appear in the data
Source and time columns let you group by system or hour. You notice that most errors come from the nightly import at 02:00, which points to a fix far more cheaply than dealing with each error individually.
Small teams get an incident trail
Without a paid incident tool, you still end up with a dated record of what broke and how it was resolved. That record is useful in customer conversations and when reviewing reliability at quarter end.
Nothing relies on someone being in the channel
A message in chat disappears under newer ones, while a board item stays until it is closed. Errors that arrive while the engineer is on holiday are still there when they return.

How it works

What happens, step by step

When your app sends an error to the automation's private link, it starts.
It picks out the error message, which app it came from and the time it happened.
A new item is created on your monday.com errors board with those details, so every error is logged in one place.

Before it runs live

Connect monday.com
Paste your automation's link into the other app's webhook settings

What you get

RunsThe moment it happens

Log app errors as monday.com itemsjust nowSucceeded

monday.com · ErrorsTimeoutError: payment gateway did not respond · App: checkout-api · 2026-10-19 14:02

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

log_errors_to_a_board.pyexample

import json
from clickruntime import on_event, http, credentials

BOARD_ID = 1234567890  # your Errors board
MUTATION = """mutation ($board: ID!, $name: String!, $cols: JSON) {
  create_item(board_id: $board, item_name: $name, column_values: $cols) { id }
}"""

@on_event
def handle(event):
    err = event.json or {}
    message = str(err.get("message", "Unknown error"))[:250]
    columns = {"text": err.get("app", "unknown"), "date4": {"date": event.received_at[:10], "time": event.received_at[11:19]}}
    resp = http.post("https://api.monday.com/v2", headers={"Authorization": credentials.secret("MONDAY_API_TOKEN"), "API-Version": "2024-10"},
                     json={"query": MUTATION, "variables": {"board": BOARD_ID, "name": message, "cols": json.dumps(columns)}})
    resp.raise_for_status()
    return {"item": resp.json()["data"]["create_item"]["id"]}

FAQ

Common questions

What can send errors to the link?

Any code or service that can make an HTTP request with JSON, such as a try/catch handler in your app, a serverless function, a CI job or a monitoring tool with a webhook option. Send the message, source and time as fields.

Will a repeating error create hundreds of items?

Each post makes an item, so a loop of failures could create many. You can ask for a duplicate check on the message and source, so repeats within a set window are skipped or added as an update to the existing item.

Can I choose the board group or priority?

Yes. The create step can place items in a group like Production and set a priority column from the payload, for example marking anything with a severity of critical as High. Tell your AI assistant which field decides it.

What permissions does it need?

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

The moment it happens