Toolzz SSO icon

Toolzz SSO

ToolzzSSO

Toolzz SSO

AI-generated

Overview

The Toolzz SSO node facilitates Single Sign-On (SSO) authentication with the Toolzz platform. It is designed to initiate an SSO redirect by sending a POST request to the Toolzz API, using institution and user details provided as input. This node is useful in scenarios where you need to automate or integrate SSO flows for users of an educational institution, such as onboarding users, automating login processes, or connecting n8n workflows to Toolzz's authentication system.

Example use cases:

  • Automating user access provisioning to Toolzz-based platforms.
  • Integrating Toolzz SSO into larger workflow automations for educational institutions.
  • Triggering SSO redirects as part of user management or onboarding pipelines.

Properties

Name Type Meaning
Url of Institution String The URL associated with the institution on Toolzz. Used as a header in the API request.
Email String The email address of the user for whom the SSO is being initiated.
Subdomain String The subdomain of the institution (not directly used in the request).
Ambiente Options The environment endpoint for the Toolzz API. Typically set to production.

Note: There is a reference to institution_code in the code, but it is not present in the defined properties. This may cause issues if the property is required by the API.

Output

The node outputs the JSON response received from the Toolzz SSO API endpoint. The structure of this output depends on the API's response, but typically includes information relevant to the SSO redirect, such as tokens, URLs, or status messages.

[
  {
    // Example fields (actual structure depends on Toolzz API)
    "redirect_url": "https://...",
    "status": "success",
    "message": "SSO redirect created"
  }
]

If the API returns binary data, it will be passed through as-is, but the primary output is expected to be JSON.

Dependencies

  • External Service: Requires access to the Toolzz API at the specified environment URL.
  • API Endpoint: ${Ambiente}/api/auth/sso/redirect
  • No credentials are configured in the node, so ensure the endpoint does not require additional authentication or that it is handled elsewhere.

Troubleshooting

  • Missing Property Error:
    The code references an institution_code parameter, which is not defined in the properties. This will likely result in an error such as:

    Cannot read property 'institution_code' of undefined

    Resolution:
    Add an "Institution Code" property to the node configuration, or ensure the API does not require it.

  • Invalid URL or Environment:
    If the "Url of Institution" or "Ambiente" values are incorrect, the API call will fail, possibly returning a 404 or connection error.
    Resolution:
    Double-check the URLs and environment selection.

  • API Response Errors:
    If the API returns an error (e.g., invalid email, missing parameters), the node will return the error message from the API.
    Resolution:
    Ensure all required fields are filled correctly and match the expected format.

Links and References

Discussion