How to Display a Notion Database in WordPress

Updated July 2026 • By Fahad Murtaza • 5 min read

Notion reached 30 million registered users in 2023 (Notion, 2023), making it one of the most widely adopted collaborative databases — and TableCrafter can pull any Notion database directly into WordPress as a live, sortable, filterable table. No intermediary sync service is required. The Notion source is a Pro feature; this guide walks through the complete setup from creating an integration token to embedding the table on a page.

Step 1: How Do I Create a Notion Integration?

Go to notion.so/my-integrations and click New integration. Give it a name such as "TableCrafter Sync", associate it with your workspace, and leave the type set to Internal integration. Click Submit and copy the Internal Integration Secret — it starts with secret_ and is only shown once, so save it somewhere secure.

Next, open the Notion database you want to display in WordPress. Click the ... menu at the top right of the database page, select Add connections, and search for the integration you just created. Select it to grant the integration read access to that database.

Finally, copy the database ID from the URL. In a Notion database URL the ID is the 32-character alphanumeric string between the last / and any ?v= query parameter. For example, in notion.so/yourworkspace/abc123def456..., the database ID is abc123def456.... Notion formats this as a UUID with hyphens when accessed via the API, but you can paste the plain version — TableCrafter normalizes it automatically.

Step 2: How Do I Connect It in TableCrafter?

In your WordPress admin, go to TableCrafter → Add New Table and select Notion as the data source. Paste your Internal Integration Secret into the API Token field and paste the database ID into the Database ID field, then click Test Connection.

If the test succeeds, TableCrafter lists all Notion properties detected in that database as available columns. If the test fails, the most common causes are: (1) the integration was not connected to the database in Step 1 — return to the database's connections menu and confirm the integration appears; (2) the database ID was copied with extra characters or spaces — paste it fresh from the URL.

Once the connection succeeds, select which Notion properties to show and set column labels. Notion property types map automatically: Select and Multi-select properties become filterable dropdown columns; Date properties are sortable; Number properties support numeric sorting and range filters; Title and Rich text render as plain text. Click Save to store the table configuration.

Step 3: How Do I Configure Display and Refresh?

In the table's Display tab, enable search, sorting, and filters. For databases that have Select or Multi-select Notion properties, TableCrafter generates dropdown filters automatically — no additional configuration needed. Set the rows-per-page default and choose whether to show a row count.

TableCrafter caches the Notion API response to avoid hitting Notion's rate limits on busy pages. In the Performance tab, set the Cache TTL to match how often your database changes. A team directory updated weekly can use a 24-hour TTL. A content calendar updated daily might use 2 hours. A live roadmap updated continuously should use 15–30 minutes. The cache is invalidated automatically when you save the table configuration, so you will always see fresh data immediately after any admin change.

Place the shortcode on any WordPress page or post: [tablecrafter id="1" search="true" filter="true"]. To override the default rows-per-page for one specific embed without changing the saved configuration, add the parameter inline: [tablecrafter id="1" per_page="25"]. After publishing, verify the table by loading the page in a private or incognito window while logged out — this confirms the table renders correctly for public visitors, not just admin users.

What Are Some Good Use Cases?

Notion-powered WordPress tables work well whenever the data lives in Notion and needs a public or semi-public frontend view without giving site visitors access to the Notion workspace. Common patterns include: a public product roadmap or changelog maintained in Notion and displayed on a marketing site; a team directory or knowledge base that HR updates in Notion and employees browse on an intranet; an events or session schedule for a conference that organizers manage in Notion and attendees view on the event site; and a content calendar that a marketing team maintains in Notion and an agency or client reviews on a WordPress dashboard page. In all of these cases, the source of truth stays in Notion while WordPress shows a clean, searchable, always-current view to the right audience.