Skip to content

Document Notion integration, AI-generated PR details, and per-page feedback #4864

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
mintlify wants to merge 1 commit into from
Closed

Document Notion integration, AI-generated PR details, and per-page feedback #4864

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions agent/index.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -48,6 +48,9 @@ Add the agent to your Slack workspace.
<Card title="Connect Linear" horizontal icon="linear" href="/agent/linear">
Add the agent to your Linear workspace.
</Card>
<Card title="Connect Notion" horizontal icon="notebook" href="/agent/notion">
Connect your Notion workspace as context for the agent.
</Card>
<Card title="Customize behavior" horizontal icon="wrench" href="/agent/customize">
Configure the agent with an `AGENTS.md` file.
</Card>
Expand Down
22 changes: 22 additions & 0 deletions agent/notion.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,22 @@
---
title: "Connect the agent to Notion"
description: "Give the agent access to your Notion workspace to read and write pages as context for documentation updates."
keywords: ["Notion integration", "Notion workspace", "agent integration", "knowledge base"]
---

Connect your Notion workspace to the agent so it can read and write Notion pages. When the agent has access to Notion, it can pull context from your team's knowledge base and reference internal documents when creating documentation updates.

## Connect your Notion workspace

Check warning on line 9 in agent/notion.mdx

View check run for this annotation

Mintlify / Mintlify Validation (mintlify) - vale-spellcheck

agent/notion.mdx#L9 

'Connect your Notion workspace' should use sentence-style capitalization.

1. Go to the [Agent](https://dashboard.mintlify.com/products/agent) page in your dashboard.
2. In the "Agent settings" section, click **Install Notion app**.
3. Follow the Notion prompts to authorize the Mintlify app and select which pages or databases to share.

Once connected, the agent settings show Notion as connected.

## Disconnect Notion

Check warning on line 17 in agent/notion.mdx

View check run for this annotation

Mintlify / Mintlify Validation (mintlify) - vale-spellcheck

agent/notion.mdx#L17 

'Disconnect Notion' should use sentence-style capitalization.

To disconnect your Notion workspace:

1. Go to the [Agent](https://dashboard.mintlify.com/products/agent) page in your dashboard.
2. In the "Agent settings" section, click **Disconnect** next to the Notion integration.
1 change: 1 addition & 0 deletions docs.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -95,6 +95,7 @@
"pages": [
"agent/slack",
"agent/linear",
"agent/notion",
"agent/workflows",
"agent/customize",
"agent/effective-prompts",
Expand Down
6 changes: 6 additions & 0 deletions editor/publish.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -55,6 +55,12 @@

If there are no pending changes or a pull request for the current branch is already open, the **Publish** button is unclickable.

### AI-generated PR details

Check warning on line 58 in editor/publish.mdx

View check run for this annotation

Mintlify / Mintlify Validation (mintlify) - vale-spellcheck

editor/publish.mdx#L58 

'AI-generated PR details' should use sentence-style capitalization.

When your publishing workflow creates a pull request, the editor automatically generates a title and description based on your changes. The generated details appear in the publish dialog while you review the file changes.

You can edit the generated title and description before publishing. If you modify a field and the editor regenerates the details (for example, after additional file changes), your edits are preserved and the generated content is appended.

Check warning on line 62 in editor/publish.mdx

View check run for this annotation

Mintlify / Mintlify Validation (mintlify) - vale-spellcheck

editor/publish.mdx#L62 

In general, use active voice instead of passive voice ('are preserved').

Check warning on line 62 in editor/publish.mdx

View check run for this annotation

Mintlify / Mintlify Validation (mintlify) - vale-spellcheck

editor/publish.mdx#L62 

In general, use active voice instead of passive voice ('is appended').

<Note>
Your live documentation site updates after Mintlify builds and deploys your published changes. This typically takes 30 seconds to a few minutes. Check the deployment status of your changes on your [dashboard](https://dashboard.mintlify.com).
</Note>
Expand Down
6 changes: 6 additions & 0 deletions optimize/feedback.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -75,13 +75,13 @@
Best practices for setting feedback statuses:

- **Pending**: Feedback is awaiting review.
- **In Progress**: Feedback has been validated and is being worked on.

Check warning on line 78 in optimize/feedback.mdx

View check run for this annotation

Mintlify / Mintlify Validation (mintlify) - vale-spellcheck

optimize/feedback.mdx#L78 

In general, use active voice instead of passive voice ('been validated').

Check warning on line 78 in optimize/feedback.mdx

View check run for this annotation

Mintlify / Mintlify Validation (mintlify) - vale-spellcheck

optimize/feedback.mdx#L78 

In general, use active voice instead of passive voice ('being worked').
- **Resolved**: Feedback has been resolved.

Check warning on line 79 in optimize/feedback.mdx

View check run for this annotation

Mintlify / Mintlify Validation (mintlify) - vale-spellcheck

optimize/feedback.mdx#L79 

In general, use active voice instead of passive voice ('been resolved').
- **Dismissed**: Feedback has been dismissed as not actionable, irrelevant, or inaccurate.

Check warning on line 80 in optimize/feedback.mdx

View check run for this annotation

Mintlify / Mintlify Validation (mintlify) - vale-spellcheck

optimize/feedback.mdx#L80 

In general, use active voice instead of passive voice ('been dismissed').

### Filter by status

Use the status filter to control which feedback is displayed. Clear a status to hide all feedback with that status. By default, all feedback is displayed.

Check warning on line 84 in optimize/feedback.mdx

View check run for this annotation

Mintlify / Mintlify Validation (mintlify) - vale-spellcheck

optimize/feedback.mdx#L84 

In general, use active voice instead of passive voice ('is displayed').

Check warning on line 84 in optimize/feedback.mdx

View check run for this annotation

Mintlify / Mintlify Validation (mintlify) - vale-spellcheck

optimize/feedback.mdx#L84 

In general, use active voice instead of passive voice ('is displayed').

### Add internal notes

Expand All @@ -89,6 +89,12 @@

Use notes to add information for collaboration, link relevant support or engineering tickets, or remember any other useful information.

## View feedback by page

Switch between **All feedback** and **Feedback by page** views at the top of the feedback tab. The per-page view groups thumbs up and thumbs down votes by page so you can see which pages receive the most positive or negative feedback.

Use the per-page view to quickly identify pages that need attention without scrolling through individual feedback entries.

## Use feedback data

Review your feedback data to:
Expand Down
Loading