Skip to main content

Create Team

Creates a new Microsoft Teams team with specified name, description, and template.

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 ContinueOnError property is true, no error is caught when the project is executed even if Catch node is used.

Input​

  • Client Id - The client ID from the Connect node. Optional if using direct credentials.
  • Display Name - The name of the team (required). This will be visible to all team members.
  • Description - A description of the team's purpose (required). Helps users understand what the team is for.

Output​

  • n/a - No output (team is created asynchronously by Microsoft)

Options​

  • Credentials - OAuth2 credentials JSON (optional if using Client ID). Allows direct authentication without Connect node.
  • Template Name - The template to use for team creation. Defaults to "standard" if not specified.
    • standard - Default team template with basic channels
    • Other templates may be available in your organization
note

Team creation is asynchronous. After this node completes, the team may take a few seconds to appear in Microsoft Teams.

How It Works​

The Create Team node:

  1. Sends a team creation request to Microsoft Graph API
  2. Uses the specified template to configure default channels and settings
  3. Returns immediately (actual team provisioning happens asynchronously)
  4. Team will be available for use within a few seconds

Examples​

Create Standard Team​

Create a basic team for project collaboration:

// Using Connect node
client_id = "your-client-id"
display_name = "Project Alpha Team"
description = "Collaboration space for Project Alpha"

// Create Team node will create the team
// Template: standard (default)

Create Team for Event​

Create a team for a specific event:

display_name = "Annual Conference 2025"
description = "Planning and coordination for annual company conference"

// Use descriptive names so team members immediately understand the purpose

Create Multiple Teams​

Automate team creation for multiple projects:

// Read project list from Excel or data table
projects = [
    {name: "Project Alpha", desc: "Customer portal development"},
    {name: "Project Beta", desc: "Mobile app redesign"},
    {name: "Project Gamma", desc: "Infrastructure upgrade"}
]

// Loop through projects
for (project of projects) {
    // Create Team node
    // Display Name: project.name
    // Description: project.desc

    // Add delay between creations
    // Wait 5 seconds
}

Using Direct Credentials​

Create team without using Connect node:

// Credentials from vault
credentials = {
    "client_id": "your_client_id",
    "client_secret": "your_client_secret",
    "tenant_id": "common"
}

display_name = "Marketing Team"
description = "Marketing department collaboration"

// Create Team node
// Credentials: credentials (from vault)
// Client Id: (leave empty)

Tips for Effective Use​

  • Naming convention: Use clear, consistent naming for teams (e.g., "Department - Purpose")
  • Detailed descriptions: Provide meaningful descriptions to help users understand team purpose
  • Template selection: Use "standard" template for most cases
  • Batch creation: Add delays between creating multiple teams to avoid rate limiting
  • Async awareness: Remember that team appears after a few seconds, not instantly
  • Permissions: Ensure the authenticated user has rights to create teams
  • Verification: Use ListTeams to verify team creation

Common Errors and Solutions​

"Display Name cannot be empty"​

Cause: The Display Name input is not provided.

Solution: Provide a valid team name:

display_name = "My Team Name"
// Must not be empty or whitespace

"Description cannot be empty"​

Cause: The Description input is not provided.

Solution: Provide a meaningful description:

description = "This team is for..."
// Must not be empty or whitespace

"Either Credentials or Client ID must be provided"​

Cause: Neither credentials nor client ID was supplied.

Solution: Use one of these approaches:

// Option 1: Use Connect node
client_id = message.client_id

// Option 2: Use direct credentials
// Set Credentials option to vault credential

Permission Denied / Unauthorized​

Cause: User doesn't have permission to create teams.

Solution:

  • Ensure user is allowed to create teams in your organization
  • Check Azure AD application has required permissions
  • Verify user is not a guest account
  • Contact your IT admin to grant team creation rights

Rate Limiting​

Cause: Creating too many teams too quickly.

Solution:

// Add delays between team creations
for (team of teams) {
    // Create Team

    // Delay 5-10 seconds
    await delay(5000)
}

Best Practices​

  1. Naming standards: Establish and follow team naming conventions
  2. Descriptive info: Always provide clear, helpful descriptions
  3. Rate awareness: Don't create many teams in rapid succession
  4. Verification: Verify team creation completed before adding channels
  5. Error handling: Use Try-Catch to handle creation failures gracefully
  6. Audit logging: Log team creation for tracking and compliance
  7. Template consistency: Use consistent templates for similar team types
  8. Async operations: Allow time for team provisioning before subsequent operations