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 allows you to resend a user invite by specifying the unique identifier of the invite. It is useful in scenarios where an initial invitation email or notification was not received by the user, or if the invite needs to be reissued for any reason (e.g., expired invite, lost email). For example, an administrator can trigger this node to resend an invitation to a new team member who has not yet accepted their invite.
Properties
| Name | Meaning |
|---|---|
| User Invite Id | The unique identifier of the user invite that you want to resend. This is required. |
| Request Id | Optional client-generated identifier used to trace and debug the request. Sent as a header. |
| Correlation Id | Optional client-generated identifier to trace and debug a series of related requests. Sent as a header. |
Output
The output JSON contains the response from the API after attempting to resend the user invite. Typically, it will include confirmation details such as status messages or metadata about the resent invite. There is no binary data output for this operation.
Dependencies
- Requires an API key credential for authentication with the external service.
- The node uses HTTP headers
request-idandcorrelation-idoptionally for tracing requests. - The base URL for the API is dynamically set based on the environment credential parameter.
Troubleshooting
Common issues:
- Invalid or missing User Invite Id will cause the operation to fail.
- Network or authentication errors if the API key credential is incorrect or missing.
- If the invite was already accepted or expired beyond resending, the API might return an error or no action.
Error messages:
- "User Invite Id is required" — Ensure the ID is provided.
- Authentication errors — Verify the API key credential is correctly configured.
- API rate limits or server errors — Retry after some time or check API status.
Links and References
- Refer to the external service's API documentation for detailed information on user invites and resend operations.
- Use standard HTTP tracing tools to debug requests using the optional
Request IdandCorrelation Idheaders.