@notionhq/apps 0.0.25 → 0.0.26

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
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@notionhq/apps",
3
- "version": "0.0.25",
3
+ "version": "0.0.26",
4
4
  "description": "An SDK for building workflow apps for Notion",
5
5
  "license": "MIT",
6
6
  "bin": {
@@ -155,6 +155,11 @@ declarations in `access` work too. Importing a declaration alone provisions the
155
155
  resource but does not create a `context.access` alias. An `access` entry declares
156
156
  the needed permission level and a named binding for that NaC resource.
157
157
 
158
+ For a workflow that uses `triggers.scheduled()`, also declare a "triggers"
159
+ database with a page-added trigger bound to it. This lets the user manually
160
+ trigger a run at any time by adding a page to that database, without waiting
161
+ for the schedule.
162
+
158
163
  `access.view()`, `access.comment()`, `access.edit()`, and `access.fullAccess()`
159
164
  accept page, database, and data-source handles. `access.call()` accepts custom-agent
160
165
  handles. Keys are workflow-local aliases. The handler's