Winker Delete NodeInstall

Overview

The Winker Delete Node is designed to inactivate a user in the Winker system by making an HTTP POST request to the Winker API. This node is useful in automation scenarios where you need to programmatically deactivate users, such as offboarding employees, managing access control, or integrating with HR systems.

Practical examples:

• Automatically inactivate a user when they leave an organization.
• Integrate with other n8n workflows to manage user lifecycle events.
• Batch process multiple user deactivations based on external triggers.

Properties

Output

• The output will contain a json field for each input item, populated with the response data from the Winker API after attempting to inactivate the user.
• The structure of the json output depends on the Winker API's response to the inactivation request.

Dependencies

• External Service: Requires access to the Winker API at https://api.winker.com.br/v1/users/inactivate.
• API Key: A valid "Token De Autorização" (Authorization Token) is required for authentication.
• n8n Configuration: No special configuration beyond standard node setup.

Troubleshooting

Common Issues:

• Invalid Authorization Token: If the provided token is invalid or expired, the API will likely return an authentication error.
• Missing or Invalid User ID: If the "ID Do Usuario" is missing or incorrect, the API may return an error indicating the user was not found.
• Network Errors: Connectivity issues with the Winker API endpoint can cause failures.

Error Handling:

• The node throws errors using n8n's NodeOperationError. Error details are logged to the console and surfaced in the workflow execution log.
• Typical error messages may include:
  • 401 Unauthorized: Check your "Token De Autorização".
  • 404 Not Found: Verify the "ID Do Usuario" exists.
  • 500 Internal Server Error: Retry later or contact Winker support.

Links and References

• Winker API Documentation (if available)
• n8n Documentation
• Axios Documentation