Overview
This node signs Stellar blockchain transactions using a secret key from a wallet credential. It takes an unsigned transaction in XDR format and produces a signed transaction XDR along with its hash and related metadata. This is useful when you want to programmatically sign Stellar transactions within an n8n workflow, for example, to automate payments, asset transfers, or other operations on the Stellar network.
Typical use cases include:
- Signing payment transactions before submitting them to the Stellar network.
- Automating multi-step workflows where transaction signing is required.
- Integrating Stellar transaction signing into broader automation pipelines.
Properties
| Name | Meaning |
|---|---|
| Transaction XDR | The unsigned Stellar transaction encoded as an XDR string that needs to be signed. |
| Network | The Stellar network to use for signing: either "Mainnet" (public network) or "Testnet". |
Output
The node outputs an array of items where each item contains a json object with the following fields:
signedXdr: The signed transaction encoded as an XDR string.txHash: The hexadecimal string of the transaction hash.publicKey: The public key derived from the secret key used to sign the transaction.network: The network object used for signing (either Mainnet or Testnet).
If the node encounters an error and is configured to continue on failure, it outputs an item containing the original input JSON plus an error field describing the issue.
No binary data output is produced by this node.
Dependencies
- Requires a Stellar wallet secret key credential to sign transactions.
- Uses the official Stellar SDK (
@stellar/stellar-sdk) for transaction parsing and signing. - Needs proper configuration of the API key credential holding the secret key.
- No additional environment variables are required beyond the credential.
Troubleshooting
- Missing Credentials: If the wallet secret key credential is not provided or invalid, the node will throw an error indicating that Stellar wallet credentials are required.
- Invalid Transaction XDR: If the input transaction XDR is empty or malformed, the node will throw an error stating that the Transaction XDR is required or fail during parsing.
- Network Mismatch: Ensure the selected network matches the transaction's intended network; otherwise, signing may fail or produce invalid results.
- Error Handling: When multiple items are processed, errors in individual items can be handled gracefully if "Continue On Fail" is enabled, allowing partial success.