Board Setup Best Practices
TL;DR: At minimum, your board needs an Item Name and a Date column. For the best sync experience, also add columns for Time, Duration, Location, Description, and Attendees.
When you create a sync, you'll map your board columns to calendar event fields — like Item Name → Event Title, or Date → Event Date. The columns you set up on your board determine what's available to map. No column, no mapping.
First time? Start with a template — it creates a board with all the recommended columns already set up. This page is for users who want to set up their own board or understand what each column does.
Recommended Board Structure
Here's the ideal setup for a meeting/calendar sync board:
Meeting Name
Item Name
The title of your meeting
Event Title
Date
Date
When the meeting occurs
Event Date
Time
Hour
Start time of the meeting. If this is empty or not mapped - this will be a whole day event
Event Start Time
Duration (min)
Number
This will be the duration in minutes of the event
Event Duration
Location
Text or Location
Where the meeting takes place
Event Location
Description
Long Text
Meeting details/agenda
Event Body
Attendees
Text
Who should attend. Email addresses separated by commas.
Event Attendees*
How does this connect to your sync? When you create a new sync, the setup wizard asks you to map each board column to a calendar event field. For example: you have a Date column on your board → in the sync wizard you map it to Event Date → now every item's date becomes a calendar event on that day. The "Maps To" column in the table above shows you exactly which event field each board column feeds into. For the full breakdown of how field mapping works, see Field Mapping .
For Event Timing
Use separate Date and Hour columns for the best control over your events:
- Use a Date column for the date
- Use an Hour column for the start time
- Use duration for the event duration or use another hour column for the end time
No Time column? If you don't map a Time column, events will be created as all-day events. Add an Hour column if you need specific start times on your calendar.
For Event Details
Location: Use a Text column or the native Location column type
Description: Use a Long Text column for meeting agenda and notes. Rich text formatting is supported — bullet points, links, and bold text will carry over to your calendar event body.
Attendees: Use a Text column with email addresses separated by commas (e.g.,
alice@company.com, bob@company.com). Don't use a People column — the sync needs email addresses, not monday.com user references.For Automations & Triggers
Create a Status column with labels like:
- Scheduled
- Confirmed
- Completed
- Cancelled
Use status changes to trigger automations (e.g., "When status changes to Confirmed → create event")
Common gotchas
- Keep column names clear — "Date" is better than "When is it happening." Simple names make field mapping easier.
- Use consistent column types — don't mix Date and Text columns for similar fields across groups.
- Don't change column types after a sync is running — switching from Date to Text mid-sync will break your field mapping and cause sync errors.
- Fill in required fields — items without a Date value can't create calendar events. The sync will skip them silently.
- Use a Text column for attendees, not People — the sync needs email addresses, not monday.com user references. A People column won't map correctly.
- Avoid formula or mirror columns for mapped fields — these are read-only and can't be written back to during a 2-way sync. Use native column types instead.
Next up
Your board is ready — now set up your first sync.