Meeting Actions
ivy.agent.meeting-actions · v1.0.0
ivyx
Has a model pull the action items out of meeting notes, checks each one has an owner and a task, and writes them as a table.
Steps
In the order the agent's file lists them, each with where its inputs come from and the values the file fixes. A branch or a loop is a step too.
- 01Model turnExtract the action items
List the action items in these meeting notes. An action item is something a named person agreed to do. For each one give owner (the person's name), task (what they will do, in a few words) and due (the date or day the notes give, or an empty string when none is given). Leave out decisions and remarks that nobody has to act on.
- takes
contextfrom the agent's input,notes
- 02Ivy NodeCheck each itemivy.node.rows-validate
Checks every row against a JSON Schema and splits the rows into valid ones and invalid ones with their problems.
- takes
rowsfrom step 1,output.items- set
schema{"type":"object","required":["owner","task"],"properties":{"owner":{"type":"string","minLength":1},"task":{"type":"st...- returns
actions,rejected
- 03Ivy NodeLay out the tableivy.node.markdown-table
Formats rows as a Markdown table, with the columns in the order given or as they first appear.
- takes
rowsfrom step 2,valid_rows- set
columns["owner","task","due"]- returns
count,markdown
- 04Ivy NodeWrite the tableivy.node.file-write
Writes text to a file, creating its folder, and returns the absolute path and the number of bytes written.
- takes
textfrom step 3,markdown- set
pathreports/actions.mdoverwritetrue- returns
path
Nodes it brings
Adding this agent in IVYX Studio adds these nodes with it. A node your workspace already has is kept as it is, even at another version.
What it touches
Collected from what each of its nodes declares and what the agent's own file declares, such as moving a robot, plus the model call when a step is a model turn. A declaration is the author's statement, and it is what policy rules select on.
Inputs
| Field | Type | Description |
|---|---|---|
| notesrequired | string | The meeting notes, as text. |
Outputs
| Field | Type | Description |
|---|---|---|
| actions | array | The action items that have an owner and a task, as {owner, task, due}. |
| count | integer | How many action items were written. |
| rejected | integer | How many extracted items lacked an owner or a task. |
| markdown | string | The table that was written. |
| path | string | The file the table was written to. |
Tests
2 of 2 test cases passed on Oct 4, 2026, in the publisher's own environment, before this version was published. The registry keeps that record; it does not run the cases again.
Requires: python:3.9, a model core
- weekly-sync
Three people took a task and one point was a decision: three rows, none about the logo.
- given
notesWeekly sync, 3 October. Present: Ayla, Bram, Chen. - Checkout bug: Bram will ship the fix by Friday 9 October. - Ayla...- expects
countequals 3markdownmatches Bram[\s\S]*Ayla[\s\S]*Chen|Ayla[\s\S]*Bram[\s\S]*Chenpathmatches reports/actions\.md$
- design-review
Other notes give other owners.
- given
notesDesign review. Dana presents the onboarding flow. Decision: keep three steps. Dana to update the mockups by Monday. E...- expects
countequals 2markdownmatches Dana[\s\S]*Erik