Marketplace
3,557 ready-made workflow files you can download, plus 10,661 source-linked n8n references.
Deploy Gainium DCA bot pairs with Telegram approval and Google Sheets logging
Quick overview This workflow runs daily, pulls top coins from the Gainium crypto screener, formats them into USDT trading pairs, and asks for Telegram approval before updating and starting a Gainium DCA bot, with optional deployment logging to Google Sheets and Telegram error alerts. How it works Runs every day at 08:00 on a schedule. Queries the Gainium screener for coins meeting the configured filters (market cap threshold, Binance listing, positive 24h change) and sorts them by 24h volume. Cleans the screener results and selects the top N unique SYMBOL_USDT pairs. Sends the proposed pairs to Telegram with Deploy/Skip buttons and pauses until you respond. If approved, replaces the Gainium DCA bot’s pairs, starts the bot, appends a deployment row to Google Sheets, and sends a Telegram confirmation. If skipped, leaves the bot unchanged and sends a Telegram message confirming the skip. Sends Telegram alerts if the Gainium screener call fails or if any other workflow node errors. Setup Install the community node n8n-nodes-gainium and add a Gainium API credential with permission to manage your bot. Create a Telegram bot, add a Telegram API credential in n8n, and set your telegram_chat
WGenerate SEO-friendly robots.txt with OpenAI and Google Drive
Quick overview This workflow runs manually to check a website’s existing robots.txt, detect the site’s CMS from the homepage HTML using OpenAI, and generate an optimized robots.txt (including the provided sitemap URL) that is saved as a file and uploaded to Google Drive. How it works Starts when you click “Execute workflow” and sets the target website URL and sitemap URL. Requests the site’s existing robots.txt via HTTP and checks whether the response returns status code 200. If robots.txt exists, the workflow stops without making changes. If robots.txt is missing, it fetches the website homepage HTML via HTTP. Sends the HTML to OpenAI to detect the CMS and parses the model output into structured JSON. Uses OpenAI again to generate a production-ready robots.txt tailored to the detected CMS and including the sitemap directive. Converts the generated text into a robots.txt file and uploads it to a chosen folder in Google Drive. Setup Add an OpenAI API credential and ensure the selected chat model is available for both CMS detection and robots.txt generation. Add a Google Drive OAuth2 credential and choose the target Drive and folder for the uploaded robots.txt file. Update the websit
Route patients to the best nearby hospital using Google Maps, GPT-4.1 and Twilio
Quick overview This workflow accepts emergency location requests (or runs on a 5-minute schedule), finds and ranks nearby hospitals/clinics using Google Places, capacity data, and Google Distance Matrix, generates a routing message with OpenAI, sends the recommendation via Twilio SMS, logs the event to Google Sheets, and returns a JSON response. How it works Receives an emergency request via a webhook POST (or runs every 5 minutes on a schedule) and normalizes latitude, longitude, severity, phone number, and a request ID. Validates the GPS coordinates, maps severity to a numeric score, and sets a search radius, returning an error response if the location is invalid. Queries the Google Places API for nearby hospitals and clinics, then merges and deduplicates the results into a single facility list. Looks up each facility’s ED capacity metrics from a capacity API and calculates real-time driving time to each facility with the Google Distance Matrix API. Scores and ranks facilities using a severity-adjusted composite score (travel time, available beds, wait time, and ED diversion penalties) and selects the best match plus two alternatives. Uses OpenAI to generate a calm routing messag
Validate startup ideas and generate business plans with Claude and SendGrid
Quick overview This workflow receives a startup idea via webhook, uses Anthropic Claude to expand it, run market research, competitor analysis, and demand validation, then generates a structured business plan, emails it through SendGrid, logs a summary row to Google Sheets, and returns a JSON response to the webhook caller. How it works Receives a startup idea via an HTTP POST webhook request. Normalizes the submission details (idea, founder, industry, budget) and uses Anthropic Claude to expand the idea into a structured concept with an initial score. Filters out ideas below the viability threshold (ideaScore < 4) to stop low-quality submissions early. Uses Anthropic Claude to produce market sizing and persona research, then parses the results into structured market data. Uses Anthropic Claude to analyze direct and indirect competitors and compute a competitive position score. Uses Anthropic Claude to validate demand signals, risks, and go-to-market recommendations, then calculates a composite score and PROCEED/VALIDATE_FURTHER/PIVOT_OR_ABANDON recommendation. Uses Anthropic Claude to generate a 10-section business plan, appends a tracking row to Google Sheets, emails the report v
Triage Typeform survey feedback with GPT-4o-mini, Slack, Gmail, and Sheets
Quick overview This workflow triggers on new Typeform survey responses, uses OpenAI GPT-4o-mini to classify sentiment and draft reply emails, routes negative feedback through a Slack human-approval loop with revisions, sends emails via Gmail, and logs outcomes to a Google Sheets CRM. How it works Triggers when a new Typeform survey response is submitted. Extracts the respondent’s name, email, rating, and free-text feedback and sends it to OpenAI GPT-4o-mini to classify the response as positive or negative. If the response is negative, OpenAI GPT-4o-mini drafts an empathetic follow-up email, posts a Slack alert to the team, and sends the draft to a Slack review channel that waits for a reply. If the reviewer replies with “approved”, the workflow sends the approved draft to the respondent via Gmail and appends a “Sent” record to Google Sheets. If the reviewer requests changes, OpenAI GPT-4o-mini revises the email based on the Slack feedback and the workflow loops back to Slack for another review. If the response is not negative, OpenAI GPT-4o-mini drafts a thank-you email, sends it automatically via Gmail, and logs the sent email to Google Sheets. Setup Connect credentials for Typefo
Draft personalized cold emails from Google Sheets with Apify and GPT-4o mini
Quick overview This workflow reads pending medical or dental practice leads from Google Sheets, scrapes each practice website with Apify, uses OpenAI (gpt-4o-mini) to identify conversion gaps, and drafts a short personalized cold email, then writes the analysis and draft back to the sheet. How it works Manually starts the workflow and reads leads from a Google Sheets worksheet. Filters the rows to only those with Status set to "pending" and processes them one at a time. Uses Apify Website Content Crawler to scrape up to a few pages of each lead’s WebsiteURL and compiles the extracted text into a trimmed site summary. If enough website text is available, sends it to OpenAI (gpt-4o-mini) to produce a strict-JSON analysis of 2–3 concrete booking/chatbot/after-hours/intake gaps and a best outreach angle. Alternates between “soft” and “direct” framing and asks OpenAI (gpt-4o-mini) to generate a short JSON email draft (subject and body) tailored to the selected gap. Updates the matching row in Google Sheets with ScrapedNotes, WeakPoints, DraftEmail, and sets Status to "drafted", then waits briefly before moving to the next lead. If the scrape returns insufficient content, updates the lea
Send AI market briefings to email and Discord with AlphaAI and GPT-4
Quick Overview This workflow runs every 15 minutes to fetch AlphaAI’s trending market news, filter for new high-relevance, ticker-linked stories, and post them to a Discord channel via webhook as rich embed cards with sentiment and impact details. How it works Runs every 15 minutes on a schedule trigger. Requests the current trending news feed from the AlphaAI API using Bearer authentication. Filters out already-posted articles, keeps only stories with relevance score ≥ 8 and at least one ticker, and formats up to 10 items into Discord embed cards with AlphaAI sentiment, confidence, actionability, and likely price impact. Posts a single Discord webhook message containing a header and the generated embeds, and stores the posted article IDs to prevent duplicates in future runs. Setup Create an AlphaAI API key and add it as an n8n HTTP Bearer Auth credential used by the AlphaAI request. Create a Discord channel webhook and paste its URL into the Discord webhook HTTP request node. Activate the workflow and keep it running on the same n8n instance so its stored posted-article IDs can be reused across executions.
W
Process signed DocuSign contracts with Supabase, Claude, Stripe, Outlook and Gmail
Quick overview This workflow listens for DocuSign Connect envelope-completed events, looks up the related assessment in Supabase, updates contract and client records, sends a welcome email (optionally drafted with Anthropic), creates an onboarding session and invite, and for non-pilot clients creates a Stripe Checkout payment link and emails it. How it works Receives a POST webhook from DocuSign Connect and continues only when the envelope status indicates the contract is completed. Queries Supabase for the assessment record matching the DocuSign envelope ID and normalizes the returned data to a single assessment object. Updates the assessment in Supabase to mark the contract as completed, upserts a client record in Supabase, and calls an internal webhook to fetch the signed contract. Sends either a pilot welcome email or a standard welcome email via Microsoft Outlook, with the standard email body drafted by Anthropic and optionally logged to a separate cost-tracking workflow. Generates a resume token, creates an onboarding session in Supabase, waits 24 hours, then sends the onboarding questionnaire invite via Microsoft Outlook and emails an internal notification via Gmail. For non
Send DocuSign envelopes with Supabase contract data
Quick overview This workflow is triggered by another n8n workflow, fetches an assessment record from Supabase, generates an HTML contract, and sends it as a DocuSign envelope using JWT authentication in either production or sandbox based on the recipient email, then writes the envelope ID and status back to Supabase. How it works Receives an execution request from another workflow with an assessment ID (and optional contract title). Retrieves the matching assessment record from the Supabase assessments table. Generates a styled contract HTML document from the assessment data and Base64-encodes it for DocuSign. Chooses the DocuSign sandbox or production path based on whether the contact email contains a specific marker string. Calls a Supabase Edge Function to create a DocuSign JWT assertion, exchanges it for a DocuSign access token, and creates a “sent” envelope with two signers and anchor-based signature tabs. Updates the Supabase assessment record with the DocuSign envelopeId and sets the contract status to envelope_sent. Setup Create and connect Supabase credentials in n8n, and update the Supabase project URL for the Edge Function endpoint (/functions/v1/docusign-sign-jwt). Conf
CResearch Reddit trends and publish LinkedIn posts with Gemini and PostPeer
Quick overview This workflow runs daily, scrapes a selected subreddit with Apify, researches sources via Brave Search and Jina Reader, and uses Eden AI (DeepSeek) plus Google Gemini to draft a LinkedIn post with an image. It logs state in Google Sheets/Drive, sends approval emails, and publishes via PostPeer. How it works Runs daily on a schedule, loads Global Constants, and picks an ACTIVE subreddit row from Google Sheets using a random ID. Scrapes recent posts from that subreddit using an Apify Reddit scraper, then normalizes, scores, and deduplicates candidates. Uses an Eden AI (DeepSeek) agent to vet the candidates and either selects one post idea or stops and records a NO_VIABLE_IDEA entry in Google Sheets and emails the rationale. For a selected idea, a second Eden AI (DeepSeek) agent generates a research brief and up to five Brave Search queries, then Brave Search and Jina Reader collect and extract a small set of non-social sources. A third Eden AI (DeepSeek) agent writes the LinkedIn draft and an accompanying image prompt, then Google Gemini generates the image. Uploads the image to Google Drive, writes the draft and metadata to a Google Sheets post log, and emails a two-s
WReview GitHub pull requests with Mistral and send decisions to Slack
Quick overview This workflow receives GitHub webhook events for pull requests, pushes, and branch/tag creates, filters out actions from the repo owner, and posts alerts to Slack (optionally Discord). For pull requests, it uses Mistral to generate an AI review from the PR diff and supports a human approval form. How it works Receives a GitHub webhook request and filters for push, create, and pull_request events coming from non-owner accounts (and non-deleted branches). Routes the event by type and, for push and create events, extracts key details and posts a notification to Slack (optionally Discord). For pull request opened, reopened, or synchronize events, extracts PR metadata such as title, URLs, branch refs, and change counts. Uses Mistral (via an AI agent) to fetch the PR unified diff over HTTP and generate a structured JSON review, optionally consulting existing GitHub PR reviews for synchronize re-reviews. Posts the AI recommendation to Slack with a link to a hosted PR review form (optionally Discord) and waits up to 24 hours for a reviewer decision. Applies the reviewer decision back to GitHub by approving the PR and merging it, requesting changes with a comment, or closing
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
WTriage and deduplicate GitHub issues with Claude Sonnet 4.5
Quick overview Detect and merge duplicate GitHub issues automatically using Claude AI. This n8n automation triggers on new GitHub issues, checks them against open issues for duplicates, merges duplicate reports into the original, and applies AI-generated labels or requests missing reproduction steps. How it works Triggers automatically when a new GitHub issue is opened, kicking off AI-powered issue triage. Fetches up to 30 currently open GitHub issues from the same repository as duplicate-detection candidates. Sends the new issue and the candidate list to Claude AI, which assigns labels, detects duplicate issues, and drafts a reproduction-request comment when needed. If Claude AI flags the issue as a duplicate, the automation labels the new issue, links it to the original GitHub issue, and comments with a reference back to it. For duplicate issues, the workflow also updates the original issue's body with a tracked "reported by N users" summary and posts a comment merging in the new report's details — keeping duplicate GitHub issues consolidated instead of scattered across separate threads. If the issue isn't a duplicate, Claude AI applies the right labels and, when reproduction ste
Triage and retry failed workflow executions with Anthropic, Jira and OpenTelemetry
Quick overview This workflow triggers on n8n execution errors, uses Anthropic (Claude) to classify the failure as transient or logic, and then either retries the failed execution via the n8n API with exponential backoff or creates a Jira issue, while also sending incident telemetry to an OpenTelemetry collector. How it works Triggers automatically when an n8n workflow execution errors. Extracts key telemetry like workflow name, failing node, error message/stack, execution URL, and any detected HTTP status code. Sends the error context to Anthropic (Claude) to return structured JSON with a category, confidence, and remediation guidance. Combines the AI diagnostics with telemetry and tracks a per-incident retry counter (up to three attempts) to decide if the failure is eligible for automated retry. If the error is transient with sufficient confidence and retry budget remains, waits using exponential backoff and calls the n8n API to retry the failed execution, then records the retry outcome. If the error is not retry-eligible (or the retry budget is exhausted), creates a Jira issue with the diagnostics, execution link, and failure details. Posts an OpenTelemetry trace span to your col
Monitor target account funding, acquisitions, and exec moves with Datahyena and Slack
Quick overview This workflow runs every morning and checks Datahyena for funding events, acquisitions, and executive moves from the last 24 hours, then posts matching updates for your target account domains to a Slack channel. How it works Runs every day at 9:00 AM. Loads a list of target company domains to monitor. Fetches the last 24 hours of funding events from the Datahyena API, filters to events where the company domain matches your target list, and posts each match to Slack. Fetches the last 24 hours of acquisition events from the Datahyena API, filters to deals where either the acquirer or target domain matches your list, and posts each match to Slack. Fetches the last 24 hours of executive move events from the Datahyena API, filters to moves where the current or previous company domain matches your list, and posts each match to Slack. Setup Create a Datahyena API key and configure an HTTP Header Auth credential with header name X-API-Key for the three Datahyena HTTP requests. Update the target domain list in the workflow’s target accounts step (the domains array). Connect your Slack credential and select the channel for the three Slack message steps.
Monitor AI search citations and competitors with OpenAI, Google Sheets, and Gmail
Quick overview This workflow runs weekly to test whether fairyfrills.in is cited in OpenAI answers to 15 shopping queries, logs citation details to Google Sheets, and emails a weekly HTML visibility report via Gmail, with optional Slack alerts on workflow errors. How it works Runs once a week on a schedule and generates 15 predefined shopping queries along with the target domain, brand name, and competitor domains. Sends each query to two OpenAI models in parallel: gpt-4o-mini (no browsing) and gpt-4o-search-preview (web search with URLs). Splits the two AI answers into separate items per platform and uses OpenAI to extract citation data (target-domain URLs, competitor citations, citation position, and totals) as structured JSON. Parses the extracted citation JSON, formats key fields (including URL lists, counts, and a response preview), and appends one log row per query and platform to a Google Sheets “Citation Log” sheet. After the final query (ID 15) completes, fetches the logged results from Google Sheets, calculates weekly citation metrics and breakdowns, and generates an HTML report. Sends the weekly citation report email through Gmail to the configured recipient. If any node
Monitor AI brand visibility and GEO gaps with OpenAI, Gmail and Slack
Quick Overview This workflow runs daily to test whether Fairy Frills appears in AI shopping recommendations by querying OpenAI with 10 brand-focused questions (with and without web search), extracting mention and competitor data, generating a GEO gap analysis, and emailing a consolidated HTML report via Gmail. How it works Runs every 24 hours on a schedule. Generates 10 predefined shopping queries for Fairy Frills and includes the brand URL and a competitor list with each query. Sends each query to OpenAI twice in parallel, once to gpt-4o-mini (no search) and once to gpt-4o-search-preview (web search enabled). Combines the two model responses per query and uses OpenAI to extract structured metrics such as whether Fairy Frills is mentioned, mention count and position, competitor mentions, sentiment, and a key snippet. Uses OpenAI again to perform a GEO (Generative Engine Optimization) gap analysis that explains why competitors ranked, why the target brand missed, and which content actions and exact phrases to add. Deduplicates and aggregates insights across all checks, builds an HTML summary, and sends the daily GEO report email via Gmail. Sends a Slack message when the workflow enc
Capture and route real estate leads with Google Sheets, Gmail, and Slack
Quick overview This workflow captures real estate property inquiries via a webhook, validates and normalizes lead details, upserts the lead into Google Sheets, sends an auto-reply through Gmail, and notifies your team in Slack, with separate handling for high-priority leads and workflow failure alerts. How it works Receives a website property inquiry via a POST webhook. Extracts the lead fields (name, email, phone, property ID, message, source, and timestamp) and rejects invalid submissions with a 400 JSON response explaining what’s missing. Normalizes the lead data by lowercasing the email address and stripping non-numeric characters from the phone number. Classifies the inquiry as high or standard priority based on keywords found in the message and property text. Appends or updates the lead in a Google Sheets CRM table, matching on email to avoid duplicates. Sends a Gmail auto-reply and posts a Slack notification, routing high-priority leads to a senior-agent message and standard leads to the general team. Returns a JSON confirmation to the webhook caller and posts a Slack alert if the workflow errors. Setup Copy the webhook URL from the trigger and configure your website form/ap
Predict sprint slip risk in Jira with OpenAI via OpenRouter and Slack alerts
Quick Overview This workflow runs on a weekday morning schedule (or manually) to pull the active Jira sprint and its issues, compute sprint health metrics, use an OpenRouter-hosted OpenAI model to assess slip risk, and post a motivating alert to a Slack channel when the sprint is behind. How it works Runs every weekday at 08:00 (or when executed manually). Calls the Jira Software Cloud Agile API to fetch the board’s active sprint and all issues in that sprint, including status, labels, and story points. Calculates sprint timing, completion percentage, slip margin, velocity gap, and a list of potentially blocked issues based on labels or status. Sends the computed metrics to an OpenRouter (OpenAI) chat model to return a structured JSON risk assessment (on_track, at_risk, or critical) with recommendations and tickets to watch. Parses the model output into JSON and merges it with the computed sprint metrics for reporting. If the risk level is not on_track, a second OpenRouter (OpenAI) agent drafts a team-focused status update and posts it to the configured Slack channel. If the risk level is on_track (or parsing fails and defaults to on_track), the workflow ends without posting to Sla
WCreate studio-quality car listing photos using Google Drive and Gemini 2.5
Quick overview This workflow manually processes car photos from Google Drive, sends each image plus a studio backdrop and logo to the Google Gemini Image API for background replacement and license-plate branding, and uploads the generated studio-style images back to an output Google Drive folder. How it works Runs when you manually execute the workflow. Lists all image files in a specified Google Drive input folder and processes them one at a time. Downloads the current car photo and also lists and downloads the studio asset images (virtual backdrop and logo) from a separate Google Drive folder. Builds a multimodal request that instructs Google Gemini to classify the shot (exterior vs interior/engine), replace the background accordingly, and swap any visible license plate with the provided logo. Sends the request to the Google Gemini image generation endpoint and receives a generated image in the response. Extracts the generated image, names it using the original filename with a “_studio.jpg” suffix, and uploads it to a specified Google Drive output folder. Setup Add Google Drive OAuth2 credentials and set the input, studio assets, and output folder IDs in the Google Drive nodes’ q
Generate vendor negotiation strategies from pricing data with GPT-4 and SendGrid
Quick overview This workflow ingests vendor pricing via a webhook or a weekly schedule, analyzes variance against historical and market benchmarks, uses OpenAI to draft negotiation strategies for high-priority cases, then emails recommendations through SendGrid and appends the analysis to a Google Sheets tracker. How it works Receives vendor pricing data from a POST webhook endpoint or runs every Monday at 8:00 to process a scheduled input. Normalizes incoming fields (vendor, pricing, benchmarks, volume, currency, renewal date, and notes) into a consistent schema. Calculates price variance versus historical and market benchmarks, estimates potential savings, derives a confidence score, and flags whether the opportunity is high priority. Filters to only high-priority opportunities and waits briefly to help manage API rate limits. Uses OpenAI to generate a structured, under-300-word negotiation strategy including tactics, target and walk-away prices, projected savings range, and risk flags. Formats the AI output into a report, emails it via the SendGrid API, and appends the analyzed record to a Google Sheets tab for tracking. Setup Add an OpenAI API credential for the OpenAI Chat Mod
Generate SRT subtitles for Google Drive audio with Smallest.ai
Quick Overview This workflow watches a Google Drive folder for new audio files, transcribes them with Smallest.ai, converts the transcription into an SRT subtitle file, and uploads the .srt back to the same Google Drive folder. How it works Triggers every minute when a new file is created in a specified Google Drive folder. Checks the file extension to confirm it is a supported audio format (mp3, wav, aac, ogg, flac, m4a, wma). Downloads the audio file from Google Drive. Sends the audio to Smallest.ai for speech-to-text transcription. Formats the transcription into timestamped SRT cues (using returned segments when available, otherwise estimating timings). Uploads the generated .srt subtitle file back to the watched Google Drive folder. Setup Add a Google Drive OAuth credential and select the folder to watch/upload to in both the trigger and upload steps. Add your Smallest.ai credentials in the transcription step. Ensure the monitored folder receives audio files with supported extensions, or update the extension-matching pattern to fit your media types.
Generate rich character bibles for writers with GPT-4.1 and Google Sheets
Quick overview This workflow accepts character details via webhook or manual trigger, uses OpenAI to generate psychology, backstory, and emotional arc drafts in parallel, then synthesizes them into a structured “Character Bible” JSON response and optionally appends a log row to Google Sheets. How it works Receives a POST request on an n8n webhook (or runs manually) with character parameters like name, age, archetype, world setting, story role, traits, and constraints. Normalizes the incoming fields, validates the archetype, and derives genre tags from the world setting using Python logic. Sends the enriched character inputs to OpenAI three times in parallel to generate a psychology profile, a backstory, and an emotional arc document. Combines the three AI documents into a single context object and passes it to OpenAI again to synthesize a unified Character Bible with defined sections. Parses the Character Bible into structured JSON fields (identity snapshot, personality core, backstory highlights, emotional arc, voice, and story hooks) and adds metadata like request ID and timestamp. Returns the completed character profile as a JSON webhook response and optionally appends a summary
Enrich contact emails and phone numbers with Tomba and Google Sheets
Quick overview This workflow runs on a schedule to read “Pending” contacts from Google Sheets, uses Tomba to find email addresses and (when available) phone numbers, then writes the enriched results back to the same spreadsheet. How it works Runs on a scheduled trigger. Reads rows from a Google Sheets worksheet where the Status column equals “Pending”. Processes the contacts in batches and sends each contact’s name, company, and domain to Tomba to find an email address. If Tomba indicates phone data is available, looks up the phone number in Tomba using the found email address. Normalizes the output (email, phone, score, and enrichment status) and updates the matching row in Google Sheets with the results and Status set to “Done”. Setup Connect your Google Sheets OAuth credentials and set the target spreadsheet and worksheet that contains your contacts. Add a Tomba API credential. Ensure your Google Sheet includes the expected columns (First Name, Last Name, Company, Domain, Status) and output columns (Email, Phone, Score), with Status set to “Pending” for rows you want to enrich.