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 member within a particular team of a group. It is useful when you need to display or process the response object representing a single team member's data in the context of group teams management. For example, it can be used to fetch user details for access control, auditing, or displaying member profiles in an application integrated with the service.
Properties
| Name | Meaning |
|---|---|
| Group Id | Identifier of the Group to which the team belongs. |
| Team Id | Identifier of the specific team within the group. |
| Member Id | Identifier of the member (userId in Payhawk) whose details are to be retrieved. |
Output
The output contains a JSON object representing the detailed response of the specified team member within the given team and group. This typically includes all relevant member attributes as returned by the API, such as user identifiers, roles, permissions, status, and other metadata associated with that team member.
If the node supports binary data output, it would represent any files or attachments related to the team member, but based on the provided code and properties, the primary output is JSON data describing the member.
Dependencies
- Requires an API key credential for authenticating requests to the external service.
- The node depends on the external API endpoint corresponding to group teams and members.
- Proper configuration of the base URL and authentication credentials in n8n is necessary for successful execution.
Troubleshooting
- Missing or invalid identifiers: Ensure that the Group Id, Team Id, and Member Id 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 member data.
- Network issues: Check connectivity to the external API endpoint and confirm that the base URL is correctly configured.
- Unexpected response structure: If the output JSON does not match expectations, verify if the API version or schema has changed.
Links and References
- Refer to the external service’s official API documentation for "Group Teams" and "Team Members" endpoints for detailed schema and examples.
- n8n documentation on creating and configuring API credentials and HTTP request nodes.