Single-ticket export is the fastest path when you want to send one issue, escalation, or bug report into Notion without opening the bulk workflow.
Where the single export button lives
Open a Zendesk ticket, then click the extension icon in your browser toolbar.
In the popup, you will see the Ready to Export section with the button:
Export Current Ticket
If setup is incomplete, the button stays disabled until Notion is connected and a database is selected.
What the popup export actually uses
The extension reads the current Zendesk tab and extracts:
- the Zendesk host
- the current ticket ID
If the tab is not a Zendesk ticket page, the popup shows an error telling you to open a ticket page first.
What gets exported
When you export one ticket, the extension pulls both metadata and conversation content.
The resulting Notion page includes metadata such as:
- Subject
- Ticket ID
- Status
- Priority
- Ticket Type
- Requester email
- Zendesk link
- Created At
- Last Updated
- Tags
If present, the export can also include:
- Assignee name
- Assignee email
The page body is where the important reading context goes:
- ticket description
- public replies
- internal notes
- attachment links
How duplicate handling affects a single export
Before creating the page, the extension checks whether the ticket already exists in your selected Notion database by ticket ID.
Then it follows your configured behavior:
- Skip: returns the existing Notion page and does not create a new one
- Add New: creates another Notion page for the same ticket
- Replace: archives the existing page and writes a fresh page
This is especially useful when you are exporting recurring tickets into an operating database that already has prior versions.
What success looks like
After a successful export, the popup shows a success message and an Open in Notion link.
If the ticket was skipped because it already existed, the popup makes that explicit instead of pretending a new export happened.
Common reasons single export fails
The most common causes are:
- Notion is not connected
- no database is selected
- the current tab is not a Zendesk ticket page
- required Notion database fields are missing or have the wrong type
The extension also enforces export limits for free usage. If the current account has already used the daily free quota, the popup tells the user to subscribe and activate first.
Best use cases for single export
Single export is the right choice when:
- a support engineer wants to send one high-context issue to product
- a PM wants a clean Notion page for one customer-reported bug
- a support lead wants to preserve one ticket thread without loading a full view
If you need to work with many tickets from the same queue, switch to batch export instead.