Extract Japanese RFP Requirements Matrix to CSV with n8n Code Nodes

Turn Japanese RFP text into a requirements matrix CSV—automatically

This n8n workflow extracts Japanese RFP requirements from plain text and converts them into a structured requirements matrix, adding IDs, priority (必須/推奨), category, evidence needs, and status. It outputs both JSON and a UTF-8 CSV you can open in Excel or Google Sheets.

What this workflow does

When you manually run the workflow, it transforms your RFP text into an actionable matrix:

• Loads input data (a sample project_name and rfp_text), which you can replace with your own source later (e.g., webhook, form, or file import).
• Splits the RFP into individual lines and evaluates each line for priority and category using keyword rules.
• Generates structured requirement records, including a requirement ID plus default fields such as evidence needed and status.
• Builds a single requirements matrix, then calculates a summary (counts by priority and unique categories).
• Creates a BOM-prefixed UTF-8 CSV string suitable for spreadsheets.
• Outputs a final payload containing: requirements (array), summary, and csv_utf8.

Use cases

• Convert Japanese RFP documents into a spreadsheet-ready requirements tracker for procurement or solution planning.
• Standardize requirement capture across SaaS operators and automation engineers when reviewing multiple RFPs.
• Speed up evidence planning by ensuring each requirement row includes “evidence needed” and a workflow-friendly status field.

Technical details

• Trigger: Manual Trigger
• Core logic: Code nodes to split, classify, assign IDs, compile the matrix, and generate the BOM-prefixed UTF-8 CSV
• Documentation/UI: Sticky Note

To use it, replace the sample input with your own mapping for project_name and rfp_text, and adjust the priority/category keyword rules to match your organization’s RFP terminology.