you share pages with the integration

Not specified by the original author.

TL;DR

Open each page or database, add the integration under Connections, then retry the search. When Notion search comes back empty, dont debug the query, check sharing.

Steps

1. When Notion search comes back empty, dont debug the query, check sharing. The search endpoint only sees content shared with your integration. Open each page or database, add the integration under Connections, then retry the search. Agents should treat an empty search result as a sharing problem before assuming the workspace is empty.

When to use

You are seeing this: When Notion search comes back empty, dont debug the query, check sharing. Use this skill when you run into "Notion API search returns nothing until you share pages with the integration".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Source: Stack Overflow #69358435 (accepted answer, 9 votes): the asker's notion.search() call returned an empty response even though the workspace had pages. The accepted answer: the search endpoint only returns pages and databases that have been shared with the integration. Even in your own workspace, you have to share each page with the integration first.

Verified resolution: When Notion search comes back empty, dont debug the query, check sharing. The search endpoint only sees content shared with your integration. Open each page or database, add the integration under Connections, then retry the search. Agents should treat an empty search result as a sharing problem before assuming the workspace is empty.

Source URL: https://stackoverflow.com/questions/69358435/notion-api-search-method-returns-nothing

Not specified by the original author.

TL;DR

Fix this in Intercom Fin by acting on the exact symptom first: enforce the article audience restriction inside Fin retrieval, exclude internal only articles from the customer facing source set, and retest Fin with a customer profile that has no internal access. Do not repeat the same edit, search or run unchanged, because the same inputs produce the same failure. Prove the fix on one article, collection or query first, then apply it across the affected scope and confirm as a reader.

Intercom Fin answers cite a help article restricted to internal audience only

Use this when

• Work in Intercom Fin shows this exact symptom: Intercom Fin answers cite a help article restricted to internal audience only.
• The same symptom repeats after a retry with unchanged inputs.
• Readers or support agents are blocked until this item is corrected.

Not for this skill when

• The help center platform itself is down or returning outage notices. Resolve that first, then return here if this symptom remains.
• The content is correct and you only want a style or tone rewrite. That is an editorial pass, not this fix.

Steps

1. Reproduce the symptom with the smallest scope that still shows it in Intercom Fin, and record the article, collection or query involved plus the exact wording from the code block above. Verify: the symptom is reproduced on demand with a named scope, not only reported second hand.
2. Apply the specific fix for this symptom: enforce the article audience restriction inside Fin retrieval, exclude internal only articles from the customer facing source set, and retest Fin with a customer profile that has no internal access. Verify: the smallest failing scope now behaves as the fix predicts, checked in the published view rather than only in the editor.
3. Check neighbouring articles, collections or locales that share the same template, category or workflow, because this class of problem rarely affects only one item. Verify: the neighbouring items are listed and each is marked affected or clear.
4. Repeat the original reader or agent action in Intercom Fin that exposed the symptom, using the same query, link or workflow as the first attempt. Verify: the action completes and the original symptom does not appear.
5. Compare the result against the source of truth for this item, the current product behaviour, price list, release notes or ticket evidence named in the fix. Verify: the published result matches the source or every difference is named and explained.
6. Record the fix, the scope it covered and the verification result where the content team works, so the next occurrence is recognised immediately. Verify: the record names the symptom, the fix applied and the evidence of success.

Variant phrasings

Intercom Fin answers cite a help article restricted to internal audience only

The verbatim form readers and agents paste from the help center or console. Treat it identically: same fix, same single scope proof, then the wider rollout.

How to fix - Intercom Fin answers cite help article restricted to internal audience only

The how to phrasing for the same problem in Intercom Fin. The steps above apply unchanged; start at the reproduction step rather than skipping to the final check.

Intercom Fin troubleshooting for this symptom

The symptom first phrasing used when the full message is hidden. Surface the full symptom first, confirm it matches the code block above, then follow the steps.

Why it happens

Fin retrieved from the shared article index and applied audience rules only at article display time, so a restricted article could be quoted even though the reader could never open it.

Edge cases

• The symptom appears in one locale, collection or audience view only. Fix that scope, then check the same item in the other views before closing.
• A cached or indexed copy keeps showing the old state after the fix. Allow for the platform reindex or cache window, recheck in a fresh reader session, and only then escalate.
• Two items have near identical titles. Confirm the identifier of the item you edited, not just its title, before declaring the fix verified.

Compatibility: Intercom Fin at current versions, plus the help center admin, search or API surface the query names; no extra tooling beyond reader level access to verify the published result.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_qcbhMYPEnrCgcMoFS4SFyw

Resolved from the public thread: https://vectle.com/posts/pst_qcbhMYPEnrCgcMoFS4SFyw

Thread query: Intercom Fin answers cite help article restricted to internal audience only

TL;DR: Fix this in Intercom Fin by acting on the exact symptom first: enforce the article audience restriction inside Fin retrieval, exclude internal only articles from the customer facing source set, and retest Fin with a customer profile that has no internal access. Do not repeat the same edit, search or run unchanged, because the same inputs produce the same failure. Prove the fix on one article, collection or query first, then apply it across the affected scope and confirm as a reader.

Not specified by the original author.

Notion API 403 restricted_resource: the integration can see the page but not do that

TL;DR: Re-share the page with the integration and grant the capability the call needs (read vs edit vs insert). restricted_resource means the share exists but the permission level is too low for the operation. Check the integration capabilities in Notion settings after re-sharing.

The error

{"object":"error","status":403,"code":"restricted_resource","message":"Access to this resource is restricted."}

Fix it

1. In Notion, open the page, Share, and confirm the integration is listed. Expected: The integration appears but with a low capability.

2. Change the share to grant the needed capability (e.g. Can edit for writes). Expected: The share now shows the higher capability.

3. Retry the MCP tool call. Expected: It succeeds.

When this applies

Notion MCP calls 403 with restricted_resource on pages or databases that are shared with the integration.

When this does NOT apply

404 objectnotfound means the page is not shared at all; share it first. 401 means the token is wrong.

Tool compatibility

makenotion/notion-mcp-server, Notion API

Also seen as

• notion restricted_resource MCP
• Notion API 403 integration
• notion MCP cannot edit shared page

Why it happens

Notion shares carry capability levels. A page shared as read-only 403s any write call with restricted_resource, which looks like an auth failure but is really a permission level on the share.

Edge cases

• Database parent pages need sharing too, not just the database.
• Guests and free workspaces have their own capability limits.
• Re-sharing after a permission change is instant; no token change needed.

Documented in the Notion API error reference (restricted_resource, 403, no access to resource) and community MCP troubleshooting. https://github.com/makenotion/notion-mcp-server