Overview
This node retrieves real-time token price data from the Dexscreener API based on a provided smart contract address (token address). It is useful for workflows that need to fetch up-to-date pricing information for specific tokens on decentralized exchanges. Common scenarios include monitoring token prices, triggering alerts when prices change, or integrating live token data into dashboards and reports.
Practical examples:
- Automatically check the current price of a specific ERC-20 token.
- Build a workflow that notifies you if a token's price crosses a certain threshold.
- Aggregate token price data for portfolio tracking.
Properties
| Name | Meaning |
|---|---|
| Token Address | Smart contract address for the token (e.g., 0x31C91D8Fb96BfF40955DD2dbc909B36E8b104Dde). This is required and identifies which token's price to fetch. |
Output
The output is a JSON object (or array of objects if multiple items are processed) containing the response from the Dexscreener API for the specified token address. The structure of the output matches the API's response, which typically includes:
- Token details (name, symbol, address)
- Price information (current price, price changes, etc.)
- Market data (liquidity, volume, etc.)
Example output:
[
{
"pair": "...",
"priceUsd": "...",
"liquidity": "...",
// ...other fields as returned by dexscreener.com API
}
]
Note: The exact fields depend on the Dexscreener API response.
Dependencies
- External Service: Requires access to the Dexscreener public API.
- No API Key Required: The endpoint used does not require authentication.
- n8n Configuration: No special configuration needed beyond standard internet access.
Troubleshooting
Common issues:
- Invalid Token Address: If the provided token address is incorrect or not supported by Dexscreener, the API may return an error or empty result.
- Network Issues: If n8n cannot reach the Dexscreener API (due to firewall, DNS, or connectivity problems), requests will fail.
- API Changes: If the Dexscreener API changes its response format, the output structure may differ.
Error messages and resolutions:
"Request failed with status code 404": The token address is likely invalid or not found. Double-check the address."ENOTFOUND"or"ECONNREFUSED": Network connectivity issue. Ensure your n8n instance can access external APIs.