Getting Started

This page is the fastest path from a blank account to a useful workflow.

1. Connect an integration

Open Integrations and add the app you want Gondo to work with.

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.

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.

2. Ask Gondo for help

You can describe what you want in normal language. Start with the outcome, then add the systems involved.

Good prompts look like this:

• "Every weekday, check Gmail for invoice emails, summarize the invoices, and ask me before updating the finance sheet."
• "When a Trello card is moved to Done, create a weekly summary of completed work."
• "Read this folder in Google Drive and tell me which contracts need review."

You do not need to know the final workflow shape before asking. Gondo can help turn the idea into steps.

3. Build or refine the workflow

A workflow is made from nodes. Each node does one part of the job.

• Triggers start the workflow.
• Task nodes let an AI agent read, reason, classify, summarize, or use tools.
• Code nodes run deterministic JavaScript for structured API work.
• Human nodes pause the workflow for review, input, or approval.

For a first workflow, keep the process small. One trigger, one or two work steps, and one clear output is enough.

4. Run and review

When a workflow runs, it creates a run in Activity. Activity is where you see whether the run is queued, running, completed, failed, or waiting for input.

If a run pauses for a human step, open the run, review the information, and submit the requested decision or input.

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.

5. Improve over time

Most useful workflows improve after a few real runs.

Look for:

• Steps where the agent needed more specific instructions.
• Data fields that should be required.
• Places where a human approval should be added.
• Repeated failures caused by a missing permission or wrong connected account.

Small changes are usually better than a full rewrite.