How do I give each Notion form submission a unique ID?

Add Notion's ID property to the responses database and every form submission gets a unique, auto-numbered ID like REQ-42 that never changes.

Nookesh KarriNovember 18, 20265 min read
Light cover card with the title 'How do I give each Notion form submission a unique ID?' in dark text and a blue accent bar

To give each Notion form submission a unique ID, add Notion’s ID property to the database that stores the form’s responses. Notion numbers every row on its own, starting at 1, and adds a prefix you choose, so a response shows up as something like REQ-42. The number can’t be edited and never changes, which makes it a safe reference number.

Does a Notion form create a submission ID by itself?

A Notion form doesn’t add a submission ID out of the box. The forms help page says responses are stored in a table view named Responses, with each question as a database property. Nothing in that setup numbers the rows.

The database already has a hidden ID for every page. The formula reference lists id(), which “returns the id of the page.” That value is a long internal string, useless to read out over the phone.

How to add a unique ID to form responses

Adding a Notion form submission unique ID takes one property and about a minute. The unique ID guide covers the menu. For a form:

  1. Open the responses database that your form writes to.
  2. Click the + at the far right of the column headers and pick ID.
  3. Set the prefix. Notion fills one in from the teamspace and database names, and you can change it anytime. For a request form, REQ reads well.
  4. Submit a test response and check that the new row has the next number.

Existing rows get numbers too. Notion says “IDs are automatically created for each new and existing database item.”

How Notion numbers submissions

Notion’s ID numbers start at 1, go up by one per page, and can’t be changed by hand. The database properties guide puts it plainly: “IDs are unique and cannot be manually changed.”

Three rules shape what you see in a form database:

Rule What it means for your form
Numbers start at 1 Your first submission is REQ-1
Deleted pages keep their number Deleting test responses leaves gaps
Numbers never change Reordering or editing a row doesn’t renumber it

The unique ID guide says numbers “are assigned to every page, including deleted pages.” Send five test submissions, delete them, and your first real response won’t be number 1. If a clean start matters, test the form in a copy of the database first.

The prefix is the only editable part. Rename REQ to TICKET later and every row’s label changes, but the numbers stay put.

Look up a submission by its ID

A prefixed ID doubles as a short link to the response. The unique ID guide gives the example of a page with the ID TASK-123 opening at notion.so/TASK-123, and that only works when the ID has a prefix.

On a support or request form, someone emails “about REQ-42,” and you paste notion.so/REQ-42 into the browser instead of filtering a table. Notion doesn’t allow comments in unique ID properties, so keep notes in the page body.

Build a reference number with a formula

A formula can turn the ID into a reference number with more context, such as the date. The property object docs show that format(prop("ID")) returns the ID as text, like "TASK-1", so you can join it with other values.

Add a formula property called Reference to the responses database:

formatDate(prop("Created time"), "YYYYMMDD") + "-" + format(prop("ID"))

You’ll need a Created time property, which records when each row was created and can’t be edited. Each response then reads as the date (year, month, day), a dash, and REQ-42. If you only want the bare number, the formula reference shows prop("Task ID").split("-").last(), which returns the number as text.

My take: skip the date unless someone outside your team needs it. REQ-42 is easier to say and type, and Created time already sits on the row.

What a unique ID can’t do

The ID is assigned by Notion, so nothing outside Notion can choose it. The page property values reference says Notion assigns the number and “you cannot set it in a page write.” A form tool can read REQ-42 after the row exists, but it can’t pick the number for you.

The bigger limitation: a native Notion form doesn’t show the new ID to the respondent. The forms help page says nothing about displaying it, so the person who submitted leaves with no reference number unless something sends it to them.

Public forms add one more wrinkle. Forms shared with anyone on the web are automatically anonymous, so the ID is often the only handle you have on a response. Collect an email question if you’ll need to reply.

Using IDs with nDBForms

nDBForms writes each submission as a new row in your Notion database, so the ID property numbers those rows exactly like native responses. It also sends you an email for every new submission, and the row it points to carries its ID.

To send the ID back to the respondent, you need a follow-up step, covered in the confirmation email guide and the automation guide. For forms where a reference number matters most, see the IT support ticket template and the notes on anonymous Notion forms.

FAQ

Does a Notion form give submissions an ID automatically?

Not by default. Responses land as rows in the database, and you add the ID property yourself. Once it’s there, every new and existing row gets a number.

Can I change or reset a Notion unique ID?

No. Notion says the numbers can’t be changed by hand, always start at 1 and never change. You can only edit the prefix.

Why are there gaps in my submission numbers?

Notion assigns numbers to every page, including deleted ones. Delete a few test submissions and their numbers are simply skipped.

Can I open a submission from its ID?

Yes, if the ID has a prefix. A row with the ID REQ-42 opens at notion.so/REQ-42.

Can the API or a form tool set the ID number?

No. Notion assigns the number, and the API doesn’t let a page write set it. Tools can only read the ID after the row exists.

Sources