Connect Apps
Connected apps let a Gobii work with external services through supported integration flows. Gobii uses Pipedream-backed app connections for many app capabilities.
When to connect an app
Connect an app when the Gobii's job requires direct access to a system, such as a messaging channel, task system, spreadsheet, CRM, or other SaaS tool.
Do not connect an app only because it might be useful later. Each connection increases the Gobii's available surface area.
Typical setup
- Open the Gobii.
- Find the tools, apps, or integrations area.
- Search for the app.
- Connect or authorize the app when prompted.
- Assign the connected app to the Gobii.
- Send a test instruction in chat.
- Review the timeline for tool activity or pending requests.
Some app connections may appear in just-in-time flows when a Gobii needs a specific app to complete a request.
App channels and triggers
Some connected app flows can act like inbound channels. For example, an app event can trigger Gobii to respond to a message or event.
Current app-channel behavior may vary by app and deployment. Treat Discord-style inbound message subscriptions as the conservative V1 pattern unless the product UI for your workspace shows broader support.
Safety checklist
- Connect the app only to the Gobii that needs it.
- Prefer read-only scopes when the app supports them and the workflow allows it.
- Ask Gobii to summarize what it will do before external writes.
- Use approvals for outreach, posting, deletion, purchases, or account changes.
- Remove app connections that are no longer needed.
Developer note
Pipedream app connections, direct app tools, and Pipedream trigger webhooks are different surfaces. Developers should start with Webhooks And Events and use product app connections only through documented public APIs or UI flows.