How to Update Existing monday.com Items with a Form
Published on August 05, 2026
The item already exists on your board. A client needs to update their address, a vendor needs to upload a renewed certificate, an employee needs to report progress on their task. You want to send them a form — and every form you build creates a new item instead of updating the one you have.
This is the single most persistent forms request in the monday.com ecosystem: the community thread asking for it has been open since 2019 with more than 165 replies . Here are the three real options, with the tradeoffs of each.
Quick answer
- monday.com WorkForms creates a new item on every submission; it has no general-purpose way for a respondent to edit an existing item.
- You can approximate updates with automation matching (fragile) or, on Enterprise, with the narrow edit-submission option.
- The direct path is a marketplace app with dedicated update forms: each item gets its own link, and submissions write back to that item.
Why WorkForms Cannot Do This
WorkForms is built as an intake channel: a form attached to a board where every submission becomes a new item . There is no field on the form that says “this submission belongs to item X,” so there is nothing for a respondent’s answers to write back to. That design is fine for lead capture and requests. It is the wrong shape for updates.
Option 1: Enterprise Edit Submission
monday.com’s edit-submission option lets the person who submitted a form go back and revise their own submission. The scope is narrow: it covers items created by that form, edited by the original submitter. It does not let you send someone a form for an item that already existed on your board, and third-party writeups describe further constraints on what can be edited — check monday.com’s current documentation for the exact behavior on your plan.
Fits when: respondents only ever need to correct their own recent submissions, and you are on Enterprise.
Option 2: Automation Matching
The classic workaround: keep using an insert form, then use automations or integration recipes to match each new submission to an existing item — usually by email address or name — copy the values across, and delete the duplicate.
It works until it does not. Matching breaks on typos, duplicate names, and missing fields; every submission consumes automation actions; and while the automation runs, your board briefly holds both the original and the duplicate. Teams running this at volume spend real time cleaning up mismatches.
Fits when: update volume is low, the matching key is reliable, and someone owns the cleanup.
Option 3: An App with Dedicated Update Forms
Marketplace form apps solve this at the root by making the item part of the link. With FormFlow’s update forms, every item on the board gets its own unique form URL. The form opens prefilled with that item’s current data, the respondent edits what they need, and the submission writes back to the same item — no matching, no duplicates.
The pieces that make it workable in production, all documented in the feature checklist:
- Per-item links, generated automatically by monday.com automations the moment an item is created
- Per-item passwords (stored in a column, also automation-generated), so each respondent can only open their own record
- Read-only fields to show context without allowing edits, and visibility rules to show only the fields that apply
- Prefill from the item’s existing data, so respondents see what is on file and change only what changed
FormFlow is not the only app in this category: SuperForm’s marketplace listing also advertises item and subitem updates. If you are evaluating, shortlist both and test your own workflow — the comparison points that matter are per-item security, prefill behavior, routing, and pricing model. Our FormFlow vs SuperForm comparison lines them up.
What About Jotform or Typeform?
External form builders push submissions into monday.com through connectors, and those connectors create things rather than edit them. Typeform’s integration actions are create-only, with several question types unsupported . Jotform’s own support threads document submission edits producing duplicate items in monday.com instead of updates. If updating existing items is the requirement, an external form tool does not meet it — details in our Jotform and Typeform breakdowns.
How to Choose
- Count your update volume. A handful per month: automation matching may be tolerable. Weekly or per-item: it will not be.
- Check who edits. Only the original submitter fixing their own submission points to Enterprise edit-submission; anyone else points to update forms.
- Check sensitivity. If each respondent must see only their own record, you need per-item links and passwords — that is update-form territory.
- Test before committing. Install a trial on a sandbox board, generate a per-item link, and run one real update end to end.
Frequently Asked Questions
Can monday.com forms update existing items natively?
No. WorkForms submissions create new items. The Enterprise edit-submission option only lets the original submitter revise items created by that form; it does not cover editing pre-existing board items.
How do update form links get created for every item?
With an automation: when an item is created, the automation generates that item’s unique form link (and optionally a per-item password) and stores them in columns. Nobody creates links by hand.
Is it safe to let external people edit board items through a form?
The respondent never sees the board. They see only the fields you put on the form, restricted by per-item passwords and read-only fields, and the submission writes to their item alone.
Next Steps
- Update forms documentation →
- 12 best practices for monday.com update forms →
- Install FormFlow and send yourself the first per-item link.
Last reviewed: 2026-08-03. WorkForms behavior verified against monday.com support documentation ; Typeform constraints per monday.com’s Typeform article ; Jotform behavior per their public support threads. Features and plans change; re-check before deciding.