ToolzzLogout icon

ToolzzLogout

Make Logout Toolzz API

Overview

The ToolzzLogout node is designed to log out a user from the Toolzz API. It sends a POST request to the /api/auth/logout endpoint of the selected environment, using the provided access token for authentication. This node is useful in workflows where you need to programmatically terminate a user's session with the Toolzz platform, such as after completing a series of automated actions or when enforcing security policies.

Practical examples:

  • Logging out users after automated data synchronization.
  • Ensuring sessions are closed at the end of an n8n workflow for compliance.
  • Remotely terminating user sessions in response to certain triggers (e.g., account deactivation).

Properties

Name Type Meaning
AccessToken String The access token used to authenticate the logout request.
Ambiente Options Selects the environment (Prod, Homol, Release) to which the logout request will be sent.

Output

The node returns the JSON response from the Toolzz API's logout endpoint. The structure of this output depends on the API's response, but typically it may include fields indicating the success or failure of the logout operation. Example output might look like:

[
  {
    "success": true,
    "message": "Logged out successfully"
  }
]

Dependencies

  • External Service: Requires access to the Toolzz API.
  • API Key/Token: A valid AccessToken is required.
  • Network: The selected environment URL must be reachable from the n8n instance.

Troubleshooting

  • Invalid AccessToken: If the access token is missing or invalid, the API may return an authentication error. Ensure the token is current and correct.
  • Incorrect Environment: Selecting the wrong environment (Ambiente) could result in failed requests if the endpoint is not available or configured differently.
  • Network Issues: If the n8n instance cannot reach the specified URL, the request will fail. Check network/firewall settings.

Common error messages:

  • 401 Unauthorized: The access token is invalid or expired. Obtain a new token.
  • 404 Not Found: The endpoint URL is incorrect; verify the selected environment.
  • Connection refused or timeout errors: The environment server is unreachable.

Links and References

Discussion