Skip to main content
After Knoq answers a question, that answer lives only in your chat session — until you use write-back. Write-back lets you push any AI-generated response directly into your team’s documentation system with a few clicks, creating a new page in Notion or Confluence that includes the answer text, the original question, and inline citations linking back to the sources Knoq used. It’s the fastest way to turn a research conversation into a living document your whole team can reference.
Write-back is available on the Team and Business plans only. If you’re on the Free or Solo plan, you’ll need to upgrade before this feature becomes available. Contact your organization’s admin or visit your billing settings for details.

​
Prerequisites

Before you can use write-back, make sure the following are in place:

Team or Business plan

Your organization must be on the Team or Business tier. Write-back is not available on Free or Solo plans.

Connected destination

At least one write-back destination — Notion or Confluence — must be connected to Knoq via OAuth. An admin can set this up under Admin → Settings → Integrations.
Once both conditions are met, a Save to… button will appear in the chat panel after each AI response.

​
Save to Notion

Knoq creates the new page inside your connected Notion workspace. Your admin configures which workspace and where new pages are created under Admin → Settings → Integrations.
1

Get an answer in chat

Ask your question and wait for Knoq to return a response in the chat panel.
2

Click Save to…

Below the response, click the Save to… button. A destination picker appears.
3

Choose Notion

Select Notion from the list of available destinations.
4

Confirm the save

Knoq creates the page and shows you a confirmation with a direct link to the new Notion page. Click the link to open it immediately.
The new page opens with a title derived from your question, the full answer text, provenance metadata (the date, the originating question, and a note that it was generated by Knoq), and clickable citations.

​
Save to Confluence

Knoq creates the page in a Confluence space that your admin has authorized. An admin can review and update which space is used under Admin → Settings → Integrations.
1

Get an answer in chat

Ask your question and wait for Knoq to return a response.
2

Click Save to…

Below the response, click the Save to… button.
3

Choose Confluence

Select Confluence from the destination picker.
4

Confirm the save

Knoq creates the Confluence page and shows a confirmation with a direct link. Click the link to view the page in your Confluence instance.
The page is created using Confluence wiki markup and includes the same provenance metadata as a Notion save.

​
What gets saved

Every write-back page contains the following:
ContentDescription
Page titleDerived from your original question
Answer textThe full AI-generated response, formatted for the destination
CitationsLinks back to the original Slack messages, Notion docs, GitHub issues, or other sources Knoq referenced
Provenance noteThe date and time of the save, and a note that the content was generated by Knoq
Original questionThe exact question you asked, included for context
Write-back does not save your entire session history — only the specific question-and-answer pair you chose to save.

​
Limitations

GitHub Wiki write-back is coming in a future release. The current write-back destinations are Notion and Confluence. If you attempt to use GitHub Wiki before it is available, Knoq will display a message directing you to use Notion or Confluence in the meantime.
A few other things to keep in mind:
  • Each click of Save to… creates a new page. Saving the same answer twice creates two separate pages; there is no automatic deduplication.
  • If your Notion or Confluence connection expires or is revoked, write-back will fail with a reconnection prompt. An admin can refresh the connection under Admin → Settings → Integrations.
  • The write-back destination (Notion workspace or Confluence space) is configured at the organization level by an admin, not by individual users.