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 an account. It is useful when you need to fetch metadata or configuration details of a team associated with an account, such as for auditing, reporting, or integration purposes. For example, you might use this node to get the team name, members, roles, or other attributes before performing further automation or synchronization tasks.
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 to query.
Output
The output will be a JSON object containing the team information retrieved from the external service. This typically includes fields describing the team's attributes such as its ID, name, members, roles, and other relevant metadata. The exact structure depends on the external API's response schema but generally provides comprehensive details about the specified team.
No binary data output is expected from 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 and headers preset for JSON communication.
- The external service must support the endpoint to get team information by account and team identifiers.
Troubleshooting
- Missing or invalid Account Id or Team Id: Ensure both IDs are correctly provided and correspond to existing entities in the external system.
- Authentication errors: Verify that the API key or authentication credentials are correctly set up and have sufficient permissions.
- Network or connectivity issues: Check network access to the external API endpoint.
- Unexpected response format: Confirm that the external API has not changed its response schema, which could cause parsing errors.
Links and References
- Refer to the external service’s official API documentation for "Get Team Information" endpoint details.
- n8n documentation on setting up API credentials and using HTTP request nodes may provide additional context.