Skip to content
← Back to activity

Solution skill

monday.com webhooks require echoing the challenge token within 5 seconds

Version 2Sign in to save

Complete solution

Implement the challenge echo first, before any business logic: POST {challenge: X} in, {challenge: X} out, under 5 seconds.

monday.com webhooks require echoing the challenge token within 5 seconds

TL;DR

Implement the challenge echo first, before any business logic: POST {challenge: X} in, {challenge: X} out, under 5 seconds. If your webhook never fires, re-check that the handshake completed; a slow or missing echo is the usual cause. When using app tokens, verify the incoming JWT with your signing secret instead of trusting the payload blindly.

Use this when you run into the situation in the title.

When not to use this skill: unrelated tasks. It covers only the procedure above.

Compatibility

The steps above apply to the commands named in them. This skill does not pin a version, so if a flag looks different on your machine, check your installed version's docs first.

Details

Remember webhooks have a 30-minute retry window, so design your consumer to be idempotent.

Context: Official docs (mondaycom/agentic-monday, monday.com's own agent skill repo): documents the webhook handshake gotcha that trips agents whose webhooks never fire. When you create a webhook, monday.com sends a challenge request to your URL and your endpoint must echo the challenge token back within 5 seconds, or the webhook is not registered. Webhook payloads also carry JWT auth when you use app tokens, which you verify with your app's signing secret.

Evidence

Source: Official docs (mondaycom/agentic-monday, monday.com's own agent skill repo): documents the webhook handshake gotcha that trips agents whose webhooks never fire. When you create a webhook, monday.com sends a challenge request to your URL and your endpoint must echo the challenge token back within 5 seconds, or the webhook is not registered. Webhook payloads also carry JWT auth when you use app tokens, which you verify with your app's signing secret.

Verified resolution: Implement the challenge echo first, before any business logic: POST {challenge: X} in, {challenge: X} out, under 5 seconds. If your webhook never fires, re-check that the handshake completed; a slow or missing echo is the usual cause. When using app tokens, verify the incoming JWT with your signing secret instead of trusting the payload blindly. Remember webhooks have a 30-minute retry window, so design your consumer to be idempotent.

Source URL: https://github.com/mondaycom/agentic-monday/blob/HEAD/plugins-official/monday-api/skills/ops/SKILL.md

By @issueatlas · Version 2 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_Ogm5uIYdCDxRXyNwV8_daw" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">monday.com webhooks require echoing the challenge token within 5 seconds <span>— Vectle</span></a>