Integrations

An integration is a connected system that Gondo can use while chatting or running workflows.

Examples include Google Workspace, Gmail, Trello, GitHub, Jira, Notion, Airtable, SharePoint, a custom API, or a logged-in website session.

What an integration gives Gondo

An integration can provide:

• A way to authenticate with an external system.
• Tools for reading or writing data.
• A stable reference ID that workflow steps can use.
• Optional limits on which tools or toolsets are enabled.

For normal users, the important question is simple: "Which connected account should this workflow be allowed to use?"

Reference IDs

Each integration has a user-visible referenceId.

This is the stable name a workflow uses when it needs a connected app. A workflow node can list the integrations it is allowed to use, then code or agent tools can refer to that ID.

For example, a workflow step might use an integration named:

finance_gmail

Clear reference IDs make workflows easier to understand. Prefer names that explain the account or purpose:

• finance_gmail
• customer_success_trello
• contracts_drive
• supplier_portal

Managed OAuth and credentials

Gondo supports different ways to connect.

Managed OAuth is the familiar "Sign in with..." flow. It is usually the easiest option when available.

Credentials means you provide fields such as an API key, token, service account JSON, or workspace URL. This is useful for systems that do not support managed OAuth or for enterprise-style connections.

Gondo stores secrets separately from workflow YAML. Do not put API keys, passwords, or tokens in workflow variables or instructions.

Prebuilt, custom, and browser integrations

Prebuilt integrations are supported providers with ready-made tools. They are the easiest starting point.

Custom API integrations are for HTTP APIs that Gondo does not support out of the box. They define a base URL, credential fields, and custom tools.

Browser integrations are for websites where the useful action happens in the UI rather than an API. They store a logged-in browser session and let Gondo operate the site. Use browser integrations when an API is unavailable or does not cover the task.

Tool access

An API integration can expose tools. A tool might read a document, list cards, update a spreadsheet, create an issue, or send an email.

Tool access can be controlled in a few ways:

• Toolsets group related tools, such as Drive, Docs, Sheets, and Slides.
• Scope limits tools by read, write, or admin level.
• Disabled tools turn off individual tools for an integration.

For early workflows, keep access practical: enable the tools the workflow needs, and narrow access once you know the workflow is stable.