Zitadel

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 information about an identity provider intent during authentication or user management workflows.
• Automating user identity verification processes by retrieving intent status or metadata.
• Integrating Zitadel's identity management capabilities into broader automation pipelines.

Practical example:

• A workflow that triggers when a new user attempts to authenticate via an external identity provider can use this node to retrieve the intent details and decide subsequent actions based on the response.

Properties

Output

The node outputs a JSON object containing the full response from the Zitadel API for the requested operation. For retrieveIdentityProviderIntent, the output JSON includes all data fields returned by the Zitadel UserService related to the specified identity provider intent.

No binary data output is produced by this node.

Example output structure (simplified):

{
  "idpIntentId": "string",
  "status": "string",
  "userInfo": { /* user-related info */ },
  "metadata": { /* additional intent metadata */ }
}

Dependencies

• Requires an API authentication token credential for Zitadel (referred generically as an API key credential).
• Connects to the Zitadel API endpoint at https://zitadel.studentcouncil.dk.
• Uses gRPC client libraries internally to communicate with Zitadel services.

Troubleshooting

• Invalid or missing credentials: Ensure the API authentication token is correctly configured in n8n credentials.
• Incorrect idpIntentId or idpIntentToken: Verify these values are accurate and correspond to existing intents in Zitadel.
• Operation not found error: Confirm that the selected Service and Operation match and that the operation exists in the Zitadel API.
• JSON parsing errors: Input properties like idpIntentId and idpIntentToken must be valid strings; malformed JSON inputs will cause failures.
• Network or connectivity issues: Check network access to the Zitadel API endpoint and firewall settings.

Links and References

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