by Dick
Basis workflow to convert FileMaker Data API ... to Flat File Array ...
by Matan Grady
Auto-resolve Jira tickets with coding agents Improve issue resolution by assigning Jira tickets to coding agents with full operational context from Port, ensuring faster, accurate, and context-aware development How it works Listen for Jira ticket updates and detect when an issue moves to In Progress with the label product_approved and without copilot_assigned. Query the Port catalog to extract only contextual information relevant to the Jira issue (services, repos, docs, resources, dependencies). Generate a concise GitHub issue title and a self-contained issue body that summarizes the Jira description and includes any found Port context. Create the GitHub issue in the target repository and post a comment that requests Copilot to take ownership. Write the GitHub link back to the Jira ticket and add the copilot_assigned label so the ticket is marked as handled. Setup [ ] Connect your Jira Cloud account and enable issue_updated events [ ] Register for free on Port.io [ ] Connect your Port.io account and add the API key [ ] Connect your GitHub account and select the target repository [ ] Ensure a Copilot bot or @copilot user has access to the repository [ ] Confirm the workflow webhook or Jira trigger URL is active [ ] Test by moving a product_approved ticket to In Progress.
by Omer Fayyaz
This n8n template implements a Calendly Availability Checker that provides real-time availability information for your Calendly event types via a simple API endpoint Who's it for This template is designed for developers, businesses, and service providers who need to programmatically check Calendly availability. It's perfect for: Web developers** building custom booking interfaces that need real-time availability data Chatbot developers** who want to suggest available times to users Website builders** who want to display available slots on their site Integration developers** who need to check availability before creating bookings Businesses** that want to build custom scheduling experiences on top of Calendly Service providers** who need availability data for their own applications or dashboards How it works / What it does This workflow creates a RESTful API endpoint that returns real-time availability information from your Calendly account. The system: Accepts webhook requests via POST with optional parameters: event_type_uri (optional) - Specific event type to check days_ahead (optional, default: 7) - Number of days to check ahead Authenticates with Calendly API using OAuth2 credentials to access your account Retrieves user information to get your Calendly user URI and account details Lists all active event types from your Calendly account Selects the target event type: Uses the event_type_uri from the request if provided Otherwise defaults to the first active event type Fetches available time slots from Calendly's availability API for the specified date range Formats the availability data into a structured response including: Total number of available slots Next available slot (formatted and ISO timestamp) Array of all available slots with formatted times and booking URLs Slots grouped by day for easy consumption Complete list of all event types Returns a comprehensive JSON response with all availability information ready for integration How to set up 1. Configure Calendly OAuth2 Credentials Go to calendly.com/integrations Click "API & Webhooks" Create an OAuth2 application or use Personal Access Token In n8n, create a new credential: Type: "Calendly OAuth2 API" Follow the OAuth flow to connect your Calendly account The credential will be used by all HTTP Request nodes in the workflow 2. Activate the Workflow Open the workflow in n8n Ensure the Calendly OAuth2 credential is properly configured Activate the workflow to make the webhook endpoint available 3. Test the Workflow Use the "Test workflow" button in n8n to manually trigger it Or send a POST request to the webhook URL: { "event_type_uri": "optional-event-uri", "days_ahead": 7 } Verify the response contains availability data Check that the "Get Current User" node successfully retrieves your account info 4. Customize (Optional) Adjust the default days_ahead value in the "Set Configuration" node (currently 7 days) Modify the date range calculation in "Get Available Times" node Customize the response format in "Respond with Availability" node Add filtering logic to select specific event types Add caching to reduce API calls Requirements Calendly account** with at least one active event type n8n instance** (self-hosted or cloud) Calendly OAuth2 API credentials** configured in n8n Webhook access** (if using n8n cloud, webhooks are automatically available) How to customize the workflow Modify Date Range Edit the "Set Configuration" node to change the default days_ahead value Update the start_time and end_time calculations in "Get Available Times" node Currently checks from tomorrow (1 day ahead) to 7 days ahead by default Adjust the date calculation expressions as needed Filter Specific Event Types Modify the "Select Event Type" node to add filtering logic Add an IF node to check event type names or slugs Filter by duration, active status, or custom criteria Return multiple event types if needed Customize Response Format Edit the "Respond with Availability" node to change the JSON structure Add or remove fields from the response Format dates/times differently Include additional metadata from event types Add pagination for large slot lists Add Caching Insert a Code node before "Get Available Times" to check cache Store availability data temporarily to reduce API calls Set appropriate cache expiration times Consider using n8n's built-in cache or external storage Add Error Handling Enhance error handling in HTTP Request nodes Add validation for request parameters Return meaningful error messages in the response Handle cases where no event types exist Handle cases where no availability exists Integrate with Other Services Add nodes to log availability checks to a database Send availability data to analytics platforms Trigger notifications when availability changes Sync availability with external calendars Build availability dashboards Key Features RESTful API endpoint** - Simple POST endpoint for checking availability Real-time availability** - Fetches current availability directly from Calendly API Flexible event type selection** - Supports specific event type or auto-selects first available Configurable date range** - Customizable number of days to check ahead Comprehensive response format** - Returns formatted and raw availability data Multiple data views** - Provides slots as array, grouped by day, and summary statistics Event type information** - Includes details about all available event types Human-readable formatting** - Formats dates and times for easy display Booking URLs included** - Each slot includes direct booking URL Error resilience** - Nodes configured with continueRegularOutput to handle API errors gracefully Use Cases Custom booking widgets** - Display available slots on your website without embedding Calendly Chatbot integration** - Let AI assistants suggest available times to users Mobile app integration** - Check availability before showing booking options in mobile apps Multi-calendar systems** - Aggregate availability from multiple Calendly accounts Availability dashboards** - Build internal dashboards showing team availability Smart scheduling** - Check availability before sending meeting invitations Booking confirmation flows** - Verify availability before processing bookings Calendar sync verification** - Ensure Calendly availability matches other calendar systems Analytics and reporting** - Track availability patterns and booking trends Custom scheduling UIs** - Build completely custom scheduling interfaces using availability data Data Fields Returned User Information User name, email, scheduling URL User URI and organization URI Event Type Information Event type name, duration (minutes), URI Complete list of all active event types with details Availability Summary has_slots - Boolean indicating if any slots are available total_slots - Total number of available slots next_available - Human-readable formatted string of next available slot next_available_iso - ISO 8601 timestamp of next available slot Available Slots Array Each slot includes: start_time - ISO 8601 timestamp formatted - Human-readable date/time string booking_url - Direct URL to book this specific slot Slots by Day Grouped object with days as keys Each day contains array of time slots with formatted times and booking URLs Format: { "Monday, Dec 2": [{ time: "10:00 AM", url: "..." }] } Metadata checked_at - ISO timestamp of when availability was checked success - Boolean indicating successful execution Workflow Architecture The workflow uses a linear processing pattern with data transformation at each step: Webhook Trigger → Receives POST requests with optional parameters Set Configuration → Extracts and sets default values for event_type_uri and days_ahead Get Current User → Authenticates and retrieves Calendly user information Extract User Info → Parses user data to extract URIs and account details Get Event Types → Fetches all active event types for the user Select Event Type → Chooses target event type (from request or first available) Get Available Times → Queries Calendly API for available time slots Format Availability → Transforms raw API data into structured, formatted response Respond with Availability → Returns comprehensive JSON response to caller Example Scenarios Scenario 1: Check Default Availability Developer sends POST request to webhook endpoint with empty body Workflow uses default 7-day lookahead period Workflow selects first active event type automatically Returns availability for next 7 days with all slots formatted Developer displays slots in custom booking interface Scenario 2: Check Specific Event Type Developer sends POST request with specific event_type_uri Workflow uses provided event type instead of default Checks availability for that specific event type only Returns slots grouped by day for easy calendar display Developer shows availability in day-by-day calendar view Scenario 3: Extended Date Range Developer sends POST request with days_ahead: 30 Workflow checks availability for next 30 days Returns comprehensive list of all available slots Developer uses data to show monthly availability view User can see all available times for the next month Scenario 4: Chatbot Integration User asks chatbot "When are you available?" Chatbot calls webhook endpoint to get availability Workflow returns next available slot and total count Chatbot responds: "I have 15 slots available. Next available: Monday, Dec 2 at 10:00 AM" Chatbot offers to book the next available slot This template provides a powerful API endpoint for checking Calendly availability, enabling developers to build custom scheduling experiences while leveraging Calendly's robust scheduling infrastructure.
by Piotr Sobolewski
How it works This intelligent workflow allows you to generate new tweets that closely mimic the unique style of any public Twitter user. It's perfect for content creators, marketers, or anyone wanting to create engaging content with a specific brand voice or personal flair. It automatically: Fetches recent tweets from a specified Twitter handle to understand their distinctive writing style. Analyzes the stylistic patterns (tone, vocabulary, common phrases, emoji use, brevity, etc.) of these tweets using advanced AI. Generates new tweet content on your desired topic, reapplying the learned style. Provides the AI-generated tweet for your review, ready to be copied or directly published. Unleash your content's potential by speaking in a voice that resonates, even if it's not your own! Set up steps Setting up this sophisticated workflow takes around 20-30 minutes, as it involves Twitter API integration and advanced AI prompting. You'll need to: Authenticate your Twitter account (required to fetch tweets). Obtain API keys for your preferred AI service (e.g., OpenAI, Google AI). Provide the Twitter handle of the user whose style you want to copy. Input the new content/topic you want to generate a tweet about. All detailed setup instructions and specific configuration guidance are provided within the workflow itself using sticky notes.
by Chris Jadama
Who it's for YouTube creators, content marketers, and anyone who wants to automatically enrich YouTube links added to a Notion database. What it does Automatically extracts important video and channel data — including title, views, likes, comments, thumbnail, channel name, subscribers, and a custom viral score — whenever a new YouTube URL is added to Notion. How it works A Notion Trigger fires when a new page is added to your database. The workflow extracts the YouTube video ID from the provided URL. A YouTube API request retrieves video details (title, views, likes, comments, thumbnail). A second YouTube API request retrieves channel information (name and subscriber count). Both sets of data are cleaned and formatted. The enriched data is written back to the same Notion page. Requirements YouTube Data API (OAuth2 recommended) Notion integration connected to your workspace This Notion template (includes all required fields): https://lunar-curler-d17.notion.site/2a71d9a77486807a9006d048aa512d16?v=2a71d9a7748680eda620000ca9c112a4 Setup steps Duplicate the Notion template linked above. Connect your Notion credentials in n8n. Create and connect a YouTube OAuth2 credential. Assign your credential to the YouTube API nodes. Test once with a manual execution.
by Marko Korhonen
This workflow contains community nodes that are only compatible with the self-hosted version of n8n. How it works It creates a nested folder in your OneDrive's My Files You could be creating folders like: Foobar Foobar/Barfur Foobar/Barfur/Furbar Workflow checks if any of the folders in the path exists and created only the ones that don't exist. The usual case it to use it in your other workflows and execute it as Sub-workflow. Requirements n8n-nodes-datastore Community node Microsoft Drive account credential
by Alok Kumar
Learn Supabase Storage Fundamentals with n8n This template demonstrates how to integrate Supabase Storage with n8n for uploading, fetching, generating temporary signed URLs, and listing files. It’s a beginner-friendly workflow that helps you understand how to connect Supabase’s storage API with n8n automation. Who it’s for Developers and teams new to Supabase who want a hands-on learning workflow. Anyone looking to automate file uploads and retrieval from Supabase Storage. Educators or technical teams teaching Supabase fundamentals with practical demos. How it works Upload File – A user uploads a file through an n8n form, which gets stored in a Supabase storage bucket. Fetch File – Retrieve files by providing their filename. Temporary Access – Generate signed URLs with custom expiry for secure file sharing. List Objects – View all stored files in the chosen Supabase bucket. How to set up Create a Supabase account and set up a project. Create a bucket in Supabase (e.g., test-n8n). Get your Project URL and Anon Key from Supabase. In n8n, create a Supabase API Credential using your keys. Import this workflow and connect it with your credentials. Run the forms to test file upload, retrieval, and listing. Requirements A Supabase project with storage enabled. A configured Supabase API Credential in n8n. Customization Change the bucket name (test-n8n) to your own. Adjust signed URL expiry times for temporary file access. Replace Supabase with another S3-compatible storage if needed. Extend the workflow with notifications (Slack, Email) after file upload. 📝 Lessons Included Lesson 1** – Upload file to Supabase storage. Lesson 2** – Fetch file from storage. Lesson 3** – Create a temporary signed document with expiry. Lesson 4** – List all items in Supabase storage. 🔑 Prerequisites Supabase account + project. Project URL and API Key (Anon). Bucket created in Supabase. Policy created to allow read/write access. n8n with Supabase API credentials configured.
by Luis Acosta
🤖📝 Auto-Document Workflows with GPT-4o-mini Sticky Notes Skip the tedious part of writing documentation and turn your n8n workflows into clear, shareable blueprints — fully automated. This workflow takes any workflow JSON, parses its nodes, generates structured sticky notes (both per-node and a general overview), and arranges them neatly on your canvas. No more messy layouts or missing documentation — everything is handled in one click. It’s perfect if you want to publish to the n8n marketplace, onboard teammates quickly, or just keep your own automations easy to understand months later. 💡 What this workflow does ✅ Loads your existing workflow from a JSON file 🔍 Parses and unwraps real nodes (ignoring old stickies) 🤖 Uses AI to create concise sticky notes for each node 📝 Adds a general overview sticky with goals, flow, parameters, and gotchas 📐 Arranges all nodes + stickies (node above, sticky below, right-to-left) 💾 Saves a new documented workflow JSON, ready to reuse or share ⚙️ Step-by-step setup Prepare your workflow file Export your n8n workflow JSON or point to an existing file path. Configure the “Load Workflow” node Update the file selector to your JSON path, e.g. /workflows/myflow.json. Add your OpenAI credentials In the OpenAI API nodes (Node Sticky Notes + Overall Sticky Note), insert your API key. Run the workflow Trigger manually with the Execute Workflow node. The script will parse your nodes, generate stickies, and align them on the canvas. Save the result The “Save Documented Workflow” node writes a new file, e.g. /workflows/myflow-with-sticky.json. 🛠 Customization Sticky layout:** Adjust spacing, colors, and alignment in the Layout Blocks RTL node (tweak GAP_X, GAP_Y, or STICKY_COLOR). Word count & style:** Edit prompts inside the OpenAI nodes to make notes shorter, longer, or more technical. Overview focus:** Customize the Your Workflow Description node to pass context (e.g., project goals, intended audience). File outputs:** Save to a new path/version for version control of your documentation. ⚠️ Limitations / Gotchas Maximum of ~50 nodes are summarized in the overview for brevity. Old sticky notes are removed and replaced — you can’t preserve them unless you fork the workflow. Complex nodes (large Code / AI prompts) may require manual edits for clarity. Ensure n8n has read/write access to your workflow JSON paths. 🎯 Expected result After execution, you’ll get a fully documented workflow JSON where each node is paired with a clean sticky note, plus an overview note neatly placed on the canvas. You can open this new file in n8n, share it, or submit it directly to the marketplace. 📬 Contact & Feedback Need help customizing this? Have ideas for improvement? 📩 Luis.acosta@news2podcast.com 🐦 DM me on Twitter @guanchehacker If you’re working on advanced workflow documentation + AI, let’s talk — this template can be a foundation for more powerful tools.
by CustomJS
> ⚠️ Notice: > This workflow uses the CustomJS Invoice Generator node from customjs.space, which requires a self-hosted n8n instance and a CustomJS API key. Google Spreadsheet → Invoice Generation → Email Workflow This workflow demonstrates how to: Pull invoices ready to be sent from Airtable. Retrieve client details and invoice items from Airtable. Generate a professional invoice PDF using CustomJS Invoice Generator. Send the completed invoice via email to the client. Update the invoice status in Airtable automatically. Public Airtable Example Workflow Overview 1. Trigger Workflow Node:** When clicking ‘Execute workflow’ (Manual Trigger) Starts the workflow when executed manually in n8n. 2. Get Ready Invoices Node:** Get Ready Invoices (Airtable) Retrieves all invoices from Airtable where Status = 'Ready'. 3. Loop Over Items Node:** Loop Over Items (Split In Batches) Processes each invoice individually. 4. Get Clients Node:** Get Clients (Airtable) Fetches client details for the current invoice: Name Address Tax ID 5. Get Invoice Items Node:** Get Invoice Items (Airtable) Retrieves all items associated with the invoice and passes them for aggregation. 6. Map Fields Node:** Map Fields (Set) Maps the invoice items into a structured format for the invoice generator: Description Quantity / Hours Unit Price Invoice ID 7. Aggregate Node:** Aggregate Aggregates all invoice items into a single JSON array for the invoice. 8. Set Company Details Node:** Set Company Details (Set) Defines issuer and payment information: Company Name Address Tax ID Email & Phone Bank Details 9. Generate Invoice Node:** Generate Invoice (CustomJS Invoice Generator) Generates a PDF invoice using all collected data: Issuer / Company information Recipient / Client information Invoice items Billing information (Invoice number, date, currency, tax, notes) 10. Send Email With Attachment Node:** Send Email With Attachment (Email Send) Sends the generated invoice PDF to the client: From: {{ $json.InvoiceEmail }} To: info@yourcomp.org Subject: Your Invoice for Last Month Body Text: Hello, Please find attached your invoice for the last month. Thank you very much for your cooperation. Best regards, Henrik Uses SMTP credentials for sending emails. 11. Update Record Node:** Update record (Airtable) Marks the invoice as Sent in Airtable. Requirements Self-hosted n8n instance CustomJS API key SMTP credentials Airtable API key and base access
by PDF Vector
This workflow contains community nodes that are only compatible with the self-hosted version of n8n. Comprehensive Literature Review Automation Automate your literature review process by searching across multiple academic databases, parsing papers, and organizing findings into a structured review document. Features: Search multiple academic databases simultaneously (PubMed, ArXiv, Google Scholar, etc.) Parse and analyze top papers automatically Generate citation-ready summaries Export to various formats (Markdown, Word, PDF) Workflow Steps: Input: Research topic and parameters PDF Vector Search: Query multiple academic databases Filter & Rank: Select top relevant papers Parse Papers: Extract content from PDFs Synthesize: Create literature review sections Export: Generate final document Use Cases: PhD students conducting systematic reviews Researchers exploring new fields Grant writers needing background sections
by AppUnits AI
Generate Invoices for Customers with Jotform and QuickBooks This workflow automates the entire process of receiving a product/service order, checking or creating a customer in QuickBooks Online (QBO), generating an invoice, and emailing it — all triggered by a form submission (via Jotform). How It Works Receive Submission Triggered when a user submits a form. Collects data like customer details, selected product/service, etc. Check If Customer Exists Searches QBO to determine if the customer already exists. If Customer Exists:* *Update** customer details (e.g., billing address). If Customer Doesn’t Exist:* *Create** a new customer in QBO. Get The Item Retrieves the selected product or service from QBO. Create The Invoice Generates a new invoice for the customer using the item selected. Send The Invoice Automatically sends the invoice via email to the customer. Who Can Benefit from This Workflow? Freelancers** Service Providers** Consultants & Coaches** Small Businesses** E-commerce or Custom Product Sellers** Requirements Jotform webhook setup, more info here QuickBooks Online credentials, more info here
by Fabian Perez
This workflow automates the process of scraping, analyzing, and storing real estate data from Zillow using Apify, OpenAI, and Google Sheets. It begins by running an Apify Actor that extracts live property details such as price, location, and key features. The data is then cleaned and processed before being analyzed by an AI model that assigns an investment potential score (1–10). To maintain reliable results, the AI only scores properties that include all required fields — for example, listings missing price or description data are automatically skipped. This ensures that only complete and accurate information is evaluated. Finally, all valid results are appended or updated in a Google Sheet, creating a central, always-up-to-date property database for future analysis. Ideal for real estate investors, analysts, and data-driven agencies, this template provides a fully automated loop for property collection, evaluation, and reporting — all in one flow. Tools used: Apify, OpenAI, Google Sheets, n8n