How to Get Current Date in n8n Easily 2026

Start from the Overview screen of your n8n instance, where every workflow, credential, and data table you have access to is listed. This is the same screen whether you're on n8n Cloud or a self-hosted instance, and it's where you'll either open an existing workflow or click Create workflow to start a fresh canvas for testing date expressions. The stats across the top — production executions, failure rate, run time — are a useful gut check before you start adding new logic, since a spike in failures is worth investigating before you build on top of it.

The fastest route is to skip adding a node entirely. Click into any parameter field on any node, switch it to expression mode, and reference the current date directly using n8n's built-in variable — no extra step in your workflow just to know what day it is. This works well for quick uses like stamping a note field or filtering records, but because it returns a raw JavaScript date object, it's not always in a shape that plays nicely with every API you send it to.

For anything more deliberate than a quick inline reference, drop a Date & Time node onto your canvas. Search for it from the node panel like you would any other node, and connect it after the trigger or step where you need the timestamp generated. This node exists specifically to turn a raw date into a clean, predictable string, which matters the moment that value needs to be compared, sorted, or stored somewhere outside n8n.

Inside the node, set the operation to format a date, then choose the output layout — day-month-year, year-month-day, or whatever your downstream system expects — along with the correct timezone. Getting the timezone right here matters more than it seems: a workflow that runs fine in testing can quietly log the wrong day once it's scheduled to run at midnight in a different region.

Most real workflows don't just want today — they want yesterday, seven days from now, or an expiry threshold thirty days out. The Date & Time node's offset option lets you add or subtract days and hours from the current timestamp to calculate exactly that kind of relative date, which is what you'll use for anything involving trial expirations, follow-up reminders, or rolling date-range filters.

Before wiring the date into the rest of your workflow, open the data preview pane and confirm the value looks the way you expect — right format, right timezone, right offset. If this value is heading to an external API or a CRM, format it as a standardized ISO timestamp rather than a locale-specific string; ISO keeps the structure consistent no matter which system reads it next, which saves you from parsing errors down the line. Once it checks out, drag a connection from the node into whatever step consumes the date.