Home / Integrations / monday.com via Zapier

monday.com via Zapier — Create Item from each feedback item

This works via Zapier (or the webhook destination), not natively. Not a monday.com app, and not a published Zapier template.

What it does

Zap recipe, not a monday.com app. A matching feedback item is POSTed as one JSON body to the webhook URL you paste. Point that URL at a Zapier Catch Hook, then add a monday.com Create Item action. There is no monday.com app, no monday.com OAuth, and no published Zapier template.
Same sink as Make or n8n. The webhook destination accepts any HTTPS URL. Zapier is one way to turn that POST into a item. Setup for the sink itself is on Zapier Catch Hook.
One-way. Creating the item does not update the feedback item, and FDT does not read monday.com.

Zap recipe

In Zapier, add a Webhooks by Zapier Catch Hook trigger and copy the hook URL.
In the FDT project dashboard: Project → Settings → Destinations → Add → Webhook, paste that URL, and set the project signing secret in the same Destinations panel (shown once — it is not part of the URL).
Submit one feedback item so Zapier samples the JSON. The header is x-fd-signature. A Catch Hook stores the body; it does not verify the signature for you.
Add monday.com → Create Item. Board and Group: pick them in the Zap. FDT does not send a monday.com board id or group id.

Create Item field	FDT payload key
Item Name	`whatToChange` — there is no top-level title key
Long Text column	`expectedBehavior`, then the other keys below as plain text
Page URL (inside Long Text column)	`pageContext.url` — not a top-level url or page key
Screenshot (inside Long Text column)	`screenshotUrl` — may be null. Not a screenshot key
Board and Group	Not in the payload. FDT does not send a monday.com board id or group id.

Payload keys FDT sends

Top-level keys of the JSON body, in the order the webhook sink writes them. Map only these. Do not invent fields.

event
title
itemUrl
sourceFile
prUrl
id
projectId
projectName
projectSlug
changeType
whatToChange
expectedBehavior
priority
status
pageContext
screenshotUrl
consoleLogs
networkLogs
classification
createdAt

pageContext is an object. Use pageContext.url (page URL (query and fragment already stripped)); pageContext.title (document title, only when the widget sent one). Other pageContext keys are passed through only when the widget sent them.

classification is null, or an object with intentsentimenturgencyScoresummaryconfidence. createdAt is an ISO-8601 string. consoleLogs and networkLogs are the raw captured values or null, not a summary string.

Not in this body: urlpagescreenshotcomponent. File and line arrive as sourceFile when the SDK mapped the element.

Honest limits

This is via Zapier, not natively. Not a monday.com app.
No published Zapier template. You build the Zap from the recipe above.
No two-way sync. Closing or moving the item in monday.com does not update the feedback item.
FDT does not send a monday.com board id or group id.
HMAC verification is the caller's job. Same sink as Make or n8n.

Native options: GitHub and Linear. Catch Hook setup: Zapier Catch Hook.

Other board recipes, also via Zapier: Trello, Asana, Teamwork, Azure DevOps, Basecamp.