HumationHuman + Automation
Back to Catalog

Medical symptom checker & health assistant with GPT-4-mini

Jah cooziJah coozi
2672 views
2/3/2026
Data ParsingEvent ManagementTriggerAutomationGoogle Calendar
Official Page

AI Medical Symptom Checker & Health Assistant

A responsible, privacy-focused health information assistant that provides general health guidance while maintaining strict safety protocols and medical disclaimers.

⚠️ IMPORTANT DISCLAIMER

This tool provides general health information only and is NOT a substitute for professional medical advice, diagnosis, or treatment. Always consult qualified healthcare providers for medical concerns.

🚀 Key Features

Safety First

  • Emergency Detection: Automatically identifies emergency situations
  • Immediate Escalation: Provides emergency numbers for critical cases
  • Clear Disclaimers: Every response includes medical disclaimers
  • No Diagnosis: Never attempts to diagnose conditions
  • Professional Referral: Always recommends consulting healthcare providers

Core Functionality

  • Symptom Information: General information about common symptoms
  • Wellness Guidance: Health tips and preventive care
  • Medication Reminders: General medication information
  • Multi-Language Support: Serve diverse communities
  • Privacy Protection: No data storage, anonymous processing
  • Resource Links: Connects to trusted health resources

🎯 Use Cases

  1. General Health Information: Learn about symptoms and conditions
  2. Pre-Appointment Preparation: Organize questions for doctors
  3. Wellness Education: General health and prevention tips
  4. Emergency Detection: Immediate guidance for critical situations
  5. Health Resource Navigation: Find appropriate care providers

🛡️ Safety Protocols

Emergency Keywords Detection

  • Chest pain, heart attack, stroke
  • Breathing difficulties
  • Severe bleeding, unconsciousness
  • Allergic reactions, poisoning
  • Mental health crises

Response Guidelines

  • Never diagnoses conditions
  • Never prescribes medications
  • Always includes disclaimers
  • Encourages professional consultation
  • Provides emergency numbers when needed

🔧 Setup Instructions

  1. Configure OpenAI API

    • Add your API key
    • Set temperature to 0.3 for consistency

  2. Review Legal Requirements

    • Check local health information regulations
    • Customize disclaimers as needed
    • Implement required data policies

  3. Emergency Contacts

    • Update emergency numbers for your region
    • Add local health resources
    • Include mental health hotlines

  4. Test Thoroughly

    • Verify emergency detection
    • Check disclaimer display
    • Test various symptom queries

💡 Example Interactions

General Symptom Query:

  • User: "I have a headache for 3 days"
  • Bot: Provides general headache information, self-care tips, when to see a doctor

Emergency Detection:

  • User: "Chest pain, can't breathe"
  • Bot: EMERGENCY response with immediate action steps and emergency numbers

Wellness Query:

  • User: "How can I improve my sleep?"
  • Bot: General sleep hygiene tips and healthy habits information

🏥 Integration Options

  • Healthcare Websites: Embed as support widget
  • Telemedicine Platforms: Pre-consultation tool
  • Health Apps: General information module
  • Insurance Portals: Member resource
  • Pharmacy Systems: General drug information

📊 Compliance & Privacy

  • HIPAA Considerations: No PHI storage
  • GDPR Compliant: No personal data retention
  • Anonymous Processing: Session-based only
  • Audit Trails: Optional logging for compliance
  • Data Encryption: Secure transmission

🚨 Limitations

  • Cannot diagnose medical conditions
  • Cannot prescribe treatments
  • Cannot replace emergency services
  • Cannot provide specific medical advice
  • Should not delay seeking medical care

🔒 Best Practices

  1. Always maintain clear disclaimers
  2. Never minimize serious symptoms
  3. Encourage professional consultation
  4. Keep information general and educational
  5. Update emergency contacts regularly
  6. Review and update health information
  7. Monitor for misuse
  8. Maintain audit trails where required

🌍 Customization Options

  • Add local emergency numbers
  • Include regional health resources
  • Translate to local languages
  • Integrate with local health systems
  • Add specific disclaimers
  • Customize for specific populations

Start providing responsible health information today!

n8n Medical Symptom Checker / Health Assistant with GPT-4 Mini

This n8n workflow acts as a health assistant, enabling users to check medical symptoms using an OpenAI GPT model and store the interactions in Airtable. It provides a structured way to receive symptom descriptions, process them with AI, and maintain a record of health inquiries.

What it does

  1. Receives Symptom Input: Listens for incoming POST requests via a Webhook, expecting a symptom field in the request body.
  2. Validates Input: Checks if the symptom field is present in the incoming request. If not, it responds with an error.
  3. Generates AI Response: If the symptom is present, it uses OpenAI (likely GPT-4 Mini, as hinted by the directory name) to generate a health-related response based on the provided symptom.
  4. Stores Interaction in Airtable: Records the received symptom and the AI-generated response into an Airtable base.
  5. Responds to User: Sends the AI-generated health response back to the original Webhook caller.

Prerequisites/Requirements

  • n8n Instance: A running n8n instance to host the workflow.
  • Airtable Account: An Airtable account with a configured base and table to store symptom inquiries.
    • You will need to configure the Airtable node with your API Key, Base ID, and Table Name.
  • OpenAI API Key: An OpenAI API key with access to the GPT model used (e.g., GPT-4 Mini).
    • You will need to configure the OpenAI node with your API Key.

Setup/Usage

  1. Import the Workflow:
    • Download the provided JSON file.
    • In your n8n instance, click "Workflows" in the left sidebar.
    • Click "New" -> "Import from JSON" and paste the workflow JSON or upload the file.
  2. Configure Credentials:
    • Airtable: Locate the "Airtable" node (ID: 2). Click on it, then click "Create New Credential" or select an existing one. Provide your Airtable API Key.
    • OpenAI: Locate the "OpenAI" node (ID: 1250). Click on it, then click "Create New Credential" or select an existing one. Provide your OpenAI API Key.
  3. Configure Airtable Node:
    • In the "Airtable" node, set the "Base ID" and "Table Name" to match your Airtable setup where you want to store the symptom data. Ensure your table has columns for "Symptom" and "AI Response".
  4. Activate the Workflow:
    • Click the "Activate" toggle in the top right corner of the n8n editor to enable the workflow.
  5. Trigger the Workflow:
    • The workflow is triggered by an HTTP POST request to the Webhook URL.
    • You can find the Webhook URL in the "Webhook" node (ID: 47).
    • Send a POST request to this URL with a JSON body containing a symptom field, for example: 
      {
  "symptom": "I have a persistent cough and a sore throat."
}
    • The workflow will process the request, interact with OpenAI, store data in Airtable, and return the AI's response.

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