VoltageInstall

Overview

This node integrates with the Voltage API to manage various resources including wallets, payments, lines of credit, and webhooks. Specifically for the Webhook resource and the Generate Key operation, it allows users to generate a new signing key for an existing webhook within a specified organization.

This functionality is useful when you need to rotate or regenerate the security key used to verify webhook payloads, enhancing security by invalidating old keys and preventing unauthorized access.

Practical example:
If your application receives webhook events from Voltage and you suspect the current signing key has been compromised, you can use this node operation to generate a new key. You would provide the organization ID and the webhook ID, and the node will return the new signing key details.

Properties

Output

The output JSON contains the response from the Voltage API after generating a new webhook signing key. This typically includes details about the newly generated key such as its value and metadata related to the webhook.

The node does not output binary data.

Example output structure (simplified):

{
  "key": "newlyGeneratedSigningKeyValue",
  "webhook_id": "theWebhookId",
  "created_at": "timestamp",
  ...
}

Dependencies

• Requires an API key credential for the Voltage API configured in n8n.
• Uses the voltage-api-sdk library internally to communicate with the Voltage API.
• The node expects valid organization and webhook IDs to perform operations successfully.

Troubleshooting

Common Issues

• Invalid API credentials or missing API key:
  The node will fail authentication if the API key is incorrect or missing.

• Incorrect organization or webhook ID:
  If the provided IDs do not exist or are mistyped, the API will return a "Not Found" error.

• Permission errors:
  Insufficient permissions on the API key may cause access denied errors.

Common Error Messages and Resolutions

• Validation Error (422):
  Indicates invalid request data. Check that all required parameters (organization ID, webhook ID) are correctly set.

• Authentication Error (401):
  Invalid API key or credentials. Verify your API key configuration in n8n.

• Permission Error (403):
  Access denied due to insufficient permissions. Ensure the API key has rights to manage webhooks.

• Not Found (404):
  Organization or webhook not found. Confirm the IDs are correct and exist in your Voltage account.

• Server Error (5xx):
  Temporary issues with the Voltage API. Retry later or contact Voltage support.

• Failed to parse response as JSON:
  Usually indicates an authentication issue or invalid organization ID. Double-check credentials and IDs.

Links and References

• Voltage API Documentation (replace with actual URL if available)
• Voltage API SDK GitHub Repository (replace with actual URL if available)
• n8n Documentation: Creating Custom Nodes