Actions81
- Users Actions
- Organizations Actions
- Representatives Actions
- Bridge Actions
- Platforms Actions
- Tools Actions
- User Invites Actions
- Customers Actions
- Paykeys Actions
- Reports Actions
- Charge Actions
- Funding Events Actions
- Payments Actions
- Payout Actions
- Accounts Actions
- Get Account By Id
- put__v1_accounts_account_id
- Create Account
- get__v1_accounts
- post__v1_accounts_account_id_onboard
- post__v1_accounts_account_id_simulate
- patch__v1_internal_accounts_account_id
- get__v1_internal_accounts_account_id
- patch__v1_internal_accounts_account_id_status
- get__v1_internal_accounts_account_id_settings
- Capability Requests Actions
- Linked Bank Accounts Actions
Overview
This node operation retrieves detailed information about a specific user invite by its unique identifier. It is useful in scenarios where you need to fetch the status or details of an invitation sent to a user, for example, to verify if the invite is still valid, check who it was sent to, or audit invite history.
Practical examples include:
- Automating workflows that require confirmation of user invites before proceeding.
- Integrating with user management systems to synchronize invite statuses.
- Debugging or auditing invite-related issues by fetching invite metadata.
Properties
| Name | Meaning |
|---|---|
| User Invite Id | The unique identifier of the user invite to retrieve. This is required to specify which invite to get. |
| Request Id | Optional client-generated identifier used to trace and debug this particular request. |
| Correlation Id | Optional client-generated identifier used to trace and debug a series of related requests. |
Output
The output JSON contains the full details of the user invite identified by the provided ID. This typically includes all metadata associated with the invite such as invitee information, status, timestamps, and any other relevant fields defined by the API.
No binary data output is indicated for this operation.
Dependencies
- Requires an API key credential for authentication with the external service.
- The base URL for API requests is dynamically set based on the configured environment.
- The node expects JSON responses from the API.
Troubleshooting
- Missing or invalid User Invite Id: The operation requires a valid invite ID; ensure this is provided and correctly formatted.
- Authentication errors: Verify that the API key credential is correctly configured and has necessary permissions.
- Network or connectivity issues: Check network access to the API endpoint and confirm the environment setting is correct.
- Request tracing headers not working: If using
Request IdorCorrelation Idfor debugging, ensure these are unique and properly propagated.
Common error messages might include:
- "Invite not found" — indicates the specified invite ID does not exist.
- "Unauthorized" — indicates issues with API credentials.
- "Bad Request" — may indicate malformed input parameters.
Resolving these usually involves verifying input values, credentials, and network connectivity.
Links and References
- Refer to the external API documentation for user invites for detailed schema and field descriptions.
- n8n documentation on how to configure API key credentials and use HTTP request nodes for similar operations.