HumationHuman + Automation
Back to Catalog

Create literary English/German to Chinese dictionary with GPT-4o-mini & Supabase

Xiaoyuan ZhangXiaoyuan Zhang
457 views
2/3/2026
FormsWebhookHubSpotIntegrationHTTP Request
Official Page

Description

This workflow creates a sophisticated bilingual dictionary that provides literary-style definitions and examples for English and German words. The system automatically detects the input language, generates comprehensive definitions in Chinese, creates three literary-style example sentences with translations, and stores everything in a Supabase database for future reference.

Who Is This For?

  • Language Learners & Students: Perfect for those studying English or German who want to understand words in literary contexts with Chinese translations.
  • Writers & Content Creators: Ideal for bilingual writers working with English, German, and Chinese who need rich, literary examples for their work.
  • Educators & Translators: Excellent tool for language teachers and professional translators who need comprehensive word definitions with contextual examples.
  • Literary Enthusiasts: Great for readers of literature who encounter unfamiliar words and want to understand their poetic or literary usage.

What Problem Does This Workflow Solve?

Traditional dictionaries often provide basic definitions without literary context or cross-language examples. This workflow addresses several key challenges:

  • Limited Literary Context: Most dictionaries lack poetic, expressive, or literary-style examples that help understand how words are used in sophisticated writing.
  • Cross-Language Learning: Provides seamless translation between English/German and Chinese with culturally appropriate examples.
  • Data Persistence: Automatically saves all lookups to a database, creating a personalized vocabulary collection over time.
  • API Accessibility: Provides a clean webhook interface that can be integrated into apps, websites, or other tools.

How It Works

Main Dictionary Lookup Flow

  1. Input Processing: Receives a word via webhook POST request and automatically detects if it's English or German
  2. AI Analysis: Uses OpenAI GPT-4o-mini to generate comprehensive definitions with literary context
  3. Response Formatting: Processes the AI response to extract structured data (word, meaning, examples)
  4. Quality Control: Validates the response and handles unclear or invalid inputs gracefully
  5. Database Storage: Saves the word, Chinese meaning, and examples to Supabase for future reference
  6. API Response: Returns formatted JSON with the complete dictionary entry

Data Storage Flow

  1. Parallel Processing: Simultaneously returns the dictionary data to the user and saves it to the database
  2. Structured Storage: Organizes data in Supabase with fields for words, Chinese meanings, and example arrays
  3. Success Confirmation: Provides confirmation when data is successfully stored

Setup Instructions

Prerequisites & Accounts

You'll need accounts and API access for:

  • n8n (Cloud or self-hosted)
  • OpenAI (API key required)
  • Supabase (Database and API credentials)

Webhook Configuration

  • The workflow uses two webhook endpoints with the same path for different operations
  • Note the webhook URL provided by n8n for API integration
  • Test the webhook endpoints to ensure they're accessible approach

Customization Options

  • Extend to support additional input languages by modifying the AI prompt
  • Add support for other target languages beyond Chinese
  • Customize the literary style for different cultural contexts

This workflow transforms simple word lookups into rich, contextual learning experiences while building a personalized vocabulary database over time.

Create Literary English/German to Chinese Dictionary with GPT-4o Mini & Supabase

This n8n workflow automates the creation of a literary dictionary, translating English and German terms into Chinese, leveraging the power of GPT-4o Mini and storing the results in Supabase. It's designed to process input, generate translations, and manage the data efficiently.

What it does

This workflow streamlines the process of building a multilingual dictionary:

  1. Receives Input: It starts by listening for incoming data via a webhook, which likely contains the English or German terms to be translated.
  2. Initial Data Processing: The received data is then processed by an "Edit Fields (Set)" node, which prepares the data for the subsequent AI processing.
  3. Conditional Logic: An "If" node evaluates the incoming data, likely checking for specific conditions or data integrity before proceeding.
  4. AI-Powered Translation: If the conditions are met, an "AI Agent" node, configured with an "OpenAI Chat Model" (presumably GPT-4o Mini), takes the input and generates the Chinese translations.
  5. Code Execution: A "Code" node is used for custom logic, potentially to format the AI's output or perform additional data manipulation.
  6. Database Storage: The translated and processed data is then inserted into a Supabase database.
  7. Webhook Response: Finally, the workflow responds to the initial webhook, indicating the completion of the process.

Prerequisites/Requirements

To use this workflow, you will need:

  • n8n Instance: A running n8n instance (self-hosted or cloud).
  • OpenAI API Key: An API key for OpenAI to use the GPT-4o Mini model.
  • Supabase Account: Access to a Supabase project with a configured table for storing dictionary entries.
  • Webhook Trigger: An external system or application capable of sending data to the n8n webhook.

Setup/Usage

  1. Import the Workflow:

    • Download the provided JSON file for this workflow.
    • In your n8n instance, click "Workflows" in the left sidebar.
    • Click "New" and then "Import from JSON".
    • Paste the workflow JSON or upload the file.

  2. Configure Credentials:

    • OpenAI Chat Model: Locate the "OpenAI Chat Model" node. You will need to set up an OpenAI credential with your API key.
    • Supabase: Locate the "Supabase" node. You will need to set up a Supabase credential with your project URL and API key.

  3. Configure Webhook:

    • Locate the "Webhook" node.
    • Copy the webhook URL. This is the endpoint you will send your English/German terms to.

  4. Configure Nodes:

    • Edit Fields (Set): Adjust the fields being set to match your incoming data structure and the expected input for the AI model.
    • If: Review and modify the conditions in the "If" node to suit your specific validation requirements.
    • AI Agent / OpenAI Chat Model: Ensure the prompt and model parameters are correctly configured for generating the desired literary Chinese translations.
    • Code: If custom logic is required, update the JavaScript code within this node.
    • Supabase: Configure the "Supabase" node to target your specific table and columns where the dictionary entries should be stored.

  5. Activate the Workflow:

    • Once all credentials and nodes are configured, activate the workflow by toggling the "Active" switch in the top right corner of the n8n editor.

  6. Trigger the Workflow:

    • Send a POST request to the webhook URL (obtained in step 3) with the English or German terms you wish to translate. The body of the request should match the expected input structure configured in your "Edit Fields (Set)" and "If" nodes.

Related Templates

Automate Dutch Public Procurement Data Collection with TenderNed

TenderNed Public Procurement What This Workflow Does This workflow automates the collection of public procurement data from TenderNed (the official Dutch tender platform). It: Fetches the latest tender publications from the TenderNed API Retrieves detailed information in both XML and JSON formats for each tender Parses and extracts key information like organization names, titles, descriptions, and reference numbers Filters results based on your custom criteria Stores the data in a database for easy querying and analysis Setup Instructions This template comes with sticky notes providing step-by-step instructions in Dutch and various query options you can customize. Prerequisites TenderNed API Access - Register at TenderNed for API credentials Configuration Steps Set up TenderNed credentials: Add HTTP Basic Auth credentials with your TenderNed API username and password Apply these credentials to the three HTTP Request nodes: "Tenderned Publicaties" "Haal XML Details" "Haal JSON Details" Customize filters: Modify the "Filter op ..." node to match your specific requirements Examples: specific organizations, contract values, regions, etc. How It Works Step 1: Trigger The workflow can be triggered either manually for testing or automatically on a daily schedule. Step 2: Fetch Publications Makes an API call to TenderNed to retrieve a list of recent publications (up to 100 per request). Step 3: Process & Split Extracts the tender array from the response and splits it into individual items for processing. Step 4: Fetch Details For each tender, the workflow makes two parallel API calls: XML endpoint - Retrieves the complete tender documentation in XML format JSON endpoint - Fetches metadata including reference numbers and keywords Step 5: Parse & Merge Parses the XML data and merges it with the JSON metadata and batch information into a single data structure. Step 6: Extract Fields Maps the raw API data to clean, structured fields including: Publication ID and date Organization name Tender title and description Reference numbers (kenmerk, TED number) Step 7: Filter Applies your custom filter criteria to focus on relevant tenders only. Step 8: Store Inserts the processed data into your database for storage and future analysis. Customization Tips Modify API Parameters In the "Tenderned Publicaties" node, you can adjust: offset: Starting position for pagination size: Number of results per request (max 100) Add query parameters for date ranges, status filters, etc. Add More Fields Extend the "Splits Alle Velden" node to extract additional fields from the XML/JSON data, such as: Contract value estimates Deadline dates CPV codes (procurement classification) Contact information Integrate Notifications Add a Slack, Email, or Discord node after the filter to get notified about new matching tenders. Incremental Updates Modify the workflow to only fetch new tenders by: Storing the last execution timestamp Adding date filters to the API query Only processing publications newer than the last run Troubleshooting No data returned? Verify your TenderNed API credentials are correct Check that you have setup youre filter proper Need help setting this up or interested in a complete tender analysis solution? Get in touch 🔗 LinkedIn – Wessel Bulte

Wessel BulteBy Wessel Bulte
247

🎓 How to transform unstructured email data into structured format with AI agent

This workflow automates the process of extracting structured, usable information from unstructured email messages across multiple platforms. It connects directly to Gmail, Outlook, and IMAP accounts, retrieves incoming emails, and sends their content to an AI-powered parsing agent built on OpenAI GPT models. The AI agent analyzes each email, identifies relevant details, and returns a clean JSON structure containing key fields: From – sender’s email address To – recipient’s email address Subject – email subject line Summary – short AI-generated summary of the email body The extracted information is then automatically inserted into an n8n Data Table, creating a structured database of email metadata and summaries ready for indexing, reporting, or integration with other tools. --- Key Benefits ✅ Full Automation: Eliminates manual reading and data entry from incoming emails. ✅ Multi-Source Integration: Handles data from different email providers seamlessly. ✅ AI-Driven Accuracy: Uses advanced language models to interpret complex or unformatted content. ✅ Structured Storage: Creates a standardized, query-ready dataset from previously unstructured text. ✅ Time Efficiency: Processes emails in real time, improving productivity and response speed. *✅ Scalability: Easily extendable to handle additional sources or extract more data fields. --- How it works This workflow automates the transformation of unstructured email data into a structured, queryable format. It operates through a series of connected steps: Email Triggering: The workflow is initiated by one of three different email triggers (Gmail, Microsoft Outlook, or a generic IMAP account), which constantly monitor for new incoming emails. AI-Powered Parsing & Structuring: When a new email is detected, its raw, unstructured content is passed to a central "Parsing Agent." This agent uses a specified OpenAI language model to intelligently analyze the email text. Data Extraction & Standardization: Following a predefined system prompt, the AI agent extracts key information from the email, such as the sender, recipient, subject, and a generated summary. It then forces the output into a strict JSON structure using a "Structured Output Parser" node, ensuring data consistency. Data Storage: Finally, the clean, structured data (the from, to, subject, and summarize fields) is inserted as a new row into a specified n8n Data Table, creating a searchable and reportable database of email information. --- Set up steps To implement this workflow, follow these configuration steps: Prepare the Data Table: Create a new Data Table within n8n. Define the columns with the following names and string type: From, To, Subject, and Summary. Configure Email Credentials: Set up the credential connections for the email services you wish to use (Gmail OAuth2, Microsoft Outlook OAuth2, and/or IMAP). Ensure the accounts have the necessary permissions to read emails. Configure AI Model Credentials: Set up the OpenAI API credential with a valid API key. The workflow is configured to use the model, but this can be changed in the respective nodes if needed. Connect the Nodes: The workflow canvas is already correctly wired. Visually confirm that the email triggers are connected to the "Parsing Agent," which is connected to the "Insert row" (Data Table) node. Also, ensure the "OpenAI Chat Model" and "Structured Output Parser" are connected to the "Parsing Agent" as its AI model and output parser, respectively. Activate the Workflow: Save the workflow and toggle the "Active" switch to ON. The triggers will begin polling for new emails according to their schedule (e.g., every minute), and the automation will start processing incoming messages. --- Need help customizing? Contact me for consulting and support or add me on Linkedin.

DavideBy Davide
1616

Tax deadline management & compliance alerts with GPT-4, Google Sheets & Slack

AI-Driven Tax Compliance & Deadline Management System Description Automate tax deadline monitoring with AI-powered insights. This workflow checks your tax calendar daily at 8 AM, uses GPT-4 to analyze upcoming deadlines across multiple jurisdictions, detects overdue and critical items, and sends intelligent alerts via email and Slack only when immediate action is required. Perfect for finance teams and accounting firms who need proactive compliance management without manual tracking. 🏛️🤖📊 Good to Know AI-Powered: GPT-4 provides risk assessment and strategic recommendations Multi-Jurisdiction: Handles Federal, State, and Local tax requirements automatically Smart Alerts: Only notifies executives when deadlines are overdue or critical (≤3 days) Priority Classification: Categorizes deadlines as Overdue, Critical, High, or Medium priority Dual Notifications: Critical alerts to leadership + daily summaries to team channel Complete Audit Trail: Logs all checks and deadlines to Google Sheets for compliance records How It Works Daily Trigger - Runs at 8:00 AM every morning Fetch Data - Pulls tax calendar and company configuration from Google Sheets Analyze Deadlines - Calculates days remaining, filters by jurisdiction/entity type, categorizes by priority AI Analysis - GPT-4 provides strategic insights and risk assessment on upcoming deadlines Smart Routing - Only sends alerts if overdue or critical deadlines exist Critical Alerts - HTML email to executives + Slack alert for urgent items Team Updates - Slack summary to finance channel with all upcoming deadlines Logging - Records compliance check results to Google Sheets for audit trail Requirements Google Sheets Structure Sheet 1: TaxCalendar DeadlineID | DeadlineName | DeadlineDate | Jurisdiction | Category | AssignedTo | IsActive FED-Q1 | Form 1120 Q1 | 2025-04-15 | Federal | Income | John Doe | TRUE Sheet 2: CompanyConfig (single row) Jurisdictions | EntityType | FiscalYearEnd Federal, California | Corporation | 12-31 Sheet 3: ComplianceLog (auto-populated) Date | AlertLevel | TotalUpcoming | CriticalCount | OverdueCount 2025-01-15 | HIGH | 12 | 3 | 1 Credentials Needed Google Sheets - Service Account OAuth2 OpenAI - API Key (GPT-4 access required) SMTP - Email account for sending alerts Slack - Bot Token with chat:write permission Setup Steps Import workflow JSON into n8n Add all 4 credentials Replace these placeholders: YOURTAXCALENDAR_ID - Tax calendar sheet ID YOURCONFIGID - Company config sheet ID YOURLOGID - Compliance log sheet ID C12345678 - Slack channel ID tax@company.com - Sender email cfo@company.com - Recipient email Share all sheets with Google service account email Invite Slack bot to channels Test workflow manually Activate the trigger Customizing This Workflow Change Alert Thresholds: Edit "Analyze Deadlines" node: Critical: Change <= 3 to <= 5 for 5-day warning High: Change <= 7 to <= 14 for 2-week notice Medium: Change <= 30 to <= 60 for 2-month lookout Adjust Schedule: Edit "Daily Tax Check" trigger: Change hour/minute for different run time Add multiple trigger times for tax season (8 AM, 2 PM, 6 PM) Add More Recipients: Edit "Send Email" node: To: cfo@company.com, director@company.com CC: accounting@company.com BCC: archive@company.com Customize Email Design: Edit "Format Email" node to change colors, add logo, or modify layout Add SMS Alerts: Insert Twilio node after "Is Critical" for emergency notifications Integrate Task Management: Add HTTP Request node to create tasks in Asana/Jira for critical deadlines Troubleshooting | Issue | Solution | |-------|----------| | No deadlines found | Check date format (YYYY-MM-DD) and IsActive = TRUE | | AI analysis failed | Verify OpenAI API key and account credits | | Email not sending | Test SMTP credentials and check if critical condition met | | Slack not posting | Invite bot to channel and verify channel ID format | | Permission denied | Share Google Sheets with service account email | 📞 Professional Services Need help with implementation or customization? Our team offers: 🎯 Custom workflow development 🏢 Enterprise deployment support 🎓 Team training sessions 🔧 Ongoing maintenance 📊 Custom reporting & dashboards 🔗 Additional API integrations Discover more workflows – Get in touch with us

Oneclick AI SquadBy Oneclick AI Squad
93