Workflow Templates

Tagged with: , , , ,

Meta long-lived user tokens typically expire after ~60 days. If a token expires, any workflows that rely on it start failing. Manual renewal is easy to forget and time consuming. This template monitors the token you store in an n8n Data Table and refreshes it automatically before expiration, so your social automations keep running without surprises or late-night fire drills. Who’s it for Agencies, marketing team, creators managing Meta apps or scheduled social automations Anyone tired of “token expired” errors breaking flows at 2 a.m. How it works / What it does Triggers: scheduled every 10 days, plus a Manual Trigger for testing. Reads: pulls the current token row from your "Meta credential" Data Table (fields: token and expires_at). Decides: IF the token expires in ≤ 15 days, proceed to renewal; otherwise do nothing. Calls the Graph API to get a new access token Updates: computes the new ISO expires_at from expires_in and writes the fresh token + expires_at back to the Data Table. Note: Meta typically issues ~60-day long-lived tokens; confirm for your app. Requirements A Meta app with an initial (short-lived or long-lived) user access token n8n Data Tables enabled (you might need to update your instance to see the option) and a table named "Meta credential" with: ** token (string) ** expires_at (datetime) How to set up Create the data table: name it "Meta credential" with columns "token" and "expires_at". Insert one row with your current token and its expiration date. Configure the IF node "Needs renewal?": keep (or tweak) the 15-day threshold logic. Run once with the Manual Trigger to validate, then enable the Schedule Trigger (10-day cadence by default). How to customize the workflow Change the Schedule Trigger interval and hour. Notify on renewal: Add a Slack/Email node after "Update Record" to alert on token refreshes.

> ⚠️ Community Node Disclaimer > This workflow uses KlickTipp community nodes and works only on self-hosted n8n instances. Introduction Automate attendance tracking for Eventbrite events and sync participation data to KlickTipp. Every 15 minutes, this workflow retrieves attendees, checks who attended, and applies the right segmentation tags. Perfect for event marketers who want real-time post-event segmentation—no manual exports needed. Who’s it for For event organizers, digital marketers, and KlickTipp users who already sync Eventbrite registrants and want to automatically track attendance and update CRM tags. > 💡 Prerequisite: Contacts must exist in KlickTipp. > Use the related workflow “Subscribe Eventbrite orders to KlickTipp” to import registrants first. How it works Schedule Trigger runs every 15 min. Eventbrite API fetches the latest attendees. Split Out processes each record. Switch (Attendance Check) evaluates checked_in: ✅ Checked in → Eventbrite | Participated ❌ Not checked in → Eventbrite | Not participated KlickTipp Nodes apply tags automatically. Segmentation in KlickTipp updates instantly. Requirements Self-hosted n8n (community node support) Eventbrite account (OAuth2) KlickTipp account (API access) Tags in KlickTipp: Eventbrite | Participated Eventbrite | Not participated How to set up Connect accounts: Eventbrite (OAuth2) & KlickTipp (API). Set Event ID: edit Eventbrite node URL → /events/{event_id}/attendees/. Update Tag IDs: replace with your KlickTipp IDs. Test: run manually or wait for trigger; verify correct tags. > ⚠️ Important: Eventbrite must record check-ins via the Organizer App or barcode scan for accurate tagging. How to customize Adjust trigger frequency (e.g., 5 min during event). Duplicate for multiple events. Extend logic for ticket type, VIP, or refunds. Combine with Eventbrite Order Sync for a full funnel: Registration → Participation → Refund. Campaign expansion ideas Refund tagging:** detect refunded: true and tag accordingly. Post-event automation:** Participated → thank-you or upsell sequence. Not participated → replay or follow-up invite. Performance insights:** use tags for segmentation analytics and ROI tracking.

🎬 YouTube to MP4 Downloader This n8n workflow allows users to submit a YouTube video URL, automatically fetches multiple MP4 and MP3 download links using YouTube Video Downloader Fast API. It logs all links into Google Sheets for easy access and tracking. With YouTube Video Downloader Fast API, users can securely download videos in different resolutions without manual tools. 🛠️ Node-by-Node Explanation 1️⃣ On Form Submission Displays a form to collect the YouTube video URL. Triggers the workflow when a URL is submitted for processing. 2️⃣ HTTP Request Sends the provided URL to YouTube Video Downloader Fast API via RapidAPI. Retrieves downloadable links for multiple resolutions (360p, 720p, 1080p) and MP3 format. Ensures the download process is fast and secure with YouTube Video Downloader Fast API. 3️⃣ If Node Checks if the API response from YouTube Video Downloader Fast API is successful. Proceeds only if valid downloadable links are available. 4️⃣ Google Sheets Saves the original YouTube URL and all MP4/MP3 download links in Google Sheets. Provides a permanent log for future access and tracking. 💡 Use Cases Content managers can bulk-download YouTube videos in different formats. Educators/trainers can easily organize video links for offline teaching. Marketing agencies can prepare high-quality video assets for campaigns. Developers can customize the workflow to integrate with other storage solutions. 🚀 Benefits Fully automated video downloading process with YouTube Video Downloader Fast API. Multiple resolutions and MP3 download options. Centralized, structured download logs in Google Sheets. Saves time, secure, and customizable for different needs. ✅ Problem Solved Eliminates the need for unsafe third-party downloaders. Provides fast and secure YouTube downloads using YouTube Video Downloader Fast API. Offers multiple video/audio formats without manual extraction. Ensures easy tracking and future accessibility of downloaded content.

Tagged with: , , , ,

Tagged with: , , , ,

Tagged with: , , , ,

Tagged with: , , , ,

Tagged with: , , , ,

Tagged with: , , , ,

Tagged with: , , , ,

Tagged with: , , , ,