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 deactivates a user by their User Id in the "Users" resource. It sends a PATCH request to an internal API endpoint designed to deactivate a specific user account. This is useful in scenarios where you need to programmatically disable or deactivate user accounts, for example, when automating user lifecycle management, suspending access due to policy violations, or cleaning up inactive users.
Practical examples:
- Automatically deactivate users who have not logged in for a certain period.
- Temporarily suspend user accounts during maintenance or investigation.
- Integrate with HR systems to deactivate users upon termination.
Properties
| Name | Meaning |
|---|---|
| User Id | The unique identifier of the user to be deactivated. |
| Request Id | Optional client-generated identifier to trace and debug this specific request (sent as HTTP header). |
| Correlation Id | Optional client-generated identifier to trace and debug a series of related requests (sent as HTTP header). |
Output
The node outputs JSON data representing the response from the user deactivation API call. This typically includes details about the updated user status, confirmation of deactivation, or any relevant metadata returned by the API.
No binary data output is indicated.
Dependencies
- Requires an API key credential for authentication to the Straddle API service.
- The base URL for the API is dynamically constructed based on the configured environment credential.
- The node expects the API to accept and return JSON content.
- Proper network connectivity to the Straddle API endpoint is necessary.
Troubleshooting
Common issues:
- Invalid or missing User Id will cause the API call to fail.
- Authentication errors if the API key credential is incorrect or expired.
- Network or connectivity issues preventing reaching the API endpoint.
- Missing required headers or malformed request payloads.
Error messages and resolutions:
- 401 Unauthorized: Check that the API key credential is correctly configured and valid.
- 404 Not Found: Verify that the User Id exists and is correct.
- 400 Bad Request: Ensure all required parameters are provided and properly formatted.
- Timeouts or network errors: Confirm network access and API availability.
Links and References
- Straddle API Documentation (hypothetical link)
- n8n documentation on HTTP Request Node for understanding how API calls are made within n8n nodes.