ZitadelInstall

Overview

This node integrates with the Zitadel API, allowing users to interact with various Zitadel services such as UserService, OrganizationService, AuthService, ManagementService, AdminService, ZITADELActions, and UserSchemaService. Specifically, for the retrieveIdentityProviderIntent operation under the UserService resource, it retrieves details about a particular identity provider intent using its ID and token.

Common scenarios where this node is beneficial include:

• Fetching authentication or identity provider intent information during user login flows.
• Integrating Zitadel's identity management features into custom workflows.
• Automating retrieval of identity provider intents for auditing or processing purposes.

Practical example:

• A workflow that triggers when a new user attempts to authenticate via an external identity provider, then uses this node to retrieve the intent details to decide further actions like provisioning or access control.

Properties

Output

The node outputs a JSON object containing the response from the Zitadel API for the requested operation. For retrieveIdentityProviderIntent, the output JSON will contain the details of the identity provider intent corresponding to the provided ID and token.

No binary data output is indicated by the source code.

Example output structure (simplified):

{
  "idpIntent": {
    "id": "string",
    "token": "string",
    "status": "string",
    "createdAt": "timestamp",
    // other relevant fields returned by Zitadel API
  }
}

Dependencies

• Requires an API key credential for Zitadel (referred generically as an API authentication token).
• Uses the Zitadel gRPC client libraries generated for various services.
• Needs network access to the Zitadel API endpoint at https://zitadel.studentcouncil.dk.
• The node internally creates a gRPC client channel and attaches an authorization interceptor with the provided token.

Troubleshooting

• Invalid or missing credentials: If the API token is invalid or missing, the node will fail to authenticate. Ensure the API key credential is correctly configured in n8n.
• Incorrect idpIntentId or idpIntentToken: Providing wrong or expired values may result in errors or empty responses. Verify these inputs carefully.
• JSON parsing errors: Input properties are parsed as JSON if possible; malformed JSON strings will cause errors. Provide valid JSON or plain strings accordingly.
• Unsupported operations: If an operation name does not exist in the selected service, the node returns an empty JSON object. Double-check the operation and service names.
• Network issues: Connectivity problems to the Zitadel API endpoint will cause request failures. Check network settings and endpoint availability.

Links and References

• Zitadel Official Documentation
• Zitadel API Reference
• n8n Documentation on Creating Custom Nodes