Understanding Credentials in Gumloop
Some Gumloop nodes require authentication with third-party services (like Gmail, Slack, etc.) to read or write data. Our multi-auth system allows you to manage multiple credentials for each service and choose the right one for each node in your workflow.
Types of Credentials at a Glance
Feature | Personal Credentials | Workspace Credentials |
---|---|---|
Visibility | Only you can see and use | All workspace members can use |
Best For | Individual projects, private accounts | Team projects, shared accounts |
Setup Location | Personal settings | Workspace settings |
When Using | Works in any workspace | Only works in the specific workspace |
Default Option | ”Use Personal Default" | "Use Workspace Default” |
When to Set Up | Immediately available | Must be configured for new workspaces |

Personal Credentials
- Private to your account
- Cannot be accessed by other workspace members
- Ideal for personal projects and flows
- Perfect for individual API keys and accounts
Workspace Credentials
Note: Workspace credentials are available to Pro users and above as part of workspace creation features.
- Shared across your workspace
- Accessible by all workspace members
- Great for team collaboration
- Ideal for shared service accounts and API keys
Important: When you create a new workspace, nodes will default to “Use Workspace Default” but no workspace credentials exist yet! You must either:
- Set up workspace credentials in the workspace settings, OR
- Switch nodes to “Use Personal Default” to use your personal credentials instead
When to Use Each Type
Personal Credentials Best For:
- Individual tasks and automations
- Personal email communications
- Testing and development work
- Private API access
- Workflows you don’t want to share
Workspace Credentials Best For:
- Team-wide automations
- Shared company email accounts
- Production environments
- Shared API resources
- Customer-facing workflows
Default Credentials
You can set two types of defaults to streamline your workflow:Default Personal Credential
- Your go-to personal credential for a service
- Used when “Use Personal Default” is selected
- Only affects your account
- Useful for consistent personal automation
Default Workspace Credential
- The workspace’s primary credential
- Used when “Use Workspace Default” is selected
- Applies to all workspace members
- Perfect for standardizing team workflows
Using Credentials in Nodes

- Use Workspace Default
- Use Personal Default
- Specific credentials you’ve added
- Run different nodes with different credentials in the same workflow
- Mix personal and workspace credentials as needed
- Easily switch between credentials for testing
Credential Setup Workflow
Managing Credentials
Adding New Credentials
- Visit the credentials page
- Choose the service to authenticate with
- Follow the OAuth2 flow or enter API keys
Authentication Methods
-
OAuth2 (Most services)
- Secure authorization flow
- No manual token management
- Example: Gmail, Slack
-
Direct Credentials (Some services)
- Manual API key entry
- Examples:
- OpenAI: Paste your API key
- AWS: Enter access credentials for S3 permissions
Multi-Auth Workflows
The multi-auth system enables powerful workflow configurations:Example Scenarios
-
Multiple Email Accounts:
- Send emails from different Gmail accounts in one flow
- Use personal email for notifications
- Use team email for customer communications
-
Mixed API Usage:
- Personal OpenAI account for testing
- Workspace OpenAI account for production
- Different API keys for different environments
Shared Flows & Personal Credentials
Using Personal Credentials in Shared Workflows
Even when working in a shared workspace, you can use your personal credentials:- Simply toggle to “Use Personal Default” in any node
- The flow will run using your personal credential instead of the workspace one
- Other team members won’t be able to access your personal credentials
Example: Marketing Team Email Flow
Imagine a shared email campaign flow in your marketing workspace: Original Flow (Using Workspace Credential):- Team uses shared marketing@company.com email
- All team members can run the flow
- Everyone sees the same results
- Sarah duplicates the flow
- Toggles Gmail node to “Use Personal Default”
- Flow now sends from sarah@company.com
- Only Sarah can run this version successfully
Important Notes:
- A flow using personal credentials will use the personal credentials of the person running the flow
- If another team member tries to run Sarah’s flow:
- It’ll run using their personal account
- They’ll get an authentication error if they don’t have the available credential
- This enables team members to:
- Use shared flow templates
- Customize them for personal use
- Maintain privacy of personal accounts
Pro Tip: When creating shared workflows, start with workspace credentials. Team members can always duplicate and switch to personal credentials later.
Credential Management
-
Viewing Credentials
- See all personal credentials on the credentials page
- Check last refresh time
-
Revoking Access
- Simple one-click revocation
- Immediate effect
- All traces of auth tokens removed
- Re-authentication required for future use
Microsoft Office Admin Setup
For organizations using Microsoft Office integrations (Teams, Outlook, Excel, Word, OneLake), administrators need to configure consent in Microsoft Entra ID before users can authenticate.Quick Setup Options
Option 1: Tenant-Wide Consent (Recommended)- Go to Microsoft Entra admin center
- Navigate to Entra ID > Enterprise apps > All applications

- Search for Gumloop (client ID:
0e6d512b-3ac5-452a-a4d8-a3e1b5b9b721
)

- Under Security > Permissions, click Grant admin consent
- Go to Entra ID > Enterprise apps > Consent and permissions > Admin consent settings
- Set Users can request admin consent to Yes

- Configure reviewers and approval workflow
App Provisioning
If Gumloop isn’t in your tenant yet, use this URL (replace{tenant}
with your tenant ID):
Required Permissions
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 |
Note: You must be a Global Administrator, Cloud Application Administrator, or Application Administrator to grant consent.