Build academic citation networks with PDF Vector API for Gephi visualization
This workflow contains community nodes that are only compatible with the self-hosted version of n8n.
Build Citation Networks from Research Papers
Automatically build and visualize citation networks by fetching papers and their references. Discover influential works and research trends in any field.
Workflow Features:
- Start with seed papers (DOIs, PubMed IDs, etc.)
- Fetch cited and citing papers recursively
- Build network graph data
- Export to visualization tools (Gephi, Cytoscape)
- Identify key papers and research clusters
Process Flow:
- Input: Seed paper identifiers
- Fetch Papers: Get paper details and references
- Expand Network: Fetch cited papers (configurable depth)
- Build Graph: Create nodes and edges
- Analyze: Calculate metrics (centrality, clusters)
- Export: Generate visualization-ready data
Applications:
- Research trend analysis
- Finding seminal papers in a field
- Grant proposal background research
n8n Workflow: Academic Citation Network Builder with PDF Vector API for Gephi Visualization
This n8n workflow is designed to process academic citation data, likely extracted from a PDF Vector API, and prepare it for visualization in Gephi or other network analysis tools. It focuses on transforming and structuring data to represent academic papers and their citation relationships.
What it does
This workflow performs the following key steps:
- Initial Data Transformation (Edit Fields): This node is typically used to rename, remove, or modify fields in the incoming data. For academic citations, this might involve standardizing author names, publication years, or abstract fields.
- Custom Code Execution (Code): This node allows for advanced data manipulation using JavaScript. In the context of academic citation networks, this could involve:
- Parsing complex citation strings to extract individual references.
- Creating unique identifiers for papers and authors.
- Generating edge lists (source-target pairs) for citations.
- Aggregating metadata for nodes (papers, authors).
- Filtering out irrelevant data or handling missing values.
- Output to Binary File (Write Binary File): The final processed data is written to a binary file. This is often used for exporting data in formats like CSV, JSON, or GEXF (for Gephi) that can be easily consumed by other applications.
Prerequisites/Requirements
- n8n Instance: A running n8n instance (self-hosted or cloud).
- Data Source: An upstream process or API that provides academic citation data. While not explicitly defined in this JSON, the directory name suggests a "PDF Vector API" is the intended source. The input to this workflow is expected to be the raw or semi-processed output from such an API.
- Understanding of Data Structures: Familiarity with how academic citation data is structured (e.g., authors, titles, publication venues, cited references) will be beneficial for configuring the "Edit Fields" and "Code" nodes.
- JavaScript Knowledge (for Code node): To customize the data transformation logic in the "Code" node.
Setup/Usage
- Import the Workflow:
- Download the provided JSON content.
- In your n8n instance, go to "Workflows" and click "New".
- Click the "Import from JSON" button and paste the workflow JSON.
- Configure the "Edit Fields" Node (ID: 38):
- Adjust the field transformations based on your input data structure to standardize or clean relevant fields (e.g.,
title,authors,year,abstract,references).
- Adjust the field transformations based on your input data structure to standardize or clean relevant fields (e.g.,
- Configure the "Code" Node (ID: 834):
- This is the most critical node for defining the network structure. You will need to write JavaScript code to:
- Parse the input data to identify individual academic papers (nodes).
- Extract cited references from each paper to establish connections (edges).
- Format the output into a structure suitable for network visualization (e.g., a list of nodes with attributes and a list of edges with source/target IDs).
- Consider generating data in a format like CSV (for nodes and edges separately) or GEXF/GraphML if supported by your Gephi import process.
- This is the most critical node for defining the network structure. You will need to write JavaScript code to:
- Configure the "Write Binary File" Node (ID: 46):
- Specify the
File NameandFile Pathwhere the processed data should be saved. - Ensure the
File Contentis linked to the output of the "Code" node, formatted as a string or buffer representing your desired output file content (e.g., CSV string, JSON string). - Select the appropriate
File Encodingif needed.
- Specify the
- Trigger the Workflow:
- This workflow does not have an explicit trigger defined in the JSON. You will need to manually execute it, or connect it to an upstream workflow (e.g., a "Webhook" or "Schedule" node) that provides the input data from your PDF Vector API.
Once executed, the workflow will process the input citation data and save the structured network data to the specified file, ready for import into Gephi for visualization.
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.
Two-way property repair management system with Google Sheets & Drive
This workflow automates the repair request process between tenants and building managers, keeping all updates organized in a single spreadsheet. It is composed of two coordinated workflows, as two separate triggers are required — one for new repair submissions and another for repair updates. A Unique Unit ID that corresponds to individual units is attributed to each request, and timestamps are used to coordinate repair updates with specific requests. General use cases include: Property managers who manage multiple buildings or units. Building owners looking to centralize tenant repair communication. Automation builders who want to learn multi-trigger workflow design in n8n. --- ⚙️ How It Works Workflow 1 – New Repair Requests Behind the Scenes: A tenant fills out a Google Form (“Repair Request Form”), which automatically adds a new row to a linked Google Sheet. Steps: Trigger: Google Sheets rowAdded – runs when a new form entry appears. Extract & Format: Collects all relevant form data (address, unit, urgency, contacts). Generate Unit ID: Creates a standardized identifier (e.g., BUILDING-UNIT) for tracking. Email Notification: Sends the building manager a formatted email summarizing the repair details and including a link to a Repair Update Form (which activates Workflow 2). --- Workflow 2 – Repair Updates Behind the Scenes:\ Triggered when the building manager submits a follow-up form (“Repair Update Form”). Steps: Lookup by UUID: Uses the Unit ID from Workflow 1 to find the existing row in the Google Sheet. Conditional Logic: If photos are uploaded: Saves each image to a Google Drive folder, renames files consistently, and adds URLs to the sheet. If no photos: Skips the upload step and processes textual updates only. Merge & Update: Combines new data with existing repair info in the same spreadsheet row — enabling a full repair history in one place. --- 🧩 Requirements Google Account (for Forms, Sheets, and Drive) Gmail/email node connected for sending notifications n8n credentials configured for Google API access --- ⚡ Setup Instructions (see more detail in workflow) Import both workflows into n8n, then copy one into a second workflow. Change manual trigger in workflow 2 to a n8n Form node. Connect Google credentials to all nodes. Update spreadsheet and folder IDs in the corresponding nodes. Customize email text, sender name, and form links for your organization. Test each workflow with a sample repair request and a repair update submission. --- 🛠️ Customization Ideas Add Slack or Telegram notifications for urgent repairs. Auto-create folders per building or unit for photo uploads. Generate monthly repair summaries using Google Sheets triggers. Add an AI node to create summaries/extract relevant repair data from repair request that include long submissions.
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