HumationHuman + Automation
Back to Catalog

AI-Powered Employee Database Management via Telegram using OpenAI and Airtable

Billy ChristiBilly Christi
2512 views
2/3/2026
Financial DataOpenAIAutomationTwelve DataStock Market
Official Page

Who is this for?

This workflow is perfect for:

  • HR professionals seeking to automate employee and department management
  • Startups and SMBs that want an AI-powered HR assistant on Telegram
  • Internal operations teams that want to simplify onboarding and employee data tracking

What problem is this workflow solving?

Managing employee databases manually is error-prone and inefficient—especially for growing teams. This workflow solves that by:

  • Enabling natural language-based HR operations directly through Telegram
  • Automating the creation, retrieval, and deletion of employee records in Airtable
  • Dynamically managing related data such as departments and job titles
  • Handling data consistency and linking across relational tables automatically
  • Providing a conversational interface backed by OpenAI for smart decision-making

What this workflow does

Using Telegram as the interface and Airtable as the backend database, this intelligent HR workflow allows users to:

  1. Chat in natural language (e.g. “Show me all employees” or “Create employee: Sarah, Marketing…”)

  2. Interpret and route requests via an AI Agent that acts as the orchestrator

  3. Query employee, department, and job title data from Airtable

  4. Create or update records as needed:

    • Add new departments and job titles automatically if they don’t exist
    • Create new employees and link them to the correct department and job title

  5. Delete employees based on ID

  6. Respond directly in Telegram, providing user-friendly feedback

Setup

  1. View & Copy the Airtable base here: 👉 Employee Database Management – Airtable Base Template

  2. Telegram Bot: Set up a Telegram bot and connect it to the Telegram Trigger node

  3. Airtable: Prepare three Airtable tables:

    • Employees with links to Departments and Job Titles
    • Departments with Name & Description
    • Job Titles with Title & Description

  4. Connect your Airtable API key and base/table IDs into the appropriate Airtable nodes

  5. Add your OpenAI API key to the AI Agent nodes

  6. Deploy both workflows: the main chatbot workflow and the employee creation sub-workflow

  7. Test with sample messages like:

    • “Create employee: John Doe, john@company.com, Engineering, Software Engineer”
    • “Remove employee ID rec123xyz”

How to customize this workflow to your needs

  • Switch databases: Replace Airtable with Notion, PostgreSQL, or Google Sheets if desired
  • Enhance security: Add authentication and validation before allowing deletion
  • Add approval flows: Integrate Telegram button-based approvals for sensitive actions
  • Multi-language support: Expand system prompts to support multiple languages
  • Add logging: Store every user action in a log table for auditability
  • Expand capabilities: Integrate payroll, time tracking, or Slack notifications

Extra Tips

  • This is a two-workflow setup. Make sure the sub-workflow is deployed and accessible from the main agent.
  • Use Simple Memory per chat ID to preserve context across user queries.
  • You can expand the orchestration logic by adding more tools to the main agent—such as “Get active employees only” or “List employees by job title.”

Contact me for consulting and support:
📧 billychartanto@gmail.com

AI-Powered Employee Database Management via Telegram using OpenAI and Airtable

This n8n workflow streamlines employee database management by integrating Telegram, OpenAI's AI Agent, and Airtable. It allows users to interact with an employee database through natural language commands in Telegram, leveraging AI to understand requests and perform actions like adding, updating, or retrieving employee information in Airtable.

What it does

  1. Listens for Telegram Messages: The workflow is triggered by incoming messages to a configured Telegram bot.
  2. Initializes AI Agent: An AI Agent is set up with a conversational memory and an OpenAI chat model.
  3. Defines a Tool for Airtable Interaction: A "Call n8n Workflow Tool" is configured, which is likely designed to interact with Airtable (though the specific Airtable operations are not detailed in this JSON, the presence of an Airtable node and the workflow's title strongly suggest this). This tool allows the AI Agent to perform actions on the employee database.
  4. Processes Natural Language Input: The AI Agent receives the Telegram message, interprets the user's intent using the OpenAI Chat Model, and decides whether to use the defined Airtable tool.
  5. Executes Airtable Operations (via Tool): If the AI determines an Airtable operation is needed (e.g., "add employee", "find employee"), it calls the "Call n8n Workflow Tool" which, in turn, would execute a sub-workflow or logic to interact with Airtable.
  6. Formats Output: A "Structured Output Parser" is used, likely to format the AI's response or the results from the Airtable operation into a structured format.
  7. Responds via Telegram: The processed information or AI-generated response is sent back to the user through Telegram.

Prerequisites/Requirements

  • n8n Instance: A running n8n instance.
  • Telegram Bot: A Telegram bot token and chat ID.
  • OpenAI API Key: An API key for OpenAI to use the Chat Model.
  • Airtable Account: An Airtable account with a base and table configured for employee data.
  • Airtable Credentials in n8n: Configured Airtable credentials within n8n.
  • Sub-workflow for Airtable Operations: While not explicitly in this JSON, a separate n8n workflow (or logic within this one, if the "Call n8n Workflow Tool" points to itself or a simple branch) is required to handle the actual CRUD operations on Airtable. This workflow would be triggered by the "Call n8n Workflow Tool".

Setup/Usage

  1. Import the Workflow: Import this JSON definition into your n8n instance.
  2. Configure Telegram Trigger:
    • Set up a Telegram Bot credential in n8n.
    • In the "Telegram Trigger" node, select your Telegram Bot credential.
  3. Configure OpenAI Chat Model:
    • Set up an OpenAI API Key credential in n8n.
    • In the "OpenAI Chat Model" node, select your OpenAI credential.
  4. Configure Call n8n Workflow Tool:
    • The "Call n8n Workflow Tool" node needs to be configured to execute another n8n workflow. This sub-workflow should contain the logic for interacting with Airtable (e.g., "Airtable" node configured for create, update, get operations).
    • Ensure the sub-workflow is active and accessible.
  5. Configure Airtable Node (within the sub-workflow):
    • In your Airtable interaction sub-workflow, configure the "Airtable" node with your Airtable API Key and Base/Table IDs.
  6. Activate the Workflow: Once all credentials and configurations are set, activate the workflow.

Now, when you send messages to your Telegram bot, the AI agent will process them and interact with your Airtable employee database accordingly.

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.

Ranjan DailataBy 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

Daniel NkenchoBy 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.

Le NguyenBy Le Nguyen
942