Actions22
- Kanban Actions
- Meeting Actions
- Project Actions
- Team Actions
- User Actions
Overview
The node integrates with a Workspace API to manage team data, specifically allowing the creation of new teams within an organization. It is useful in scenarios where automated workflows need to organize users into teams programmatically, such as onboarding new employees, restructuring departments, or synchronizing team data from other systems.
For example, you could use this node to automatically create a new project team with designated leads and members when a new project is initiated in your project management system.
Properties
| Name | Meaning |
|---|---|
| Name | The name of the team to be created. (Required) |
| Description | A textual description of the team. |
| Slug | A URL-friendly identifier for the team. Must be alphanumeric and can contain dashes or underscores. (Required) |
| Team Lead IDs | List of user IDs who will be assigned as team leads. Must contain at least one ID. |
| Member IDs | List of user IDs who will be assigned as team members. |
Output
The node outputs JSON data representing the newly created team object as returned by the Workspace API. This typically includes the team's unique identifier, name, slug, description, lists of team leads and members, and possibly metadata such as creation timestamps.
If the API supports it, the output may also include status or confirmation fields indicating successful creation.
The node does not output binary data.
Dependencies
- Requires connection to the Workspace API.
- Needs an API key credential and tenant information configured in n8n credentials.
- The base URL for the API must be set in the node's credential configuration.
Troubleshooting
- Missing Required Fields: Errors may occur if required fields like "Name", "Slug", or "Team Lead IDs" are missing or empty. Ensure these are provided.
- Invalid Slug Format: The slug must be alphanumeric and may include dashes or underscores only. Invalid characters will cause API errors.
- Authentication Failures: If the API key or tenant info is incorrect or missing, authentication errors will occur.
- User IDs Not Found: Providing invalid or non-existent user IDs for team leads or members may result in errors or partial failures.
- API Connectivity Issues: Network problems or incorrect base URL settings can prevent the node from reaching the Workspace API.
To resolve these issues, verify all required inputs, confirm credential correctness, and ensure network connectivity to the API endpoint.
Links and References
- Workspace API Documentation (Replace with actual link)
- n8n Documentation on Creating Custom Nodes