Skip to main content

Dates and time zones in automations

Learn how Tape stores dates in automations, why scripts run in UTC, and how to format dates and set a date field correctly so the time matches what people see.

Written by Leo

Automations run in UTC (Coordinated Universal Time, the time standard without daylight saving), while the people who use Tape work in their own time zone. This is meant to keep automations the same for every team, wherever they are.

Hovering above the automation name Expense approval shows Time zone UTC+01:00, and selecting it opens the list of time zones with Search for a time zone…

You can use this page for many things, including:

  • Working out why a date set by a script is one hour off.

  • Writing a date in an email in the format your customers expect.

Note:

  • Built-in actions handle time zones for you. When Update record copies a date from one field to another, the date matches what people see in the record.

  • Scripts don't. Perform calculation and Execute script read and write dates in UTC.

How dates are written

Tape uses the same text formats for dates in automations as in the Tape API:

  • Date and time: YYYY-MM-DD HH:mm:ss, for example 2026-11-10 15:00:00.

  • Date: YYYY-MM-DD, for example 2026-11-10.

  • Time: HH:mm:ss, for example 15:00:00.

These texts don't show a time zone. The name of the variable tells you which one it is. A name that ends in _utc holds UTC. The same name without the ending holds the same moment in the automation's time zone, which you set above the automation name.

Date values of a field

A date field adds several values you can use in actions and scripts. For a field called Due date with a time, in a database app called Tasks, you get values like these:

  • A start time in the automation's time zone, for example 15:00:00, and the same time in UTC, for example 14:00:00.

  • A start date in the automation's time zone, and the same date in UTC. Near midnight, the UTC date can be a different day.

  • A display text with date and time, in the automation's time zone and without seconds, for example 2026-11-10 15:00.

If the field holds a whole day without a time, there is no start time, and the date is the same in both time zones. Tape doesn't convert whole days between time zones.

When you set a date field with a script, use the UTC values.

Format a date

To show a date differently, format it with the date_fns library in Perform calculation or Execute script. For example, date_fns.format(your_date_value, 'y') returns the year. Learn more about scripts →

Set a date with a script

A script reads the text 2026-11-10 15:00 as UTC. If your team works in Central European Time (UTC+1), the record then shows 16:00 instead of 15:00.

To fix this, convert the date from your time zone to UTC before you save it, with the date_fns_tz.zonedTimeToUtc function and the name of your time zone:

var_target_datetime = date_fns_tz.zonedTimeToUtc(new Date('2026-11-10 15:00'), 'Europe/Amsterdam');

After this change, the record shows 15:00 for people in that time zone.

The action Execute a script with the code var_target_datetime = date_fns_tz.zonedTimeToUtc(new Date('2026-11-10 15:00'), 'Europe/Amsterdam') in the automation Set the meeting time in UTC

Let's look at an example

Let's say your property management team wants a follow-up date one day before each showing, at 9:00 AM local time. Here's how:

  1. Select Add action → Perform calculation and enter the code for the showing's start date minus one day, at 09:00.

  2. Convert the result with date_fns_tz.zonedTimeToUtc and your time zone name.

  3. Select Add action → Update record, choose your follow-up date field, select Calculation, and use the result.

  4. Select Create automation, or Save changes if the automation already exists.

The follow-up date now matches 9:00 AM for people in your time zone.

Time zone setting in the editor

Hover over the area above the automation name to show the time zone, for example Time zone UTC+01:00, next to Add description or Show description. Select it to choose another time zone from the list, for example UTC-08:00 Pacific Time (US and Canada), or type in Search for a time zone…. The setting is saved per automation. The time zone is used for schedules, for When a date field arrives, for date filters, and for every date value that isn't marked UTC.

Time zone UTC+01:00 above the automation name, with the list of time zones and Search for a time zone… open

Date errors

  • A date is one hour or one day off. Check whether a script wrote the date without converting from your time zone to UTC. Learn how to fix this above.

  • A date on a record has a different day than in your email. A UTC date near midnight can fall on a different day. Use the date value in the automation's time zone for text that people read.

  • A trigger runs at an unexpected time. On a scheduled time or interval runs in the automation's time zone. Check the time zone above the automation name.

Learn more

FAQs

Which time zone do automations use?

Scripts work in UTC. Each automation also has its own time zone setting in the editor. Tape actions convert dates for you. Scripts don't, so convert dates yourself when you set them with code.

Why is a date in my email different from the record?

If the email uses a UTC value, its time or day can differ from what the record shows. Use the value in the automation's time zone for text that people read.

Can I change the time zone of an automation?

Yes, hover over the area above the automation name, select the time zone, for example Time zone UTC+01:00, and choose another one from the list. The setting is saved per automation.

How do I show only the month or year?

Format the date in Perform calculation with date_fns.format. Use 'y' for the year, for example.

Are you a developer using the Tape API for automations?

The automation API has its own documentation for developers. Full reference: Date, time and time zones in the developer docs →

Still have questions? Find answers and get help from community experts in the Tape community →

Did this answer your question?