[{"data":1,"prerenderedAt":230},["ShallowReactive",2],{"\u002Fdocs\u002Fgetting-started":3,"docs-navigation":156,"docs-surround:\u002Fdocs\u002Fgetting-started":227},{"id":4,"title":5,"body":6,"description":147,"extension":148,"meta":149,"navigation":150,"path":151,"seo":152,"stem":154,"__hash__":155},"docs\u002Fdocs\u002F1.getting-started.md","Getting Started",{"type":7,"value":8,"toc":138},"minimark",[9,13,18,26,29,32,36,39,42,55,58,62,65,91,94,98,105,108,111,115,118,121,135],[10,11,12],"p",{},"This page is the fastest path from a blank account to a useful workflow.",[14,15,17],"h2",{"id":16},"_1-connect-an-integration","1. Connect an integration",[10,19,20,21,25],{},"Open ",[22,23,24],"strong",{},"Integrations"," and add the app you want Gondo to work with.",[10,27,28],{},"An integration is a connected account or system, such as Google Workspace, Gmail, Trello, GitHub, Jira, Notion, Airtable, or a website session. Once connected, Gondo can use the tools made available by that integration.",[10,30,31],{},"After connecting, give the integration a clear label if the account has a specific purpose. For example, \"Finance Gmail\" is more useful than \"Gmail\" when you have several accounts.",[14,33,35],{"id":34},"_2-ask-gondo-for-help","2. Ask Gondo for help",[10,37,38],{},"You can describe what you want in normal language. Start with the outcome, then add the systems involved.",[10,40,41],{},"Good prompts look like this:",[43,44,45,49,52],"ul",{},[46,47,48],"li",{},"\"Every weekday, check Gmail for invoice emails, summarize the invoices, and ask me before updating the finance sheet.\"",[46,50,51],{},"\"When a Trello card is moved to Done, create a weekly summary of completed work.\"",[46,53,54],{},"\"Read this folder in Google Drive and tell me which contracts need review.\"",[10,56,57],{},"You do not need to know the final workflow shape before asking. Gondo can help turn the idea into steps.",[14,59,61],{"id":60},"_3-build-or-refine-the-workflow","3. Build or refine the workflow",[10,63,64],{},"A workflow is made from nodes. Each node does one part of the job.",[43,66,67,73,79,85],{},[46,68,69,72],{},[22,70,71],{},"Triggers"," start the workflow.",[46,74,75,78],{},[22,76,77],{},"Task nodes"," let an AI agent read, reason, classify, summarize, or use tools.",[46,80,81,84],{},[22,82,83],{},"Code nodes"," run deterministic JavaScript for structured API work.",[46,86,87,90],{},[22,88,89],{},"Human nodes"," pause the workflow for review, input, or approval.",[10,92,93],{},"For a first workflow, keep the process small. One trigger, one or two work steps, and one clear output is enough.",[14,95,97],{"id":96},"_4-run-and-review","4. Run and review",[10,99,100,101,104],{},"When a workflow runs, it creates a run in ",[22,102,103],{},"Activity",". Activity is where you see whether the run is queued, running, completed, failed, or waiting for input.",[10,106,107],{},"If a run pauses for a human step, open the run, review the information, and submit the requested decision or input.",[10,109,110],{},"If a run fails, the troubleshooting page can help you find the usual cause: missing integration permission, unclear workflow instructions, unavailable files, expired browser login, or a schema mismatch.",[14,112,114],{"id":113},"_5-improve-over-time","5. Improve over time",[10,116,117],{},"Most useful workflows improve after a few real runs.",[10,119,120],{},"Look for:",[43,122,123,126,129,132],{},[46,124,125],{},"Steps where the agent needed more specific instructions.",[46,127,128],{},"Data fields that should be required.",[46,130,131],{},"Places where a human approval should be added.",[46,133,134],{},"Repeated failures caused by a missing permission or wrong connected account.",[10,136,137],{},"Small changes are usually better than a full rewrite.",{"title":139,"searchDepth":140,"depth":140,"links":141},"",2,[142,143,144,145,146],{"id":16,"depth":140,"text":17},{"id":34,"depth":140,"text":35},{"id":60,"depth":140,"text":61},{"id":96,"depth":140,"text":97},{"id":113,"depth":140,"text":114},"Connect an integration, ask Gondo for help, build a workflow, and watch it run.","md",{},"[object Object]","\u002Fdocs\u002Fgetting-started",{"title":153,"description":147},"Getting Started with Gondo","docs\u002F1.getting-started","T1l2MdLLAnh1NiKsyp0Q0M68u7MVDzR_jcrAoTE_LNA",[157],{"title":158,"path":159,"stem":160,"children":161,"page":-1},"Docs","\u002Fdocs","docs",[162,166,167,187,202,222],{"title":163,"path":159,"stem":164,"description":165},"Gondo Docs","docs\u002Findex","Learn the basic ideas behind Gondo, from integrations and workflows to runs, approvals, and workflow YAML.",{"title":5,"path":151,"stem":154,"description":147},{"title":168,"path":169,"stem":170,"children":171,"page":186},"Concepts","\u002Fdocs\u002Fconcepts","docs\u002F2.concepts",[172,176,181],{"title":24,"path":173,"stem":174,"description":175},"\u002Fdocs\u002Fconcepts\u002Fintegrations","docs\u002F2.concepts\u002F1.integrations","Integrations are the connected apps, accounts, websites, and systems Gondo can use.",{"title":177,"path":178,"stem":179,"description":180},"Workflows","\u002Fdocs\u002Fconcepts\u002Fworkflows","docs\u002F2.concepts\u002F2.workflows","Workflows are repeatable processes made from triggers, AI tasks, code, human review, and edges.",{"title":182,"path":183,"stem":184,"description":185},"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":188,"path":189,"stem":190,"children":191,"page":186},"Guides","\u002Fdocs\u002Fguides","docs\u002F3.guides",[192,197],{"title":193,"path":194,"stem":195,"description":196},"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":198,"path":199,"stem":200,"description":201},"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":203,"path":204,"stem":205,"children":206,"page":186},"Reference","\u002Fdocs\u002Freference","docs\u002F4.reference",[207,212,217],{"title":208,"path":209,"stem":210,"description":211},"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":213,"path":214,"stem":215,"description":216},"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":218,"path":219,"stem":220,"description":221},"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":223,"path":224,"stem":225,"description":226},"Troubleshooting","\u002Fdocs\u002Ftroubleshooting","docs\u002F5.troubleshooting","Fix common problems with integrations, workflow runs, human input, browser sessions, and YAML.",[228,229],{"title":163,"path":159,"stem":164,"children":-1},{"title":24,"path":173,"stem":174,"children":-1},1782191063528]