[{"data":1,"prerenderedAt":289},["ShallowReactive",2],{"\u002Fdocs\u002Fconcepts\u002Fworkflows":3,"docs-navigation":214,"docs-surround:\u002Fdocs\u002Fconcepts\u002Fworkflows":286},{"id":4,"title":5,"body":6,"description":204,"extension":205,"meta":206,"navigation":207,"path":208,"seo":209,"stem":212,"__hash__":213},"docs\u002Fdocs\u002F2.concepts\u002F2.workflows.md","Workflows",{"type":7,"value":8,"toc":190},"minimark",[9,13,16,21,24,58,61,65,68,73,76,83,90,94,97,100,103,106,109,112,115,119,122,125,129,132,138,144,150,154,157,160,187],[10,11,12],"p",{},"A workflow is a repeatable process that Gondo can run for you.",[10,14,15],{},"It might check for new items, read information, make a judgement, update another system, or ask a person to approve something before continuing.",[17,18,20],"h2",{"id":19},"the-graph-model","The graph model",[10,22,23],{},"A workflow is a graph.",[25,26,27,35,41,47],"ul",{},[28,29,30,34],"li",{},[31,32,33],"strong",{},"Nodes"," are steps.",[28,36,37,40],{},[31,38,39],{},"Edges"," connect steps.",[28,42,43,46],{},[31,44,45],{},"Conditions"," can decide whether a path should run.",[28,48,49,52,53,57],{},[31,50,51],{},"Data"," flows from earlier nodes to later nodes through ",[54,55,56],"code",{},"ctx.data",".",[10,59,60],{},"This lets a workflow be simple or branching. A small workflow may be a straight line. A larger one may branch based on approval, category, risk, or missing information.",[17,62,64],{"id":63},"node-types","Node types",[10,66,67],{},"Gondo workflows use four main node types.",[69,70,72],"h3",{"id":71},"trigger","Trigger",[10,74,75],{},"A trigger starts a workflow.",[10,77,78,79,82],{},"A ",[31,80,81],{},"command trigger"," starts when a person or chat asks the workflow to run.",[10,84,85,86,89],{},"An ",[31,87,88],{},"auto trigger"," runs on a schedule. It can either always start a run or check a connected app first and only start runs when there is new work.",[69,91,93],{"id":92},"task","Task",[10,95,96],{},"A task node is an AI reasoning step.",[10,98,99],{},"Use task nodes for work that involves judgement, messy inputs, documents, images, file reading, classification, drafting, or browser UI operation.",[10,101,102],{},"If the step is \"look at this and figure out what it means\", it is probably a task node.",[69,104,105],{"id":54},"Code",[10,107,108],{},"A code node runs deterministic JavaScript.",[10,110,111],{},"Use code nodes for structured API calls, data transformation, or reliable writes when the input is already clear.",[10,113,114],{},"If the step is \"given these fields, call this API\", it is probably a code node.",[69,116,118],{"id":117},"human","Human",[10,120,121],{},"A human node pauses the workflow and asks a person for input.",[10,123,124],{},"Use human nodes for approval, review, editing, escalation, or missing information. The run waits until someone completes the human step.",[17,126,128],{"id":127},"drafts-publishing-and-runs","Drafts, publishing, and runs",[10,130,131],{},"Workflows can have draft changes before they are published.",[10,133,78,134,137],{},[31,135,136],{},"published workflow"," is the version used for normal scheduled or command runs.",[10,139,78,140,143],{},[31,141,142],{},"draft"," is an editable version used while building or testing.",[10,145,78,146,149],{},[31,147,148],{},"run"," is one execution of a workflow. Runs keep a record of what happened, which nodes completed, which data was produced, and whether the workflow finished or paused.",[17,151,153],{"id":152},"workflow-settings","Workflow settings",[10,155,156],{},"Some workflow information is metadata, not part of the normalized graph definition. The workflow title shown in lists is metadata.",[10,158,159],{},"The graph definition focuses on:",[25,161,162,167,172,177,182],{},[28,163,164],{},[54,165,166],{},"version",[28,168,169],{},[54,170,171],{},"runDisplay",[28,173,174],{},[54,175,176],{},"variables",[28,178,179],{},[54,180,181],{},"nodes",[28,183,184],{},[54,185,186],{},"edges",[10,188,189],{},"This distinction matters mostly when reading the YAML reference.",{"title":191,"searchDepth":192,"depth":192,"links":193},"",2,[194,195,202,203],{"id":19,"depth":192,"text":20},{"id":63,"depth":192,"text":64,"children":196},[197,199,200,201],{"id":71,"depth":198,"text":72},3,{"id":92,"depth":198,"text":93},{"id":54,"depth":198,"text":105},{"id":117,"depth":198,"text":118},{"id":127,"depth":192,"text":128},{"id":152,"depth":192,"text":153},"Workflows are repeatable processes made from triggers, AI tasks, code, human review, and edges.","md",{},"[object Object]","\u002Fdocs\u002Fconcepts\u002Fworkflows",{"title":210,"description":211},"Gondo Workflows","Learn how Gondo workflows are structured and when to use each kind of node.","docs\u002F2.concepts\u002F2.workflows","81bQc6q5wvG0tOYqIw2BZVb0hq05GkuBYwgcOqRNJeg",[215],{"title":216,"path":217,"stem":218,"children":219,"page":-1},"Docs","\u002Fdocs","docs",[220,224,229,246,261,281],{"title":221,"path":217,"stem":222,"description":223},"Gondo Docs","docs\u002Findex","Learn the basic ideas behind Gondo, from integrations and workflows to runs, approvals, and workflow YAML.",{"title":225,"path":226,"stem":227,"description":228},"Getting Started","\u002Fdocs\u002Fgetting-started","docs\u002F1.getting-started","Connect an integration, ask Gondo for help, build a workflow, and watch it run.",{"title":230,"path":231,"stem":232,"children":233,"page":245},"Concepts","\u002Fdocs\u002Fconcepts","docs\u002F2.concepts",[234,239,240],{"title":235,"path":236,"stem":237,"description":238},"Integrations","\u002Fdocs\u002Fconcepts\u002Fintegrations","docs\u002F2.concepts\u002F1.integrations","Integrations are the connected apps, accounts, websites, and systems Gondo can use.",{"title":5,"path":208,"stem":212,"description":204},{"title":241,"path":242,"stem":243,"description":244},"Runs and Activity","\u002Fdocs\u002Fconcepts\u002Fruns-and-activity","docs\u002F2.concepts\u002F3.runs-and-activity","Learn what happens when a workflow runs and how to read statuses, approvals, failures, and reauth pauses.",false,{"title":247,"path":248,"stem":249,"children":250,"page":245},"Guides","\u002Fdocs\u002Fguides","docs\u002F3.guides",[251,256],{"title":252,"path":253,"stem":254,"description":255},"Connect an Integration","\u002Fdocs\u002Fguides\u002Fconnect-an-integration","docs\u002F3.guides\u002F1.connect-an-integration","Add a connected app or system so Gondo can use it in chats and workflows.",{"title":257,"path":258,"stem":259,"description":260},"Build Your First Workflow","\u002Fdocs\u002Fguides\u002Fbuild-your-first-workflow","docs\u002F3.guides\u002F2.build-your-first-workflow","A practical walkthrough for turning a plain-English process into a small Gondo workflow.",{"title":262,"path":263,"stem":264,"children":265,"page":245},"Reference","\u002Fdocs\u002Freference","docs\u002F4.reference",[266,271,276],{"title":267,"path":268,"stem":269,"description":270},"Workflow YAML","\u002Fdocs\u002Freference\u002Fworkflow-yaml","docs\u002F4.reference\u002F1.workflow-yaml","The technical shape of Gondo workflow definitions, including version, run display, variables, nodes, edges, and schema rules.",{"title":272,"path":273,"stem":274,"description":275},"Node Types","\u002Fdocs\u002Freference\u002Fnode-types","docs\u002F4.reference\u002F2.node-types","Reference for trigger, task, code, and human nodes, including configs and runtime context.",{"title":277,"path":278,"stem":279,"description":280},"Integration Tools","\u002Fdocs\u002Freference\u002Fintegration-tools","docs\u002F4.reference\u002F3.integration-tools","How integration tools, toolsets, scopes, disabled tools, and custom tools fit together.",{"title":282,"path":283,"stem":284,"description":285},"Troubleshooting","\u002Fdocs\u002Ftroubleshooting","docs\u002F5.troubleshooting","Fix common problems with integrations, workflow runs, human input, browser sessions, and YAML.",[287,288],{"title":235,"path":236,"stem":237,"children":-1},{"title":241,"path":242,"stem":243,"children":-1},1782191063528]