Overview
This node integrates with the Chainstream API to retrieve detailed information about blockchain tokens. Specifically, the Token - Get operation fetches data for a single token on a specified blockchain network by its address.
Typical use cases include:
- Fetching metadata and details of a specific token on a given blockchain.
- Integrating token data into workflows that require up-to-date token information.
- Automating token data retrieval for analytics, portfolio tracking, or DeFi applications.
For example, you might use this node to get the name, symbol, decimals, and other attributes of an ERC-20 token on Ethereum by providing its contract address and chain ID.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authentication; currently supports only "API Key" to authorize requests to the Chainstream API. |
| Chain ID | The identifier of the blockchain network (e.g., Ethereum mainnet, Binance Smart Chain). Selectable from a dynamic list loaded via the API. Required. |
| Token Address | The blockchain address of the token contract to retrieve information for. Required. |
| Options | Additional optional parameters: • Fields: Comma-separated string specifying which fields of the token data to return. If empty, all fields are returned. |
| Query (q) | A search query string (not used in the "get" operation but present in properties). |
Output
The node outputs JSON data representing the token's details as returned by the Chainstream API. This typically includes fields such as:
- Token name
- Symbol
- Decimals
- Contract address
- Other metadata related to the token on the specified chain
The output is structured as an array of JSON objects, each corresponding to one token (in this case, always one token for the "get" operation).
No binary data output is produced by this operation.
Dependencies
- Requires access to the Chainstream API.
- An API key credential must be configured in n8n to authenticate requests.
- The node dynamically loads available blockchain networks ("chains") from the API to populate the Chain ID options.
Troubleshooting
Common issues:
- Invalid or missing API key will cause authentication failures.
- Providing an incorrect or unsupported Chain ID may result in errors or empty responses.
- Incorrect token address format or non-existent token addresses will lead to errors or no data found.
Error messages:
- Errors returned from the API are caught and can be output as error messages if "Continue On Fail" is enabled.
- Typical error messages include authentication failures, invalid parameters, or resource not found.
Resolutions:
- Verify the API key is correctly set and has necessary permissions.
- Ensure the Chain ID is selected from the provided list or valid according to Chainstream documentation.
- Double-check the token address format and existence on the specified chain.
Links and References
- Chainstream API Documentation (for detailed API endpoints and parameters)
- n8n Expressions Documentation (for using expressions in property fields)