@stacklink/sdk 0.4.0 → 0.6.3
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/README.md +31 -0
- package/compatibility.json +1 -1
- package/dist/src/domain/billing-plans.d.ts +827 -0
- package/dist/src/domain/billing-plans.d.ts.map +1 -0
- package/dist/src/domain/billing-plans.js +893 -0
- package/dist/src/domain/billing-plans.js.map +1 -0
- package/dist/src/domain/bot-contract.d.ts +838 -747
- package/dist/src/domain/bot-contract.d.ts.map +1 -1
- package/dist/src/domain/bot-contract.js +8 -2
- package/dist/src/domain/bot-contract.js.map +1 -1
- package/dist/src/domain/memory-contract.d.ts +231 -231
- package/dist/src/domain/platform-approval-contract.d.ts +24 -24
- package/dist/src/domain/provider-branding.d.ts.map +1 -1
- package/dist/src/domain/provider-branding.js +3 -0
- package/dist/src/domain/provider-branding.js.map +1 -1
- package/dist/src/domain/stacklink-meta-tools.d.ts +18 -2
- package/dist/src/domain/stacklink-meta-tools.d.ts.map +1 -1
- package/dist/src/domain/stacklink-meta-tools.js +26 -15
- package/dist/src/domain/stacklink-meta-tools.js.map +1 -1
- package/dist/src/domain/workflow-contract.d.ts +24747 -0
- package/dist/src/domain/workflow-contract.d.ts.map +1 -0
- package/dist/src/domain/workflow-contract.js +123 -0
- package/dist/src/domain/workflow-contract.js.map +1 -0
- package/dist/src/sdk/index.d.ts +225 -10
- package/dist/src/sdk/index.d.ts.map +1 -1
- package/dist/src/sdk/index.js +72 -7
- package/dist/src/sdk/index.js.map +1 -1
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -72,6 +72,37 @@ console.log(result.output ?? result.finalText);
|
|
|
72
72
|
|
|
73
73
|
Reuse the returned `conversationId` for the next message. Preserve the last event sequence to resume observation. Published invocations are available through the existing session MCP endpoint using `STACKLINK_BOTS`; no separate server per bot is needed.
|
|
74
74
|
|
|
75
|
+
## Workflows (0.6.3)
|
|
76
|
+
|
|
77
|
+
Use `https://api.stacklink.in` for production.
|
|
78
|
+
Workflow trigger changes now follow draft → publish. `workflows.triggers(id)`
|
|
79
|
+
returns the draft `revision`, draft `triggers`, and active `liveTriggers`.
|
|
80
|
+
Pass `expectedRevision` to `saveTrigger`, or as the third argument to
|
|
81
|
+
`deleteTrigger`. Publish the returned revision to apply the change. A stale
|
|
82
|
+
revision returns 409; saving a trigger no longer activates it immediately.
|
|
83
|
+
|
|
84
|
+
Bot steps, child workflows, For each and Bot attachments accept `"live"` in place
|
|
85
|
+
of a numeric revision/version. New runs resolve live references once and retain
|
|
86
|
+
that setup through waits, retries and every item. Existing numeric pins remain
|
|
87
|
+
supported. Pausing blocks new starts; publishing does not resume a paused workflow.
|
|
88
|
+
The [Workflows guide](https://docs.stacklink.in/docs/workflows) covers definitions,
|
|
89
|
+
permissions, stable job keys and recovery.
|
|
90
|
+
|
|
91
|
+
Drafting supports exact resource mentions. Use `workflows.searchMentions({ search, kind, offset, limit })` and `resolveMentions(references, workflowId)`
|
|
92
|
+
to discover and recheck permitted apps, Bots, workflows and saved API operations.
|
|
93
|
+
Pass optional `mentions` with UTF-16 `start`/`end` ranges to `suggest`; the server
|
|
94
|
+
rechecks access before drafting. A mention never grants permissions or connects an account.
|
|
95
|
+
|
|
96
|
+
Embedded authoring uses the same workflow methods. Your backend calls
|
|
97
|
+
`workflows.issueEmbeddedAccess` with the customer and person from its authenticated
|
|
98
|
+
session. The separate `@stacklink/workflow-builder` browser package mounts the
|
|
99
|
+
hosted editor using that one-use access; never send your project key to the browser.
|
|
100
|
+
Use `workflows.withEmbeddedAccess(projectId, accessToken)` for person-scoped lists,
|
|
101
|
+
approvals and analytics, or `workflows.forCustomer(customerId)` for trusted backend
|
|
102
|
+
administration. Customer ownership, assigned approvals and usage visibility are
|
|
103
|
+
enforced by the server. See the [embedded guide](https://docs.stacklink.in/docs/workflows#embed-the-builder-in-your-application)
|
|
104
|
+
for setup, renewal, connections, publishing and the retained Acme Desk example.
|
|
105
|
+
|
|
75
106
|
## Shared approvals (0.3.3)
|
|
76
107
|
|
|
77
108
|
`client.approvals` lists and retrieves approvals for an authorized session, submits a permitted decision or customer correction, and observes reconnectable approval events. A project key represents an application; it cannot substitute for a required human company approver. `asCustomer` derives the customer from the authenticated session and still requires a scoped customer grant. Continue observing the original execution after deciding; do not resubmit the action.
|