@lotics/cli 0.321.58 → 0.321.59

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.
@@ -3909,7 +3909,7 @@ above. A provider's refusal carries the provider's own words.
3909
3909
  ### send_notification (workflow step)
3910
3910
 
3911
3911
  - Notify workspace members.
3912
- - Lotics shows it to each recipient and emails it to their own address, through no connection; a member who signs in with an identifier an admin issued has no mailbox and sees it in Lotics alone.
3912
+ - Each recipient sees it in their Lotics inbox; it is also mailed to a recipient who has chosen email for their notifications, and to no other.
3913
3913
  - A member is named by the member_id get_workspace kind member lists. (chat, MCP, CLI)
3914
3914
  - In a workflow body, every member is { type: "organization", id: runtime.organization_id } and the member who started the run { type: "member", id: runtime.triggered_by_member_id }; a run a schedule, a webhook or an email starts was started by no member; the card and its email name the member who started the run. blocks draw under the message: text, stat, chart, fields, link, and record (table_id and record_id; the card shows the record's own title, read as the sender can read it). actions are buttons: each runs workflow_id under its owner's access when pressed, and its owner or an admin may name it.
3915
3915
  - A workflow a card can run declares notification inputs. inputs are the values the sender fixes; asks are the values the presser answers, each ask key an input of the workflow that inputs does not fix; every required input of the workflow is fixed or asked as required. decision is "any" (one decision for all recipients: the first press decides it) or "each" (every recipient decides alone); it is required with actions and refused without.
package/docs/workflows.md CHANGED
@@ -96,9 +96,10 @@ caller can use. The app's owner must be able to use that connection, so a
96
96
  save, and one read from an input, a record or a call is refused. A template may come from data; a run refuses one its
97
97
  owner cannot use.
98
98
 
99
- In a workflow, email reaches a member of the workspace through the step `send_notification`: Lotics shows it to them and
100
- mails it to their own address, with no connection. Its recipients are members by `member_id` (`get_workspace` with
101
- `kind: "member"` lists them), member groups or the whole organization. Mail to anyone else goes from a
99
+ In a workflow, the step `send_notification` reaches a member of the workspace: the member sees it in their Lotics
100
+ inbox, and it is mailed only to a member who has chosen email for their notifications. Its recipients are members by
101
+ `member_id` (`get_workspace` with `kind: "member"` lists them), member groups or the whole organization. Mail that
102
+ must arrive, to a member or anyone else, goes from a
102
103
  connected Gmail or Outlook (`gmail_send_email`, `outlook_send_email`), which leaves an unsent draft unless `draft` is
103
104
  `false`.
104
105
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@lotics/cli",
3
- "version": "0.321.58",
3
+ "version": "0.321.59",
4
4
  "description": "Lotics SDK and CLI for AI agents",
5
5
  "type": "module",
6
6
  "bin": {