Get Team

Retrieves information about the current Lemlist team, including team members, settings, and account details.

Common Properties

Name - The custom name of the node.
Color - The custom color of the node.
Delay Before (sec) - Waits in seconds before executing the node.
Delay After (sec) - Waits in seconds after executing node.
Continue On Error - Automation will continue regardless of any error. The default value is false.

info

If the ContinueOnError property is true, no error is caught when the project is executed, even if a Catch node is used.

Inputs

Client Id - (Optional) The client identifier returned from the Connect node. If not provided, you must provide Credentials instead.

Options

Credentials - (Optional) The Lemlist API key credential. Provide this if you're not using the Connect/Disconnect pattern. If both Client Id and Credentials are provided, Credentials takes priority.
User Url - (Optional) User URL filter for retrieving specific team member information.

Output

Team - An object containing comprehensive team information returned by the Lemlist API, including team members, settings, and account details.

How It Works

The Get Team node retrieves information about your Lemlist workspace. When executed, the node:

Validates authentication (either via Client ID or direct credentials)
Constructs a GET request to the Lemlist /api/team endpoint
Sends the authenticated request to the Lemlist API
Processes the response and returns the team data
Outputs the team information as a structured object

This node is useful for:

Validating API credentials
Retrieving team member information
Accessing account settings and limits
Building team management dashboards
Auditing team access and permissions

Requirements

A valid Lemlist account
Either a Client ID from the Connect node OR API credentials
Appropriate API permissions to access team information

Error Handling

The node will return specific errors in the following cases:

ErrInvalidArg: Neither Client ID nor valid credentials were provided
ErrInternal: Network errors or failed HTTP requests
HTTP Status Errors: If the API returns a non-2xx status code (e.g., 401 Unauthorized, 403 Forbidden)

Usage Examples

Example 1: Using Connect/Disconnect Pattern

Retrieve Team Information:

1. Connect Node
   └─> Output: client_id = "abc123"

2. Get Team Node
   └─> Input: client_id = "abc123"
   └─> Output: team = {
         "name": "Marketing Team",
         "users": [
           {"email": "user@example.com", "role": "admin"},
           {"email": "member@example.com", "role": "member"}
         ],
         "plan": "professional",
         "limits": {...}
       }

3. Disconnect Node
   └─> Input: client_id = "abc123"

Example 2: Direct Credentials (Without Connect)

Quick Team Info Lookup:

Get Team Node
└─> Credentials: [Lemlist API Key]
└─> Output: team = {
      "name": "Sales Team",
      "users": [...],
      "plan": "enterprise"
    }

Example 3: Validate API Credentials

Test Connection Flow:

Try:
  └─> Get Team Node
      └─> Credentials: [Lemlist API Key]
      └─> Output: team (if successful, credentials are valid)

Catch:
  └─> Log: "Invalid Lemlist credentials"
  └─> Send notification to admin

Practical Automation Scenarios

Scenario 1: Team Audit Report

Daily team access audit:

1. Get Team
   └─> Retrieve current team members

2. Compare with authorized users list
   └─> Identify unauthorized access

3. Generate audit report
   └─> Email to security team

4. Log results to database

Scenario 2: Account Limit Monitoring

Monitor API usage and limits:

1. Get Team
   └─> Extract: team.limits

2. Check remaining quotas
   └─> If usage > 80%:
       └─> Send alert to admin
       └─> Pause new campaigns

3. Log usage metrics
   └─> Store in monitoring database

Scenario 3: Multi-Account Management

Manage multiple Lemlist accounts:

For each account in accounts_list:
  1. Get Team
     └─> Using account's credentials

  2. Extract team information
     └─> name, plan, user_count

  3. Update dashboard
     └─> Display all accounts in central view

  4. Check for anomalies
     └─> Unexpected users, plan changes

Team Object Structure

The team output typically includes:

{
  "name": "Your Team Name",
  "users": [
    {
      "email": "user@example.com",
      "role": "admin",
      "firstName": "John",
      "lastName": "Doe"
    }
  ],
  "plan": "professional",
  "limits": {
    "emailsSent": 1000,
    "emailsLimit": 5000,
    "activeCampaigns": 5,
    "maxCampaigns": 10
  },
  "settings": {
    "timezone": "America/New_York",
    "workingHours": {...}
  }
}

Note: The exact structure may vary based on your Lemlist plan and API version.

Usage Notes

This node does not modify any data - it's a read-only operation
The team information includes all team members and their roles
You can use this node to validate credentials before performing other operations
The response structure may vary depending on your Lemlist account type and plan
No pagination is needed as this returns complete team information in a single response
The User Url option is typically optional and rarely used

Best Practices

Use Get Team as a health check before running complex automation workflows
Cache team information if you need to reference it multiple times in a flow
Implement error handling to gracefully handle credential or permission issues
For credential validation, prefer Get Team over Connect as it doesn't create a persistent session
Monitor changes in team data to detect unauthorized access or configuration drift
Use the team limits information to implement smart rate limiting in your automations

Common Errors and Solutions

Error: "Response Status: 401 Unauthorized"

Cause: Invalid or expired API key
Solution: Verify your API key in Lemlist settings and update the credential in Robomotion

Error: "Response Status: 403 Forbidden"

Cause: Insufficient permissions to access team information
Solution: Ensure your API key has the necessary permissions, or contact your Lemlist admin

Error: "Either API Key credentials or Client ID must be provided"

Cause: Neither Client ID nor Credentials were provided
Solution: Provide either a Client ID from Connect node or direct API credentials

Error: "Failed to parse response"

Cause: Unexpected response format from Lemlist API
Solution: Check Lemlist API status, verify your account is active, and ensure you're using the latest package version

Tips for Effective Use

Credential Validation: Use Get Team at the start of workflows to validate credentials before performing write operations
Team Monitoring: Schedule periodic checks to monitor team composition and detect unauthorized changes
Quota Management: Extract and monitor API limits to avoid hitting rate limits during automation
Multi-Workspace: Build dashboards that aggregate team info from multiple Lemlist workspaces
Audit Trail: Log team information changes over time for compliance and security auditing
Debugging: When troubleshooting other Lemlist operations, use Get Team to verify account status and permissions

Security Considerations

Team information may contain sensitive data about users and account settings
Restrict access to automation flows that retrieve team information
Don't log or expose team member email addresses unnecessarily
Use secure storage for any team data you cache or persist
Regularly audit who has access to Lemlist API credentials

Common Properties​

Inputs​

Options​

Output​

How It Works​

Requirements​

Error Handling​

Usage Examples​

Example 1: Using Connect/Disconnect Pattern​

Example 2: Direct Credentials (Without Connect)​

Example 3: Validate API Credentials​

Practical Automation Scenarios​

Scenario 1: Team Audit Report​

Scenario 2: Account Limit Monitoring​

Scenario 3: Multi-Account Management​

Team Object Structure​

Usage Notes​

Best Practices​

Common Errors and Solutions​

Tips for Effective Use​

Security Considerations​