​
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

​
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

​
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

Each node that requires authentication has a “Credentials to use” dropdown with options:

  • Use Workspace Default
  • Use Personal Default
  • Specific credentials you’ve added

This allows you to:

  • Run different nodes with different credentials in the same workflow
  • Mix personal and workspace credentials as needed
  • Easily switch between credentials for testing

​
Managing Credentials

​
Adding New Credentials

  1. Visit the credentials page
  2. Choose the service to authenticate with
  3. 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

  1. Multiple Email Accounts:

    • Send emails from different Gmail accounts in one flow
    • Use personal email for notifications
    • Use team email for customer communications

  2. 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

Personal Version (Using Personal Credential):

  1. Sarah duplicates the flow
  2. Toggles Gmail node to “Use Personal Default”
  3. Flow now sends from sarah@company.com
  4. 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

  1. Viewing Credentials

  2. Revoking Access

    • Simple one-click revocation
    • Immediate effect
    • All traces of auth tokens removed
    • Re-authentication required for future use

​
Security and Compliance

Gumloop is officially SOC2 Type II certified & GDPR compliant! Learn more about our security practices and certifications at our Trust Center.

​
Getting Help

​
Adding New Services

Need support for a new third-party service?

AlertsWorking With Files