Automate daily YouTrack task summaries to Discord by assignee
Daily YouTrack In-Progress Tasks Summary to Discord by Assignee
Keep your team in sync with a daily summary of tasks currently In Progress in YouTrack β automatically posted to your Discord channel.
This workflow queries issues, filters them by status, groups them by assignee and priority, and sends a formatted message to Discord. It's perfect for teams that need a lightweight, automated stand-up report.
> π This workflow uses Discord as an example. You can easily replace the messaging integration with Slack, Mattermost, MS Teams, or any other platform that supports incoming webhooks.
Use Case
- Remote development teams using YouTrack + Discord
- Replacing daily stand-up meetings with async updates
- Project managers needing quick visibility into active tasks
Features
- Scheduled daily execution (default: weekdays at 09:00)
- Status filter: only issues marked as
In Progress - Grouping by assignee and priority
- Custom mapping for user mentions (YouTrack β Discord)
- Clean Markdown output for Discord, with direct task links
Setup Instructions
YouTrack Configuration
-
Get a permanent token:
- Go to your YouTrack profile β Account Security β Authentication
- Create a new permanent token with "Read Issue" permissions
- Copy the token value
-
Set the base API URL:
- Format:
https://yourdomain.youtrack.cloud/api/issues - Replace
yourdomainwith your actual YouTrack instance
- Format:
-
Identify custom field IDs:
- Method 1: Go to YouTrack β Administration β Custom Fields β find your "Status" field and note its ID
- Method 2: Use API call
GET /api/admin/customFieldSettings/customFieldsto list all field IDs - Method 3: Inspect a task's API response and look for field IDs in the
customFieldsarray - Example Status field ID:
105-0or142-1
Discord Configuration
- Create a webhook URL in your Discord server:
- Server Settings β Integrations β Webhooks β New Webhook
- Choose target channel and copy the webhook URL
- Extract webhook ID from URL (numbers after
/webhooks/)
Environment Variables & Placeholders
| Placeholder | Description |
|-------------|-------------|
| {{API_URL}} | Your YouTrack API base URL |
| {{TOKEN}} | YouTrack permanent token |
| {{FIELD_ID}} | ID of the "Status" custom field |
| {{QUERY_FIELDS}} | Fields to fetch (e.g., summary, id) |
| {{PROJECT_LINK}} | Link to your YouTrack project |
| {{USER_X}} | YouTrack usernames |
| {{DISCORD_ID_X}} | Discord mentions or usernames |
| {{NAME_X}} | Display names |
| {{WEBHOOK_ID}} | Discord webhook ID |
| {{DISCORD_CHANNEL}} | Discord channel name |
| {{CREDENTIAL_ID}} | Your credential ID in n8n |
Testing the Workflow
-
Test YouTrack connection:
- Execute the "HTTP Request YT" node individually
- Verify that issues are returned from your YouTrack instance
- Check if the Status field ID is correctly filtering tasks
-
Verify filtering:
- Run the "Filter fields" node
- Confirm only "In Progress" tasks pass through
-
Check message formatting:
- Execute the "Discord message" node
- Review the generated message content and formatting
-
Test Discord delivery:
- Run the complete workflow manually
- Verify the message appears in your Discord channel
-
Schedule verification:
- Enable the workflow
- Test weekend skip functionality by temporarily changing dates
Customization Tips
- Language: All labels/messages are in English β customize if needed
- User mapping: Adjust assignee β Discord mention logic in the message builder
- Priorities: Update the
priorityMapto reflect your own naming structure - Schedule: Modify the trigger time in the
Schedule Triggernode - Alternative platforms: Swap out the Discord webhook for another messaging service if preferred
Automate Daily YouTrack Task Summaries to Discord by Assignee
This n8n workflow automates the process of fetching daily task summaries from YouTrack and posting them to a Discord channel, organized by assignee. It helps teams stay updated on task progress and ensures accountability by highlighting individual contributions.
What it does
- Triggers Daily: The workflow is scheduled to run automatically at a specific time each day.
- Fetches YouTrack Tasks: It makes an HTTP request to the YouTrack API to retrieve a list of tasks.
- Filters Tasks: It filters the retrieved tasks based on certain criteria (e.g., tasks updated today, specific project, etc.).
- Processes and Groups Tasks: It uses a Code node to process the YouTrack data, likely grouping tasks by assignee and formatting them into a digestible summary.
- Checks for Data: An If node checks if there are any tasks to report after processing.
- Posts to Discord: If tasks are found, it sends the formatted summary to a designated Discord channel.
Prerequisites/Requirements
- n8n Instance: A running n8n instance.
- YouTrack Account & API Token: Access to a YouTrack instance and an API token with permissions to read tasks.
- Discord Webhook: A Discord channel and a configured webhook URL to post messages.
Setup/Usage
- Import the Workflow:
- Copy the provided JSON code.
- In your n8n instance, go to "Workflows" and click "New".
- Click the "Import from JSON" button and paste the workflow JSON.
- Configure Credentials:
- HTTP Request Node (ID: 19):
- Update the URL to your YouTrack API endpoint (e.g.,
https://your-youtrack-instance.com/api/issues). - Configure the authentication method (e.g., "Header Auth" with your YouTrack API token).
- Adjust query parameters or body to fetch the desired tasks (e.g.,
fields=id,summary,assignee(name),updated).
- Update the URL to your YouTrack API endpoint (e.g.,
- Discord Node (ID: 60):
- Select or create a Discord credential.
- Enter your Discord Webhook URL.
- Customize the message content to display the YouTrack summary as desired.
- HTTP Request Node (ID: 19):
- Configure Schedule Trigger (ID: 839):
- Set the desired time and frequency for the workflow to run (e.g., daily at 9 AM).
- Configure Code Node (ID: 834):
- Review and adjust the JavaScript code to correctly parse the YouTrack API response and format the task summary as needed for your Discord message. This is where you'll define how tasks are grouped by assignee.
- Configure Filter Node (ID: 844):
- Adjust the conditions to filter YouTrack tasks according to your specific requirements (e.g.,
updated > today(), specific project IDs, etc.).
- Adjust the conditions to filter YouTrack tasks according to your specific requirements (e.g.,
- Activate the Workflow: Once configured, activate the workflow to start receiving daily YouTrack task summaries in Discord.
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.
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
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.