[{"data":1,"prerenderedAt":221},["ShallowReactive",2],{"\u002Fdocs\u002Fguides\u002Fconnect-an-integration":3,"docs-navigation":147,"docs-surround:\u002Fdocs\u002Fguides\u002Fconnect-an-integration":218},{"id":4,"title":5,"body":6,"description":138,"extension":139,"meta":140,"navigation":141,"path":142,"seo":143,"stem":145,"__hash__":146},"docs\u002Fdocs\u002F3.guides\u002F1.connect-an-integration.md","Connect an Integration",{"type":7,"value":8,"toc":128},"minimark",[9,13,18,45,52,56,59,62,77,85,89,92,96,99,102,106,109,112,115,119,122,125],[10,11,12],"p",{},"Integrations are usually the first setup step. They decide what Gondo can access.",[14,15,17],"h2",{"id":16},"add-the-integration","Add the integration",[19,20,21,30,36,39,42],"ol",{},[22,23,24,25,29],"li",{},"Open ",[26,27,28],"strong",{},"Integrations",".",[22,31,32,33,29],{},"Choose ",[26,34,35],{},"Add integration",[22,37,38],{},"Pick the app, system, or website you want to connect.",[22,40,41],{},"Follow the connection flow.",[22,43,44],{},"Check that the integration appears in the list.",[10,46,47,48,51],{},"If the provider supports managed OAuth, you will usually sign in through the provider. If it uses credentials, Gondo will show the fields it needs. Public APIs can use ",[26,49,50],{},"No authentication"," and are ready without a credential form.",[14,53,55],{"id":54},"give-it-a-useful-label","Give it a useful label",[10,57,58],{},"If you have more than one account for the same service, label the integration by purpose.",[10,60,61],{},"Good labels:",[63,64,65,68,71,74],"ul",{},[22,66,67],{},"Finance Gmail",[22,69,70],{},"Contracts Drive",[22,72,73],{},"Customer Success Trello",[22,75,76],{},"GitHub Product Repo",[10,78,79,80,84],{},"The label is for people. The ",[81,82,83],"code",{},"referenceId"," is the stable name workflows use.",[14,86,88],{"id":87},"check-the-connection","Check the connection",[10,90,91],{},"After connecting, use the connection check when available. This catches common setup problems early, such as an expired token, missing API permission, or incorrect service account data.",[14,93,95],{"id":94},"adjust-tool-access","Adjust tool access",[10,97,98],{},"Some integrations expose many tools. You can restrict access by toolset, read\u002Fwrite scope, or individual tools.",[10,100,101],{},"For a new workflow, start with the access needed for the job. If the workflow only needs to read files, keep it read-only. If it must update cards, sheets, issues, or documents, it needs write access for those actions.",[14,103,105],{"id":104},"use-it-in-a-workflow","Use it in a workflow",[10,107,108],{},"When a workflow step needs an integration, that node should list the integration reference ID.",[10,110,111],{},"For example, a step that reads from a finance mailbox should be allowed to use the finance Gmail integration. A step that writes to a tracker should be allowed to use the tracker integration.",[10,113,114],{},"This keeps workflow access explicit and easier to review.",[14,116,118],{"id":117},"when-to-create-a-custom-integration","When to create a custom integration",[10,120,121],{},"Create a custom integration when the system you need is not in the prebuilt catalog.",[10,123,124],{},"Use a custom API integration when the system has an HTTP API. Use a browser integration when the useful action only exists in a website UI.",[10,126,127],{},"For a public API, tell Gondo its base URL and that no authentication is required. You can still disable the integration or restrict which workflows and tools can use it.",{"title":129,"searchDepth":130,"depth":130,"links":131},"",2,[132,133,134,135,136,137],{"id":16,"depth":130,"text":17},{"id":54,"depth":130,"text":55},{"id":87,"depth":130,"text":88},{"id":94,"depth":130,"text":95},{"id":104,"depth":130,"text":105},{"id":117,"depth":130,"text":118},"Add a connected app or system so Gondo can use it in chats and workflows.","md",{},"[object Object]","\u002Fdocs\u002Fguides\u002Fconnect-an-integration",{"title":144,"description":138},"Connect an Integration in Gondo","docs\u002F3.guides\u002F1.connect-an-integration","_Ho1lhtcgtnADZOpIoqFs4y4WJeIK12k_JaAfgNt3IM",[148],{"title":149,"path":150,"stem":151,"children":152},"Docs","\u002Fdocs","docs",[153,157,162,182,193,213],{"title":154,"path":150,"stem":155,"description":156},"Gondo Docs","docs\u002Findex","Learn the basic ideas behind Gondo, from integrations and workflows to runs, approvals, and workflow YAML.",{"title":158,"path":159,"stem":160,"description":161},"Getting Started","\u002Fdocs\u002Fgetting-started","docs\u002F1.getting-started","Connect an integration, ask Gondo for help, build a workflow, and watch it run.",{"title":163,"path":164,"stem":165,"children":166,"page":181},"Concepts","\u002Fdocs\u002Fconcepts","docs\u002F2.concepts",[167,171,176],{"title":28,"path":168,"stem":169,"description":170},"\u002Fdocs\u002Fconcepts\u002Fintegrations","docs\u002F2.concepts\u002F1.integrations","Integrations are the connected apps, accounts, websites, and systems Gondo can use.",{"title":172,"path":173,"stem":174,"description":175},"Workflows","\u002Fdocs\u002Fconcepts\u002Fworkflows","docs\u002F2.concepts\u002F2.workflows","Workflows are repeatable processes made from triggers, AI tasks, code, human review, and edges.",{"title":177,"path":178,"stem":179,"description":180},"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":183,"path":184,"stem":185,"children":186,"page":181},"Guides","\u002Fdocs\u002Fguides","docs\u002F3.guides",[187,188],{"title":5,"path":142,"stem":145,"description":138},{"title":189,"path":190,"stem":191,"description":192},"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":194,"path":195,"stem":196,"children":197,"page":181},"Reference","\u002Fdocs\u002Freference","docs\u002F4.reference",[198,203,208],{"title":199,"path":200,"stem":201,"description":202},"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":204,"path":205,"stem":206,"description":207},"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":209,"path":210,"stem":211,"description":212},"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":214,"path":215,"stem":216,"description":217},"Troubleshooting","\u002Fdocs\u002Ftroubleshooting","docs\u002F5.troubleshooting","Fix common problems with integrations, workflow runs, human input, browser sessions, and YAML.",[219,220],{"title":177,"path":178,"stem":179,"children":-1},{"title":189,"path":190,"stem":191,"children":-1},1791285442573]