[{"data":1,"prerenderedAt":306},["ShallowReactive",2],{"\u002Fdocs\u002Fconcepts\u002Fworkflows":3,"docs-navigation":231,"docs-surround:\u002Fdocs\u002Fconcepts\u002Fworkflows":303},{"id":4,"title":5,"body":6,"description":221,"extension":222,"meta":223,"navigation":224,"path":225,"seo":226,"stem":229,"__hash__":230},"docs\u002Fdocs\u002F2.concepts\u002F2.workflows.md","Workflows",{"type":7,"value":8,"toc":207},"minimark",[9,13,16,21,24,58,61,65,68,73,76,83,90,104,107,111,114,117,120,123,126,129,132,136,139,142,146,149,155,161,167,171,174,177,204],[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],{},"Every published workflow has one trigger that describes how it normally starts.",[10,77,78,79,82],{},"A ",[31,80,81],{},"manual 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.",[10,91,78,92,95,96,99,100,103],{},[31,93,94],{},"webhook trigger"," starts when an external service sends an authenticated request. Its code reads the event and calls ",[54,97,98],{},"triggerWorkflow(data)"," for each run. Use ",[54,101,102],{},"store"," for handled-event markers, just as Auto uses it for polling progress.",[10,105,106],{},"An employee can also explicitly run any of its own published jobs by supplying the trigger's expected inputs, regardless of trigger kind.",[69,108,110],{"id":109},"task","Task",[10,112,113],{},"A task node is an AI reasoning step.",[10,115,116],{},"Use task nodes for work that involves judgement, messy inputs, documents, images, file reading, classification, drafting, or browser UI operation.",[10,118,119],{},"If the step is \"look at this and figure out what it means\", it is probably a task node.",[69,121,122],{"id":54},"Code",[10,124,125],{},"A code node runs deterministic JavaScript.",[10,127,128],{},"Use code nodes for structured API calls, data transformation, or reliable writes when the input is already clear.",[10,130,131],{},"If the step is \"given these fields, call this API\", it is probably a code node.",[69,133,135],{"id":134},"human","Human",[10,137,138],{},"A human node pauses the workflow and asks a person for input.",[10,140,141],{},"Use human nodes for approval, review, editing, escalation, or missing information. The run waits until someone completes the human step.",[17,143,145],{"id":144},"drafts-publishing-and-runs","Drafts, publishing, and runs",[10,147,148],{},"Workflows can have draft changes before they are published.",[10,150,78,151,154],{},[31,152,153],{},"published workflow"," is the version used for normal Manual, Auto, or Webhook runs.",[10,156,78,157,160],{},[31,158,159],{},"draft"," is an editable version used while building or testing.",[10,162,78,163,166],{},[31,164,165],{},"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,168,170],{"id":169},"workflow-settings","Workflow settings",[10,172,173],{},"Some workflow information is metadata, not part of the normalized graph definition. The workflow title shown in lists is metadata.",[10,175,176],{},"The graph definition focuses on:",[25,178,179,184,189,194,199],{},[28,180,181],{},[54,182,183],{},"version",[28,185,186],{},[54,187,188],{},"runDisplay",[28,190,191],{},[54,192,193],{},"variables",[28,195,196],{},[54,197,198],{},"nodes",[28,200,201],{},[54,202,203],{},"edges",[10,205,206],{},"This distinction matters mostly when reading the YAML reference.",{"title":208,"searchDepth":209,"depth":209,"links":210},"",2,[211,212,219,220],{"id":19,"depth":209,"text":20},{"id":63,"depth":209,"text":64,"children":213},[214,216,217,218],{"id":71,"depth":215,"text":72},3,{"id":109,"depth":215,"text":110},{"id":54,"depth":215,"text":122},{"id":134,"depth":215,"text":135},{"id":144,"depth":209,"text":145},{"id":169,"depth":209,"text":170},"Workflows are repeatable processes made from triggers, AI tasks, code, human review, and edges.","md",{},"[object Object]","\u002Fdocs\u002Fconcepts\u002Fworkflows",{"title":227,"description":228},"Gondo Workflows","Learn how Gondo workflows are structured and when to use each kind of node.","docs\u002F2.concepts\u002F2.workflows","YCXK3oYd1Jf2zWpdH2X5oMJ6PKqVZ1fECSZxsLSca7s",[232],{"title":233,"path":234,"stem":235,"children":236},"Docs","\u002Fdocs","docs",[237,241,246,263,278,298],{"title":238,"path":234,"stem":239,"description":240},"Gondo Docs","docs\u002Findex","Learn the basic ideas behind Gondo, from integrations and workflows to runs, approvals, and workflow YAML.",{"title":242,"path":243,"stem":244,"description":245},"Getting Started","\u002Fdocs\u002Fgetting-started","docs\u002F1.getting-started","Connect an integration, ask Gondo for help, build a workflow, and watch it run.",{"title":247,"path":248,"stem":249,"children":250,"page":262},"Concepts","\u002Fdocs\u002Fconcepts","docs\u002F2.concepts",[251,256,257],{"title":252,"path":253,"stem":254,"description":255},"Integrations","\u002Fdocs\u002Fconcepts\u002Fintegrations","docs\u002F2.concepts\u002F1.integrations","Integrations are the connected apps, accounts, websites, and systems Gondo can use.",{"title":5,"path":225,"stem":229,"description":221},{"title":258,"path":259,"stem":260,"description":261},"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":264,"path":265,"stem":266,"children":267,"page":262},"Guides","\u002Fdocs\u002Fguides","docs\u002F3.guides",[268,273],{"title":269,"path":270,"stem":271,"description":272},"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":274,"path":275,"stem":276,"description":277},"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":279,"path":280,"stem":281,"children":282,"page":262},"Reference","\u002Fdocs\u002Freference","docs\u002F4.reference",[283,288,293],{"title":284,"path":285,"stem":286,"description":287},"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":289,"path":290,"stem":291,"description":292},"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":294,"path":295,"stem":296,"description":297},"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":299,"path":300,"stem":301,"description":302},"Troubleshooting","\u002Fdocs\u002Ftroubleshooting","docs\u002F5.troubleshooting","Fix common problems with integrations, workflow runs, human input, browser sessions, and YAML.",[304,305],{"title":252,"path":253,"stem":254,"children":-1},{"title":258,"path":259,"stem":260,"children":-1},1791285442519]