Actions28
- Domain Actions
- DNS Record Actions
- SSL Actions
- User Actions
Overview
This node integrates with the Namecheap API to manage SSL-related tasks, including parsing Certificate Signing Requests (CSRs). The "Parse CSR" operation specifically takes a CSR in PEM format and extracts its details. This is useful when you need to validate or inspect the contents of a CSR before submitting it for certificate issuance or renewal.
Practical examples:
- Extracting information such as the common name, organization, or subject alternative names from a CSR.
- Validating that a CSR is correctly formatted and contains the expected data before proceeding with SSL certificate activation or reissue.
- Automating workflows where CSRs are generated externally and need to be parsed within n8n for further processing.
Properties
| Name | Meaning |
|---|---|
| CSR | The Certificate Signing Request in PEM format. This multiline string input should contain the full CSR text to be parsed. |
Output
The node outputs a JSON object with the following structure:
success: A boolean indicating whether the operation succeeded.data: An object containing the parsed details of the CSR. This typically includes fields extracted from the CSR such as subject information, public key details, and extensions.
Example output snippet (conceptual):
{
"success": true,
"data": {
"subject": {
"commonName": "example.com",
"organization": "Example Corp",
...
},
"publicKeyAlgorithm": "RSA",
"keySize": 2048,
...
}
}
No binary data output is involved in this operation.
Dependencies
- Requires an active connection to the Namecheap API using a valid API authentication token configured in n8n credentials.
- The node depends on the Namecheap service being available and accessible from the n8n environment.
Troubleshooting
- Invalid CSR Format: If the CSR provided is not in proper PEM format, the node may fail to parse it. Ensure the CSR includes the correct header and footer lines (
-----BEGIN CERTIFICATE REQUEST-----and-----END CERTIFICATE REQUEST-----) and no extraneous characters. - API Errors: Network issues or invalid API credentials can cause failures. Verify that the API key credential is correctly set up and has necessary permissions.
- Unknown Operation or Resource: The node throws errors if an unsupported operation or resource is specified. Confirm that "ssl" is selected as the resource and "parseCSR" as the operation.
- Continue On Fail: If enabled, the node will continue processing subsequent items even if one fails, returning error messages in the output JSON.