All docs

Editing

Modify a submission's payload or status after it lands.

Updated . 4 min read.

Most submissions you'll never touch - they came in clean, you saw them, you moved on. But sometimes you need to change one. A typo in an email address, a mis-categorised support ticket, a status flip from received to processed after you've handled it.

Submissions are editable. Sparingly.

Why you'd edit

Three legitimate reasons:

  • Correcting typos. A visitor typed florain@example.com instead of florian@. You want the autoresponder retry to land in the right inbox.
  • Flagging status. You've replied to a support submission. Flip its status to processed so the next teammate doesn't double-handle it.
  • Sanitising sensitive data. Someone pasted a full credit-card number into a message field. You want it scrubbed from your backend before backups roll.

Reasons not to edit:

  • Building a workflow on top. Status fields aren't a kanban - use a webhook into your real ticketing system.
  • Faking submissions. Edit doesn't create new rows; for that, just POST to the endpoint.
  • Routinely "cleaning up" payloads. If you're doing this often, the form schema is probably wrong. Fix the form, not the rows.

What you can edit

Payload

Every key in the submission's payload is editable. From the inbox detail panel, click the pencil icon next to any value, type the new value, save. Validation runs against the form's current schema - if you try to set email to not-an-email, we 422 and reject the change.

For complex types:

  • Array fields (multi-checkbox values) - comma-separate in the input.
  • File fields - you can detach a file (removes the bytes too, irreversibly). A respondent who reopens their own response can replace a file by uploading a new one; see Saved drafts and edits.

Status

The status pill is editable too. Allowed transitions:

From To Effect
received processed Flag handled. No side-effects.
received spam Same as Mark as spam. Moves to spam folder.
spam received Same as Mark not spam. Re-fires notifications, autoresponder, webhooks.
failed received Re-process - re-runs notifications and webhooks.

We don't allow setting failed manually. That's a system-only state.

Metadata

Read-only. You can't rewrite the IP, user agent, AI moderation score, or submitted_at timestamp. If those were wrong at submission time, they stay wrong - those fields exist for forensics, not narrative.

How to edit

From the dashboard

Open the submission's detail panel, click the pencil icon next to a value, type, save. Each edit is a separate write - there's no batch "edit several values then commit" flow in the UI.

From the REST API

text
PUT /api/v1/forms/{form}/submissions/{submission}
Content-Type: application/json
Authorization: Bearer ...

{
  "payload": { "email": "florian@example.com" },
  "expected_revision": 3,
  "status": "processed"
}

All three are optional. payload replaces the answers, so send the full set. expected_revision is the revision you read; if someone saved first, you get 409 with error: "revision_conflict" and the latest answers instead of overwriting them. Leave it out to edit whatever is current.

From MCP

text
update_submission(
  submission_id="01K2M...",
  payload={ "email": "florian@example.com" },
  expected_revision=3
)

Requires submissions:write. Use get_submission first to read the current revision.

Audit trail

Every payload edit is kept as an immutable revision. Nothing is overwritten, and each revision records who made it (the respondent through an edit link, or a named team member), where it came from and which fields changed. The original submission is always revision 1.

  • In the dashboard, open a submission to see its history, newest first.
  • Over the API, GET /api/v1/forms/{form}/submissions/{submission}/revisions returns every revision with its answers.
  • Over MCP, call get_submission with include_revisions.

Staff edits also appear in your workspace audit log. Status, assignee and due-date changes are not answer edits and do not create revisions.

What's next