Skip to main content

Stock market information assistant with Telegram, Yahoo Finance, and GPT-4 Nano

Workflow preview

Workflow preview
100%
Stock market information assistant with Telegram, Yahoo Finance, and GPT-4 Nano preview
Open on n8n.io

Important notice

This workflow is provided as-is. Please review and test before using in production.

1. Workflow Overview

How it works 1. Listens to Telegram messages to detect stock related queries. 2. Extracts company name and identifies its exact stock ticker symbol. 3. Searches Yahoo Finance for stock info using t...

Best for

  • Crypto Trading automation workflows
  • AI Chatbot automation workflows
  • advanced n8n builders looking for reusable templates

Tools used

n8n-nodes-base.telegramtrigger, @n8n/n8n-nodes-langchain.lmchatopenrouter, n8n-nodes-base.executeworkflowtrigger, @n8n/n8n-nodes-langchain.toolworkflow, @n8n/n8n-nodes-langchain.informationextractor, n8n-nodes-base.httprequest, n8n-nodes-base.set, n8n-nodes-base.httprequesttool

Source and attribution

This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Archit Jain.

Original n8n.io source

1.1 Workflow description

Title
Stock market information assistant with Telegram, Yahoo Finance, and GPT-4 Nano
Workflow name
Stock market information assistant with Telegram, Yahoo Finance, and GPT-4 Nano

How it works

  1. Listens to Telegram messages to detect stock-related queries.
  2. Extracts company name and identifies its exact stock ticker symbol.
  3. Searches Yahoo Finance for stock info using the ticker.
  4. Fetches and formats the latest stock data like price and key stats.
  5. Sends a clean, simplified reply back to the user on Telegram.

Set up steps

  • Requires Telegram Bot Token and Apify API credentials.
  • Import workflow to n8n and link both Apify actors (Google Search + Yahoo Finance).
  • Link OpenRouter for AI and enable Telegram trigger.
  • Takes ~10–15 min to connect services and test.
  • Includes sticky notes with setup links and tutorial videos.

1.2 Logical Blocks

This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.

2. Block-by-Block Analysis

Block 1 - Telegram Trigger

Type / Role
n8n-nodes-base.telegramTrigger - telegramTrigger
Config choices
Version 1.2

Block 2 - OpenRouter Chat Model

Type / Role
@n8n/n8n-nodes-langchain.lmChatOpenRouter - lmChatOpenRouter
Config choices
Version 1

Block 3 - When Executed by Another Workflow

Type / Role
n8n-nodes-base.executeWorkflowTrigger - executeWorkflowTrigger
Config choices
Version 1.1

Block 4 - Get Ticker Name

Type / Role
@n8n/n8n-nodes-langchain.toolWorkflow - toolWorkflow
Config choices
Version 2.2

Block 5 - Information Extractor

Type / Role
@n8n/n8n-nodes-langchain.informationExtractor - informationExtractor
Config choices
Version 1.1

Block 6 - OpenRouter Chat Model1

Type / Role
@n8n/n8n-nodes-langchain.lmChatOpenRouter - lmChatOpenRouter
Config choices
Version 1

Block 7 - Google Search

Type / Role
n8n-nodes-base.httpRequest - httpRequest
Config choices
Version 4.2

Block 8 - Ticker Name Search

Type / Role
n8n-nodes-base.httpRequest - httpRequest
Config choices
Version 4.2

Block 9 - Set Ticker

Type / Role
n8n-nodes-base.set - set
Config choices
Version 3.4

Block 10 - Get Stock Info

Type / Role
n8n-nodes-base.httpRequestTool - httpRequestTool
Config choices
Version 4.2

Block 11 - Telegram

Type / Role
n8n-nodes-base.telegram - telegram
Config choices
Version 1.2

Block 12 - Sticky Note

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 13 - Sticky Note1

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 14 - Simple Memory

Type / Role
@n8n/n8n-nodes-langchain.memoryBufferWindow - memoryBufferWindow
Config choices
Version 1.3

Block 15 - Stock Market Agent

Type / Role
@n8n/n8n-nodes-langchain.agent - agent
Config choices
Version 2

3. Summary Table

Workflow Stock market information assistant with Telegram, Yahoo Finance, and GPT-4 Nano
Complexity advanced
Nodes 15
Categories Crypto Trading, AI Chatbot
Author Archit Jain
Published 19 Jun 2025

4. Reproducing the Workflow from Scratch

  1. 1. Download the workflow JSON

    Use the JSON export at /data/workflows/5039/5039.json as the source template for this automation.

  2. 2. Import the template into n8n

    Open n8n, import the downloaded JSON, and review each node before activating the workflow.

  3. 3. Configure credentials and variables

    Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.

  4. 4. Test with sample data

    Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.

  5. 5. Activate and monitor

    Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.

5. General Notes & Resources

Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.

Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.

Frequently asked questions

What does Stock market information assistant with Telegram, Yahoo Finance, and GPT-4 Nano do?

How it works 1. Listens to Telegram messages to detect stock related queries. 2. Extracts company name and identifies its exact stock ticker symbol. 3. Searches Yahoo Finance for stock info using t...

What do I need before importing this workflow?

Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.

Can I customize this workflow?

Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your Crypto Trading, AI Chatbot use case.