Actions99
- Expenses Actions
- Group Accounts Actions
- Group Account Codes Actions
- Accounts Actions
- Purchase Orders Actions
- Get A List Of Purchase Orders
- Create A New Purchase Order
- Get A Purchase Order
- Update A Purchase Order
- Open A Purchase Order
- Get A List Of Purchase Orders Items For A Specific Purchase Order
- Create A Purchase Order Item
- Get A Purchase Order Item
- Update A Purchase Order Item
- Delete A Purchase Order Item
- Get A List Of Goods Received Notes For A Specific Purchase Order
- Create A Goods Received Note
- Attach A File To A Goods Received Note
- Delete A Goods Received Note
- Suppliers Actions
- Fund Accounts Actions
- Cards Actions
- Expense Categories Actions
- Tax Rates Actions
- Amortizations Actions
- Account Teams Actions
- Account Codes Actions
- External Teams Actions
- Custom Fields Actions
- Get Custom Fields
- Create A New Custom Field
- Get Custom Field
- Update Custom Field
- Delete A Custom Field And All Its Values
- Get Custom Field Values
- Create A Custom Field Value
- Delete Custom Field Values
- Get A Custom Field Value
- Update A Custom Field Value
- Delete A Custom Field Value
- Get Managers For A Specific Custom Field Value
- Adds Managers For A Specific Custom Field Value
- Replaces Managers For A Specific Custom Field Value
- Removes Managers For A Specific Custom Field Value
- Webhook Subscriptions Actions
- Group Teams Actions
Overview
This node operation creates a new team within an account in an external system. It is useful for automating the management of organizational structures by programmatically adding teams under specific accounts. For example, a company using this node can automatically create teams when onboarding new departments or projects, ensuring consistent team setup without manual intervention.
Properties
| Name | Meaning |
|---|---|
| Account Id | Identifier of the account under which the team will be created (required). |
| Name | Name of the team to be created. |
| External Id | Unique identifier of the team in the external system, useful for synchronization. |
| Parent Id | Unique identifier of the parent team, allowing hierarchical team structures. |
Output
The node outputs JSON data representing the newly created team object as returned by the external API. This typically includes the team's identifiers, name, and any metadata provided by the service. The output does not include binary data.
Dependencies
- Requires an API key credential or similar authentication token configured in n8n to authorize requests to the external system.
- The base URL for the API must be set in the node credentials or environment variables.
- The node depends on an OpenAPI-based client internally to handle the request construction and response parsing.
Troubleshooting
- Missing required Account Id: The operation requires the Account Id property; ensure it is provided to avoid validation errors.
- Authentication errors: If the API key or authentication token is missing or invalid, the node will fail to connect. Verify credentials are correctly configured.
- Invalid Parent Id: Providing a non-existent parent team ID may cause the API to reject the request. Confirm the parent team exists before referencing it.
- API rate limits or network issues: Temporary failures might occur due to rate limiting or connectivity problems. Retrying after some time or checking network settings can help.
Links and References
- Refer to the external system’s API documentation for details on team creation endpoints and required fields.
- Consult n8n documentation on how to configure API credentials and use OpenAPI-based nodes.