General Automation
421 sonuç — tümü kaynağa bağlı n8n referansı
Generate images from text prompts with MuAPI Nano Banana 2 Pro
Quick Overview This manual workflow generates an image from a text prompt using the MuAPI Nano Banana 2 Pro text-to-image model, then extracts the generated image URL so you can view it or pass it to downstream steps. How it works Runs when you manually execute the workflow in n8n. Sets a text prompt to describe the image you want to generate. Sends the prompt to MuAPI’s Nano Banana 2 Pro text-to-image predictor to generate an image. Extracts the first returned output as an image_url field for easy reuse. Setup Install the n8n-nodes-muapi community node in your n8n instance. Create and select MuAPI API credentials (API key) for the MuAPI predictor node. Update the prompt text in the prompt-building step and confirm the predictor is set to the nano-banana-2-pro model.
Post approved Trello bookkeeping drafts to Xero with receipt attachments
Quick overview This workflow listens for an “Approved” label on a Trello card, reads the AI draft bookkeeping JSON from card comments, and posts the corresponding transaction to Xero. It then adds a Xero deep link back to Trello, uploads receipt images as Xero attachments, and moves the card to Done. How it works Triggers in Trello when a user adds the configured Approved label to a card on the target board. Fetches the card’s comments, extracts the ` payload, validates required fields, and skips processing if a ` sentinel comment already exists. For SPEND_MONEY and PAY_BILL entries, pulls active Xero bank accounts and resolves the bank account and payment reference from the draft and any reviewer comments, pausing to request confirmation on the Trello card if values are ambiguous. For PAY_BILL entries, fetches open supplier bills from Xero and either matches the payment to a single ACCPAY invoice or asks the reviewer to confirm the bill in a Trello comment. Builds and posts the appropriate Xero record (Bank Transaction, Bill, Payment, or Manual Journal) via the Xero API and generates a Xero deep link for the created entity. Immediately writes the `` deep link back to Trello, then
Draft funding-based cold email openers with Datahyena and OpenAI GPT-4o
Quick overview This workflow runs daily at 9am to fetch recent $1M+ funding events from Datahyena, uses OpenAI Chat Completions to generate a two-sentence cold email opener referencing each raise, and outputs a structured draft record with company and funding details. How it works Runs every morning at 9am on a schedule. Requests up to 15 funding events from the last day from the Datahyena Funding Events API, filtered to rounds with at least $1M raised. Splits the API response so each funding event is processed individually. Sends the company and funding details to the OpenAI Chat Completions API to generate a concise, funding-aware cold email opener. Outputs a cleaned draft object containing the company name, domain, round, amount, announcement date, and generated opener text. Setup Add an HTTP Header Auth credential for Datahyena (header X-API-Key) and select it in the Datahyena request step. Add an HTTP Header Auth credential for OpenAI (header Authorization: Bearer ) and select it in the OpenAI request step. Update the prompt text in the OpenAI request to replace “EDIT THIS WITH WHAT YOU SELL” with your actual offer. Optionally connect a destination after the final output to st
Create real estate listing video ads with OpenAI and Videotok
Quick Overview This workflow takes a real estate listing, uses OpenAI to generate ad copy and a video generation prompt, then sends it to the Videotok API to create a 9:16 vertical listing video ad with a caption and compliance notes. How it works Starts manually to test the workflow with a sample property listing. Builds a listing record containing the address, listing details, and image URLs (replace this with your real listing source). Sends the listing data to OpenAI to generate structured JSON for a video ad, including a script, generation prompt, caption, and compliance notes. Parses the OpenAI output and maps it into a Videotok generation payload with brand kit, reference images, quality, duration, and an idempotency key. Calls the Videotok Generations API to create the vertical video ad using the generated prompt and listing images. Setup Add environment variables for OPENAI_API_KEY, VIDEOTOK_API_KEY, and VIDEOTOK_BRAND_KIT_ID. Replace the sample listing step with your own source (CRM, Airtable, Google Sheets, MLS export, or scraper) and ensure it outputs address, listing_details, and listing_image_urls. Confirm the Videotok template slug (viral-video-ads) and adjust the vi
Serve text-to-speech MP3 over a webhook with Smallest.ai
Quick Overview This workflow exposes a POST webhook that converts incoming text into an MP3 audio stream using Smallest.ai, optionally using a provided custom voice ID, and returns the audio inline in the same HTTP response. How it works Receives a POST request on the /text-to-speech webhook endpoint with a JSON body. Checks whether the request includes a voice field to indicate a custom voice ID. If a custom voice ID is provided, sends the text and voice ID to Smallest.ai to generate an MP3 with that voice. If no voice ID is provided, sends the text to Smallest.ai to synthesize an MP3 using the default voice settings. Returns the generated MP3 as binary data to the caller with Content-Type: audio/mpeg and an inline filename of speech.mp3. Setup Add your Smallest.ai API credentials in both Smallest.ai speech generation steps. Activate the workflow and copy the production webhook URL, then configure your client to POST to /text-to-speech. Send requests with a JSON payload containing text (required) and voice (optional custom voice ID).
Draft bookkeeping entries from Trello cards with OpenRouter and Xero
Quick overview This workflow triggers from Trello card activity to draft bookkeeping entries by extracting transaction details with OpenRouter and enriching them with live Xero chart-of-accounts, tax rates, contacts, and bill context, then posts a review-ready summary and embedded JSON back to the Trello card. How it works Triggers from Trello when a card is moved to the Ready list or when the Retry AI label is added. Fetches the current Xero chart of accounts, bank accounts, and tax rates to use as live reference data. Loads the Trello card details, recent comments, and attachment metadata and stops with an error note if the text lacks enough detail for extraction. Sends the card title/description/comments to OpenRouter to extract a structured bookkeeping draft and normalizes key fields like dates, line items, and payment reference. Uses Xero Contacts (and, for bill payments, Xero Invoices) to resolve the vendor and refine PAY_BILL vs SPEND_MONEY before optionally asking OpenRouter to classify expense line items to Xero account codes. Validates and maps any suggested account codes against the live Xero chart of accounts, embeds Xero configuration needed for posting later, and reco
Test IVR call quality using CALL-E API from a phone task list
Quick overview This workflow manually triggers two sequential IVR quality-sample calls via the CALL-E API, validating transcripts and metadata post-call. Note: Default placeholders must be replaced with authorized E.164 test numbers before execution. How it works Runs when you start the workflow manually. Loads the CALL-E API configuration (base URL, polling interval, timeout) and stops with an error if the API key is missing. Creates a small list of IVR QA call tasks (phone, task instructions, locale/region, and metadata) to be processed. Processes the call list one item at a time, building the CALL-E /v1/calls request with a JSON result schema, metadata, and an idempotency key. Calls the CALL-E API to create the call and repeatedly polls the call status until it reaches a terminal state (completed/failed/canceled) or times out. Extracts the call outcome, structured result, transcript turns, and failure signals, then formats a demo-friendly per-call view and an overall execution summary. Setup Add your CALL-E API key by replacing replace_with_calle_api_key in the CALL-E configuration step. Replace the sample phone numbers with numbers you own or are authorized to call, and adjust
Send signed WooCommerce orders to KSeF via a self-hosted KSeF Gateway
Quick overview This workflow receives WooCommerce order webhooks, verifies the WooCommerce signature, converts eligible orders into a KSeF invoice payload, and submits them to a self-hosted KSeF Gateway API, skipping consumer orders that do not include a buyer NIP. How it works Receives a WooCommerce order webhook request and keeps the raw request body for signature validation. Verifies the X-WC-Webhook-Signature HMAC against your shared webhook secret and rejects invalid requests with a 401 response. Extracts the buyer NIP from WooCommerce order meta data and maps the order (seller, buyer, line items, VAT rates, and payment details) into a KSeF invoice payload. Skips processing and responds to WooCommerce with a success message when the order has no buyer NIP (consumer purchase). Sends the invoice payload to your self-hosted KSeF Gateway endpoint over HTTP with an X-Api-Key header. Responds to WooCommerce with the resulting KSeF number (when available) or an error from the gateway. Setup Deploy a KSeF Gateway instance and note its base URL. Update the workflow configuration values for the gateway URL and API key, seller NIP/name/address, and the WooCommerce webhook secret. In WooC
Create KSeF invoices from completed Sellf purchases via KSeF Gateway
Quick overview This workflow receives signed Sellf purchase webhooks, validates the HMAC signature, and when the buyer requests an invoice with a NIP it builds a KSeF-ready invoice and submits it to a self-hosted KSeF Gateway, capturing the returned KSeF number or an error. How it works Receives a POST webhook from Sellf with the raw request body and the X-Sellf-Signature header. Verifies the webhook signature using HMAC-SHA256 and rejects the request with a 401 response if the signature is invalid. Responds immediately with a JSON OK response and continues processing in the background. Filters the event to purchase.completed and extracts the customer, order, and invoice details from the webhook payload. Continues only if the customer requested an invoice and provided a non-empty NIP. Builds a KSeF invoice payload using your seller details and the purchase data, then posts it to your KSeF Gateway /ksef/invoice endpoint with an X-Api-Key header. Stores the KSeF submission result by extracting the ksefNumber and status on success, or capturing the returned error details on failure. Setup Set up Sellf webhooks to send purchase.completed events to this workflow’s production webhook URL
Poll and download received invoice PDFs with KSeF Gateway to disk storage
Quick overview This workflow runs every 20 minutes to poll a self-hosted KSeF Gateway for newly received KSeF invoices, maintains a cursor checkpoint in n8n static data, downloads each new invoice PDF via the gateway API, and saves the files to local disk. How it works Runs every 20 minutes on a schedule. Reads the last successful polling checkpoint from the workflow’s static data and calls the KSeF Gateway /ksef/invoices/received/new endpoint with the since cursor. If the gateway response is unsuccessful, records the error details for alerting and leaves the checkpoint unchanged so the next run retries the same window. If the response is successful, stores the returned nextSince value as the new checkpoint. If new invoices are returned, processes each invoice summary individually. Downloads each invoice PDF from the KSeF Gateway /ksef/invoice/{ksefNumber}/pdf endpoint and saves it to the configured local folder. Outputs invoice metadata (number, seller, amount, and saved file path) as a placeholder where you can plug in notifications (Slack, email, or Discord). Setup Deploy and configure a self-hosted KSeF Gateway (https://github.com/jurczykpawel/ksef-gateway) with a token or cert
Upload CSV test cases to Qase and send completion alerts to Slack
Quick overview This workflow upload test cases from a CSV file into Qase App and sends a confirmation message to your Slack channel. How it works Receives a form submission containing a public CSV URL and a selected Qase project option. Downloads the CSV file from the provided URL and extracts its rows into individual test-case items. Maps each row into the JSON payload Qase expects (including project code, fields like severity/priority/type, and optional parsed steps). Creates the test cases in Qase by sending a POST request per item to the Qase Cases API for the mapped project. Aggregates the upload responses into a single result. Sends a Slack incoming-webhook message confirming the test case upload is complete. Setup Create a Qase API token and add it to the Qase HTTP Header Auth credentials used for the Qase API request. Create a Slack Incoming Webhook, paste the webhook URL into the Slack notification HTTP request node, and customize the message text if needed. Ensure the uploaded CSV is publicly accessible via URL and uses the expected columns (for example: title, description, preconditions, postconditions, severity, priority, type, layer, behavior, automation, and optional
Solve PopularCaptcha image challenges with CaptchaSonic via webhook
Quick Overview This workflow receives a PopularCaptcha image challenge via webhook or manual test input, sends it to CaptchaSonic for recognition/classification, and returns the solved result as JSON to the caller or as formatted output for testing. How it works Receives a POST webhook request containing a base64 image, question, websiteURL, and optional extra fields. Sends the challenge details to CaptchaSonic using the PopularCaptcha image recognition/classification operation. Returns CaptchaSonic’s solution data as a JSON webhook response. Optionally, runs a manual test path that loads sample image/question data and submits it to CaptchaSonic. Formats the manual test output by stringifying the solution data and adding a status and timestamp. Setup Install the n8n-nodes-captchasonic community node in your n8n instance. Create and select a CaptchaSonic credential with your CaptchaSonic API key. If using the webhook path, copy the production webhook URL for /solve-popularcaptcha and configure your client to POST image, question, websiteURL, and optionally extraFields in the request body. If needed, replace the hardcoded sample data in the manual test input to match your PopularCapt
Rank resumes by job description similarity using Gemini embeddings
Quick overview This workflow collects resume PDFs and a job description via an n8n form, generates embeddings with Google Gemini, calculates cosine similarity between each resume and the job description, and returns a CSV-style ranked list of filenames. How it works Receives resume PDF uploads and a job description text through an n8n Form trigger. Creates a semantic embedding for the job description using the Google Gemini Embeddings API (gemini-embedding-2). Splits the uploaded files into individual resume items and converts each PDF binary to a Base64 string. Sends each Base64-encoded PDF to the Google Gemini Embeddings API to generate a multimodal embedding for the resume. Calculates cosine similarity between the job description embedding and each resume embedding, then sorts resumes from most similar to least similar. Returns a CSV-formatted ranking (Rank, File Name) in the form completion response. Setup Create and add a Google Gemini (PaLM) API credential in n8n with an API key that can access the gemini-embedding-2 model. Ensure the Google Gemini credential is selected on both HTTP requests that create the job description embedding and the resume embeddings. Use the workflo
Rank resumes by job description similarity using OpenRouter embeddings
Quick overview This workflow collects resume PDFs and a job description through an n8n form, extracts text (with OCR for scanned PDFs), generates embeddings via OpenRouter, and ranks the resumes by cosine similarity to the job description, returning a CSV-style list of ranked filenames. How it works Receives resume PDFs and a job description from an n8n form submission. Creates an embedding for the job description using OpenRouter’s embeddings endpoint with openai/text-embedding-3-large. Processes each uploaded resume one at a time, converting the PDF to text using built-in PDF extraction. If the extracted text is too short (likely scanned), sends the PDF to OpenRouter chat completions with the file-parser plugin (mistral-ocr) to OCR the document and return plain text. Creates an embedding for each resume’s extracted text (from direct extraction or OCR) using openai/text-embedding-3-large. Computes cosine similarity between each resume embedding and the job description embedding, then sorts resumes from most similar to least similar. Returns a completion page containing a CSV-style list of rank and filename. Setup Add an OpenRouter API credential in n8n and select it on the embeddi
Sync Etsy customers with Meta custom audiences using hashed emails
Quick overview This workflow runs daily to fetch recent Etsy receipt emails via an Etsy Shop Operations sub-workflow, normalizes and SHA-256 hashes the emails, and either previews the hashed payload or uploads it to a Meta Custom Audience using the Meta Graph API. How it works Runs every day on a schedule. Sets sync parameters (lookback window, maximum receipts, dry-run mode, Meta audience ID, and API version). Requests recent Etsy receipt records from a connected Etsy Shop Operations workflow and extracts buyer/payment email addresses. Normalizes, deduplicates, and SHA-256 hashes the email addresses to build a Meta Custom Audience upload payload. If dry-run is enabled, returns counts and a small sample of hashes for verification. If dry-run is disabled, sends the hashed EMAIL payload to the Meta Graph API endpoint for the specified Custom Audience. Setup Configure and connect the “Get Etsy customer receipts” execute-workflow step to an Etsy Shop Operations (PRO) workflow that returns receipt records including buyer/payment emails. Create or choose a Meta Custom Audience and paste its ID into the configuration values. Add a Meta access token to the HTTP header auth for the upload r
Generate daily Etsy sales and ledger reports via Shop Operations API
Quick overview This workflow runs daily to pull recent Etsy receipts and payment-account ledger entries via a linked sub-workflow, then aggregates sales metrics by currency and fee totals by ledger type and outputs a consolidated report object for downstream accounting or BI tools. How it works Runs every day on a schedule. Sets the reporting window and maximum record count used for all Etsy queries. Calls a separate Etsy Shop Operations workflow to fetch receipts for the configured date range. Calls the same Etsy Shop Operations workflow to fetch payment-account ledger entries for the same date range. Aggregates receipts into per-currency totals (orders, revenue, shipping, tax, discounts, and average order value) and groups ledger amounts by ledger type. Outputs the final report payload (including summaries plus the raw receipts and ledger entries) for use in other steps like saving to a database or sending by email. Setup Set up Etsy OAuth credentials in the workflow that performs the Etsy API calls (the Etsy Shop Operations sub-workflow). In both Execute Workflow steps, select the Etsy Shop Operations workflow to run by filling in the referenced workflow ID. Update the reporting
Manage Etsy OAuth 2.0 tokens and API headers between workflows
Quick Overview This workflow manages Etsy OAuth 2.0 (PKCE) authorization in n8n, stores access and refresh tokens in workflow static data, refreshes tokens when needed, and returns ready-to-use Etsy API request headers to other workflows via an Execute Workflow call. How it works Runs either manually to start authorization, via a webhook callback from Etsy after consent, or when another workflow requests a token. Loads the Etsy app configuration (client ID, shared secret, redirect URI, scopes) and routes the run to start authorization, handle the callback, or return an access token. When starting authorization, generates a PKCE verifier/challenge and returns an Etsy authorization URL while storing the pending state for validation. When Etsy redirects to the callback webhook, validates the returned state and authorization code and then exchanges the code for tokens using the Etsy OAuth token endpoint. Stores the authorized access and refresh tokens (with expiry timestamps) in n8n workflow static data and returns a confirmation response to the callback request. When another workflow requests a token, loads the stored refresh token, refreshes the access token with Etsy if it is missin
Trigger Coolify deployments from new Docker Hub and GHCR image digests
Quick overview 🔄 Monitor Container Images from Docker Hub or GHCR. This workflow checks Docker Hub or GitHub Container Registry (GHCR) image tags for new digests. When an update is detected, it calls your Coolify API to restart the mapped service so the latest image is deployed. How it works Runs on a schedule to check for new image versions automatically. Loads configured Docker Hub image tags and their matching Coolify service UUIDs, then checks Docker Hub for each tag’s current digest. Skips Docker Hub digests already seen in previous workflow executions and prepares standardized metadata for any new digests. Loads configured GHCR image tags and their matching Coolify service UUIDs, fetches a GHCR auth token, and then retrieves each tag’s current OCI digest from the response headers. Skips GHCR digests already seen in previous workflow executions and prepares standardized metadata for any new digests. Combines new updates from both registries and calls the Coolify “restart service” endpoint for each matching service UUID (with latest image enabled). Setup Add an HTTP Bearer Auth credential for your Coolify API token and replace https://your-coolify-instance.com and the endpoint
Evaluate counters and key-value storage with the KeyValue community node
Quick overview This workflow demonstrates the n8n KeyValue community node by using a counter to run one-time initialization logic per workflow, storing a per-day execution flag to allow the main logic only once per day, and showcasing basic directory, record, and counter operations. How it works Starts when you manually execute the workflow. Reads a KeyValue counter named after the current n8n workflow ID and runs a one-time “first execution” branch only when the counter does not yet exist. Sets the workflow-ID counter in KeyValue to mark that the one-time initialization logic has been executed. Reads a KeyValue record (keyed by workflow ID) from the businessprocess directory and compares its stored date with today’s date. If today’s date is already stored, it stops in a “logic already executed” branch; otherwise it runs the main logic branch. Writes today’s date back to KeyValue (businessprocess directory) to enforce “run once per day” behavior on subsequent executions. Setup Install the KeyValue community node (n8n-nodes-keyvalue) in n8n under Settings → Community nodes. Ensure your n8n instance has persistent filesystem storage for the KeyValue root directory (so counters and re
Run LDXhub document jobs from one form with StructFlow, RefineLoop, RenderOCR, CastDoc, and ExtractDoc
Quick overview This workflow provides a single n8n form that routes to six LDXhub services (StructFlow, AnalyzeDoc, RefineLoop, RenderOCR, CastDoc, and ExtractDoc) to run one-off document processing jobs and return the generated output file directly to the user. How it works Receives a submission from an n8n Form that collects an LDXhub API key, API host, and the target service. Routes the request to the selected service and fetches available models or engines from the LDXhub gateway using an HTTP request. Collects the remaining service-specific inputs via follow-up forms (for example model/engine selection, prompts/options, file upload, output format, and OCR language where applicable). Filters the available output formats based on the uploaded file’s extension for the conversion-style services. Submits the job to LDXhub (StructFlow, AnalyzeDoc, RefineLoop, RenderOCR, CastDoc, or ExtractDoc) and polls until the result is ready. Returns the processed file as a direct download in the form completion step, or shows an error page if the job fails. Setup Create an LDXhub API key in the LDXhub portal and add an LDXhub API credential in n8n for the LDXhub node. Confirm the LDXhub gateway
Send SAP Business One order and invoice alerts via WhatsApp Cloud API
Quick overview This workflow polls SAP Business One every 15 minutes for newly updated Sales Orders and AR Invoices and sends a formatted alert for each document via the WhatsApp Cloud API, using an n8n Data Table timestamp to prevent duplicate notifications between runs. How it works Runs every 15 minutes on a schedule. Reads the last-checked timestamp from an n8n Data Table and falls back to 15 minutes ago if no value exists. Logs in to the SAP Business One Service Layer and queries the Orders and Invoices OData endpoints for documents updated after the last-checked date. Normalizes the returned records, labels each one as a Sales Order or AR Invoice, and combines them into a single stream. For each new document found, formats a WhatsApp text message with key fields like document number, date, customer, total, currency, and comments. Sends the message through the WhatsApp Cloud API (Meta Graph) and then logs out of SAP Business One. Upserts the current timestamp back into the Data Table so the next run only alerts on newer documents. Setup Provide your SAP Business One Service Layer URL and credentials (CompanyDB, UserName, Password) in the SAP login request and ensure the Orders
Proxy OpenAI-style chat completions to Gemini with async webhooks
Quick overview This workflow exposes an OpenAI-compatible /v1/chat/completions endpoint in n8n that forwards requests (including optional file attachments) to a configurable LLM HTTP provider, supporting both synchronous replies and asynchronous processing via a callback URL. How it works Receives a POST request on /v1/chat/completions via a webhook, accepting JSON or multipart form-data with optional binary file uploads. Converts any uploaded files into OpenAI-style message content (images as image_url data URLs and other files as text entries) and merges them into the last user message. Prepares a job ID, extracts optional callback and provider override settings (URL and headers), and keeps the original request body for later use. If a callback URL is provided, immediately returns HTTP 202 with the job ID, then sends the request (without callback/provider fields) to the configured LLM provider endpoint. Formats the provider response (or error) into a completion payload with a status code and posts the result to the callback URL with job metadata. If no callback URL is provided, sends the request to the LLM provider synchronously and returns the provider response (or error) to the
Solve image CAPTCHAs via webhook using CaptchaSonic
Quick overview This workflow exposes a POST webhook that accepts base64 CAPTCHA images and uses the CaptchaSonic community node to solve multiple CAPTCHA types (OCR, reCAPTCHA v2, AWS WAF, TikTok, Binance, and more), returning a standardized JSON response. How it works Receives a POST request on the captchasonic-solve webhook containing a JSON body with a type and required fields like image (base64) and sometimes question. Validates the request payload, checks required fields for the requested CAPTCHA type, and routes the request to the matching solver. Sends the image challenge to CaptchaSonic using the appropriate recognition operation for the selected type. Normalizes the CaptchaSonic result into a consistent JSON structure with success, type, solution, and a solvedAt timestamp. Returns the formatted solution to the original webhook caller, or responds with HTTP 400 and an error message if validation fails. Setup Self-host n8n and install the n8n-nodes-captchasonic community node. Create and select a CaptchaSonic API credential (API key from https://my.captchasonic.com) for the CaptchaSonic nodes. Activate the workflow, copy the production webhook URL for captchasonic-solve, and
Sync Shopify customers with Cegid Y2 on create or update
Quick overview This workflow receives Shopify customer create/update webhooks and syncs the customer record to CEGID Y2 by creating the customer when missing or updating the existing customer when CEGID reports a duplicate. How it works Receives a POST webhook from Shopify when a customer is created or updated. Builds a CEGID Y2 customer payload with identifiers, tax/currency details, and the default store/workspace settings. Formats the customer address and chooses whether to send individual or company contact details based on whether a company name is present. Sends the assembled payload to CEGID Y2 to create the customer. If CEGID returns a “customer already exists” error, extracts the existing CEGID customer ID from the error message and sends a PATCH request to update that customer in CEGID. If the create request fails for any other reason, stops the workflow and surfaces the CEGID error. Setup In Shopify, create a customer webhook for create/update events and point it to this workflow’s webhook URL, matching the allowed shop domain. Add CEGID Y2 HTTP Basic Auth credentials and ensure the API user has permission to create and update customers. Update the CEGID API base URL, wo