Setup Documentation

Get Started with Zendesk to Notion

Set up the extension, connect Notion, choose your database, and configure duplicate handling before your first export.

Get Started with Zendesk to Notion

In this doc

Zendesk to Notion setup connect Notion database Zendesk to Notion getting started

Zendesk to Notion has two export modes, but both depend on the same setup flow.

Before you export a single ticket or a full saved view, make sure the extension can talk to the right Notion database and knows how to behave when the same ticket already exists.

Step 1: Open the extension from a Zendesk tab

The extension is designed to work while you are already inside Zendesk.

For single-ticket export:

  • Open any Zendesk ticket page
  • Click the extension icon in your browser toolbar
  • The popup will open with the setup and export controls

For batch export:

  • Open any Zendesk page
  • Click the folder sync button in the popup, or open the bulk export page directly

If the extension cannot find a usable Zendesk tab, export actions will stay blocked.

Step 2: Connect your Notion account

In the setup section, the first step is Connect to Notion.

When you click the button, the extension opens the Notion OAuth flow and waits for the callback. Once authorization succeeds:

  • the Notion token is stored locally in the extension
  • the setup step switches to a connected state
  • the extension starts searching for available Notion databases

If you reconnect later, the extension simply reruns the same authorization flow.

Step 3: Select the destination database

After Notion is connected, choose the database where ticket pages should be created.

The extension supports:

  • selecting from discovered Notion databases
  • manually refreshing the list
  • opening the currently selected database in Notion

There is also an auto-refresh behavior if a newly created or newly shared database does not appear yet. If no database is found, the extension checks again every 10 seconds.

Step 4: Choose existing ticket behavior

This setting controls what happens when the same Zendesk ticket already exists in Notion.

You have three options:

  1. Skip: do not create a new page if the ticket already exists
  2. Add New: keep the current page and create another page for the same ticket
  3. Replace: archive the existing page first, then create a fresh page

For most teams, Replace or Skip are the safest defaults depending on whether you want history or a single current record.

The extension expects the Notion database to include the right property types for metadata.

Use these properties:

  • Subject: Title
  • Ticket ID: Number
  • Status: Select
  • Priority: Select
  • Ticket Type: Select
  • Requester: Email
  • Zendesk Link: URL
  • Tags: Multi-select
  • Created At: Date
  • Last Updated: Date

Optional fields such as Assignee and Assignee Email are also supported if you add them with the correct types.

What goes into page content vs database properties

Database properties store metadata for filtering and sorting.

The ticket body itself is written into the Notion page content area, not squeezed into one field. That includes the parts people actually need to read later:

  • public replies
  • internal notes
  • structured ticket details
  • attachment references

This is what keeps the exported page useful after the export is done.

Before your first export

You are ready when all of the following are true:

  • Notion is connected
  • a database is selected
  • your duplicate-handling behavior is set
  • you are on a usable Zendesk page

Once that is done, you can move on to either single-ticket export or batch export.