General Automation
421 sonuç — tümü kaynağa bağlı n8n referansı
Generate Pinterest pin copy CSV from blog RSS with OpenAI-compatible chat
Quick overview Turn your latest blog posts into Pinterest-ready pin titles, descriptions and keywords, exported as a CSV formatted for Pinterest's native bulk upload. An AI writes one conversion-focused pin per post from your RSS feed — curiosity-preserving titles under 90 characters, natural keywords, no clickbait. How it works Starts when you manually execute the workflow. Loads configuration values such as the RSS feed URL, number of posts to process, target Pinterest board name, and the AI API base URL and model. Reads the blog’s RSS feed and collects the newest N posts with their titles, links, and short snippets. Sends the post list to an OpenAI-compatible Chat Completions endpoint to generate one Pinterest pin title, description, and keyword set per post as structured JSON. Transforms the AI response into Pinterest bulk upload columns (including Title, Description, Keywords, Link, and Pinterest board) and inserts a placeholder Media URL for you to replace. Converts the rows into a CSV file and provides it for download. Setup Add an HTTP Header Auth credential for your OpenAI-compatible API (for example, Authorization: Bearer ) and select it on the AI request step. Update the
Govern enterprise marketplace support actions with OSuite approvals
Quick overview This workflow runs on demand to preflight a high-value marketplace support action and send it to OSuite for governance review, then blocks, waits for approval, or proceeds to draft a safe internal refund-risk recommendation and records the final outcome in OSuite. How it works Starts manually to create a structured enterprise support action request with risk, data classification, systems touched, and expected side effects. Runs a local preflight that validates required fields, normalizes the risk score, and computes exposure level, blast radius, and a recommended control. Stops with an intake-fix status if the request is incomplete, including the blockers and warnings to address. Retrieves an OSuite runtime exposure snapshot and submits the planned work to OSuite for policy review with the preflight and decision context. Builds an operator approval packet from OSuite’s response and stops immediately if OSuite blocks the action. Checks OSuite to confirm whether the specific action ID has been approved, and stops in a waiting state until approval is granted. After approval, drafts an internal-only refund-risk recommendation (no refunds or external messages) and records
Audit Meta pixel deduplication risks with Graph API and Claude
Quick overview This workflow audits Meta (Facebook) Pixels for potential duplicate conversion counting by comparing browser Pixel vs Conversions API (server) activity and highlighting events active campaigns optimize for, then uses Anthropic Claude to generate pixel-by-pixel verification next steps and prints a prioritized audit report. How it works Runs manually to start the audit. Calls the Meta Graph API to list ad account pixels and fetch ad sets to identify the optimization events used by ACTIVE campaigns. Selects which pixels to audit (prioritizing pixels tied to optimization events, optionally overridden by a dataset ID list) and limits the scope to reduce API calls. For each selected pixel, queries the Meta Graph API for browser-vs-server event source totals and per-event counts. Classifies each pixel’s tracking setup (browser-only, server-only, or dual-source) and prioritizes pixels where optimization events may need deduplication verification. Sends the flagged pixel stats to Anthropic Claude to produce a concise JSON summary and a concrete “verify dedup” action per pixel focused on the optimization events. Prints a formatted audit report showing source split, key convers
Create voiceover MP3s and karaoke subtitles using Edge TTS and FFmpeg
Quick overview This self-hosted workflow takes text and a selected language from an n8n form, generates an MP3 voiceover using the Edge TTS CLI, analyzes the audio with FFmpeg/FFprobe to detect real pauses, and outputs a matching .ass karaoke subtitle file with word-by-word timing. How it works Receives text and a language selection from an n8n form submission. Maps the selected language to a specific Microsoft Edge TTS voice name. Writes the submitted text to a temporary file and uses the edge-tts CLI to generate an MP3 voiceover. Runs FFprobe to read the audio duration and FFmpeg silencedetect to find silence start/end markers. Calculates word-level timestamps that allocate timing to speech segments (excluding detected silences) and aligns sentences to pause-separated speech groups when possible. Builds an Advanced SubStation Alpha (.ass) subtitle file with \k karaoke tags and line wrapping based on character width. Saves the .ass subtitle file to disk alongside the generated MP3 for download or use in a video editor. Setup Use a self-hosted n8n instance with the Execute Command node enabled and file access configured to allow writing under /tmp. Install edge-tts on the n8n host
Draft weekly blog newsletter digests from RSS with OpenAI-compatible APIs
Quick overview This workflow runs every Monday at 08:00, reads your blog’s RSS feed, filters posts from the last 7 days, and uses an OpenAI-compatible Chat Completions API to generate a markdown newsletter digest you can copy into your email tool. How it works Runs every Monday at 08:00 on a schedule. Loads configuration values (RSS feed URL, OpenAI-compatible base URL, model name, and desired tone). Reads the RSS feed and keeps only items published in the last 7 days, collecting each post’s title, link, and a short snippet. Stops with a “nothing to send” outcome when no posts are found for the week. Sends the weekly post list to an OpenAI-compatible Chat Completions endpoint to write a clean markdown digest (intro, one bullet per post, and a sign-off). Extracts the generated markdown content into a single field so you can copy the draft from the final output. Setup Update the RSS feed URL (and optionally the model, tone, and API base URL) in the configuration step. Create an HTTP Header Auth credential with an Authorization: Bearer header and attach it to the HTTP request that calls the Chat Completions API. If you use a non-OpenAI provider, set the API base URL to your OpenAI-com
Generate Seedance videos with the Vancine Doubao API using polling
Quick overview Generate Seedance videos through the Vancine API, automatically poll asynchronous tasks, return the final video URL, and handle failed or timed-out generations with bounded retries. How it works Starts manually to define the Seedance model, prompt, video size, base URL, and polling limits. Sends a POST request to the Vancine /v1/video/generations endpoint to create a video generation task. Extracts and stores the returned task ID and initializes polling state (interval and maximum attempts). Waits for the configured interval, then sends a GET request to /v1/video/generations/{task_id} to check task status. Repeats polling until the task status is completed or until the maximum poll count is reached. Outputs the generated video result_url when completed, or stops with an error if the task fails or times out. Setup Create an HTTP Header Auth credential with Name set to Authorization and Value set to Bearer YOUR_VANCINE_API_KEY. Assign the same credential to both HTTP Request nodes: submitTask and pollTask. Confirm the Vancine API base URL in the workflow (default https://vancine.com) matches your environment. Update the prompt, model, size, and polling settings (interv
Start ScraperAPI crawler jobs from webhooks and store results in data tables
Quick Overview This workflow starts a ScraperAPI crawler job from an incoming webhook request and stores each crawled page returned via a callback webhook into an n8n Data Table. How it works Receives a POST request on a webhook with crawl inputs like startUrl, optional includeRegexp, and optional maxDepth. Builds ScraperAPI crawler parameters, including defaults (includeRegexp scoped to the start URL, maxDepth 1, country code, and render setting) and a callback URL for results. Creates a ScraperAPI crawler job and returns the job details in the webhook response. Receives per-page crawl results from ScraperAPI on a second webhook callback endpoint. Filters out job-summary payloads and failed page fetches, then extracts each page’s URL, markdown content, status code, and scrape timestamp. Upserts the parsed page results into an n8n Data Table named crawl_results keyed by URL. Setup Create and connect your ScraperAPI credentials in n8n so the workflow can create crawler jobs. Run the manual storage setup once (or ensure it exists) to create the crawl_results Data Table with the required columns. Replace the CALLBACK_URL in the crawl-parameter code with your “Receive crawl results” pr
Draft incident postmortems with PagerDuty, Confluence, Slack and Google Sheets
Quick overview This workflow creates a Confluence postmortem draft for resolved PagerDuty incidents, then notifies the incident owner in Slack and optionally logs the draft in Google Sheets. How it works Triggers manually for testing or receives a PagerDuty webhook when an incident is resolved. Loads shared configuration values like PagerDuty and Confluence URLs, Confluence space and parent page, Slack channel, and optional Google Sheets settings. Normalizes the incoming incident payload and fetches the incident details and log entries from the PagerDuty API. Builds an HTML postmortem draft containing an incident summary, placeholders for impact and root cause, a basic timeline, and action-item prompts. Creates a new Confluence page under the configured parent page using the generated postmortem content. Posts a Slack message to the configured channel and optionally appends a row to a Google Sheets “Postmortems” tab with key incident metadata. Setup Add PagerDuty API credentials to the PagerDuty HTTP Request steps and configure a PagerDuty webhook pointing to this workflow’s webhook URL for resolved incidents. Add Confluence (Atlassian) credentials and set your Confluence base URL,
Analyze URLs and extract SEO metadata with forms and HTTP requests
Quick Overview This workflow collects a URL via an n8n Form, follows HTTP redirects to the final destination, extracts page and Open Graph/Twitter metadata from the final HTML, and displays the results back in a form response using only built-in n8n nodes. How it works Receives a URL submission from the n8n Form trigger. Normalizes the input so it includes an http/https scheme. Requests the URL with redirect-following disabled to capture the HTTP status and Location header. If the response is a redirect (301/302/307/308), tracks visited URLs and redirect count, detects loops or exceeding the redirect limit, and either continues to the next Location URL or shows a redirect/loop error. If the response is 200 OK, parses the HTML to extract the title, meta description, canonical URL, language, Open Graph tags, Twitter Card tags, and common tracking parameters. Displays the extracted metadata and final URL in a results form, then redirects back to the input form page. Setup Activate the workflow so the n8n Form trigger has a Production URL. Copy the Form trigger Production URL and paste it into the Set URL value to replace REPLACE_WITH_PRODUCTION_FORM_URL so the completion step redirect
Draft security questionnaire answers with Notion, Google Docs, and Slack
Quick overview This workflow runs on demand to match security questionnaire questions against an approved-answer library in Notion, then creates a Google Docs draft and notifies reviewers in Slack, optionally updating a Notion tracker page. How it works Starts manually to run a test questionnaire and load configuration values like the Notion database ID, Google Drive folder ID, and confidence threshold. Loads a list of questionnaire questions and queries the Notion database for answers whose Status equals the configured approved value. Compares each questionnaire question to the approved Notion questions, selects the closest match, and marks low-confidence matches as “Needs review” instead of auto-answering. Branches based on whether any answers need review and posts a corresponding Slack notification to the configured review channel. Builds a formatted draft body containing each question, match confidence, owner, and either the approved answer or a “Needs review” placeholder. Creates a new Google Docs document for the draft and optionally updates a Notion questionnaire tracker page with “Draft ready for review” and the needs-review count. Setup Add Notion credentials and set the a
Register credential overwrites on startup with the n8n API
Quick Overview This workflow helps you set and maintain n8n credential overwrites by fetching credential schemas via the n8n REST API and registering overwrite values on every n8n startup using the credential overwrite endpoint. How it works Runs manually to collect your target credential type and n8n base URL for testing. Calls the n8n REST API to fetch the schema for the specified credential type so you can see which fields are available to overwrite. Triggers when n8n starts and sends a POST request to the credential overwrite endpoint to register the overwrite payload. Stores the overwrite JSON securely inside an HTTP custom auth credential and uses it as the request body to apply defaults that users cannot change in the UI. Setup Self-host n8n and set CREDENTIALS_OVERWRITE_ENDPOINT=creds-overwrite (and CREDENTIALS_OVERWRITE_PERSISTENCE=true if you run queue mode). Create an n8n API key with at least read permissions, add it as an n8n API credential, and set the correct base URL in the schema request. Enter the credential type name you want to overwrite (for example googleOAuth2Api) in the input fields used by the manual test. Create an HTTP Custom Auth credential that contains
Track data deletion requests from Gmail with Jira, BigQuery, and Slack
Quick Overview This workflow monitors a Gmail inbox for potential privacy/data deletion requests, classifies each email, creates the appropriate Jira issue, logs a minimal audit record to BigQuery, and alerts the team in Slack, with an optional Gmail confirmation draft for human review. How it works Triggers when a new email matching deletion-related keywords arrives in Gmail (or runs manually for testing). Loads shared configuration values like Jira project details, BigQuery destination, SLA window, Slack channel, and confidence threshold. Cleans the email text, extracts the requester address, classifies the request type (deletion/access/correction), and calculates an SLA due date with a confidence score. Creates a Jira task for the privacy team when the classification is confident, or creates a separate Jira task labeled for manual review when it is not. Inserts an audit row into Google BigQuery with metadata such as request type, confidence, received time, due date, and whether a Jira issue was created. Posts a Slack message to the configured channel about the routed request or the need for manual review. Creates a draft confirmation email in Gmail for the requester after a rout
Migrate visible product categories from Lightspeed to Shopify via GraphQL
Quick Overview This workflow runs manually to migrate visible category data from Lightspeed to Shopify by creating Shopify collections via the Admin GraphQL API, adding URL redirects from old category paths, and publishing the new collections to all Shopify publication channels. How it works Starts when you manually execute the workflow in n8n. Fetches all publication channels from your Shopify store using the Shopify Admin GraphQL API. Retrieves up to 250 categories from the Lightspeed API and splits the response into one item per category. Filters the list to only categories marked as visible in Lightspeed. For each visible category, creates a Shopify collection with title, handle, description, SEO fields, and an optional image. Creates a Shopify URL redirect from the original Lightspeed category URL path to the new Shopify /collections/{handle} URL. Publishes the created collection to all fetched Shopify publication channels and stops with an error if any Shopify mutation returns userErrors. Setup Add a Shopify Admin API access token as an HTTP Header Auth credential (header name X-Shopify-Access-Token) and assign it to the Shopify GraphQL requests. Add your Lightspeed API key a
Ping IndexNow when new blog posts are published from your RSS feed
Quick overview This workflow polls your blog’s RSS feed for newly published posts and sends each new URL to the IndexNow API, helping Bing and other IndexNow-enabled search engines pick up updates quickly. How it works Polls the specified RSS feed every 15 minutes to detect new blog posts. Sets your site host and IndexNow key for the request payload. Sends a POST request to the IndexNow API with the new post URL, your key, and the key file location on your domain. Checks the HTTP response status code to determine whether the ping succeeded. Routes successful runs to a “Pinged OK” endpoint and failures to a “Ping Failed” endpoint for optional downstream notifications. Setup Obtain an IndexNow key and host it as a text file at https:///.txt containing the key. Update the RSS feed URL in the RSS trigger (for example, https://your-domain.com/feed/). Activate the workflow, publish a test post, and check the execution log — a 200 or 202 response from IndexNow confirms the ping was received successfully.
Organize VNTANA showroom assets by style and color via webhook and CSV report
Quick overview This workflow receives a VNTANA showroom event (or a manual UUID) via webhook, fetches the showroom, validates naming and metadata rules, reorganizes products into ordered groups, updates the showroom in VNTANA, and returns a CSV report of the new layout. How it works Receives a POST webhook containing either a showroomUuid field or a VNTANA showroom event payload with showroom.uuid. Validates and extracts the showroom UUID from the request body. Calls the VNTANA API to fetch the full showroom details and product list. Enforces organization rules by requiring a Style attribute on every product, a _.ext filename pattern, and unique color codes within each style group, then builds grouped and sorted ordering data. Updates the same showroom in VNTANA by writing the computed groups and per-product order back via the API. Generates a CSV “receipt” listing each asset UUID, name, assigned group, and order, and returns it as a downloadable file in the webhook response. Setup Create and configure a VNTANA API credential in n8n and assign it to the VNTANA API requests. Ensure showroom assets in VNTANA have a non-empty Style attribute and follow the _.ext naming pattern with un
Monitor competitor web page changes with HTTP and Slack or Discord
Quick overview This workflow checks a list of competitor web pages every six hours, detects content changes by hashing cleaned page text, and posts a diff-style alert to a Discord or Slack channel via an incoming webhook. How it works Runs every 6 hours on a schedule. Loads a configured list of target competitor page URLs and the destination Discord/Slack webhook URL. Fetches each target page over HTTP with browser-like headers and continues even if a request fails. Converts the fetched HTML into cleaned plain text, stores a baseline on first run, and compares the latest hash against the previously saved version. When a change (or fetch error) is detected, generates a message including the URL and a small list of added/removed lines. Sends the alert message to your Discord or Slack webhook endpoint. Setup Create an incoming webhook in Discord or Slack and paste its URL into the workflow configuration. Update the target list with the competitor page names and URLs you want to monitor. Ensure n8n can persist workflow static data between runs (so change history is retained) and that your instance can reach the target sites over HTTP. Requirements n8n version 1.60+. A Discord or Slack
Look up Brazilian company data by CNPJ with forms and Minha Receita API
Quick overview This workflow hosts an n8n form that accepts a Brazilian CNPJ, validates and normalizes the input, then queries the public Minha Receita API to fetch company registration details and displays either a formatted results page or an error page with a link back to the form. How it works Receives a CNPJ through an n8n form submission. Sets the base URL for the Minha Receita API and the redirect URL used by the “Search Again” button. Removes punctuation from the CNPJ and validates that it contains exactly 14 digits. Requests company data from the Minha Receita API endpoint for the cleaned CNPJ. Displays a results form with key company fields (for example, status, CNAE, partners, and address) when the API returns data. Displays an error form when the CNPJ format is invalid or the API request fails, then redirects back to the input form. Setup Activate the workflow and copy the Production URL from the form trigger. Paste that URL into the Set URL step (replace REPLACE_WITH_PRODUCTION_FORM_URL) so completion pages can redirect users back to the search form. Ensure outbound HTTP access to https://minhareceita.org/ from your n8n instance, since the workflow relies on the public
Audit digital identities with Apify BreachHound and PDF.co
Quick overview This workflow starts from an n8n form submission, runs the BreachHound actor on Apify to discover where an email address is registered, then summarizes the results into an HTML audit report and converts it to a downloadable PDF using PDF.co. How it works Receives an email address (and options) when a user submits the n8n form. Sends the submitted inputs to the BreachHound actor on Apify to check the email across online services. Loads the actor’s results from the Apify dataset. Aggregates the dataset into audit statistics and a list of platforms where the email is found. Generates an HTML report containing the totals and a table of found accounts. Converts the HTML report to a PDF using the PDF.co Convert from HTML API and fetches the generated file via HTTP. Setup Connect an Apify API credential and select/configure the BreachHound actor in the Apify “Run an Actor” step. Create a PDF.co account, replace YOUR_API_KEY_HERE with your PDF.co API key, and keep the HTML-to-PDF endpoint settings as needed. Review the form fields and the default options (for example, the “onlyUsed” and “useResidentialProxy” values) to match the audit behavior you want before activating the
Search and preview GIFs with forms and GIPHY
Quick overview This workflow publishes an n8n Form where users enter a search term, queries the GIPHY Search API for the top 9 G-rated GIFs, and renders the results as a clickable HTML gallery on the form completion page with copy-to-clipboard links. How it works Receives a submission from an n8n Form at the gif-finder path with a required query field. Calls the GIPHY Search API with the submitted query, limiting results to 9 GIFs and filtering to G-rated content. Transforms the GIPHY response into responsive HTML that shows a grid of GIF thumbnails and a fallback message when no results are returned. Displays the generated HTML on the form completion page so users can click any GIF to copy its direct URL to the clipboard. Setup Create a GIPHY developer app and generate an API key. Add an HTTP Query Auth credential and set the api_key value to your GIPHY API key, then select it in the HTTP Request that calls GIPHY. Activate the workflow and share the n8n Form URL for the gif-finder form with your users.
Generate llms.txt from a website sitemap using forms and HTTP requests
Quick overview This workflow uses an n8n Form and HTTP requests to read a website sitemap, fetch each listed page, extract the page title and meta description, and generate an llms.txt file that you can preview, copy, or download. How it works Receives a form submission with the site name, site description, sitemap URL, and a maximum page limit. Fetches the sitemap XML and, if it is a sitemap index, extracts the child sitemap URLs. Fetches each leaf sitemap and extracts, deduplicates, and caps page URLs while grouping them into sections based on the first URL path segment. Requests each page’s HTML content and continues even if some pages fail to load. Extracts the HTML title and meta description (or falls back to a title derived from the URL), then compiles the results into a sectioned llms.txt markdown file. Renders a completion page that displays the generated llms.txt content and provides Copy and Download actions. Setup Copy the n8n Form URL from the Form Trigger node and open it in your browser (or use the test form in the editor). Submit your site name, sitemap URL, and optionally a site description and max pages value. Upload the downloaded or copied llms.txt file to your w
Calculate profit margin and markup with interactive web forms
Quick Overview This workflow exposes an n8n Form that calculates a product’s selling price from cost, tax, and marketplace fees using either a target profit margin or a target markup, then displays the resulting price, profit, margin, and markup (or a validation error) and lets users return to the form. How it works Receives an n8n Form submission with product cost, tax percentage, fee percentage, a desired value, and a chosen calculation method (Profit Margin or Markup). Validates that product cost is greater than 0 and that tax and fee percentages are 0 or higher, otherwise shows an error result page. Routes the request based on the selected method (Profit Margin vs Markup). For Profit Margin, verifies that tax + fee + desired margin is less than 100%, calculates selling price and profit, and shows the results page. For Markup, verifies that the markup is 0% or higher, calculates selling price, profit, and the resulting profit margin, and shows the results page. After any results or error page, redirects the user back to the initial form using the configured form URL. Setup Activate the workflow and open the Form Trigger node to copy its Production URL. Paste that Production URL
Generate daily LinkedIn B2B leads with DataForB2B and LinkUp
Quick overview Automate B2B lead generation on autopilot: every weekday morning, DataForB2B finds fresh leads matching your ICP (800M+ profiles, 50+ filters), skips anyone already contacted, and sends up to 10 personalized LinkedIn connection requests per day via LinkUp API - with safe, human-like limits. How it works Runs every weekday at 9:00 AM using a schedule trigger. Searches for people matching your ICP in DataForB2B (for example, “Head of Sales” in the United States) and returns up to 25 results. Normalizes the lead data into consistent fields such as LinkedIn profile URL, name, title, company, and location. Skips leads whose LinkedIn URLs were already processed in previous executions to avoid re-contacting the same profiles. Limits the list to a daily cap of 10 leads. Sends a personalized connection request for each remaining lead using the LinkUp API, continuing even if individual invites fail. Setup Create a DataForB2B API key at app.dataforb2b.ai and adjust the people filters to match your ICP. Get your LinkUp API key at app.linkupapi.com and connect your account in the LinkUp dashboard. Update the schedule (cron expression) if you want a different time or cadence. Cust
Send personalized cold emails from Google Sheets with Claude MCP and Gmail
Quick overview This template turns a Google Sheet of leads into an outreach engine controlled by any MCP-compatible AI assistant, including Claude, ChatGPT,and others. Instead of manually drafting emails, you instruct the assistant to draft or send them through rotating Gmail accounts, while every action logs back to the sheet automatically How it works Receives a tool-call request from any MCP-capable assistant (Claude, ChatGPT, or others) via the MCP Server Trigger endpoint Reads all rows from a Google Sheets "Leads" tab so the assistant can find queued leads and avoid contacting anyone twice Creates a Gmail draft in one of several connected Gmail accounts, using the recipient, subject, and plain-text body the assistant provides Optionally sends the email immediately from one of the three Gmail accounts when the assistant provides the final recipient, subject, and body. Updates the matching row in Google Sheets with status, assigned account, sent date, and any error note, keeping the sheet as the single source of truth Setup Connect your Google Sheets OAuth credentials, then set the Spreadsheet document ID and the "Leads" sheet name in both the read and update nodes Connect Gmail
Handle Shopify Admin GraphQL requests with error handling and retries
Quick Overview This sub-workflow is called by another n8n workflow to execute Shopify Admin GraphQL queries and mutations via HTTP, adding input validation, detailed error detection (including rate limits), and automatic retries with exponential backoff before returning the final Shopify response. How it works Receives input from a parent workflow execution, including a Shopify GraphQL query, shop API endpoint, and Admin API access token. Validates required inputs, normalizes the shop endpoint, and builds the Shopify Admin GraphQL request payload with variables and API version defaults. Sends the POST request to the Shopify Admin GraphQL endpoint with the X-Shopify-Access-Token header and captures the full HTTP response. Parses the response to detect HTTP/network failures, GraphQL errors, Shopify userErrors, bulk/job failures, and throttle status from Shopify cost extensions. If throttled or encountering retryable server/network errors, waits for the calculated backoff interval and retries the same Shopify GraphQL request up to the configured maximum. If non-retryable errors remain, stops the execution and returns a formatted error object; otherwise returns the Shopify data, rate-l