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 cancel a previously sent user invite within the "User Invites" resource. It is useful in scenarios where an invitation to a user needs to be revoked before it is accepted, such as when the invite was sent by mistake or the user's access should no longer be granted.
Practical examples include:
- Revoking an invitation sent to a contractor who will no longer join a project.
- Canceling a user invite if the email address was incorrect.
- Managing user onboarding workflows by programmatically withdrawing invites that are no longer valid.
Properties
| Name | Meaning |
|---|---|
| User Invite Id | The unique identifier of the user invite to cancel. This is required to specify which invite to revoke. |
| Request Id | Optional client-generated identifier used to trace and debug this specific request. |
| Correlation Id | Optional client-generated identifier used to trace and debug a series of related requests. |
Output
The output JSON contains the response from the API after attempting to cancel the user invite. Typically, this will include confirmation of cancellation or details about the invite status. The exact structure depends on the API response but generally includes fields indicating success or failure and any relevant metadata.
No binary data output is expected for this operation.
Dependencies
- Requires an API key credential for authentication with the Straddle API.
- The node uses the base URL dynamically set based on the configured environment (e.g., sandbox or production).
- Proper network connectivity to the Straddle API endpoint is necessary.
Troubleshooting
- Invalid User Invite Id: If the provided invite ID does not exist or is malformed, the API may return an error indicating the invite cannot be found. Verify the invite ID is correct.
- Authentication Errors: Missing or invalid API credentials will cause authentication failures. Ensure the API key credential is correctly configured.
- Request/Correlation Ids: These are optional but can help trace issues in logs. If debugging problems, use these IDs to correlate requests with server logs.
- API Endpoint Issues: Make sure the environment parameter is set correctly to target the right API base URL.
Links and References
- Straddle API Documentation (general reference for API endpoints and usage)
- n8n documentation on creating custom nodes