See llms.txt for all machine-readable content.

Back to Templates

Send daily UK public tender digests from Contracts Finder and Find a Tender

Quick overview

This workflow runs every weekday morning to fetch UK public-sector tenders from Contracts Finder and Find a Tender, filters and scores them against your criteria, deduplicates against an n8n Data Table of previously seen notices, and optionally emails a ranked digest.

How it works

  1. Runs manually or every weekday at 07:30 (Europe/London).
  2. Fetches recent open tender notices from the Contracts Finder OCDS feed and the Find a Tender OCDS API with pagination and continues even if one feed fails.
  3. Merges both sources, removes duplicates and non-active tenders, and scores matches using your keywords, CPV prefixes, location keywords, value band, deadline window, and SME suitability rules.
  4. Loads previously seen tender OCIDs from an n8n Data Table and filters out any tenders that have already been included in a prior digest.
  5. Builds a plain-text and HTML digest (including a warning if a feed could not be read) and only proceeds if there are new matches or fetch errors to report.
  6. If send_mode is set to send, emails the digest via SMTP; otherwise it keeps the digest as a draft output in n8n.
  7. Writes the new tenders into the n8n Data Table so they are not repeated on future runs (and skips saving if the email send fails so they retry next run).

Setup

  1. Update the Config values (keywords, cpv_prefixes, optional location_keywords, value/deadline thresholds, and seen_table_name) to match what you want to track.
  2. Ensure n8n Data Tables are available in your environment, as the workflow creates and uses a table to store previously seen tender OCIDs.
  3. To email the digest, configure SMTP credentials for the Send Email node and set digest_to and from_email in Config, then change send_mode from draft to send.