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.

Example use case:

• A workflow that triggers when a user attempts to authenticate via an external identity provider, then uses this node to retrieve the intent details by providing the intent ID and token, enabling further conditional logic based on the retrieved data.

Properties

Output

The node outputs a JSON object containing the response from the Zitadel API corresponding to the requested operation. For the retrieveIdentityProviderIntent operation, the output JSON includes the details of the identity provider intent fetched from Zitadel.

If the operation returns binary data (not indicated in this code), it would be included accordingly, but this specific operation deals with JSON data only.

Example output structure (simplified):

{
  "idpIntent": {
    "id": "string",
    "token": "string",
    "status": "string",
    "createdAt": "timestamp",
    ...
  }
}

Dependencies

• Requires an API authentication token credential for Zitadel (referred generically as an API key credential).
• Uses the Zitadel gRPC client libraries generated for various services.
• Connects to the Zitadel API endpoint at https://zitadel.studentcouncil.dk.
• The node depends on the nice-grpc library for gRPC communication.
• Proper configuration of the Zitadel API credentials in n8n is necessary.

Troubleshooting

• Invalid or missing credentials: If the API token is invalid or not provided, the node will fail to authenticate. Ensure the API key credential is correctly configured.
• Incorrect idpIntentId or idpIntentToken: Providing wrong or expired values will result in errors or empty responses. Verify these inputs are correct.
• Operation not found: Selecting an operation not supported by the chosen service will cause the node to return an empty JSON object.
• JSON parsing errors: Input properties that expect JSON strings must be valid JSON; otherwise, the node falls back to treating them as plain strings.
• Network issues: Connectivity problems to the Zitadel API endpoint will cause request failures.

Links and References

• Zitadel Official Documentation
• Zitadel API Reference
• gRPC Nice Client Library