Task and item boards

Zenkit holds work as items in collections viewed as lists, boards, or tables. A Beam agent reads new and changing items, applies the workflow rule you approved, and updates each item stage, owner, or fields as work moves, closing items when the finish criteria are met. Clear transitions happen on their own. An item with conflicting field values, or one whose move would skip a required review, is left in place and routed to a person, since a card marked done before the work truly is hides the remaining effort from everyone counting on the board.

Custom field updates

Each Zenkit collection defines its own fields: dates, references, labels, and formulas. When source data changes, the agent reads the affected items, applies your mapping rule, and writes the new field values so the collection stays current with the systems around it. Straightforward updates are made directly. Values that fail validation, references that point at a missing item, or a change that would overwrite a manually set field are held for a person, because silently replacing a deliberate entry with an automated one erases a decision someone made for a reason the agent cannot see.

Collection linking

Zenkit lets items in one collection reference items in another, tying related work together. A Beam agent reads incoming records, applies your matching rule, and creates or updates the link between the right items so a task connects to its project or client. Confident, single matches are linked automatically. A record that could link to several items, or one with no clear counterpart, is left unlinked and flagged for a person, since a wrong reference threads unrelated work together and is far more tedious to untangle later than to place correctly the first time.