Overview
Gumloop connects to external services like Gmail, Slack, Salesforce, and more. Connectors 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 Connectors
Private to you. Perfect for individual work, testing, and personal accounts.
Team Connectors
Shared with your team. Ideal for collaborative agents and flows where everyone uses the same account.
Personal vs Team Connectors
| Personal Connectors | Team Connectors | |
|---|---|---|
| Who can use? | Only you | All team members |
| Where do they work? | Any space (personal or team) | Specific team only |
| Default in nodes? | Yes, automatic default | No, must be selected manually |
| Setup | One-time, works everywhere | Per team |
| Best for | Individual work, testing, personal accounts | Team collaboration, shared accounts |
| Privacy | Fully private, even in teams | Shared with all team members |
Connect a Connector
Connect an account once, then reuse it across every agent and flow. You can connect a connector just for yourself (personal) or for everyone on a team (team).Connect a Personal Connector
Go to your Connectors page
Visit your Connectors page or navigate via Settings → Connectors
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.
Privacy guaranteed: Even in teams, other members cannot see or use your personal connectors.
Connect a Team Connector
Team connectors are shared integrations that everyone on a specific team can use. They are scoped to that team only, and a team’s default credential applies to all of its members. Set one up from the team’s Connectors page (right-click the team in the sidebar, or go to Settings → Teams → your team → Connectors), then click Add Connector. For a step-by-step walkthrough, see How do I add shared team credentials (team apps)? in the Knowledge Base.Choose Which Account to Use
A connector can have several connected accounts for the same service (for example, three Gmail logins). You pick which account is used, and the options depend on whether you are configuring an agent or a flow.In Agents
Each connector connected to your agent has a credential menu (the three-dot icon). Agents can be shared with your organization or with specific people, and the account is resolved for whoever runs the agent, which is not always you. How to choose:Everyone as themselves
Pick Use Personal Default. Each person who runs the agent uses their own account, so data stays private to each user. This is the default.
Everyone as one shared login
In a team agent, pick Use Team Default (or pin a team account). Every team member who runs the agent uses that same shared account.
Which account does the agent run with? It depends on the option you pick and who runs the agent:
- Use Personal Default (the default for both personal and team agents): the agent uses the running user’s own default account. Share the agent and each person uses their own account, so data stays private to each user.
- Use Specific Account on a personal agent pins one of your personal accounts. It only applies when you run the agent. Anyone you share it with cannot use your personal account, so it falls back to their personal default.
- Use Team Default or Use Specific Account on a team agent uses a shared team account, so every team member who runs the agent uses that same account. Anyone outside the team (for example, through an org-wide share) falls back to their own personal default.
- Agent-owned credentials are the exception. When you explicitly pin an account as agent-owned, everyone who can access the agent uses that account when tools are called, including people you share it with. See Agent-Owned Credentials below.
Personal Agents
Personal agents offer two choices. A personal agent can still be shared, so the table shows which account is used when you run it versus when someone you shared it with runs it.
| Option | What it does | Account used at runtime |
|---|---|---|
| Use Personal Default | Uses the default account of whoever runs the agent. This is the default setting. | Each person uses their own account |
| Use Specific Account | Pins one of your personal accounts to this agent (e.g., one of two Outlook inboxes). | You: your pinned account. Anyone you share it with: their own personal default |
Team Agents
Team agents have a third option: Use Team Default. This lets all team members share one account without each person needing their own credentials for that service.
| Option | What it does | Account used at runtime |
|---|---|---|
| Use Personal Default | Uses the personal account of whoever runs the agent. The default setting. | Each person uses their own account |
| Use Team Default | Uses the team’s shared default account for this service. | All team members use the shared team account |
| Use Specific Account | Pins one team-connected account so the agent always uses it. | All team members use that team account (anyone outside the team uses their own default) |
Agent-Owned Credentials
By default, connectors are user-owned: each person who runs the agent uses the account available to them, and a specific account you pin only applies when you run the agent. Agent-owned credentials change this. When a connector is agent-owned, everyone who can access the agent uses the one account or connection you pinned, without getting direct access to the underlying credential.Selection and ownership are separate. Choosing a specific account decides which account the agent uses. Ownership decides whose identity runs the tool. Selecting a specific account does not make it agent-owned on its own. You turn that on explicitly.
Which ownership mode to use
User-owned / User/Team-owned
Each person who runs the agent acts as themselves, using the account available to them. Pick this when a shared agent should work on each user’s own data and that data should stay private to each user. This is the default.
Agent-owned
The agent is bound to one specific account, and everyone who can access it acts as that account no matter who runs the agent. Pick this when you want to hardcode a credential to the agent, such as a shared service account or a support inbox, so the agent always behaves the same way for every user.
Turn on agent-owned for a connector
Select a specific account
In your agent’s Apps, open the connector’s detail view and select the specific account you want to pin.
Set Credential ownership
A Credential ownership control appears once a specific account is selected. Choose one of:
- User-owned (labeled User/Team-owned on team agents): each user uses the accounts available to them when tools are called. This is the default.
- Agent-owned: everyone using this agent uses the pinned credential when tools are called.
Enterprise availability
For organizations, agent-owned credentials are restricted by default. An admin turns them on per custom role with the Agent-owned credentials feature toggle. Members whose roles do not grant it see the Agent-owned option disabled. You can only pin an account you have access to, and Gumloop re-checks that when the agent is saved.In Flows
Flows use the same connectors and accounts as agents. Credential selection works a little differently because it happens per node.Using connectors in flows
Using connectors in flows
In flows, every node that requires authentication has a “Credentials to use” dropdown. If you have multiple accounts connected for the same service (e.g., three Gmail accounts), you can pick exactly which one to use on each node.
| Option | What it does |
|---|---|
| Personal Default | Uses your default personal account for this service. Selected by default on all new nodes. Use it when working in your personal space, testing, or to use your own account inside a team. |
| Team Default | Uses the team’s default account 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 connector is set up for this service, the node will fail, so configure team connectors first. |
| Specific Credential | Choose any specific account you’ve connected. Useful when you need different accounts for different parts of the same flow. |
Manage Your Connectors
Viewing your connectors
Viewing your connectors
Visit your Connectors page to see all your personal connectors, last refresh time, connected services, and defaults.
Refreshing a connector
Refreshing a connector
OAuth connectors automatically refresh when needed. If you see authentication errors:
- Go to your Connectors page
- Click Reauthenticate on the affected service
- Complete the authorization flow again
Removing a connector
Removing a connector
- Go to your Connectors page
- Find the connector to remove and click Revoke
- Confirm removal
Setting defaults
Setting defaults
Personal default: Your go-to connector for a service. Used when “Personal Default” is selected in a node. Only affects your account.Team default: The team’s primary connector for a service. Used when “Team Default” is selected. Applies to all team members.
Admin Setup
Some services require an administrator to authorize Gumloop before anyone on the team can connect their own account.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.- Tenant-Wide Consent
- Admin Consent Workflow
- App Provisioning
Option 1: Grant Admin Consent (Recommended)
Access Microsoft Entra admin center
Required Permissions by Service
| Integration | Key Permissions |
|---|---|
| Teams | Team.ReadBasic.All, ChannelMessage.Read.All, Chat.ReadWrite |
| Outlook | Mail.ReadWrite, Mail.Send |
| Excel/Word | Files.ReadWrite, Sites.ReadWrite.All |
| OneLake | https://storage.azure.com/user_impersonation |
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.
- Admin Connects Directly (Recommended)
- Non-Admin User Flow
The easiest way is for a Salesforce administrator to authenticate directly from Gumloop:
Go to your Connectors page
Visit the Salesforce connectors page in Gumloop
Click Connect and authorize
Click Connect next to Salesforce and sign in with your Salesforce admin account.
Managing the Connected App in Salesforce
- Go to Setup > Apps > Connected Apps > Manage Connected Apps
- Find the Gumloop app to view or modify settings
- 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
Related Documentation
Organization and Teams
Understand how personal spaces and teams work
User Roles & Permissions
Organization and team permission levels