Skip to main content

Scheduled Daily Log for n8n

A daily n8n workflow that runs at 9:00 in your time zone, catches up after downtime and logs every run in a data table, with n8n 2.48.7 in Docker.

  • n8n
  • n8n Schedule Trigger node
  • n8n Data table node
  • Docker Compose
  • Docker Engine

Screenshots

Screenshot 1 of 6: Title card of Scheduled Daily Log for n8n: the promise, the stack chips, a terminal saving the time zone and running docker compose up -d, and the Daily log workflow.

Title card of Scheduled Daily Log for n8n: the promise, the stack chips, a terminal saving the time zone and running docker compose up -d, and the Daily log workflow.

One-off price

  • ₹19+ GST, ₹22.42 in total
  • $0.50
  • Download it from your library as soon as your payment is confirmed.
  • Every later release of this project is included, at no extra cost.
Latest release
1.0.0 · Nov 21, 2026

Overview

The complete source of a daily scheduled workflow for n8n. It runs every day at 9:00 in your time zone, runs once more when n8n comes back after a missed run, and saves the day and time of each run in an n8n data table. Includes the workflow, a one-click table setup and Docker Compose with n8n 2.48.7. Tested on macOS.

Most automations start as a job that has to run every day. Scheduled Daily Log for n8n gives you that job, ready to run: a daily schedule in your own time zone, a catch-up run after downtime, and a record of every run in a table you can read and download. Every step was tested in real runs on macOS with n8n 2.48.7 and Docker Desktop.

What it does

  • Runs every day at 9:00 in your time zone. Save your time zone once in .env, and change the time of day in one node.
  • Catches up after downtime. If n8n is off at 9:00, the Daily log runs once as soon as n8n starts again, then carries on with the schedule.
  • Logs every run. Each run becomes a row in the Daily log data table, with the day and the time it ran.
  • Leaves room for your own job. A Your steps here placeholder marks where your steps go, and the log keeps working whatever you add.
  • Sets up its own table. A setup workflow creates the table and its columns in one click. Running it again changes nothing.
  • Runs n8n for you if you need it. compose.yml starts n8n 2.48.7 in Docker, reachable only from your computer.

Install

  1. Unzip the archive and open a terminal in its folder.
  2. Save your time zone: echo "GENERIC_TIMEZONE=Asia/Kolkata" > .env.
  3. Start n8n with docker compose up -d. Skip this if you already run n8n 2.
  4. Open http://localhost:5678, create your owner account and import both workflows from the workflows folder.
  5. Run Set up the Daily log table once, then publish Daily log.

Every step with screenshots: How to Set Up and Run the Scheduled Daily Log for n8n (opens in a new tab).

Good to know

  • It runs while n8n runs. If several runs were missed, the catch-up runs once, for the most recent.
  • n8n isn't bundled. compose.yml downloads n8n's official image, and n8n's own licence applies to it.
  • Tested on macOS with Docker Desktop.

Learn how it works

The free n8n Tutorial for Beginners (opens in a new tab) teaches n8n from the start, and Part 3: Run a Workflow on a Schedule (opens in a new tab) builds this Daily log step by step.

n8n is a trademark of n8n GmbH. Docker is a trademark of Docker, Inc. Other names are trademarks of their respective owners.

Free tutorial series

n8n Tutorial for Beginners

Prefer to learn by building it? This free, step-by-step guide on our blog shows how the project is made.

Read the series (opens in a new tab)

What you get

Everything in the archive, at a glance.

  • Version 1.0.0 of the complete source: two n8n workflows, a Docker Compose file and a README
  • The Daily log workflow: a daily schedule at 9:00, a placeholder for your steps and a step that logs each run to a data table
  • Catch-up on missed runs: one late run when n8n starts again after missing 9:00
  • A setup workflow that creates the Daily log table in one click
  • compose.yml with n8n 2.48.7, private to your computer, taking your time zone from .env
  • A README with the setup steps, settings, troubleshooting and clean-up

Built with

The exact runtimes and versions it was built and tested against.

  • n8n2.48.7
  • n8n Schedule Trigger node1.4
  • n8n Data table node1.1
  • Docker Compose5.7.0
  • Docker Engine29.9.3

What is in the archive

The file tree you get once you unzip it.

scheduled-daily-log-n8n/

  • .env.example
  • .gitattributes
  • .gitignore
  • README.md
  • compose.yml
  • workflows/
    • daily-log.json
    • set-up-daily-log-table.json

What it needs from you

The accounts and services it expects to find, so nothing is a surprise.

  • n8n 2 that you run yourself (the free Community Edition is enough), or Docker to run the included n8n
  • Docker Desktop on macOS or Windows, or Docker Engine on Linux, to use compose.yml
  • A free port on your computer, 5678 by default
  • n8n running at the scheduled time, on a computer that stays on or on a server

Releases

Every version so far, newest first.

  1. 1.0.0Latest

    First release of the complete source.

    • A Daily log workflow that runs every day at 9:00 in your time zone and logs each run to an n8n data table.
    • Catch-up on missed runs: one late run when n8n starts again.
    • A setup workflow that creates the Daily log table in one click.
    • n8n 2.48.7 in Docker with compose.yml, tested on macOS.

Source Code Licence

What you may do with it

What you may and may not do with the source code you buy.

Read the full licence
  1. What this licence covers

This licence governs every file included in a product you buy from Dewiride Store: source code, configuration, database scripts, sample data, documentation and any other file in the download. It takes effect when your payment is confirmed and applies to every release of that product that reaches your library. Files that reach your library through an annual updates membership are governed in exactly the same way.

It forms part of the Terms of Sale and Use. Where a product page states different or additional licence terms for that product, those terms prevail for that product. The membership page may likewise state different or additional licence terms for the files a membership carries, and those terms then prevail for those files.

  1. The licence we grant you

We grant you a perpetual, worldwide, non-exclusive, non-transferable licence to use, reproduce, adapt, translate and modify the files, and to include the result in your own work, on the conditions set out below.

Perpetual means it does not expire. Worldwide means it is not limited to any country. Non-exclusive means we license the same product to other customers. Non-transferable means you cannot pass it on to someone else.

The licence is granted to you — either you personally, or the organisation you identified when buying. Everyone working within that organisation may use the files for that organisation’s projects. Nobody outside it may.

  1. What you may do
  • Use and change the files in your own projects, commercial or otherwise, with no limit on the number of projects.
  • Build a product or a service on them and charge your own customers for it.
  • Deploy the result for a client, as part of work you are doing for that client.
  • Distribute the result in compiled, deployed or otherwise non-source form.
  • Keep as many back-up copies as you reasonably need.
  • Study, observe and test how the code works, and obtain the information you need to make it work with your own software.

The last two are yours by law under sections 52(1)(aa) to (ac) of the Indian Copyright Act, 1957, and nothing in this licence is intended to take them away.

  1. What you may not do
  • Resell, sublicense, redistribute or publish the files themselves, in whole or in substantial part, in source form.
  • Include them in a template, starter kit, course, tutorial repository or component library that you sell or give away, where the code is the thing being supplied.
  • Share your account, your download links or your invoices with anyone outside your organisation.
  • Publish the files in a public repository, or in any other place where they can be obtained without buying them.
  • Remove or obscure the copyright and attribution notices in the source files.
  • Use the files to build something whose main purpose is to compete with Dewiride Store as a supplier of the same code.

The distinction that matters is simple: you may sell what you build with the code; you may not sell the code.

  1. Third-party components

Our products depend on open-source libraries, frameworks and services that we did not write. Those remain under their own licences, which we do not and cannot change. Where a product includes or requires such a component, its licence is named in the product’s documentation, and complying with it is your responsibility.

  1. Releases

Every release of a product you own is covered by this same licence and appears in your library at no extra cost. A release you have already downloaded remains licensed to you even if we later stop publishing the product. A release that reached your library through an annual updates membership is licensed to you on these same terms, and stays licensed after the period that carried it has ended.

  1. Ownership

We keep ownership of the files and of the copyright in them. You own whatever you create with them: your changes, your additions and the product you build are yours.

  1. If this licence ends

This licence ends if you materially breach it and do not put the breach right within thirty days of us asking you to in writing. It also ends if your payment is reversed or refunded, because the purchase it depends on no longer stands. Where a membership period is refunded or reversed, the licence ends for the releases that period carried and for nothing else: anything you bought separately, or that another period carried, is unaffected.

If it ends, you must stop using the files and delete the copies you hold. Work you had already delivered to a client before that point may continue in use, so that ending this licence never breaks something your own customer relies on.

  1. No warranty beyond the description

The warranties and limits in section 19 and section 20 of the Terms of Sale and Use apply to this licence as well.

  1. Governing law

This licence is governed by the law of India, and section 24 of the Terms of Sale and Use applies to any dispute about it. If a translation and the English version differ in meaning, the English version governs.