Notion Database Setup

Tickong writes each parsed ticket to a single Notion database. The schema is fixed — property names and types must match exactly so Tickong knows where to put each value.

You’ll set this up once, before connecting Notion in the onboard wizard.

Required properties

Create a database with these properties (or add them to an existing one). Names are case-sensitive.

Notion property	Type	What Tickong puts here
Name	Title	The page title (e.g. 4 x WorldCup | 78)
Shop	Rich text	Platform domain (e.g. ticketmaster.es)
Fecha Evento	Date	When the event happens
Fecha Compra	Date	When you purchased
Section	Rich text	Composed: section-row-lowSeat/highSeat
Retail	Number	What you paid (USD, normalised)
Account	Rich text	Email address that forwarded the confirmation
URL	URL	Gmail deep link to the original message
Listing ID	Rich text	SkyBox inventory ID (only if SkyBox is connected)
Resell	Number	Equal to Retail at insert; never updated post-listing
Stock	Select	Set to Disponible on insert

The Stock select needs an option called Disponible. Add it before connecting, otherwise the first insert will fail.

Properties Tickong won’t touch

These are useful additions for your own analytics. Tickong never writes to them — they’re entirely yours to manage:

Property	Type	Purpose
Market	Select	Manual classification (US / EU / LATAM …)
Marketplace	Select	Where you ended up listing/selling (Vivid, StubHub, Ticombo …)
Status	Select or formula	Lifecycle (Disponible → Vendido, etc.)
Profit	Formula	prop("Resell") - prop("Retail")
ROI	Formula	prop("Profit") / prop("Retail")
Días Restantes	Formula	dateBetween(prop("Fecha Evento"), now(), "days")

You can name these whatever you want — they’re invisible to Tickong’s writer.

Connect the database to Tickong

1. Go to https://www.notion.so/my-integrations and click + New integration.
2. Name it Tickong, give it your workspace, and on the Capabilities tab keep all three content capabilities checked (Read, Update, Insert).
3. Copy the Internal Integration Secret.
4. Open your tickets database. Click … (top right) → Connections → search for Tickong → Confirm.
5. From the database URL, copy the 32-character ID:
   • URL: https://www.notion.so/yourws/7a7fc27697c140308c7446210f709bfb?v=...
   • ID: 7a7fc27697c140308c7446210f709bfb

Paste both into the onboard wizard (or Settings → Notion later). Click Test schema — Tickong reads your database and tells you which properties are correct, missing, or have the wrong type.

Common mistakes

• Database not connected to the integration. Open the database page → … → Connections → add the Tickong integration. Connecting at the workspace level alone is not enough.
• Wrong ID. The 32-char hex string between notion.so/.../ and ?v=. Don’t include hyphens or the v= parameter.
• Stock is a multi-select instead of select. Use single select and create a Disponible option.
• Disponible option missing. Even a correctly-typed select fails on insert if the option doesn’t exist yet. Add it manually (any colour) before connecting.
• Renamed Fecha Evento or Fecha Compra. These names are written verbatim by Tickong — don’t translate them.

Why some property names are in Spanish

The schema was originally designed for a Spanish-language ticket-flipping workflow. Once your database is set up, you’ll never type these names again — they live in your Notion DB and Tickong’s settings, not in your day-to-day work.

How duplicates are handled

Tickong dedupes on the content of a ticket, not the email itself. If you forward the same FIFA confirmation twice, both deliveries produce the same content fingerprint (event + date + section + row + seats) and only the first one creates a Notion page. The duplicate gets routed to the Tickong/Skipped folder.

Notion itself has no equivalent guard — so if you delete a row from Notion, the next forward of the same ticket would create a fresh page. That’s usually what you want.