Skip to main content

Integrations

Integrations allow you to connect Gen8 with external services, enabling AI agents to access and interact with your tools.

Available Integrations​

Gmail lets you connect your Gmail account for email capabilities including searching emails, reading messages, sending emails, and managing labels.

ClickUp connects your ClickUp workspace so agents can manage tasks, access documents, work with checklists, and browse your workspace structure.

Fireflies connects your Fireflies.ai account to search meeting transcripts, access conversation details, review action items, and find specific discussions.

Integration Types​

Organization integrations are set up by organization admins and become available to all members. These provide centralized configuration with admin-managed credentials, making them ideal for teams that need consistent access to shared resources.

User integrations are connected by individual users using their personal accounts. Each user has their own access and configuration, which is useful when different team members need to access their own email or project management accounts.

Setting Up Integrations​

For organization setup, admins go to Organization Settings → Integrations, find the integration they want to enable, click Configure, complete the setup steps, and enable it for the organization.

For user connections, go to the Integrations page, find the enabled integration, click Connect, complete the OAuth flow or enter your API key, and the connection is established.

OAuth Integrations​

Gmail and ClickUp use OAuth for authentication. When you click Connect, you're redirected to the service's login page where you sign in and approve the requested permissions. After approval, you're redirected back to Gen8 with the connection complete.

OAuth grants specific permissions that you can review before approving. These permissions control what access Gen8 has—like read/write access or specific scopes—and you can revoke them at any time through either Gen8 or the service's settings.

API Key Integrations​

Fireflies uses API key authentication. You'll need to get your API key from the Fireflies service, enter it in Gen8's integration settings, save the configuration, and the connection is tested automatically.

Managing Integrations​

The integration status shows whether each integration is Connected (ready to use), Disconnected (needs setup), or Pending (setup in progress).

To disconnect an integration, go to its settings, click Disconnect, confirm the removal, and all credentials are removed. If a connection expires, you can reconnect by clicking Reconnect, completing the setup again, and new credentials are saved.

Using Integrations in Agents​

Once integrations are connected, you can enable the relevant tools in your agents. Edit your agent, add the tools you need (like Gmail Search or ClickUp Tasks), and those tools will automatically use your connected accounts.

Some integrations support multiple accounts—for example, you can connect different Gmail accounts and switch between them for different purposes.

Security​

Credentials are stored securely and encrypted at rest. They are never shared with the AI—the AI can only use the integrations through the tools you enable, not access your raw credentials.

Integrations only request the access they need. You can review permissions before approving and revoke them at any time. Best practices include using organization integrations when possible, regularly reviewing connected services, disconnecting unused integrations, and keeping credentials secure.

Troubleshooting​

Connection failures: Verify credentials are correct, check that the service is accessible, review permission requirements, and try reconnecting if needed.

Permission errors: Check that your account has the necessary access, verify the integration is enabled at the organization level, review the permissions you granted, and contact your organization admin if you need elevated access.

Token expiration: If tokens expire, reconnect the integration by completing the OAuth flow again. Check for any service-side issues that might be causing the expiration.

Next Steps​