Actions5
- Transaction Actions
- Escrow Wallet Actions
- 1Shot Prompt Actions
Overview
This node integrates with the 1Shot API to interact with blockchain and web3 services, specifically focusing on managing escrow wallets in this context. The "List Escrow Wallets" operation retrieves a list of escrow wallets associated with a business on a specified blockchain network (chain). This is useful for users who need to programmatically access and manage escrow wallet information across different supported chains.
Practical examples include:
- Fetching all escrow wallets your business controls on Ethereum or Avalanche networks.
- Integrating escrow wallet data into automated workflows for financial reconciliation or auditing.
- Displaying escrow wallet details in dashboards or reports that track blockchain assets.
Properties
| Name | Meaning |
|---|---|
| Chain Name or ID | Select the blockchain network by name or specify its numeric Chain ID. Supported options: |
| - Ethereum (1) | |
| - Sepolia (11155111) | |
| - Base (8453) | |
| - Base Sepolia (84531) | |
| - Avalanche (43114) | |
| - Avalanche Fuji (43113) |
The property lets you choose the blockchain network from which to list escrow wallets. You can select from predefined options or provide a custom chain ID using expressions.
Output
The node outputs a JSON array containing the escrow wallets retrieved from the 1Shot API for the specified business and chain. Each item in the array represents an escrow wallet object with details as returned by the API. The exact structure depends on the API response but typically includes wallet identifiers, addresses, and related metadata.
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to the 1Shot API via OAuth2 authentication using an API key credential.
- The node expects the business identifier to be available within the credentials for scoping the request.
- Network connectivity to
https://api.1shotapi.com/v0is necessary. - No additional environment variables are required beyond the configured OAuth2 credentials.
Troubleshooting
Common Issues:
- Invalid or expired OAuth2 token may cause authentication failures.
- Incorrect or missing business ID in credentials will result in failed requests.
- Providing an unsupported or incorrect chain ID may return empty results or errors.
- Network issues or API downtime can prevent successful data retrieval.
Error Messages:
"Unsupported resource": Occurs if the resource parameter is set incorrectly; ensure it is "escrowWallet".- HTTP 403 errors indicate token expiration or insufficient permissions; refresh or reauthenticate the API credentials.
- JSON parsing errors may arise if input parameters are malformed; verify expressions and inputs.
Links and References
- 1Shot API Documentation — Official API reference for endpoints and data structures.
- n8n Expressions Documentation — Guide on using expressions for dynamic parameter values.