You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit d51e185
Browse filesBrowse the repository at this point in the historyBrowse files
| Sync | Ticket sync | Support-system tickets | Upsert by stable external ID | Support-system connection, Support tickets database |
56
+
| Workflow | Escalate urgent ticket | Support tickets page created or updated | Run triage, update status, and notify support channel | Ticket triage agent, Support tickets database, messaging connection |
57
+
58
+
**Open questions:** Which support system and messaging channel should the App use?
59
+
60
+
Ask the user to confirm or revise the design. Do not begin implementation
61
+
until they agree. If implementation reveals a material resource or capability
62
+
not covered by the agreed design, update the proposal and confirm the change
63
+
before adding it.
64
+
7
65
## SDK imports
8
66
9
67
Import the creation helpers you use directly from the package root:
@@ -28,25 +86,36 @@ Check that the installed SDK supports these exports before building.
28
86
29
87
## Capability layout
30
88
89
+
After the user agrees on the design, compare it with the complete scaffold.
| Notion as Code | Resources declared in modules imported by workflows or syncs |`.agents/skills/notion-as-code/SKILL.md`|`node_modules/@notionhq/apps/skills/notion-as-code/SKILL.md`|
45
116
46
-
For resources declared with the App, read
47
-
`.agents/skills/notion-as-code/SKILL.md`. Notion as Code declarations belong in
48
-
modules imported by workflows or syncs; they are not a separate discovered
49
-
capability directory. Syncs can use their declared data source handles.
117
+
Notion as Code declarations are not a separate discovered capability
118
+
directory. Syncs can use their declared data source handles.
50
119
51
120
Prefer Notion as Code over other methods for equivalent supported resource
52
121
setup. Use another method when the user explicitly requests it, an existing
@@ -73,5 +142,11 @@ Building does not verify server availability, published connection setup, or
73
142
browser interactions. State separately which live checks actually ran.
74
143
75
144
For a requested deployment, enable `ntn experiments enable apps`, authenticate,
76
-
and use `ntn apps deploy --name <name>` on the first deployment; omit `--name`
77
-
for updates. Read the installed CLI help for other commands.
145
+
and use `ntn apps deploy --json` with any required arguments. On the first
146
+
deployment, pass `--name <name>`; omit `--name` for updates. Use the JSON fields
147
+
`worker_url`, `setup_url`, and `is_update` in the handoff. For a first
148
+
deployment (`is_update` is false), show the `setup_url` and tell the user to
149
+
open it to finish setup. For an update (`is_update` is true), show both URLs
150
+
with clear labels: `worker_url` opens the deployed App and `setup_url` revisits
151
+
onboarding. Use the URLs returned by the CLI; do not construct or guess them.
| Sync | Ticket sync | Support-system tickets | Upsert by stable external ID | Support-system connection, Support tickets database |
56
+
| Workflow | Escalate urgent ticket | Support tickets page created or updated | Run triage, update status, and notify support channel | Ticket triage agent, Support tickets database, messaging connection |
57
+
58
+
**Open questions:** Which support system and messaging channel should the App use?
59
+
60
+
Ask the user to confirm or revise the design. Do not begin implementation
61
+
until they agree. If implementation reveals a material resource or capability
62
+
not covered by the agreed design, update the proposal and confirm the change
63
+
before adding it.
64
+
7
65
## SDK imports
8
66
9
67
Import the creation helpers you use directly from the package root:
@@ -28,25 +86,36 @@ Check that the installed SDK supports these exports before building.
28
86
29
87
## Capability layout
30
88
89
+
After the user agrees on the design, compare it with the complete scaffold.
| Notion as Code | Resources declared in modules imported by workflows or syncs |`.agents/skills/notion-as-code/SKILL.md`|`node_modules/@notionhq/apps/skills/notion-as-code/SKILL.md`|
45
116
46
-
For resources declared with the App, read
47
-
`.agents/skills/notion-as-code/SKILL.md`. Notion as Code declarations belong in
48
-
modules imported by workflows or syncs; they are not a separate discovered
49
-
capability directory. Syncs can use their declared data source handles.
117
+
Notion as Code declarations are not a separate discovered capability
118
+
directory. Syncs can use their declared data source handles.
50
119
51
120
Prefer Notion as Code over other methods for equivalent supported resource
52
121
setup. Use another method when the user explicitly requests it, an existing
@@ -73,5 +142,11 @@ Building does not verify server availability, published connection setup, or
73
142
browser interactions. State separately which live checks actually ran.
74
143
75
144
For a requested deployment, enable `ntn experiments enable apps`, authenticate,
76
-
and use `ntn apps deploy --name <name>` on the first deployment; omit `--name`
77
-
for updates. Read the installed CLI help for other commands.
145
+
and use `ntn apps deploy --json` with any required arguments. On the first
146
+
deployment, pass `--name <name>`; omit `--name` for updates. Use the JSON fields
147
+
`worker_url`, `setup_url`, and `is_update` in the handoff. For a first
148
+
deployment (`is_update` is false), show the `setup_url` and tell the user to
149
+
open it to finish setup. For an update (`is_update` is true), show both URLs
150
+
with clear labels: `worker_url` opens the deployed App and `setup_url` revisits
151
+
onboarding. Use the URLs returned by the CLI; do not construct or guess them.
0 commit comments