Skip to main content

​
Overview

Gumloop connects to external services like Gmail, Slack, Salesforce, and more. Apps are how you authenticate these connections securely. You can connect multiple accounts for each service and choose which one to use in each agent or flow.

Personal Apps

Private to you. Perfect for individual work, testing, and personal accounts.

Team Apps

Shared with your team. Ideal for collaborative agents and flows where everyone uses the same account.
Start with personal apps for most work. Use team apps only when your team needs to run agents and flows with shared accounts.

​
Personal vs Team Apps

Personal AppsTeam Apps
Who can use?Only youAll team members
Where do they work?Any space (personal or team)Specific team only
Default in nodes?Yes, automatic defaultNo, must be selected manually
SetupOne-time, works everywherePer team
Best forIndividual work, testing, personal accountsTeam collaboration, shared accounts
PrivacyFully private, even in teamsShared with all team members

​
Connecting a Personal App

1

Go to your Apps page

Visit your Apps page or navigate via Settings → Your Apps
2

Click Connect New App

Select the service you want to connect (Gmail, Slack, OpenAI, etc.)
3

Authenticate

OAuth (most services): Click “Connect” and follow the authorization flow. No manual token management needed. Examples: Gmail, Slack, Microsoft services.API Keys (some services): Paste your API key directly. Examples: OpenAI, AWS, Anthropic.
4

Set as default (optional)

If you connect multiple accounts for the same service (e.g., three different Gmail accounts), you can choose which one is your default. If you only have one account connected for a service, it’s automatically your default.
Personal Apps page
Privacy guaranteed: Even in teams, other members cannot see or use your personal apps.

​
Selecting Credentials in Nodes

​
In Flows

In flows, every node that requires authentication has a “Credentials to use” dropdown. If you have multiple credentials connected for the same service (e.g., three Gmail accounts), you can pick exactly which one to use on each node.
Credential selection dropdown in a node
All nodes default to your personal credential, even in teams. To use a team credential, you must manually select it from the dropdown on each node.
Uses your default personal credential for this service. Selected by default on all new nodes.Use when you’re working in your personal space, testing, or want to use your own account even in a team.
Uses the team’s default credential for this service. Must be manually selected.Use when everyone on the team should use the same shared account (e.g., marketing@company.com).
If no team credential is set up for this service, the node will fail. Make sure team apps are configured first.
Choose any specific credential you’ve connected. Useful when you need different accounts for different parts of the same flow.

​
In Agents

Agents use only default credentials. You cannot select a specific credential for an agent the way you can for individual nodes in a flow.
Personal AgentTeam Agent
Credentials usedYour personal defaultPersonal default OR team default (if configured)
Who can use it?Anyone with the link or in the channelOnly team members
Best forGeneral use, maximum accessibilityShared credentials, team collaboration
When someone interacts with a personal agent, it uses their own personal default credentials, not the agent creator’s credentials.
  • Each user’s request runs on their own authenticated accounts
  • Users who haven’t connected the required service will be prompted to authenticate
  • Best for most use cases where each person should use their own accounts
Team agents can use team credentials so that everyone on the team uses the same shared account, without needing to set up their own.To configure team credentials on an agent:
  1. Move the agent to a team
  2. Add team credentials from the team’s Apps page
  3. In the agent’s settings, switch each integration from “Personal Default” to “Team Default”
Switching an agent to use team credentials
When an agent is in a team, users invoking the agent must also be members of that team. To avoid manually adding users, use your organization’s default team which automatically includes all members.
Learn more about using agents with credentials in Using Agents in Slack → Credentials & Authentication.

​
Team Apps

Team apps are shared integrations that all team members can use. There are two ways to set them up.

​
Option 1: Right-Click from the Sidebar

On the Home page, right-click on your team in the sidebar and select Apps. Then click Connect New App.
Team Apps page with Connect New App button

​
Option 2: From Organization Settings

  1. Go to Settings → Teams
  2. Click on the team, then select Apps in the sidebar
  3. Click Connect New App

​
Managing Your Apps

Visit your Apps page to see all your personal apps, last refresh time, connected services, and defaults.
OAuth apps automatically refresh when needed. If you see authentication errors:
  1. Go to your Apps page
  2. Click Reauthenticate on the affected service
  3. Complete the authorization flow again
  1. Go to your Apps page
  2. Find the app to remove and click Revoke
  3. Confirm removal
All auth tokens are removed immediately. Agents and flows using this app will fail until you reconnect.
Personal default: Your go-to app for a service. Used when “Personal Default” is selected in a node. Only affects your account.Team default: The team’s primary app for a service. Used when “Team Default” is selected. Applies to all team members.

​
Microsoft Office Setup (Admin Only)

For organizations using Microsoft services (Teams, Outlook, Excel, Word, OneLake), administrators must configure consent in Microsoft Entra ID before users can authenticate.

​
Required Permissions by Service

IntegrationKey Permissions
TeamsTeam.ReadBasic.All, ChannelMessage.Read.All, Chat.ReadWrite
OutlookMail.ReadWrite, Mail.Send
Excel/WordFiles.ReadWrite, Sites.ReadWrite.All
OneLakehttps://storage.azure.com/user_impersonation
Admin required: You must be a Global Administrator, Cloud Application Administrator, or Application Administrator to grant consent.

​
Salesforce Setup (Admin Only)

As of September 2025, Salesforce introduced new security restrictions that require administrators to pre-install the Gumloop connected app before users can authenticate with their Salesforce instances. For more details, see the official Salesforce documentation.
Gumloop is a Salesforce Connected App, not an AppExchange app. You will not find it in the Salesforce AppExchange marketplace. A Salesforce administrator needs to authorize the connection directly.

​
Managing the Connected App in Salesforce

  1. Go to Setup > Apps > Connected Apps > Manage Connected Apps
  2. Find the Gumloop app to view or modify settings
  3. Configure user access policies, IP restrictions, and session policies as needed
For more details, refer to the Salesforce Connected App documentation.

​
Security & Compliance

SOC 2 Type II

Certified secure infrastructure and processes

GDPR Compliant

Full compliance with data protection regulations

Trust Center

View our complete security documentation

Organization and Teams

Understand how personal spaces and teams work

User Roles & Permissions

Organization and team permission levels