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 an account. It is useful when you need to fetch metadata or configuration details of a team associated with an account, such as team members, roles, or permissions. Practical examples include automating reporting on team structures, synchronizing team data with other systems, or validating team existence before performing further actions.
Properties
| Name | Meaning |
|---|---|
| Account Id | Identifier of the account |
| Team Id | Identifier of the team |
Both properties are required string inputs that specify which account and which team within that account the node should query.
Output
The output will contain a JSON object representing the team information retrieved from the external service. This typically includes fields such as team name, description, members, roles, and other relevant metadata depending on the API's response schema.
No binary data output is indicated for this operation.
Dependencies
- Requires an API key credential or similar authentication token configured in n8n to access the external service.
- The node uses a base URL provided by credentials to make HTTP requests.
- The underlying implementation depends on an OpenAPI specification bundled with the node for request construction.
Troubleshooting
- Missing or invalid Account 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 read team information.
- Network or connectivity issues: Check network access to the external API endpoint.
- Unexpected response structure: If the output JSON does not match expectations, confirm that the API version and node version are compatible.
Links and References
- Refer to the external service’s official API documentation for detailed schema and additional parameters related to team information retrieval.
- Consult n8n documentation on how to configure API credentials and use custom nodes.