Monday.com webhooks
Last verified against Monday.com's documentation on September 27, 2026.
Monday.com sends webhooks when something changes on a board: an item is created, a column value changes, an update is posted. Before it sends anything, the URL has to pass a challenge. After that, Monday.com retries a failed delivery once a minute for 30 minutes, then drops the event for good, with no log to recover it from. Payloads are minimal, and the only authentication is a JWT that exists only for webhooks created by an app. This page covers what Monday.com sends, how it delivers, how to fix the common errors, and where HookDeploy fits.
What Monday.com sends webhooks for
| Event | Typical use |
|---|---|
create_item, item_deleted, item_archived | Sync items to another system |
change_column_value, change_status_column_value, change_specific_column_value | React to status and field changes |
create_update | Pick up comments |
create_subitem, change_subitem_column_value | Track subitems |
move_item_to_group | Follow items through a workflow |
Each webhook covers one event type on one board. Every delivery is a JSON POST with an event object that includes the type, boardId, pulseId, the changed value and previousValue where relevant, and a triggerUuid. For anything else about the item, query Monday.com’s API.
How Monday.com delivers webhooks
| Behavior | Detail |
|---|---|
| Challenge | On creation, a POST with {"challenge": "..."}. The URL must return the same JSON |
| Method and format | POST with a JSON body |
| Authentication | A JWT in the Authorization header, signed with your app’s signing secret, but only for webhooks created with an integration app token |
| Success | 200 |
| Retries | Once a minute for 30 minutes |
| After retries | The event is dropped. There’s no delivery log or replay |
| Scope | One event type on one board per webhook |
| URL length | At most 255 characters |
Common Monday.com webhook errors and how to fix them
Webhook creation fails
Monday.com’s challenge wasn’t answered. The URL has to return exactly the JSON it received, {"challenge": "..."}, with a 200.
Events lost after an outage
Retries stop after 30 minutes and Monday.com keeps no record, so anything during a longer outage is gone. Reconcile from Monday.com’s API after an outage.
No way to tell if a request is real
Webhooks created with a personal API token or the board’s Integrations Center have no signature at all. Only webhooks created with an integration app token carry the JWT. Protect the URL another way, such as a token in the URL.
Payload is missing fields
The payload carries the change and the IDs, not the whole item. Query the item from Monday.com’s API.
Retry bursts
During an outage, retries arrive every minute alongside new events. Respond with 200 first and process from a queue.
Why use HookDeploy with Monday.com
Stop losing events after 30 minutes
HookDeploy captures every Monday.com webhook at Cloudflare’s edge and responds right away, before forwarding it to your server. Monday.com gets its 200 right away, so its 30-minute retry window stops mattering, and every event is kept.
- Destination retries. Starter retries 3 times (after 30 seconds, 5 minutes, and 30 minutes). Pro and Scale retry up to 5 times on a schedule you choose. Free doesn’t retry automatically.
- Incidents. Forward failures are grouped into incidents, and you can bulk-replay them once your server recovers.
- History. HookDeploy keeps captured webhooks for your plan’s retention period, from 7 days on Free to 365 days on Enterprise.
Pass the challenge without code
Turn on the Monday.com handshake preset on the endpoint’s Security tab, under Verification (Starter and above). HookDeploy answers the challenge and doesn’t capture or forward it, so you can create the webhook before your handler exists.
One webhook, many systems
Send each Monday.com event to your app, a reporting database, and a team channel in parallel. A failing destination doesn’t hold up the others. Free includes 1 destination per endpoint, Starter includes 5, and Pro and above are unlimited.
Deliver to systems Monday.com can’t reach
The HookDeploy Agent connects outward from your network over mTLS and delivers events to a local port, so an internal tool or database in a private network can receive Monday.com events with no public endpoint.
Develop against real events
A tap sends a temporary copy of live Monday.com events to 127.0.0.1 on your machine while production keeps receiving them.
Know the limits
- The JWT and retries. HookDeploy redacts the
Authorizationheader from stored requests, so retries and replays don’t carry Monday.com’s JWT. See below. - Plan limits. On Free, requests beyond the monthly allowance or the daily limit get a
429, which Monday.com treats as a failed delivery. Paid plans keep accepting traffic past the included volume.
Authentication through HookDeploy
There are two connections to secure. Monday.com to HookDeploy: add HookDeploy’s endpoint token to the webhook URL as ?token= (Starter and above). The handshake preset runs after the token check, so the challenge needs the token too, and HookDeploy removes the token before forwarding.
HookDeploy to your handler: if your webhooks carry Monday.com’s JWT, the first forward includes it, but HookDeploy redacts the Authorization header from stored requests, so retries and replays don’t. Inject your own header on the destination and check that instead. HookDeploy adds it to every forward, every retry, incident replays, and manual replays you send to that destination.
Deduplicate on the event’s triggerUuid.
Set up Monday.com with HookDeploy
- In HookDeploy, create an endpoint (for example,
Monday.com board events) and copy its URL. - On the endpoint’s Security tab, under Token, generate an endpoint token. Then under Verification, choose Monday.com and save (Starter and above).
- On the Forwarding tab, add a destination pointing to your handler, or to an agent for private delivery. Add a header
Authorization: Bearer YOUR_HANDLER_SECRET, and set the destination’s retries. - Create the webhook in Monday.com, from the board’s Integrations Center or with the
create_webhookmutation, using your HookDeploy URL with?token=YOUR_ENDPOINT_TOKENadded. - Change an item on the board, and confirm the event appears in HookDeploy and reaches your handler.
Example handler (Node.js and Express)
import crypto from 'node:crypto';
import express from 'express';
const app = express();
const expectedAuth = Buffer.from(`Bearer ${process.env.HANDLER_SECRET}`);
app.post('/webhooks/monday', express.json(), async (req, res) => {
// HookDeploy answers the challenge, so only real events reach this handler.
// Check the header HookDeploy injects on every forward, retry, and destination replay.
const received = Buffer.from(req.get('authorization') ?? '');
const valid =
received.length === expectedAuth.length &&
crypto.timingSafeEqual(received, expectedAuth);
if (!valid) return res.status(401).send('Unauthorized');
res.sendStatus(200);
const { event } = req.body;
await enqueue({ id: event.triggerUuid, type: event.type, boardId: event.boardId, itemId: event.pulseId });
// Deduplicate on id, then query the item from Monday.com's API if you need more.
});
FAQ
How do I pass the Monday.com webhook challenge?
Monday.com posts a JSON body with a challenge field when you create a webhook, and your URL must respond with a 200 and the same JSON. With HookDeploy, turn on the Monday.com handshake preset and HookDeploy answers it for you.
Are Monday.com webhooks signed?
Only webhooks created with an integration app token include a JWT in the Authorization header, signed with your app's signing secret. Webhooks created with a personal API token or from the board's Integrations Center aren't signed.
How long does Monday.com retry a webhook?
Once a minute for 30 minutes. After that, the event is dropped, and Monday.com keeps no log you can replay from.
Why doesn't the Monday.com payload include the whole item?
Payloads describe the change and include IDs, not the full item. Query the item from Monday.com's API when you need more fields.
Can one Monday.com webhook cover several boards?
No. Each webhook covers one event type on one board. Point several webhooks at the same HookDeploy endpoint to collect them in one place.
Why do HookDeploy retries fail my Monday.com JWT check?
HookDeploy redacts the Authorization header from stored requests, and retries and replays are sent from the stored copy, so the JWT isn't on them. Authenticate HookDeploy's deliveries with a header you inject on the destination instead.