React to New monday.com Items with Acknowledgement and Slack Summary

People file requests where they work, and increasingly that is a monday.com board. This blueprint uses io.kestra.plugin.monday.items.Trigger to poll a requests board every minute and start an execution the moment new items appear. The flow acknowledges the newest request with an update posted straight onto the item, then summarizes the batch in Slack with the item id and name, so requests entered in the work OS start real automation instead of waiting for someone to notice them.

How it works

1. The new_items trigger (io.kestra.plugin.monday.items.Trigger) polls the board on a PT1M interval and fires when items changed since the previous evaluation. It exposes {{ trigger.count }} and {{ trigger.items }}, where each element carries the item id, name, updated_at, its group, and its column_values.
2. acknowledge_request (io.kestra.plugin.monday.updates.Create) posts an update on the newest item, {{ trigger.items[0].id }}, so the requester gets feedback inside monday.com within a minute of filing.
3. notify posts the count and the newest item's name and id to Slack.
4. The errors block posts a distinct Slack alert when the reaction fails, so requests never sit unacknowledged in silence.
5. The trigger ships disabled: true; point boardId at your board before enabling it.

What you get

• Executions that start from human activity in monday.com, with no webhook setup on the monday.com side.
• An acknowledgement update on the item itself, visible exactly where the request was filed.
• A Slack summary carrying scalar trigger outputs, count plus the newest item's id and name.
• A failure alert so a broken token or board id never hides incoming requests.

Who it's for

• Ops, IT, and HR teams running intake boards where colleagues file requests.
• Platform teams who want board entries to kick off provisioning or data flows.
• Anyone replacing a manual watch-the-board rota with automation.

Why orchestrate this with Kestra

monday.com automations stop at the platform boundary. Kestra's trigger turns a board into an event source for anything the rest of your stack needs to do, with retries on transient API errors, an execution history of every reaction, and downstream tasks limited only by the plugin catalog.

Prerequisites

• A monday.com board receiving new items, and its board id for the trigger.
• A Slack incoming webhook for summaries and failure alerts.

Secrets

• MONDAY_API_TOKEN: monday.com personal API v2 token, from Profile, Developers, My Access Tokens.
• SLACK_WEBHOOK_URL: Slack incoming webhook URL.

Quick start

1. Add the two secrets to your Kestra namespace.
2. Set boardId on the new_items trigger to your requests board and set disabled: false.
3. Add an item to the board and watch the acknowledgement update plus the Slack summary appear within a minute.

How to extend

• Process every item in the batch, not just the newest, by iterating {{ trigger.items }} with io.kestra.plugin.core.flow.ForEach.
• Narrow polling to one group by setting the trigger's groupId property.
• Route requests by a column value with io.kestra.plugin.core.flow.If, since each trigger item includes its column_values.
• Move acknowledged items to an in-progress group with io.kestra.plugin.monday.items.Move.

Links

• monday.com plugin documentation
• monday.com API reference