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 single team member within a specific account team. It is useful when you need to display or process the response object of an individual team member, for example, to verify their role, status, or other attributes in the context of an account's team management.
Practical scenarios include:
- Fetching details of a particular user in a team to audit permissions.
- Displaying team member information in a dashboard or report.
- Integrating with other systems that require up-to-date team member data.
Properties
| Name | Meaning |
|---|---|
| Account Id | Identifier of the account from which the team member belongs. |
| Team Id | Identifier of the team within the account. |
| Member Id | Identifier of the team member (corresponds to the user ID in the external system). |
Output
The node outputs a JSON object representing the detailed response of the specified team member. This typically includes all available fields returned by the external API about that member, such as their identifiers, roles, permissions, and possibly metadata related to their membership in the team.
If the node supports binary data output, it would be related to any attachments or files associated with the team member, but based on the provided code and properties, this operation focuses on JSON data only.
Dependencies
- Requires an API key credential for authenticating requests to the external service managing accounts and teams.
- The base URL for the API must be configured in the node credentials.
- Depends on the external API described in the bundled OpenAPI specification (
payhawk.api.json), which defines the endpoints and operations.
Troubleshooting
- Missing or invalid identifiers: Ensure that
Account Id,Team Id, andMember Idare 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 or API errors: Check connectivity and API availability; handle rate limits or downtime gracefully.
- Unexpected response structure: If the API changes, the node might not parse the response correctly; update the node or API spec accordingly.
Links and References
- Refer to the external API documentation for detailed schema and examples of the team member response object.
- Consult n8n documentation on how to configure API credentials and use custom nodes with OpenAPI specifications.