Actions99
- Group Accounts Actions
- Group Account Codes Actions
- Accounts Actions
- Expenses 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 a specified account. It is useful in scenarios where you want to programmatically organize users or resources into teams under an account, such as managing departments, project groups, or organizational units in a business system. For example, you might use this node to add a new sales team to an existing account or create a support team with a unique external identifier for integration with other systems.
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 an external system, useful for synchronization purposes. |
| Parent Id | Unique identifier of the parent team, allowing hierarchical team structures. |
Output
The output JSON contains the details of the newly created team as returned by the API. This typically includes the team's identifiers, name, and any metadata provided by the service. The node does not output binary data.
Dependencies
- Requires an API key credential or similar authentication token configured in n8n to authorize requests.
- Depends on connectivity to the external service's API endpoint specified in the node credentials.
- The base URL for the API is expected to be set in the node's credential configuration.
Troubleshooting
- Missing Required Fields: If "Account Id" is not provided, the node will likely fail to create a team. Ensure all required fields are filled.
- Authentication Errors: Invalid or missing API credentials will cause authorization failures. Verify that the API key or token is correctly configured.
- API Endpoint Issues: Network problems or incorrect base URL settings can prevent communication with the API.
- Duplicate External Ids: Using an external ID that already exists may cause conflicts; ensure uniqueness if used.
- Parent Id Validation: Providing an invalid parent team ID may result in errors; confirm the parent team exists.
Links and References
- Refer to the external service’s API documentation for detailed information about team creation endpoints and field requirements.
- Consult n8n documentation on how to configure API credentials and handle HTTP request nodes for further customization.