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.
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.
Last updated