Automate Bitget spot trading with GPT-4o-mini AI agent via Telegram

232 views

2/3/2026

Calendly Meetings Automation Google Calendar Scheduling

A professional-grade AI trading orchestration system for Bitget Spot Market automation via Telegram.

This agent integrates Bitget REST APIs, authenticated order management, and real-time reasoning with GPT-4o-mini, allowing direct Telegram-based execution of spot and trigger orders — all within your self-hosted n8n environment.

🎥 Watch Tutorial:

🧩 Required Workflows

You must install and activate all of the following workflows for the system to function correctly:

| ✅ Workflow Name | 📌 Function Description | | --------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------- | | Bitget AI Trader Agent | Core orchestrator. Handles user Telegram commands, routes to correct sub-agents, and formats all responses. | | Account and Wallet Agent Tool | Retrieves Bitget account info, balances, and deposit addresses using authenticated endpoints /api/v2/spot/account/*. | | Spot Order Trading Agent Tool | Places, cancels, and queries spot orders (/trade/place-order, /cancel-order, /orderInfo, /unfilled-orders). | | Trigger Order Agent Tool | Manages conditional “plan” (trigger) orders — place, modify, cancel, and list them (/trade/place-plan-order, /modify-plan-order, etc.). | | Webhook HTTP Request Nodes | Securely handle REST calls for each sub-agent via n8n webhooks. All endpoints authenticated using the Bitget Sign system. |

⚙️ Installation Instructions

Step 1: Import Workflows

Open your n8n Editor UI
Import the Bitget AI Trader Agent (Finished).json file
Ensure all sub-agents are visible in the canvas and linked properly

Step 2: Set Credentials

Configure your Bitget API Key, Secret, and Passphrase inside your n8n credentials
Add your OpenAI API Key (recommended: GPT-4o-mini)
Set Telegram bot token (from @BotFather)

Step 3: Configure Webhook Endpoints

Make sure all downstream webhooks (e.g., Get-Account-Information, Place-Order, Cancel-Order, etc.) are accessible via HTTPS. Each must use Basic Auth credentials named: Bitget Authentication for Webhooks

Step 4: Authorize Telegram Access

Replace the placeholder Telegram ID in:

if ($input.first().json.message.from.id !== &lt;&lt;Replace&gt;&gt;) { ... }

with your Telegram user ID. This ensures only you can issue trading commands.

Step 5: Test & Deploy

Trigger the Telegram bot command (e.g. /balance or /order) to verify:

Authenticated data fetch
Correct REST routing
Safe GPT-based reasoning
Telegram delivery with formatted markdown

💬 Telegram Output Examples

✅ BTCUSDT limit buy placed @ 23222.5, size 0.01 (orderId: 123456)

❌ Rejected: price tick invalid for BTCUSDT. Provide price with correct step.

💰 Balance Summary:
• USDT: 1250.34 (Available)
• BTC: 0.023 (In Trade)

🧩 System Overview

[Telegram Trigger]
→ [User Authentication]
→ [Bitget AI Trader Agent]
→ [Account/Wallet Tool] + [Spot Order Tool] + [Trigger Order Tool]
→ [Webhook Execution Layer]
→ [GPT-4o-mini Reasoning + Message Split Logic]
→ [Telegram Output]

🔒 Safety & Compliance

All API calls use Bitget Sign authentication
Orders cannot be spoofed or simulated
No keys or signatures ever exposed in chat
Strict input validation and confirmation per action

🧾 Licensing & Attribution

🔗 For support: LinkedIn – Don Jayamaha

n8n Workflow: AI-Powered Trading Assistant via Telegram

This n8n workflow creates an AI agent that can respond to commands and perform actions, potentially for trading, through a Telegram bot interface. It leverages OpenAI's language models and various n8n core nodes to process user input, execute logic, and respond.

What it does

This workflow sets up a sophisticated AI agent accessible via Telegram, capable of understanding and responding to user queries or commands. While the specific "trading" functionality hinted at by the directory name is not explicitly defined in the provided JSON (e.g., no Bitget API calls), the structure allows for such integration.

Here's a breakdown of the key steps:

Listens for Telegram Messages: The workflow is triggered by incoming messages to a configured Telegram bot.
Initial Webhook Response: Immediately responds to the Telegram webhook to acknowledge receipt, preventing timeouts.
Processes Telegram Input: Extracts the user's message text from the Telegram trigger data.
Initial AI Agent Interaction: Passes the user's message to an AI Agent powered by OpenAI's chat model (gpt-4o-mini). This agent has a memory to maintain conversation context and is equipped with a calculator tool and a "Think" tool for complex reasoning.
Handles AI Agent Output: The AI Agent's response is then processed.
Sends Response to Telegram: The final AI-generated response is sent back to the user via Telegram.
Conditional Logic (Placeholder): A Switch node is present, suggesting future expansion for branching logic based on the AI's output or specific commands (e.g., to trigger trading actions).
Image Editing (Unconnected): An Edit Image node is included but not connected to the main flow, indicating a potential future feature for image manipulation.
HTTP Request & Crypto (Unconnected): HTTP Request and Crypto nodes are also present but unconnected, suggesting capabilities for external API calls (like a trading platform) and data security/hashing, which would be crucial for a trading bot.

Prerequisites/Requirements

To use this workflow, you will need:

n8n Instance: A running n8n instance (self-hosted or n8n Cloud).
Telegram Bot: A Telegram bot token and a chat ID where the bot will operate.
OpenAI API Key: An API key for OpenAI to power the AI Agent's language model (specifically, gpt-4o-mini is configured).
n8n Langchain Nodes: Ensure the @n8n/n8n-nodes-langchain package is installed on your n8n instance, as it provides the AI Agent, OpenAI Chat Model, Simple Memory, Calculator, and Think Tool nodes.

Setup/Usage

Import the Workflow:
- Copy the provided JSON code.
- In your n8n instance, go to "Workflows" and click "New".
- Click the "Import from JSON" button and paste the copied JSON.
Configure Credentials:
- Telegram Trigger & Telegram Node: Set up a Telegram credential using your bot token.
- OpenAI Chat Model: Set up an OpenAI credential with your API key.
Configure Telegram Trigger:
- Open the "Telegram Trigger" node.
- Select your Telegram credential.
- Save and activate the workflow.
- You will receive a webhook URL. Copy this URL.
- Go to your Telegram bot (using BotFather), and set the webhook URL for your bot using the /setwebhook command.
Configure Telegram Node:
- Open the "Telegram" node.
- Ensure your Telegram credential is selected.
- Set the "Chat ID" to the ID of the chat where you want the bot to send messages.
Activate the Workflow:
- Toggle the workflow to "Active" in the top right corner of the n8n editor.

Once activated, your Telegram bot will be ready to interact with the AI agent. Send messages to your bot, and the AI agent will process them and respond.

Note: The Edit Image, HTTP Request, and Crypto nodes are currently disconnected. To enable their functionality, you would need to integrate them into the workflow logic, for example, by adding branches in the Switch node or by connecting them to the AI Agent's tools. For a Bitget trading bot, the HTTP Request and Crypto nodes would be essential for interacting with the Bitget API and signing requests.

Related Templates

Track competitor SEO keywords with Decodo + GPT-4.1-mini + Google Sheets

This workflow automates competitor keyword research using OpenAI LLM and Decodo for intelligent web scraping. Who this is for SEO specialists, content strategists, and growth marketers who want to automate keyword research and competitive intelligence. Marketing analysts managing multiple clients or websites who need consistent SEO tracking without manual data pulls. Agencies or automation engineers using Google Sheets as an SEO data dashboard for keyword monitoring and reporting. What problem this workflow solves Tracking competitor keywords manually is slow and inconsistent. Most SEO tools provide limited API access or lack contextual keyword analysis. This workflow solves that by: Automatically scraping any competitor’s webpage with Decodo. Using OpenAI GPT-4.1-mini to interpret keyword intent, density, and semantic focus. Storing structured keyword insights directly in Google Sheets for ongoing tracking and trend analysis. What this workflow does Trigger — Manually start the workflow or schedule it to run periodically. Input Setup — Define the website URL and target country (e.g., https://dev.to, france). Data Scraping (Decodo) — Fetch competitor web content and metadata. Keyword Analysis (OpenAI GPT-4.1-mini) Extract primary and secondary keywords. Identify focus topics and semantic entities. Generate a keyword density summary and SEO strength score. Recommend optimization and internal linking opportunities. Data Structuring — Clean and convert GPT output into JSON format. Data Storage (Google Sheets) — Append structured keyword data to a Google Sheet for long-term tracking. Setup Prerequisites If you are new to Decode, please signup on this link visit.decodo.com n8n account with workflow editor access Decodo API credentials OpenAI API key Google Sheets account connected via OAuth2 Make sure to install the Decodo Community node. Create a Google Sheet Add columns for: primarykeywords, seostrengthscore, keyworddensity_summary, etc. Share with your n8n Google account. Connect Credentials Add credentials for: Decodo API credentials - You need to register, login and obtain the Basic Authentication Token via Decodo Dashboard OpenAI API (for GPT-4o-mini) Google Sheets OAuth2 Configure Input Fields Edit the “Set Input Fields” node to set your target site and region. Run the Workflow Click Execute Workflow in n8n. View structured results in your connected Google Sheet. How to customize this workflow Track Multiple Competitors → Use a Google Sheet or CSV list of URLs; loop through them using the Split In Batches node. Add Language Detection → Add a Gemini or GPT node before keyword analysis to detect content language and adjust prompts. Enhance the SEO Report → Expand the GPT prompt to include backlink insights, metadata optimization, or readability checks. Integrate Visualization → Connect your Google Sheet to Looker Studio for SEO performance dashboards. Schedule Auto-Runs → Use the Cron Node to run weekly or monthly for competitor keyword refreshes. Summary This workflow automates competitor keyword research using: Decodo for intelligent web scraping OpenAI GPT-4.1-mini for keyword and SEO analysis Google Sheets for live tracking and reporting It’s a complete AI-powered SEO intelligence pipeline ideal for teams that want actionable insights on keyword gaps, optimization opportunities, and content focus trends, without relying on expensive SEO SaaS tools.

By Ranjan Dailata

161

Generate song lyrics and music from text prompts using OpenAI and Fal.ai Minimax

Spark your creativity instantly in any chat—turn a simple prompt like "heartbreak ballad" into original, full-length lyrics and a professional AI-generated music track, all without leaving your conversation. 📋 What This Template Does This chat-triggered workflow harnesses AI to generate detailed, genre-matched song lyrics (at least 600 characters) from user messages, then queues them for music synthesis via Fal.ai's minimax-music model. It polls asynchronously until the track is ready, delivering lyrics and audio URL back in chat. Crafts original, structured lyrics with verses, choruses, and bridges using OpenAI Submits to Fal.ai for melody, instrumentation, and vocals aligned to the style Handles long-running generations with smart looping and status checks Returns complete song package (lyrics + audio link) for seamless sharing 🔧 Prerequisites n8n account (self-hosted or cloud with chat integration enabled) OpenAI account with API access for GPT models Fal.ai account for AI music generation 🔑 Required Credentials OpenAI API Setup Go to platform.openai.com → API keys (sidebar) Click "Create new secret key" → Name it (e.g., "n8n Songwriter") Copy the key and add to n8n as "OpenAI API" credential type Test by sending a simple chat completion request Fal.ai HTTP Header Auth Setup Sign up at fal.ai → Dashboard → API Keys Generate a new API key → Copy it In n8n, create "HTTP Header Auth" credential: Name="Fal.ai", Header Name="Authorization", Header Value="Key [Your API Key]" Test with a simple GET to their queue endpoint (e.g., /status) ⚙️ Configuration Steps Import the workflow JSON into your n8n instance Assign OpenAI API credentials to the "OpenAI Chat Model" node Assign Fal.ai HTTP Header Auth to the "Generate Music Track", "Check Generation Status", and "Fetch Final Result" nodes Activate the workflow—chat trigger will appear in your n8n chat interface Test by messaging: "Create an upbeat pop song about road trips" 🎯 Use Cases Content Creators: YouTubers generating custom jingles for videos on the fly, streamlining production from idea to audio export Educators: Music teachers using chat prompts to create era-specific folk tunes for classroom discussions, fostering interactive learning Gift Personalization: Friends crafting anniversary R&B tracks from shared memories via quick chats, delivering emotional audio surprises Artist Brainstorming: Songwriters prototyping hip-hop beats in real-time during sessions, accelerating collaboration and iteration ⚠️ Troubleshooting Invalid JSON from AI Agent: Ensure the system prompt stresses valid JSON; test the agent standalone with a sample query Music Generation Fails (401/403): Verify Fal.ai API key has minimax-music access; check usage quotas in dashboard Status Polling Loops Indefinitely: Bump wait time to 45-60s for complex tracks; inspect fal.ai queue logs for bottlenecks Lyrics Under 600 Characters: Tweak agent prompt to enforce fuller structures like [V1][C][V2][B][C]; verify output length in executions

By Daniel Nkencho

601

Automate invoice processing with OCR, GPT-4 & Salesforce opportunity creation

PDF Invoice Extractor (AI) End-to-end pipeline: Watch Drive ➜ Download PDF ➜ OCR text ➜ AI normalize to JSON ➜ Upsert Buyer (Account) ➜ Create Opportunity ➜ Map Products ➜ Create OLI via Composite API ➜ Archive to OneDrive. --- Node by node (what it does & key setup) 1) Google Drive Trigger Purpose: Fire when a new file appears in a specific Google Drive folder. Key settings: Event: fileCreated Folder ID: google drive folder id Polling: everyMinute Creds: googleDriveOAuth2Api Output: Metadata { id, name, ... } for the new file. --- 2) Download File From Google Purpose: Get the file binary for processing and archiving. Key settings: Operation: download File ID: ={{ $json.id }} Creds: googleDriveOAuth2Api Output: Binary (default key: data) and original metadata. --- 3) Extract from File Purpose: Extract text from PDF (OCR as needed) for AI parsing. Key settings: Operation: pdf OCR: enable for scanned PDFs (in options) Output: JSON with OCR text at {{ $json.text }}. --- 4) Message a model (AI JSON Extractor) Purpose: Convert OCR text into strict normalized JSON array (invoice schema). Key settings: Node: @n8n/n8n-nodes-langchain.openAi Model: gpt-4.1 (or gpt-4.1-mini) Message role: system (the strict prompt; references {{ $json.text }}) jsonOutput: true Creds: openAiApi Output (per item): $.message.content → the parsed JSON (ensure it’s an array). --- 5) Create or update an account (Salesforce) Purpose: Upsert Buyer as Account using an external ID. Key settings: Resource: account Operation: upsert External Id Field: taxid_c External Id Value: ={{ $json.message.content.buyer.tax_id }} Name: ={{ $json.message.content.buyer.name }} Creds: salesforceOAuth2Api Output: Account record (captures Id) for downstream Opportunity. --- 6) Create an opportunity (Salesforce) Purpose: Create Opportunity linked to the Buyer (Account). Key settings: Resource: opportunity Name: ={{ $('Message a model').item.json.message.content.invoice.code }} Close Date: ={{ $('Message a model').item.json.message.content.invoice.issue_date }} Stage: Closed Won Amount: ={{ $('Message a model').item.json.message.content.summary.grand_total }} AccountId: ={{ $json.id }} (from Upsert Account output) Creds: salesforceOAuth2Api Output: Opportunity Id for OLI creation. --- 7) Build SOQL (Code / JS) Purpose: Collect unique product codes from AI JSON and build a SOQL query for PricebookEntry by Pricebook2Id. Key settings: pricebook2Id (hardcoded in script): e.g., 01sxxxxxxxxxxxxxxx Source lines: $('Message a model').first().json.message.content.products Output: { soql, codes } --- 8) Query PricebookEntries (Salesforce) Purpose: Fetch PricebookEntry.Id for each Product2.ProductCode. Key settings: Resource: search Query: ={{ $json.soql }} Creds: salesforceOAuth2Api Output: Items with Id, Product2.ProductCode (used for mapping). --- 9) Code in JavaScript (Build OLI payloads) Purpose: Join lines with PBE results and Opportunity Id ➜ build OpportunityLineItem payloads. Inputs: OpportunityId: ={{ $('Create an opportunity').first().json.id }} Lines: ={{ $('Message a model').first().json.message.content.products }} PBE rows: from previous node items Output: { body: { allOrNone:false, records:[{ OpportunityLineItem... }] } } Notes: Converts discount_total ➜ per-unit if needed (currently commented for standard pricing). Throws on missing PBE mapping or empty lines. --- 10) Create Opportunity Line Items (HTTP Request) Purpose: Bulk create OLIs via Salesforce Composite API. Key settings: Method: POST URL: https://<your-instance>.my.salesforce.com/services/data/v65.0/composite/sobjects Auth: salesforceOAuth2Api (predefined credential) Body (JSON): ={{ $json.body }} Output: Composite API results (per-record statuses). --- 11) Update File to One Drive Purpose: Archive the original PDF in OneDrive. Key settings: Operation: upload File Name: ={{ $json.name }} Parent Folder ID: onedrive folder id Binary Data: true (from the Download node) Creds: microsoftOneDriveOAuth2Api Output: Uploaded file metadata. --- Data flow (wiring) Google Drive Trigger → Download File From Google Download File From Google → Extract from File → Update File to One Drive Extract from File → Message a model Message a model → Create or update an account Create or update an account → Create an opportunity Create an opportunity → Build SOQL Build SOQL → Query PricebookEntries Query PricebookEntries → Code in JavaScript Code in JavaScript → Create Opportunity Line Items --- Quick setup checklist 🔐 Credentials: Connect Google Drive, OneDrive, Salesforce, OpenAI. 📂 IDs: Drive Folder ID (watch) OneDrive Parent Folder ID (archive) Salesforce Pricebook2Id (in the JS SOQL builder) 🧠 AI Prompt: Use the strict system prompt; jsonOutput = true. 🧾 Field mappings: Buyer tax id/name → Account upsert fields Invoice code/date/amount → Opportunity fields Product name must equal your Product2.ProductCode in SF. ✅ Test: Drop a sample PDF → verify: AI returns array JSON only Account/Opportunity created OLI records created PDF archived to OneDrive --- Notes & best practices If PDFs are scans, enable OCR in Extract from File. If AI returns non-JSON, keep “Return only a JSON array” as the last line of the prompt and keep jsonOutput enabled. Consider adding validation on parsing.warnings to gate Salesforce writes. For discounts/taxes in OLI: Standard OLI fields don’t support per-line discount amounts directly; model them in UnitPrice or custom fields. Replace the Composite API URL with your org’s domain or use the Salesforce node’s Bulk Upsert for simplicity.

By Le Nguyen

942