> For the complete documentation index, see [llms.txt](https://help.blotato.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.blotato.com/web-app-features/content-calendar/timezone.md).

# Timezone

Website scheduling uses computer-local time. API and MCP schedules need a timestamp with an explicit UTC offset or Z.

## What is the calendar timezone?

Blotato uses your computer's local timezone. The time shown in your computer's clock is the timezone used by Blotato to schedule posts.

Check your computer's timezone before choosing a time. The Create slot form labels Time as your computer's local time. Review the resulting time in Posts > Scheduled or Calendar. Do not publish a test post to check the timezone.

***

## Scheduling via API or n8n

For REST, MCP, n8n, or Make.com, resolve the user's timezone for the intended date and send `scheduledTime` as ISO-8601 with an explicit offset or `Z`. Do not infer the timezone from the API key, social account, or server location.

A timestamp without an offset is treated as UTC. See [Scheduling fields and validation](/api-and-mcp-concepts/scheduling.md).

### Examples

For the same date, `09:00:00-03:00` and `12:00:00Z` represent the same instant. Include the full date in the request. Choose a future time within the supported scheduling window, not a copied example date. Account for daylight-saving changes when resolving the offset.

### Timezone in n8n + Google Sheets

If your scheduled time comes from a Google Sheet, it often has no timezone attached. Use an n8n "Date & Time" node to convert the value to ISO-8601 with the correct offset before passing it to the Blotato "Create Post" node.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.blotato.com/web-app-features/content-calendar/timezone.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.