Webhook and Dropbox integration

WATCH THE n8n STARTER GUIDE 👇 This template is featured in the n8n Starter Guide series. The template is free, but comes with two additional PDFs and a Quick Start video if you grab the full download pack on gumroad. How it works This template is a visual map of many useful n8n nodes. It groups nodes like Triggers, AI tools, and App connectors onto the canvas. Explore the sections to learn about different nodes and easily copy them for your own workflows. It acts as a handy visual reference guide. Set up steps • Setup takes about 5 minutes. • Import the template into your n8n instance. • Explore the node categories visually on the canvas. • A Quick Start video is included in the download pack, along with a prompts PDF and PDF with links to other awesome n8n templates here on the n8n template gallery.

Automated n8n workflow: Receives videos via form, dubs/translates them to the selected languages, and—upon completion—uploads them to multiple social media channels and cloud drives, including Box, Dropbox, and YouTube, Telegram, Postiz (Facebook, Instagram, Tiktok, Reddit etc.) Workflows Via n8n form select files to dub for desired languages. Listen webhook and whenever dubbing finishes upload to desired platforms Used Stacks DubLab App (ApiKey, Webhook Setup Required) Optional (Upload) Telegram (Token Required) Box (Oauth2 Required) Dropbox (Oauth2 Required) Youtube (Oauth2 Required) Postiz (ApiKey Required)

Here's the corrected English text: Dropbox Folder Monitoring Workflow As we don't have (yet?) a Dropbox node "Watching new files" or "Watching folder", I created this central workflow to do it. How it works Triggered by Dropbox webhook I respond immediately to Dropbox to avoid webhook disabling Then I add/duplicate one branch per monitored folder, according to my needs In my case, I need to monitor several folders, like "vocal notes to process", "transcriptions to LinkedIn posts" or "quotes to add". This workflow shows 2 types of folder monitoring: Way #1: Each file in the monitored folder calls a sub-workflow Way #2: We get all files from the monitored folder and compare them to a database. If the file is not listed in DB, i supposed it's new one. Way #1 - We get all files from the monitored folder I set a variable folder_to_watch to indicate which folder to monitor. This step is here just to be homogeneous and allow setting the folder path only once in this branch. I list the folder files We keep only files (exclude folders) Then I call the specialized sub-workflow Way #2 - We want only new files from the monitored folder I set a variable folder_to_watch to indicate which folder to monitor I list the folder files and keep only files Meanwhile, I query my DB to get known files about this folder (I send the query to NocoDB (folder_to_watch,eq,{{ $json.folder_to_watch }})) Now I can exclude old files and keep only new ones by merging (I compare from Dropbox file id - as the file could be renamed by the user) I add the new file in DB to be sure to recognize it next time - I save the JSON Dropbox data: { "id":"{{ $json.id }}", "name":"{{ $json.name }}", "lastModifiedClient": "{{ $json.lastModifiedClient }}", "lastModifiedServer": "{{ $json.lastModifiedServer }}", "rev": "{{ $json.rev }}", "contentSize": {{ $json.contentSize }}, "type": "{{ $json.type }}", "contentHash": "{{ $json.contentHash }}", "pathLower": "{{ $json.pathLower }}", "pathDisplay": "{{ $json.pathDisplay }}", "isDownloadable": {{ $json.isDownloadable }} } And now I can call my sub-workflow :) My DB Columns details: folder_to_watch data (json/text) timestamp file_id (Dropbox file ID, to ease future searches) My vision: I have only one workflow in my n8n that monitors Dropbox folders/files This workflow calls the required sub-workflow specialized for the tasks required I will have as many branches as I have folders to monitor (if I have 5 different folders to watch, I will get 5 branches and 5 sub-workflows)

Public Transport Schedule & Delay Tracker with Microsoft Teams and Dropbox ⚠️ COMMUNITY TEMPLATE DISCLAIMER: This is a community-contributed template that uses ScrapeGraphAI (a community node). Please ensure you have the ScrapeGraphAI community node installed in your n8n instance before using this template. This workflow automatically scrapes public transport websites or apps for real-time schedules and service alerts, then pushes concise delay notifications to Microsoft Teams while archiving full-detail JSON snapshots in Dropbox. Ideal for commuters and travel coordinators, it keeps riders informed and maintains a historical log of disruptions. Pre-conditions/Requirements Prerequisites n8n instance (self-hosted or n8n.cloud) ScrapeGraphAI community node installed Microsoft Teams incoming webhook configured Dropbox account with an app token created Public transit data source (website or API) that is legally scrapable or offers open data Required Credentials ScrapeGraphAI API Key** – enables web scraping Microsoft Teams Webhook URL** – posts messages into a channel Dropbox Access Token** – saves JSON files to Dropbox Specific Setup Requirements | Item | Example | Notes | |------|---------|-------| | Transit URL(s) | https://mycitytransit.com/line/42 | Must return the schedule or service alert data you need | | Polling Interval | 5 min | Adjust via Cron node or external trigger | | Teams Channel | #commuter-updates | Create an incoming webhook in channel settings | How it works This workflow automatically scrapes public transport websites or apps for real-time schedules and service alerts, then pushes concise delay notifications to Microsoft Teams while archiving full-detail JSON snapshots in Dropbox. Ideal for commuters and travel coordinators, it keeps riders informed and maintains a historical log of disruptions. Key Steps: Webhook Trigger**: Starts the workflow (can be replaced with Cron for polling). Set Node**: Stores target route IDs, URLs, or API endpoints. SplitInBatches**: Processes multiple routes one after another to avoid rate limits. ScrapeGraphAI**: Scrapes each route page/API and returns structured schedule & alert data. Code Node (Normalize)**: Cleans & normalizes scraped fields (e.g., converts times to ISO). If Node (Delay Detected?)**: Compares live data vs. expected timetable to detect delays. Merge Node**: Combines route metadata with delay information. Microsoft Teams Node**: Sends alert message and rich card to the selected Teams channel. Dropbox Node**: Saves the full JSON snapshot to a dated folder for historical reference. StickyNote**: Documents the mapping between scraped fields and final JSON structure. Set up steps Setup Time: 15-25 minutes Clone or Import the JSON workflow into your n8n instance. Install ScrapeGraphAI community node if you haven’t already (Settings → Community Nodes). Open the Set node and enter your target routes or API endpoints (array of URLs/IDs). Configure ScrapeGraphAI: Add your API key in the node’s credentials section. Define CSS selectors or API fields inside the node parameters. Add Microsoft Teams credentials: Paste your channel’s incoming webhook URL into the Microsoft Teams node. Customize the message template (e.g., include route name, delay minutes, reason). Add Dropbox credentials: Provide the access token and designate a folder path (e.g., /TransitLogs/). Customize the If node logic to match your delay threshold (e.g., ≥5 min). Activate the workflow and trigger via the webhook URL, or add a Cron node (every 5 min). Node Descriptions Core Workflow Nodes: Webhook** – External trigger for on-demand checks or recurring scheduler. Set** – Defines static or dynamic variables such as route list and thresholds. SplitInBatches** – Iterates through each route to control request volume. ScrapeGraphAI** – Extracts live schedule and alert data from transit websites/APIs. Code (Normalize)** – Formats scraped data, merges dates, and calculates delay minutes. If (Delay Detected?)** – Branches the flow based on presence of delays. Merge** – Re-assembles metadata with computed delay results. Microsoft Teams** – Sends formatted notifications to Teams channels. Dropbox** – Archives complete JSON payloads for auditing and analytics. StickyNote** – Provides inline documentation for maintainers. Data Flow: Webhook → Set → SplitInBatches → ScrapeGraphAI → Code (Normalize) → If (Delay Detected?) ├─ true → Merge → Microsoft Teams → Dropbox └─ false → Dropbox Customization Examples Change to Slack instead of Teams // Replace Microsoft Teams node with Slack node { "text": 🚊 ${$json.route} is delayed by ${$json.delay} minutes., "channel": "#commuter-updates" } Filter only major delays (>10 min) // In If node, use: return $json.delay >= 10; Data Output Format The workflow outputs structured JSON data: { "route": "Line 42", "expected_departure": "2024-04-22T14:05:00Z", "actual_departure": "2024-04-22T14:17:00Z", "delay": 12, "status": "delayed", "reason": "Signal failure at Main Station", "scraped_at": "2024-04-22T13:58:22Z", "source_url": "https://mycitytransit.com/line/42" } Troubleshooting Common Issues ScrapeGraphAI returns empty data – Verify CSS selectors/API fields match the current website markup; update selectors after site redesigns. Teams messages not arriving – Ensure the Teams webhook URL is correct and the incoming webhook is still enabled. Dropbox writes fail – Check folder path, token scopes (files.content.write), and available storage quota. Performance Tips Limit SplitInBatches to 5-10 routes per run to avoid IP blocking. Cache unchanged schedules locally and fetch only alert pages for faster runs. Pro Tips: Use environment variables for API keys & webhook URLs to keep credentials secure. Attach a Cron node set to off-peak hours (e.g., 4 AM) for daily full-schedule backups. Add a Grafana dashboard that reads the Dropbox archive for long-term delay analytics.

How It Works Story Generation – Your idea is transformed into a narrative split into scenes using DeepSeek LLM. Visuals – Each scene is illustrated with AI images via Replicate, then animated into cinematic video clips with RunwayML. Voice & Music – Narration is created using ElevenLabs (text-to-speech), while Replicate audio models generate background music. Final Assembly – All assets are merged into a professional video using Creatomate. Delivery – Everything is orchestrated by n8n, triggered from Slack with /render, and the final video link is delivered back instantly. Workflow in Action Trigger from Slack Type your idea with /render in Slack - the workflow starts automatically. Final Video Output Receive a polished cinematic video link in Slack. Creatomate Template ⚠️ Important: You must create your own template in Creatomate. This is a one-time setup - the template defines where the voiceover, music, and video clips will be placed. The more detailed and refined your template is, the better the final cinematic result. Required APIs To run this workflow, you need accounts and API keys from the following services: DeepSeek – Story generation (LLM) Replicate – Images & AI music generation RunwayML – Image-to-video animations ElevenLabs – Text-to-speech voiceovers Creatomate – Video rendering and templates Dropbox – File storage and asset syncing Slack – Workflow trigger and video delivery Setup Steps Import the JSON workflow into your n8n instance. Add your API credentials for each service above. Create a Creatomate template (only once) – define layers for visuals, voice, and music. Trigger the workflow from Slack with /render Your Story Idea. Receive your final cinematic video link directly in Slack. Use Cases Automated YouTube Shorts / TikToks for faceless content creators. Scalable ad creatives and marketing videos for agencies. Educational explainers** and onboarding videos generated from text. Rapid prototyping** of cinematic ideas for developers & storytellers. With this workflow, you’re not just using AI tools – you’re running a full AI-powered studio in n8n.