Zitadel

Overview

This node interacts with the Zitadel API, a platform for identity and access management. Specifically, the retrieveIdentityProviderIntent operation under the "Default" resource (mapped to the "UserService") retrieves information about an Identity Provider Intent by its ID and token.

Common scenarios where this node is useful include:

• Fetching details of an ongoing or completed identity provider authentication intent.
• Integrating Zitadel's identity provider flows into custom workflows.
• Automating user authentication or authorization processes based on identity provider intents.

For example, after initiating an identity provider login flow, you can use this node to retrieve the intent status or data by providing the intent ID and token.

Properties

Output

The node outputs a JSON object representing the response from the Zitadel API for the requested Identity Provider Intent. This typically includes all relevant details about the intent such as its status, associated user information, timestamps, and any other metadata provided by the API.

No binary data output is produced by this operation.

Example output structure (simplified):

{
  "id": "string",
  "status": "string",
  "userId": "string",
  "createdAt": "timestamp",
  "updatedAt": "timestamp",
  // ... other intent-specific fields
}

Dependencies

• Requires an API authentication token credential for Zitadel (referred generically as an API key or personal access token).
• The node uses the Zitadel gRPC client libraries internally to communicate with the Zitadel API endpoint at https://zitadel.studentcouncil.dk.
• No additional external dependencies are required beyond the configured Zitadel credentials in n8n.

Troubleshooting

• Invalid or missing credentials: Ensure that the Zitadel API token is correctly configured in the node credentials. Missing or expired tokens will cause authorization failures.
• Incorrect idpIntentId or idpIntentToken: Providing invalid or mismatched intent IDs or tokens will result in errors or empty responses. Double-check these values.
• Network or endpoint issues: Verify network connectivity to the Zitadel API endpoint (https://zitadel.studentcouncil.dk) and ensure no firewall or proxy blocks exist.
• Parsing errors: Input properties like idpIntentId and idpIntentToken are expected as strings. Supplying malformed JSON or unexpected formats may cause parsing errors.

Common error messages might include authorization errors, not found errors for the intent ID, or validation errors for input parameters. Resolving them usually involves verifying credentials, input correctness, and network accessibility.

Links and References

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