[{"data":1,"prerenderedAt":174},["ShallowReactive",2],{"doc:\u002Fv\u002F2026.3\u002Fautomation\u002Fautomations":3},{"_path":4,"_dir":5,"_draft":6,"_partial":6,"_locale":7,"title":8,"description":9,"section":10,"version":11,"lastUpdated":12,"body":13,"_type":168,"_id":169,"_source":170,"_file":171,"_stem":172,"_extension":173},"\u002Fv\u002F2026.3\u002Fautomation\u002Fautomations","automation",false,"","Automations","Design reliable Workspace369 automations with clear triggers, conditions, actions, ownership, testing, and failure review.","Automation and AI","2026.3","2026-07-11",{"type":14,"children":15,"toc":158},"root",[16,24,38,45,50,56,61,67,72,78,83,89,94,124,130,135,144,150],{"type":17,"tag":18,"props":19,"children":20},"element","p",{},[21],{"type":22,"value":23},"text","Automations reduce repeated work by responding to events in the client-work lifecycle. A reliable automation starts with a narrow outcome and preserves enough context for the team to understand what happened.",{"type":17,"tag":18,"props":25,"children":26},{},[27,29,36],{"type":22,"value":28},"For the complete builder workflow, see ",{"type":17,"tag":30,"props":31,"children":33},"a",{"href":32},"\u002Fv\u002F2026.3\u002Fautomation\u002Fbuild-test-activate-workflow\u002F",[34],{"type":22,"value":35},"Build, test, and activate a workflow",{"type":22,"value":37},".",{"type":17,"tag":39,"props":40,"children":42},"h2",{"id":41},"define-the-outcome-first",[43],{"type":22,"value":44},"Define the outcome first",{"type":17,"tag":18,"props":46,"children":47},{},[48],{"type":22,"value":49},"Describe the result in one sentence before building the workflow. Examples include assigning a follow-up task, notifying an owner, sending an approved message, or updating a record when a known condition is met.",{"type":17,"tag":39,"props":51,"children":53},{"id":52},"choose-a-precise-trigger",[54],{"type":22,"value":55},"Choose a precise trigger",{"type":17,"tag":18,"props":57,"children":58},{},[59],{"type":22,"value":60},"Use the event that most directly represents the workflow change. Broad triggers can cause duplicate actions or run against records that were never intended to enter the automation.",{"type":17,"tag":39,"props":62,"children":64},{"id":63},"add-conditions",[65],{"type":22,"value":66},"Add conditions",{"type":17,"tag":18,"props":68,"children":69},{},[70],{"type":22,"value":71},"Conditions narrow the records that continue through a workflow. Use structured client, project, communication, billing, or status data when available instead of relying on ambiguous text.",{"type":17,"tag":39,"props":73,"children":75},{"id":74},"configure-actions",[76],{"type":22,"value":77},"Configure actions",{"type":17,"tag":18,"props":79,"children":80},{},[81],{"type":22,"value":82},"Every action should have a clear target and owner. When an action communicates with a client or changes financial context, make the review and failure path explicit.",{"type":17,"tag":39,"props":84,"children":86},{"id":85},"test-before-enabling-broadly",[87],{"type":22,"value":88},"Test before enabling broadly",{"type":17,"tag":18,"props":90,"children":91},{},[92],{"type":22,"value":93},"Use a test client or controlled record to verify:",{"type":17,"tag":95,"props":96,"children":97},"ol",{},[98,104,109,114,119],{"type":17,"tag":99,"props":100,"children":101},"li",{},[102],{"type":22,"value":103},"The trigger occurs once at the expected moment.",{"type":17,"tag":99,"props":105,"children":106},{},[107],{"type":22,"value":108},"Conditions include and exclude the right records.",{"type":17,"tag":99,"props":110,"children":111},{},[112],{"type":22,"value":113},"Actions use the correct client and workspace context.",{"type":17,"tag":99,"props":115,"children":116},{},[117],{"type":22,"value":118},"Messages render variables accurately.",{"type":17,"tag":99,"props":120,"children":121},{},[122],{"type":22,"value":123},"Errors are visible to someone responsible for resolving them.",{"type":17,"tag":39,"props":125,"children":127},{"id":126},"monitor-and-revise",[128],{"type":22,"value":129},"Monitor and revise",{"type":17,"tag":18,"props":131,"children":132},{},[133],{"type":22,"value":134},"Review automation activity after launch. Business processes change, and a workflow that was correct at launch can become misleading when ownership, status conventions, services, or communication policies change.",{"type":17,"tag":136,"props":137,"children":138},"blockquote",{},[139],{"type":17,"tag":18,"props":140,"children":141},{},[142],{"type":22,"value":143},"Automation should make ownership clearer. If a workflow creates actions that no person understands or reviews, simplify it before adding more steps.",{"type":17,"tag":39,"props":145,"children":147},{"id":146},"next-step",[148],{"type":22,"value":149},"Next step",{"type":17,"tag":18,"props":151,"children":152},{},[153,157],{"type":17,"tag":30,"props":154,"children":155},{"href":32},[156],{"type":22,"value":35},{"type":22,"value":37},{"title":7,"searchDepth":159,"depth":159,"links":160},2,[161,162,163,164,165,166,167],{"id":41,"depth":159,"text":44},{"id":52,"depth":159,"text":55},{"id":63,"depth":159,"text":66},{"id":74,"depth":159,"text":77},{"id":85,"depth":159,"text":88},{"id":126,"depth":159,"text":129},{"id":146,"depth":159,"text":149},"markdown","content:v:2026.3:automation:automations.md","content","v\u002F2026.3\u002Fautomation\u002Fautomations.md","v\u002F2026.3\u002Fautomation\u002Fautomations","md",1783880375054]