Time Zone Setup in Make.com

Managing dates and times correctly in make.com is essential when your scenarios run across multiple regions, depend on precise schedules, or process time-based data from different systems. This guide explains how time zones work in the platform and shows you exactly where to configure them for accurate automations.

How make.com handles dates and times

Before changing any settings, it helps to understand how the platform treats time under the hood. The core system stores all dates and times in the same reference zone to avoid ambiguity and calculation errors.

• All dates and times are stored in UTC.
• Time zone settings only affect how values are displayed or interpreted.
• Scheduling modules use your configured time zone to decide when to run.

With these principles in mind, you can safely adjust user, organization, and scenario settings while keeping data consistent.

Where make.com uses time zones

Different areas of the interface rely on time zone configuration. Knowing which setting applies where helps you avoid incorrect triggers or unexpected timestamps.

• Scenario schedulers and other time-based modules.
• Execution logs and operation timestamps.
• Data mapping where date and time fields are parsed or formatted.
• User-facing displays, such as history and overview screens.

The following sections walk through each place you can configure time zones and how they interact.

Setting your profile time zone in make.com

Your profile time zone controls how times appear for you personally in the interface. It is especially important when reading logs, reviewing scenario runs, or editing schedules.

Steps to change your profile time zone

1. Sign in to your make.com account.
2. Open your account menu (usually your avatar or name in the top-right corner).
3. Select the option to view or edit your Profile or Account settings.
4. Locate the Time zone field.
5. Choose the correct time zone from the dropdown list.
6. Save your changes.

After this change, times in logs, scenario overviews, and other personal views appear according to your selected time zone, while the underlying data remains in UTC.

Configuring organization time zone in make.com

Organization-level settings affect shared workspaces, especially where multiple users collaborate. The organization time zone can act as a default or reference for newly created scenarios and shared resources.

How to set the organization time zone

1. Log in to make.com with a user that has permission to manage the organization.
2. Open the Organization or Team settings from the main menu.
3. Find the Time zone option within the general or regional settings section.
4. Select the desired time zone representing your organization’s main location.
5. Confirm and save the configuration.

This setting can serve as a default reference for new users or scenarios. Individual profiles and specific scenario modules can still override it when necessary.

Scenario-level time zone behavior in make.com

Within each scenario, certain modules rely directly on a time zone to compute when operations should run or how incoming data should be interpreted. If you work with schedules or date parsing, scenario-level behavior is crucial.

Scheduling modules and time zones

When you add a scheduling or timer module, the configured time zone determines the actual execution time. For example:

• A scenario scheduled for 09:00 in a European time zone runs at a different moment than 09:00 in a US time zone.
• Adjusting the time zone later changes when future runs occur.

Always verify the time zone in each scheduling module when:

• Duplicating scenarios from other workspaces.
• Transferring ownership across regions.
• Deploying templates shared by other users.

Working with date and time fields

Many modules handle date-time values from external apps. The platform interprets and formats these values according to standard rules:

• Timestamps with an explicit offset or a Z suffix are treated as UTC-based.
• Plain date strings without time zone information may use your scenario or profile settings for interpretation.
• Conversion or formatting functions can be used to display values in a specific zone while retaining UTC internally.

When mapping date fields, review how the source application encodes time to avoid mismatched interpretations in make.com.

Best practices for time zones in make.com

To keep your automations reliable across regions, follow these practices when using time-based logic.

Use UTC for cross-region workflows

When scenarios involve users or apps in multiple countries, design your core logic around UTC wherever possible:

• Exchange timestamps between systems in UTC.
• Convert only at the presentation layer for local displays.
• Document which fields are UTC in your scenario notes.

This approach reduces confusion and dependencies on local daylight saving changes.

Document assumptions inside scenarios

When you depend on a particular time zone, document it clearly so future editors understand the intent. You can:

• Add notes to scheduling modules describing the assumed region.
• Include comments in routers or key transformers referencing the chosen time zone.
• Maintain a brief internal knowledge base with links to detail pages such as the official time zone documentation.

Check daylight saving and regional changes

Some regions adjust clocks seasonally. When you schedule critical processes, verify whether your chosen time zone follows daylight saving rules. If you need a fixed offset all year, select an appropriate region or maintain explicit logic in your scenario.

Troubleshooting time zone issues in make.com

If you see unexpected run times or mismatched log entries, use a structured approach to diagnose the problem.

Common symptoms

• Scenarios triggering earlier or later than planned.
• Timestamps in logs not matching expected local time.
• Date conditions evaluating incorrectly in filters or routers.

Step-by-step checks

1. Compare the timestamp from your external app with the value visible in make.com logs.
2. Verify your Profile time zone and update if necessary.
3. Check the Organization time zone to understand default assumptions.
4. Open each scheduling module in the scenario and confirm its configured time zone.
5. Review date parsing or formatting functions in mappers and tools modules.

By checking each layer, you can quickly pinpoint whether the issue stems from user settings, organization defaults, or individual modules.

Additional learning resources

For deeper automation strategies, integration planning, and time zone design patterns, you can explore expert resources beyond the built-in help. For example, Consultevo offers guidance on workflow design, optimization, and scaling automation solutions.

To stay aligned with the latest platform capabilities, review the official help content on managing time zones directly on the vendor site at help.make.com. Keeping your knowledge current ensures your make.com scenarios remain accurate, resilient, and easy to maintain as your automation needs grow.

Need Help With Make.com?

If you want expert help building, automating, or scaling your Make scenarios, work with ConsultEvo — certified workflow and automation specialists.

Get Help