monday.com triggers start a run from what happens on a board. All three are instant — monday.com tells Bizomate the moment it happens:

  • monday.com · New item — When an item is created on a board.
  • monday.com · Column value changed — When a column's value changes on an item.
  • monday.com · New update — When someone posts an update on an item.

Publishing adds a webhook to the board for you, and nothing needs pasting — see How instant triggers work.

Who can do this

Workspace Admins and Editors, on every plan. Viewers see the trigger and its status but cannot change it.

Before you start

A monday.com connection — see Connect monday.com — whose account can see the board.

Steps

  1. Open the workflow in the designer and open the trigger picker — Browse all triggers on an empty workflow, or select the trigger and Change how it starts.
  2. Under monday.com, select the event. It reads monday.com · instant. Or type monday in Search triggers.
  3. In Connection, choose your monday.com connection.
  4. In Board, choose the board — Boards the token can see. For example Client onboarding.
  5. For Column value changed:
    • Optional: in Column, the column — Empty: any column. For example Status.
    • Optional: in Changed to, the new value — Only when the new value is this — a status by its label. Empty: any value. For example Done.
  6. The panel reads Publishing sets this up in monday.com, and every publish sets it up again. It stays while the workflow is published — switched off, what arrives is ignored — and is taken away when the workflow is deleted or starts another way.
  7. Add the steps, then Publish. Bizomate adds a webhook to the board. The panel reads Waiting for the first event — Make one happen; it appears here within seconds.

Test with a real event:

  1. Make the event happen on the board — add an item, or set Status to Done.
  2. Within seconds the panel reads Listening — instant — Last event 10:45 · Column value changed · Onboard Northwind Logistics · Status: Working on it → Done.
  3. On Output, select Use the last event, then Test run.

What the trigger gives

The item, read back from monday.com as the monday.com steps read it — id, name, url, boardId, boardName, groupId, groupName, createdAt, and each column by its title — and user, the name of whoever did it (empty for a monday.com automation). Also:

  • Column value changed: column (its title, Status), previousValue (Working on it) and value (Done, as the board shows it now).
  • New update: updateId and text — Northwind sent the signed contract.

What happens next

  • Each event starts one run of the live version, in Production, named after it — New item · Onboard Northwind Logistics, Column value changed · Onboard Northwind Logistics · Status: Working on it → Done, New update · Onboard Northwind Logistics.
  • Each workflow has its own webhook on the board. You can see it in monday.com under the board's Integrate menu. Every publish sets it up again; changing to another trigger, board or column and publishing, or deleting the workflow, removes it.
  • When the webhook is made, monday.com first sends a challenge to Bizomate's address, which Bizomate answers. It starts nothing.

How Bizomate knows an event is monday.com's

monday.com does not sign the events a token's webhook sends. The address itself is the secret: its last part is a random code known only to monday.com and Bizomate. Bizomate also checks that each event is for the trigger's own board. Anything else is answered 401 — The signature does not match. — and starts nothing.

Good to know

  • Column value changed with a Column hears only that column — monday.com sends nothing else. Empty, it hears every column, and Changed to applies to whichever changed.
  • Moving an item to another group is not a column change and does not start Column value changed.
  • Items added by a workflow on the same board start New item too — take care that a workflow does not start itself again and again.
  • An item deleted before Bizomate reads it still starts its run, with its name and group from monday.com's event.

If something goes wrong

What you see Why What to do
Not listening — monday.com would not take Bizomate's address: Choose the board the trigger listens to. Fix it, then publish again. No board is chosen. Choose the board, then publish again.
Not listening — monday.com would not take Bizomate's address: monday.com refused it: … Fix it, then publish again. Your account cannot add a webhook to the board, or the column is gone. Ask for access to the board, or choose the column again, then publish again.
Not listening — … monday.com refused: … Check the connection's details on Connections. … The token was regenerated. Select Reconnect, paste the new token, then publish again.
Waiting for the first event stays Nothing has happened yet, or the column changed to another value than Changed to. Make the event happen.
Nothing has arrived yet — make one happen in monday.com, then try again. on Output No event has reached the trigger yet. Make one happen, wait for Listening — instant, then Use the last event.
A run did not start for an event the panel shows The workflow is switched off, or its workspace is archived. Switch it on — see Switch a workflow on or off. The missed event does not run later.