Connect an Integration
Integrations are usually the first setup step. They decide what Gondo can access.
Add the integration
- Open Integrations.
- Choose Add integration.
- Pick the app, system, or website you want to connect.
- Follow the connection flow.
- Check that the integration appears in the list.
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.
Give it a useful label
If you have more than one account for the same service, label the integration by purpose.
Good labels:
- Finance Gmail
- Contracts Drive
- Customer Success Trello
- GitHub Product Repo
The label is for people. The referenceId is the stable name workflows use.
Check the connection
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.
Adjust tool access
Some integrations expose many tools. You can restrict access by toolset, read/write scope, or individual tools.
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.
Use it in a workflow
When a workflow step needs an integration, that node should list the integration reference ID.
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.
This keeps workflow access explicit and easier to review.
When to create a custom integration
Create a custom integration when the system you need is not in the prebuilt catalog.
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.