TickAtlas
Integration Guide n8n · Last updated: March 2026

n8n Integration

Connect live Forex indicators to any n8n workflow using the HTTP Request node. Build RSI alert pipelines, multi-symbol screeners, and trading signal bots — no custom code required.

Prerequisites

  • A TickAtlas API key — get one free here
  • n8n Cloud or self-hosted n8n instance (free plan works)
n8n Advantage: Unlike Zapier, n8n's HTTP Request node works on the free plan. Self-hosted n8n is free and open-source.
1

Test the API

Verify your API key works before wiring up n8n:

cURL 
# Test your key before setting up n8n
curl -X GET \
  "https://tickatlas.com/v1/indicator?symbol=EURUSD&indicator=RSI_14&timeframe=H1" \
  -H "X-API-Key: YOUR_API_KEY"
2

Store Your API Key Securely

  1. 1. In n8n, go to Settings → Credentials → New Credential
  2. 2. Search for and select Header Auth
  3. 3. Set Name: X-API-Key
  4. 4. Set Value: your TickAtlas API key
  5. 5. Save — n8n encrypts this at rest

In your HTTP Request nodes, select this credential from the Authentication dropdown instead of hardcoding the key.

3

Configure the HTTP Request Node

In your workflow, add an HTTP Request node and configure it:

HTTP Request node 
// n8n HTTP Request Node Configuration
// ─────────────────────────────────────
// Method:  GET
// URL:     https://tickatlas.com/v1/indicator
//
// Authentication:
//   Header Auth → X-API-Key: <your-api-key>
//   (Use n8n credentials for secure storage)
//
// Query Parameters:
//   symbol    = EURUSD
//   indicator = RSI_14
//   timeframe = H1
//
// Response fields available in next nodes ($json is the whole body,
// and every success response is { success, data }):
//   {{ $json.data.value }}       → 74.3
//   {{ $json.data.bid }}         → 1.0856
//   {{ $json.data.updated_at }}  → 1711548000
// There is no signal field. Compare the value in an IF node instead:
//   {{ $json.data.value }} > 70  → overbought
Efficiency tip: Use /v1/indicators (plural) to get all 42 indicator values in a single HTTP call instead of making separate requests per indicator.
all indicators 
// GET /v1/indicators — all 42 indicators at once
// ───────────────────────────────────────────────
// URL: https://tickatlas.com/v1/indicators
// Params: symbol=EURUSD&timeframe=H1
//
// Access in downstream nodes. indicators is a flat map of name to
// number, so there is no nested .value, and the MACD lines are three
// separate keys:
//   {{ $json.data.indicators.RSI_14 }}     → 68.42
//   {{ $json.data.indicators.MACD_hist }}  → 0.0012
//   {{ $json.data.indicators.ADX }}        → 27.4
//   ... and 39 more
4

Build Your Workflow

Typical n8n workflow pattern for trading alerts:

① Schedule Trigger — Every 5 minutes, hourly, or daily
② HTTP Request — GET /v1/indicator (configured above)
③ IF Node — e.g., {{ $json.data.value }} greater than 70
④ Action — Discord, Slack, Gmail, Telegram, Google Sheets

Scanning multiple symbols? Use a Split In Batches node with a list of symbols, then pipe each through the HTTP Request node. Or use GET /v1/screener to filter all 150+ symbols by a condition in one call.

Related Resources