@lotics/cli 0.292.3 → 0.294.0
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/dist/src/cli.js +116 -29
- package/dist/src/client.d.ts +4 -0
- package/docs/workflow_steps.md +3694 -0
- package/docs/workflows.md +5 -1
- package/package.json +1 -1
package/docs/workflows.md
CHANGED
|
@@ -51,7 +51,7 @@ await send_email({
|
|
|
51
51
|
| step | syntax |
|
|
52
52
|
|---|---|
|
|
53
53
|
| tool call, kept | `const <id> = await <tool>({ ...inputs });` — also `let x = await …` and `x = await …` |
|
|
54
|
-
| tool call | `await <tool>({ ...inputs });` |
|
|
54
|
+
| tool call | `await <tool>({ ...inputs });` — a connection's tools too, each a workflow step (`bkav_submit_invoices`, `gmail_send_email`, …); a step that fails ends the run with its reason unless a `try`/`catch` around it handles it |
|
|
55
55
|
| agent | `const <id> = await agent({ instructions, input, tools, model, output });` — see **An agent step** |
|
|
56
56
|
| app agent | `const <id> = await app_agent({ alias: "<agent alias>", input: { ... } });` — runs one of the app's declared agents, in an app workflow only, and resolves to its declared outputs or its final text. `wait: false` only starts the run and resolves to `{ run_id }`; the run's failure is then its own, not the workflow's. Refused in a run an agent started. |
|
|
57
57
|
| bind | `const <id> = <expression>;` — evaluated once; later steps read `<id>`. Bind any expression used twice. |
|
|
@@ -64,6 +64,10 @@ await send_email({
|
|
|
64
64
|
| return | `return({ status: "success" \| "error", message: <expr>, field_errors: { ... }? });` |
|
|
65
65
|
| validate | `validate({ checks: [{ fail_when: <expr>, field_key: "...", message: <expr> }, ...] });` |
|
|
66
66
|
|
|
67
|
+
Every step's inputs, the values each takes and its answer: `lotics tools <name>` prints them; the steps only a body
|
|
68
|
+
runs — a connection's, a mail's — are all in `workflow_steps`. `query_integration_tools` lists the workspace's
|
|
69
|
+
connections and the steps each opens.
|
|
70
|
+
|
|
67
71
|
`return` is a call, not a JavaScript `return` statement. `validate` ends the workflow with an error
|
|
68
72
|
when a check's `fail_when` is truthy; the check's `field_key` names the control its message lands on —
|
|
69
73
|
in an app workflow a declared input, or the `fld_` key of a field on a table the body names; a field of
|