HumationHuman + Automation
Back to Catalog

Automate agile project setup with GPT-5 Mini, Jira & form interface

Billy ChristiBilly Christi
420 views
2/3/2026
S3AutomationScheduleAPICSV
Official Page

Who is this for?

This workflow is perfect for:

  • Agile development teams and project managers who need to quickly set up Jira projects
  • Product managers who want to convert feature ideas into structured user stories and tasks
  • Software development agencies that need to rapidly create detailed project structures for clients
  • Scrum masters seeking to automate the initial project setup and backlog creation process

What problem is this workflow solving?

Creating comprehensive Jira projects with detailed user stories and sub-tasks is time-consuming and often inconsistent. This workflow solves those issues by:

  • Automating project creation from basic feature descriptions to fully structured Jira projects
  • Generating professional user stories following Agile best practices with proper "As a [user], I want to [goal], so that [benefit]" formatting
  • Creating detailed sub-tasks covering design, development, testing, and documentation phases

What this workflow does

This workflow transforms raw project ideas into fully structured Jira projects with comprehensive user stories and sub-tasks using AI-powered analysis and automated Jira integration.

Step by step:

  1. Form Trigger collects project name and feature descriptions through a web form
  2. Project Naming uses GPT-4.1 mini to clean and professionalize the project name while generating a unique project key
  3. Create Project establishes a new Jira project with proper software development template and configuration
  4. Get Status ID retrieves project details and available issue types for story creation
  5. Jira Story Generator analyzes project features using AI to create structured user stories with sub-tasks
  6. Create Story generates individual Jira stories with proper titles and descriptions
  7. Execute Sub-task Workflow automatically creates all associated sub-tasks for each story
  8. Gmail Notification sends completion confirmation with project details and direct links

How to set up

  1. Connect your Jira account by adding your Jira Software Cloud API credentials to all Jira-related nodes
  2. Update Jira URL in the "Set Jira URL" node to match your Jira instance (e.g., https://yourcompany.atlassian.net)
  3. Add OpenAI API key to the OpenAI Chat Model node for AI-powered story generation
  4. Configure Gmail credentials for the notification node and update the recipient email address
  5. Update project lead in the Create Project node by replacing the leadAccountId with your user ID
  6. Test the workflow using the manual trigger with sample project data
  7. Customize story templates in the Structured Output Parser if you need different story formats
  8. Set up the sub-workflow by ensuring the Execute Workflow node points to the correct workflow ID

How to customize this workflow to your needs

  • Adjust story generation prompts: modify the AI prompts in the "Jira Story Generator" to match your team's specific story writing style or include additional fields
  • Include estimation: add story point estimation logic or time tracking fields to generated stories
  • Switch AI models: replace the OpenAI Chat Model node with other AI providers like Google Gemini, Claude, or local models by using the appropriate n8n AI nodes for different cost and performance requirements

Need help customizing?

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

Automate Agile Project Setup with GPT-5 Mini, Jira & Form Interface

This n8n workflow streamlines the process of setting up agile projects by combining a user-friendly form interface with the power of AI and Jira. It allows users to submit project details, which are then processed by an AI model to generate detailed user stories and tasks, and subsequently created as issues in Jira.

What it does

This workflow automates the following steps:

  1. Listens for Form Submissions: Triggers when a new project request is submitted via an n8n form.
  2. Generates Project Details with AI: Uses an OpenAI Chat Model (GPT-5 Mini) to generate comprehensive user stories and tasks based on the project description provided in the form.
  3. Parses AI Output: Extracts structured data (user stories, tasks) from the AI's response using a Structured Output Parser.
  4. Creates Jira Project: Initiates the creation of a new project in Jira Software.
  5. Creates Jira Issues (User Stories): Iterates through the generated user stories and creates them as separate issues in the newly created Jira project.
  6. Creates Jira Issues (Tasks): For each user story, it further iterates through the associated tasks and creates them as sub-tasks or standard tasks under their respective user stories in Jira.
  7. Sends Confirmation Email: Notifies the submitter via Gmail that their project has been successfully set up in Jira, including a link to the new project.

Prerequisites/Requirements

To use this workflow, you will need:

  • n8n Instance: A running instance of n8n.
  • OpenAI API Key: For the OpenAI Chat Model (GPT-5 Mini).
  • Jira Software Account: With appropriate API access and permissions to create projects and issues.
  • Gmail Account: Configured as a credential in n8n for sending confirmation emails.

Setup/Usage

  1. Import the workflow: Import the provided JSON into your n8n instance.
  2. Configure Credentials:
    • Set up your OpenAI API Key credential for the "OpenAI Chat Model" node.
    • Configure your Jira Software credential for the "Jira Software" nodes. This typically involves an API token and your Jira instance URL.
    • Set up your Gmail credential for the "Gmail" node.
  3. Configure the n8n Form Trigger:
    • The "On form submission" node is pre-configured with fields like "Project Name" and "Project Description". You can customize these fields as needed.
    • After saving the workflow, activate it to get the unique URL for your form.
  4. Customize AI Prompts (Optional): Review the "Basic LLM Chain" node to adjust the prompt for generating user stories and tasks if the default output isn't meeting your needs.
  5. Customize Jira Project/Issue Creation:
    • Adjust the "Jira Software" nodes for creating projects and issues to match your Jira instance's specific project types, issue types, and required fields.
  6. Customize Confirmation Email: Modify the "Gmail" node to personalize the confirmation email content.
  7. Activate the Workflow: Ensure the workflow is active to start processing form submissions.
  8. Submit a Project Request: Access the generated form URL and submit a project request to test the automation.

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