Overview
This node, named "Base Agent," interacts with Base on-chain AI agents to perform blockchain-related token operations. Specifically, the getTokenDetails operation retrieves detailed information about a specified cryptocurrency token by its ticker symbol (e.g., ETH, USDC, DAI). This is useful for users who want to fetch metadata or status of tokens on the blockchain without manually querying external services.
Practical examples include:
- Fetching token details before performing trades or swaps.
- Displaying token information in dashboards or reports.
- Validating token existence and properties during automated workflows.
Properties
| Name | Meaning |
|---|---|
| Ticker Symbol | The token ticker symbol to get details for (e.g., ETH, USDC, DAI). This identifies which token's information will be retrieved. |
Output
The node outputs an array of JSON objects, each containing the token details fetched from the blockchain or related service. The exact structure depends on the implementation of the getTokenDetails function but typically includes fields such as token name, symbol, decimals, total supply, contract address, and other relevant metadata.
If an error occurs (e.g., missing credentials or unsupported operation), the output JSON will contain an error field describing the issue.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential that provides a private key and RPC URL to interact with the blockchain network.
- The node depends on internal functions to fetch token details from the blockchain.
- Proper configuration of the private key and RPC URL credentials is mandatory for successful execution.
Troubleshooting
- Missing Credentials: If the private key or RPC URL is not provided, the node returns an error stating both are required. Ensure these credentials are correctly set up in n8n.
- Unsupported Operation: If an operation other than
getTokenDetailsis selected without proper handling, the node returns an error indicating the operation is not supported. - API or Network Errors: Failures in fetching token details due to network issues or invalid ticker symbols may result in error messages. Verify the ticker symbol is correct and the blockchain network is accessible.
- Continue On Fail: If enabled, the node will continue processing subsequent items even if one fails, returning error details in the output JSON.
Links and References
- Base Blockchain Documentation (for understanding the underlying blockchain)
- ERC-20 Token Standard (common token standard likely referenced)
- n8n Documentation on Creating Custom Nodes