Unique ID Chip
Unique ID Chip
Section titled “Unique ID Chip”Unique ID Chip
Section titled “Unique ID Chip”Display Notion Unique ID values (for example RST1) as a compact monospace Unique ID Chip on Details instead of plain body text.
What you get
Section titled “What you get”| Capability | Maker setup | End-user result |
|---|---|---|
| Chip display | Add Unique ID Chip, bind unique_id field | Monospace chip (for example RST1) |
| Prefix + number | Uses Notion’s unique ID format | Matches what Notion shows on the page |
| Placement | Details (or view layout) | Often near the title / header area |
Before you start
Section titled “Before you start”- A Notion database with a Unique ID property enabled
- At least one page that already has an ID assigned
- A Details screen and Reload Data if the property is new
Step 1 — Add Unique ID Chip
Section titled “Step 1 — Add Unique ID Chip”- Open the Details screen.
- Add component → Unique ID Chip.
- Bind it to the Unique ID property (for example Ticket ID).
- Set a label if you want “Ticket ID” above the chip.
Step 2 — Preview and publish
Section titled “Step 2 — Preview and publish”- Select a record and confirm the chip shows the expected ID (prefix + number).
- Compare with the same page in Notion.
- Publish and verify on the live app.
Checklist
Section titled “Checklist”- Unique ID property exists in Notion
- Unique ID Chip bound correctly
- Sample IDs match Notion (for example
RST1) - Published Details shows the chip
Troubleshooting
Section titled “Troubleshooting”| Symptom | Likely cause | Fix |
|---|---|---|
| Empty chip | Page created before Unique ID was enabled | Open/edit in Notion so an ID is assigned; Reload Data |
| Wrong format | Looking at a different property | Bind the Unique ID field, not a text “code” field |
| Still plain text | Old Details/Heading mapping | Replace with Unique ID Chip component |
Related reading
Section titled “Related reading”Builder options at a glance
Section titled “Builder options at a glance”This guide teaches a focused maker workflow. For the full screen option inventory (What it does / How to use / Why) and annotated builder screenshots, use the matching Types of Screens guide:
- Data screens: List (View Items), Details, Form (Add Item), Form (Update One Item), List (Update Items), Content
- Everyday chrome / Queue & activity: see the Types of Screens index
- Automation native screens: Native Automation Screens
Recommended defaults
Section titled “Recommended defaults”- Change one option family at a time, then publish and test on phone and desktop.
- Prefer screen-level settings in Content / Behaviour / Appearance before custom CSS/JS.
- Keep public access and navigation visibility intentional on every screen you link from this guide.