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 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.
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 to fetch.
Output
The output will contain a JSON object with the team's information as retrieved from the external service. This typically includes all relevant details about the team such as its name, members, roles, and other metadata defined by the API. The exact structure depends on the external API's response schema but generally represents a single team's data.
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's API endpoint that manages groups and teams.
- The base URL and headers for API requests are expected to be set via credentials or node configuration.
Troubleshooting
- Missing or invalid Group Id or Team Id: Ensure both identifiers are correctly provided and correspond to existing entities in the external system.
- Authentication errors: Verify that the API key or authentication token is valid and has sufficient permissions to access team information.
- Network issues: Confirm that the n8n instance can reach the external API endpoint without firewall or proxy restrictions.
- Unexpected API responses: Check if the external API has changed or if rate limits have been exceeded; consult API documentation for error codes.
Links and References
- Refer to the external API’s official documentation for "Groups" and "Teams" endpoints to understand the full response structure and available fields.
- n8n documentation on configuring API credentials and handling HTTP request nodes may provide additional setup guidance.