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 retrieves detailed information about a specific team within a group. It is useful when you need to access metadata or configuration details of a team identified by its unique ID inside a particular group. Typical use cases include managing team settings, auditing team membership, or integrating team data into workflows for reporting or automation purposes.
Properties
| Name | Meaning |
|---|---|
| Group Id | Identifier of the Group |
| Team Id | Identifier of the Team |
Both properties are required string inputs that specify which group's team information should be fetched.
Output
The output will contain a JSON object representing the team's information as returned by the underlying API. This typically includes fields such as team name, description, members, roles, and other relevant metadata. The exact structure depends on the external service's response schema.
No binary data output is indicated.
Dependencies
- Requires an API key credential or similar authentication token configured in n8n to authorize requests.
- Depends on connectivity to the external service hosting the group and team data.
- The node uses standard HTTP headers for JSON content negotiation.
Troubleshooting
- Missing or invalid Group Id or Team Id: Ensure both identifiers are correctly provided; otherwise, the API call will fail.
- Authentication errors: Verify that the API key or authentication credentials are properly set up and have sufficient permissions.
- Network issues: Check network connectivity to the external API endpoint.
- Unexpected API responses: Confirm that the team and group IDs exist and that the API version matches expectations.
Common error messages may include authorization failures, resource not found, or bad request errors due to invalid input parameters.
Links and References
- Refer to the external API documentation for "Group Teams" and "Get Team Information" endpoints for detailed response schemas and additional options.
- n8n documentation on setting up API credentials and handling HTTP request nodes.