Workflow Templates

This template transforms your sales and outreach process by automating deep, personalized research on any contact. Go beyond simple data enrichment; this workflow acts as an AI research assistant. Starting with just a name and company, it finds the person's professional profile, analyzes it through the lens of your specific business offering, and returns actionable insights to prepare for the perfect outreach. Stop spending hours manually researching prospects. With this template, you get a synthesized report in seconds, highlighting a contact's potential pain points and exactly how your solution can provide value, setting the stage for more meaningful and effective conversations. Who is this for? Sales Development & Business Development Reps (SDRs/BDRs):** Drastically cut down on research time and increase the quality and personalization of your outreach efforts. Account Executives:** Prepare for meetings with a deep, relevant understanding of a prospect's background and potential needs. Founders & Solopreneurs:** Handle your own sales and lead generation efficiently by automating the research phase. Marketing Teams:** Power your Account-Based Marketing (ABM) campaigns with tailored insights for key accounts. What problem does this solve? Eliminates time-consuming manual research:** Automates the entire process of finding a person, reading their profile, and connecting the dots back to your business. Prevents generic outreach:** Provides you with specific, synthesized talking points, moving you beyond "I saw your profile on LinkedIn" to a message that shows you've done your homework. Solves "writer's block":** Delivers a clear summary of a prospect's potential challenges and how you can help, making it much easier to start writing a compelling message. Creates actionable intelligence, not just data:** Instead of just returning a list of job titles and skills, it synthesizes that information into strategic summaries ready to be used. How it works Input contact details: The workflow is triggered by a form where you enter the first name, last name, and company of the person you want to research. Find the person with Apollo: The workflow uses the Apollo.io API to find the contact's professional data, including their verified LinkedIn profile URL. Define your business context: This is the "smart" part. The workflow injects information you provide about your offering and the typical pain points your customers face. Analyze profile with Linkup: Using the Linkup API, the workflow reads the person's public LinkedIn profile. Crucially, it analyzes the profile through the lens of your business context. Get synthesized insights: Linkup's AI returns three structured summaries: a general overview of the person, their potential pain points relative to your business, and a concise explanation of how your offering could bring them value. Consolidate results: The final node gathers all the enriched data and AI-generated summaries into a single, clean output, ready for your CRM or next action. Setup Define your business context (Critical Step): This is the most important part. In the Define our business context node, fill in the two fields: Area for which the prospect could experience pain points: Describe the general problems your customers face. My offering: Briefly describe your product or service. This context is what makes the AI analysis relevant to you. Connect your accounts: Apollo: Add your Apollo API key to the Enrich contact with Apollo HTTP node. Linkup: Add your Linkup API key to the Find Linkedin profile information with Linkup HTTP node. Their free plan offers €5 of credits, enough for ~1,000 runs. Activate the workflow: Toggle the workflow to "Active". You can now run it by filling out the form trigger! Taking it further Automate CRM enrichment:* Connect the final *Consolidate results* node to a *HubSpot, **Attio, or Salesforce node to automatically save these rich insights to your contact records. Generate AI-powered outreach:* Add an *OpenAI** node after this workflow to take the synthesized insights and generate a first draft of a personalized outreach email or LinkedIn message. Process leads in bulk:* Replace the *Form Trigger* with a *Google Sheets* or *Airtable** trigger to run this enrichment process for an entire list of new leads automatically.

Discover relevant contacts from target accounts using Octave intelligent prospecting Who is this for? Sales development teams, account-based marketing professionals, and RevOps teams who are tired of generic job title filtering that misses the real decision makers. Built for teams that need to find the right people based on actual responsibilities and business context, not just titles on LinkedIn. What problem does this solve? Most prospecting tools are flying blind when it comes to finding the right contacts. You search for "VP of Engineering" but miss the "Head of Platform" who actually owns your use case. You filter by "Marketing Director" but the "Growth Lead" is the real buyer. Traditional prospecting relies on job title matching, but titles vary wildly across companies. This workflow uses Octave's context engine to find contacts based on who actually does the work your solution impacts, regardless of their specific job title. What this workflow does Target Account Processing: Reads target account lists from Airtable (or other data sources) Processes company domains for intelligent contact discovery Handles batch processing for multiple target accounts Context-Aware Contact Discovery: Uses Octave's prospector agent to find relevant stakeholders within target organizations Leverages your defined personas to identify the right people based on responsibilities, not just titles Analyzes organizational structure, role responsibilities, and KPIs to match contacts to your solution Discovers decision makers and influencers who might be missed by traditional job title searches Structured Contact Output: Returns discovered contacts with complete profile information Includes LinkedIn profiles, contact details, and role context Organizes contacts by relevance and decision-making authority Exports contact lists back to Airtable for sales team action Setup Required Credentials: Octave API key and workspace access Airtable API credentials (or your preferred contact management platform) Access to your target account list Step-by-Step Configuration: Set up Target Account Source: Add your Airtable credentials to n8n Replace your-airtable-base-id and your-accounts-table-id with your actual account list Ensure your account list includes company domains for prospecting Configure trigger method (manual, scheduled, or webhook-based) Configure Octave Prospector Agent: Add your Octave API credentials in n8n Replace your-octave-prospector-agent-id with your actual prospector agent ID Configure your prospector with relevant personas and role definitions Test prospecting with sample companies to verify contact quality Set up Contact Output Destination: Replace your-contacts-table-id with your target contact list table Configure field mapping between Octave output and your contact database Set up data validation and deduplication rules Test contact creation and data formatting Customize Contact Selection: Configure which personas to prioritize in your prospector agent Set relevance thresholds for contact discovery Define organizational levels to target (individual contributors vs. management) Adjust contact volume per account based on your outreach capacity Required Account List Format: Your Airtable (or data source) should include: Company Name Company Domain (required for prospecting) Account status/priority (optional) Target personas (optional) How to customize Prospector Configuration: Customize contact discovery in your Octave prospector agent: Persona Targeting:** Define which of your Library personas to prioritize when prospecting Role Responsibilities:** Configure the specific responsibilities and KPIs that indicate a good fit Organizational Level:** Target specific levels (IC, manager, director, VP, C-level) based on your solution Company Size Adaptation:** Adjust prospecting approach based on organization size and structure Contact Selection Criteria: Refine who gets discovered: Decision-Making Authority:** Prioritize contacts with budget authority or implementation influence Problem Ownership:** Focus on roles that directly experience the pain points your solution solves Technical Influence:** Target contacts who influence technical decisions if relevant to your offering Process Ownership:** Identify people who own the processes your solution improves Data Integration: Adapt for different contact management systems: Replace Airtable with your CRM, database, or spreadsheet system Modify field mapping to match your contact database schema Add data enrichment steps for additional contact information Integrate with email platforms for immediate outreach Batch Processing: Configure for scale: Adjust processing volume based on API limits and prospecting quotas Add scheduling for regular account list updates Implement error handling for accounts that can't be prospected Set up monitoring for prospecting success rates Use Cases Account-based marketing contact list generation Sales territory planning and contact mapping Competitive displacement campaign targeting Product expansion within existing customer accounts Event-based prospecting for specific personas Market research and competitive intelligence gathering

Tagged with: , , , ,

Tagged with: , , , ,

Quick overview This workflow runs every Monday at 07:00 UTC to render a predefined list of URLs to PDFs using PDFMint, then merges the successful renders into a single dated archive PDF and outputs a short summary of what was archived. How it works Runs every Monday at 07:00 on a schedule trigger. Loads the list of web page URLs to archive and stops if the list is empty. Checks PDFMint usage to confirm enough credits remain for one PDF per page plus one merge operation. Builds a week-based archive name and file name, then renders each URL to an individual PDF with PDFMint. Drops any pages that failed to render so a broken URL does not fail the whole run. If two or more PDFs survived, merges them into a single dated PDF archive with PDFMint; otherwise keeps the single rendered PDF as the archive. Outputs a summary string describing how many pages were archived and the resulting file name. Setup Self-host n8n and install/configure the PDFMint community node, then add a PDFMint API key credential. Replace the URLs array and (optionally) the base archive name in the “Set the pages to archive” step. Adjust the schedule rule if you want the archive to run on a different day or time. Ensure your PDFMint plan has enough monthly credits for your page count (one credit per rendered page plus one credit for merging). Additional info Disclosure: I build and run PDFMint, the service this template calls. This is a self-submission, not a third-party recommendation. Executed before submitting, in n8n 2.36.7 on Node 24 with n8n-nodes-pdfmint@0.4.1 installed from the public npm registry, against the live service. Four runs: three reachable pages produced a 3,737,422-byte, 79-page merged PDF ("Archived 3 of 3"); three pages with one 404 dropped the dead page and merged the rest into 1,544,647 bytes / 70 pages ("Archived 2 of 3"); two pages with one 404 left a single survivor, where the merge is correctly skipped because PDFMint needs two PDFs, and the summary says so; and a run with credits_remaining=0 stopped at the quota check without spending anything. That single-survivor branch exists because the earlier version reported "Archived 1 of 2" when nothing had in fact been archived.

Quick overview This workflow runs manually or every morning to read three configurable RSS feeds, filter and deduplicate recent articles, score headlines against your keywords with a freshness boost, and generate a downloadable HTML digest that includes a balanced shortlist plus source health details. How it works Runs either on a manual trigger or daily at 08:00 (Europe/Warsaw). Reads three RSS/Atom feeds and labels each item with its source, keeping failures and empty feeds for reporting. Combines all feed results, validates links and publication dates, strips common tracking parameters, and keeps only articles within the configured lookback window. Deduplicates stories within the current run by normalized URL and title. Scores each headline against your comma-separated topics (and optional excluded words), adds a freshness bonus, and filters out items below the minimum score. Selects a balanced shortlist by applying a per-publisher cap and an overall story limit. Builds an HTML report with ranked links, scoring reasons, and feed health/warnings, then outputs it as a downloadable HTML file. Setup Update the three RSS feed URLs, topic keywords, lookback window, and limits in the “Choose topics and limits” step. If you use the scheduled run, confirm the timezone and adjust the cron schedule as needed. Run the workflow manually once and download the HTML from the final step’s binary output, and enable saving successful executions if you want to retrieve scheduled reports later.

Quick overview This workflow runs daily on a schedule and checks ClickUp tasks in one or more lists for inactivity based on the task’s date_updated field, automatically applying “stale” tags and escalating long-idle tasks by tagging them and posting an assignee comment. How it works Runs every day at the configured hour using the schedule trigger. Loads monitoring settings (statuses, tags, stale thresholds, and tag names) and fetches matching tasks from the selected ClickUp list(s), then merges and deduplicates them. Skips tasks that already have the second-level stale tag (for example, stale:14). For tasks without the first-level stale tag, checks the last updated timestamp and adds either the first-level stale tag (for example, stale:7) or the second-level stale tag if they already exceed the higher threshold. For tasks that already have the first-level stale tag, checks whether enough time has passed since that tag was applied and, if so, removes the first-level tag and adds the second-level stale tag. When a task is escalated to the second-level stale tag, posts a warning comment on the ClickUp task and assigns the comment to the task assignee (or the creator if no assignee exists). Setup Add a ClickUp API credential (OAuth or API token) and select it on all ClickUp nodes. In the ClickUp task search node(s), choose the list(s) you want to monitor and enable/configure the second list node if you want to pull tasks from multiple lists. Update the monitoring settings (monitoredStatuses, monitoredTags, daysUntilFirstStaleTag, daysUntilSecondStaleTag, and the stale tag names) to match your ClickUp workspace conventions. Adjust the schedule trigger time and, if needed, set the workflow timezone in n8n settings so the run time matches your local time. Requirements A ClickUp account with API access ClickUp credential configured in n8n At least one ClickUp list to monitor Customization Change thresholds — Edit daysUntilFirstStaleTag and daysUntilSecondStaleTag in SetContext to any number of days Change tag names — Update firstStaleTagName / secondStaleTagName to match your ClickUp tag naming convention Monitor different statuses — Edit monitoredStatuses and monitoredTags in SetContext (e.g. add review, blocked) Add more lists — Duplicate GetTaskFromList1, update the List ID, enable the node, and connect its output to a new input port on AppendListTasks Change schedule — Open TriggerRegularly and switch from daily to weekdays-only or any custom cron interval Disable subtasks — Open each GetTaskFromList node and set subtasks to false in the Filters section

Quick Overview This workflow captures consultation requests from an n8n Form, logs the raw submission in Twenty CRM, normalizes and scores the lead, deduplicates Companies by website and People by work email, and then creates either a qualified Opportunity with a follow-up Task or a nurture-review Task. How it works Receives a website lead submission via an n8n Form trigger. Creates a Note in Twenty CRM to store the untouched raw submission details for audit and context. Normalizes the lead data (email, website, domain) and calculates a lead score based on budget, team size, and urgency. Searches Twenty CRM for an existing Company matching the submitted website and updates it or creates a new Company if none is found. Searches Twenty CRM for an existing Person matching the work email and updates it or creates a new Person linked to the resolved Company. If the lead score meets the qualification threshold (60+), creates a Twenty CRM Opportunity and a next-day follow-up Task; otherwise, creates a nurture-review Task due in three days. Setup Install the community node package @blackswampai/n8n-nodes-twentycrm in your n8n instance. Create and select a Twenty CRM API credential (root URL and API key) for all Twenty CRM steps, with access to Notes, Companies, People, Opportunities, and Tasks. Review and publish the form, then copy the form URL (path twenty-crm-qualified-lead) to embed or link it from your website. Adjust the scoring weights and qualification threshold (currently 60), plus any Opportunity naming, currency, and task due dates to match your sales process.

Tagged with: , , , ,

This n8n template posts a quick weekly snapshot to Slack so your team sees last week’s funnel movement at a glance. It counts how many contacts entered the Lead stage in the past week—and optionally reports closed-won deals from the same period. Perfect for GTM standups and Monday pipeline reviews. How it works A weekly schedule (e.g., Mondays 07:00) kicks things off. HubSpot → Get all contacts** pulls contacts with hs_v2_date_entered_lead. A filter keeps only those whose lead date is within the last 7 days. Summarize** counts the resulting leads. Slack* posts: “Last week we generated *X** leads.” (Optional branch) Deals: HubSpot → Get all deals with hs_is_closed_won and hs_closed_won_date. Filter to closed-won last week. Summarize to report count and (if mapped) total amount. How to use Connect HubSpot on the contacts and (optional) deals nodes. Connect Slack and pick the destination channel. In Schedule the report, set your preferred day/time. (Optional) For the Deals branch, include the amount property on “Get all deals” and set Summarize → sum over amount. Activate the workflow. Requirements HubSpot** (OAuth2) Slack** (OAuth2) Notes & customization Time windows:** Adjust the filter to different periods (e.g., last 14 or 30 days). More stages:** Duplicate the contacts branch for MQL/SQL or custom lifecycle events. Richer Slack message:** Add emojis, trend vs. prior week, or a tiny leaderboard by owner. Segments:** Split by country/industry using HubSpot lists or additional filters.

Quick overview This workflow runs daily to fetch pending student fee records from Supabase, filters fees due in three days, and sends WhatsApp Business template reminders via the Meta WhatsApp Cloud API, then updates Supabase to mark each reminder as sent. How it works Runs every day at 9:00 AM on a schedule. Pulls all pending fee records from Supabase where reminder_sent is false and status is pending. Filters the results to only students whose due_date matches exactly three days from today. Sends a pre-approved WhatsApp template message (Meta WhatsApp Cloud API) to each student’s phone number. Updates the corresponding Supabase row to set reminder_sent to true so the reminder is not sent again. Setup Create a Supabase project, add a student_fees table (including student_phone, due_date, amount_due, status, and reminder_sent fields), and ensure your fee records are stored there. Add Supabase credentials in n8n and set the correct table name in the Supabase nodes. Set up Meta WhatsApp Business Cloud API access in n8n (system user token/credentials) and fill in your WhatsApp phone number ID. Create and get approval for a WhatsApp message template, then replace REPLACE_WITH_YOUR_APPROVED_TEMPLATE_NAME with your template name. Adjust the schedule time and the “due in 3 days” logic if you want reminders to go out at a different time or offset.

What This Workflow Does This workflow transforms Google Sheets into a lightweight productivity engine and connects it to Slack for automated reminders and daily recaps. No extra SaaS, no extra cost – just a simple system that keeps you on track and accountable. Pre-conditions / Requirements Before you start, make sure you have: A Google account with access to Google Sheets. A Slack workspace where you can post reminders and summaries. An n8n instance (self-hosted or cloud) with: Google Sheets credentials connected. Slack credentials connected. How It Works Task Tracking in Google Sheets Add tasks with columns: Task ID, Task Name, Due Date, Status, and Why it matters. The workflow checks for tasks that are due soon or overdue. Automated Slack Reminders Every 15 minutes, the workflow scans for tasks due in the next 30 minutes. Slack sends a ping with the task name, deadline, and reason. Daily Recap at 6 PM Slack posts a summary of how many tasks you completed vs how many are still pending. Encourages reflection and accountability. Duplicate Protection Each task has a "Last Reminder Sent" column so you don’t get spammed with repeat messages. Customization Options Reminder Frequency**: Change the Cron node to check tasks every 5, 10, 30 minutes, or hourly. Daily Recap Time**: Adjust the daily Cron node (default: 6 PM) to match your schedule. Slack Channel**: Point reminders and recaps to a private DM, a public channel, or multiple channels. Task Fields**: Add columns like Priority, Assigned To, or Category and adjust Slack messages accordingly. Weekly Review**: Extend the workflow with another Cron node on Sundays to send a weekly productivity score. Reflection Logs**: Add automation to write daily results into a second tab for trend tracking. Benefits ✅ Eliminate missed deadlines with proactive reminders. ✅ Daily accountability inside Slack – no extra dashboards. ✅ Zero SaaS costs – only Sheets, Slack, and n8n. ✅ Fully customizable to match your workflow, team, or habits. ✅ Scales easily from solo use to team task tracking. Use Cases Solo founders or freelancers who want a cheap but powerful task manager. Small teams who live in Slack and want lightweight accountability. Productivity enthusiasts who want flexibility and control without being locked into another SaaS.