0-CodeKit

Overview

The 0-CodeKit node, when configured with the Business resource and the Verify BIC operation, validates a provided Bank Identifier Code (BIC). This is useful for workflows that need to check if a BIC is valid before proceeding with financial transactions, onboarding partners, or integrating with banking systems.

Practical examples:

• Verifying user-provided BICs in a customer onboarding process.
• Ensuring payment details are correct before initiating wire transfers.
• Validating supplier bank information in automated procurement workflows.

Properties

Output

The output will be a JSON object containing the result of the BIC validation. While the exact structure depends on the API response, it typically includes fields such as:

• valid: Boolean indicating if the BIC is valid.
• bic: The BIC that was checked.
• Additional metadata about the BIC (such as bank name, country, etc.), depending on the external service's response.

If an error occurs and "Continue On Fail" is enabled, the output will include an error field with the error message.

Dependencies

• External Service: Requires access to the CodeKit API endpoint for BIC validation.
• Credentials: You must configure the codeKitApi credential in n8n for authentication.

Troubleshooting

Common issues:

• Invalid BIC format: If the BIC does not conform to standard formats, the node may return an error or mark it as invalid.
• Missing credentials: If the codeKitApi credential is not set up, the node will fail to authenticate.
• API errors: Network issues or service downtime can cause errors. These will appear in the output if "Continue On Fail" is enabled.

Error messages:

• "Missing required parameter: bic" – Ensure the BIC property is provided.
• "Authentication failed" – Check your codeKitApi credentials.
• "Network error" or similar – Verify network connectivity and API availability.

Links and References

• What is a BIC? (SWIFT code)
• n8n Documentation: Credentials
• n8n Documentation: Error Handling