For the status report somebody rebuilds every week
Prepare client updates from the work, with a review before sending.
Read live delivery state from monday.com and billing, or run the delivery operation in Bondi. Either way, the workflow identifies changes, drafts the client update, and waits for the account owner before Microsoft 365 sends it.
A schedule or delivery event starts the run. Bondi reads current milestones, time and approved commitments from the records you chose—inside Bondi or through defined connections—then drafts the update from that evidence. The account owner approves or edits it before the communication step runs, and the sent version is stored with the client record.
Illustrative workflow
Reviewing draft
monday.comDelivery milestones and status Built-in connector
Time or billing systemHours, budget or commercial exceptions API / HTTP
BondiReconciliation, draft and approval Bondi runtime
Microsoft 365Approved client communication Built-in connector
01Start on schedule or milestone change scheduleTrigger / integrationTrigger
02Read delivery and commercial state monday.com + HTTP actions
03Find the changes and draft the update filter + aiText · source records attached
04Wait for the account owner interactiveForm · approve, edit or expire
05Send and store the approved version Microsoft 365 + bondiDataUpdate
Configured human task
Account owner
The account owner approves the customer-facing summary and any changed commitment
Context shown
The source milestones, drafted update and changed commitments.
Edit and approve
Return for changes
The approved update continues to the configured communication action.
Two milestone changes and one budget exception are attached to the exact draft waiting for approval.
Delivery
2 milestones changed
Commercial
Budget threshold crossed
Current step
Account owner review
Next action
Send through Microsoft 365
Illustrative data. The connection methods, node boundaries and suspended human step
reflect current product capabilities; this is not a customer implementation.
If nobody responds
The draft remains pending, the missed review is assigned, and the customer receives nothing stale or unapproved.
Where the records live
Run the process beside your tools or within Bondi.
Keep one authoritative home for each business record. Choose the boundary that fits the process you are building.
Beside existing systems
Keep delivery and billing in their current systems
monday.com can remain the delivery board and the billing system can keep hours and value. Bondi reads defined fields and owns the cross-system draft, review and recorded outcome.
Inside your Bondi system
Run delivery operations in Bondi
Milestones, owners, client records and status history can live in a complete Bondi system. Billing may remain external, while the same review gate controls every customer-facing update.
Connection requirements
Set up the connections this example uses.
This is a worked example of a configurable workflow. Connections and decision rules must be set up for your system.