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 member within a group team. It is useful when you need to display or process the response object of a single team member, for example, to verify membership details, roles, or status within a team in an organizational context.
Practical examples include:
- Fetching user details for auditing or reporting purposes.
- Displaying team member information in a dashboard.
- Integrating with other systems that require up-to-date team member data.
Properties
| Name | Meaning |
|---|---|
| Group Id | Identifier of the Group. Specifies which group the team belongs to. |
| Team Id | Identifier of the team within the group. |
| Member Id | Identifier of the member (userId in Payhawk). Specifies the exact team member to fetch. |
Output
The output contains a JSON object representing the detailed response of the specified team member within the team. This typically includes all relevant member attributes as returned by the API, such as user identifiers, roles, permissions, and possibly metadata related to their membership.
If the node supports binary data output, it would be related to any files or attachments associated with the team member, but this is not indicated in the provided code snippet.
Dependencies
- Requires an API key credential for authentication with the external service (Payhawk API).
- The base URL for the API must be configured in the node credentials.
- Uses the OpenAPI specification defined in
payhawk.api.jsonfor request construction.
Troubleshooting
- Missing or invalid IDs: Ensure that the Group Id, Team Id, and Member Id are correctly provided and correspond to existing entities in the system.
- Authentication errors: Verify that the API key credential is valid and has sufficient permissions.
- Network issues: Check connectivity to the API endpoint and ensure the base URL is correctly set.
- Unexpected response structure: Confirm that the API version matches the expected schema used by the node.
Links and References
- Payhawk API Documentation (example placeholder, replace with actual)
- n8n OpenAPI Node integration documentation: https://docs.n8n.io/integrations/creating-nodes/openapi/