@notionhq/apps 0.0.32 → 0.0.33
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json
CHANGED
|
@@ -89,6 +89,11 @@ root exports support:
|
|
|
89
89
|
- `customAgent({ resourceId, name, ... })`; only `resourceId` and `name` are
|
|
90
90
|
required. Choose optional fields individually as described below, and inspect
|
|
91
91
|
the installed types before using them.
|
|
92
|
+
|
|
93
|
+
When an App calls a custom agent, read the
|
|
94
|
+
[Notion Agent APIs overview](https://developers.notion.com/guides/notion-agent-apis/overview)
|
|
95
|
+
first.
|
|
96
|
+
|
|
92
97
|
- `view({ databaseResourceId, resourceId, type, dataSourceResourceId, ... })`,
|
|
93
98
|
returning a handle with `resourceId`. This is also available as `notion.view`.
|
|
94
99
|
Use property resource IDs in view filters, sorts, and layout options; calendar
|
package/skills/workflow/SKILL.md
CHANGED
|
@@ -167,6 +167,10 @@ typed `context.access` exposes each declared alias as a readonly `{ type, id }`,
|
|
|
167
167
|
not the declaration handle or a permission-management API. UI-granted resources
|
|
168
168
|
are permissions only: they do not create `context.access` aliases.
|
|
169
169
|
|
|
170
|
+
When a workflow calls a custom agent, read the
|
|
171
|
+
[Notion Agent APIs overview](https://developers.notion.com/guides/notion-agent-apis/overview)
|
|
172
|
+
first.
|
|
173
|
+
|
|
170
174
|
For a resource already granted to the workflow in Notion's UI, use its live
|
|
171
175
|
record ID directly in a `context.notion` call:
|
|
172
176
|
|