Field Mapping
TL;DR: Field mapping controls how data moves between your monday columns and Google Calendar event fields. You choose which fields to connect and in which direction — only mapped fields sync. This page is the full reference for all available mappings.
Before you start
- Field mapping is step 2 of the sync wizard — you'll reach it after choosing your calendar, direction, and items/subitems
- Make sure your board has the right columns — see Board Setup Best Practices
How field mapping works
Each row in the mapping screen connects one monday column to one Google Calendar event field. You decide:
- Which fields to map — only mapped fields sync; unmapped columns are ignored
- The sync direction per field — each mapping can flow monday → Google Calendar, Google Calendar → monday, or both ways, independently of the overall sync direction
When something changes in a mapped field on one side, the other side updates automatically. If you change a column that isn't mapped, nothing happens.
Column type matters: each Google Calendar field can only map to a compatible monday column type. For example, Title maps to a Name column — you won't see it as an option if you try to map it to a Status or Number column. The mapping dropdown only shows columns that match the expected type.
Required mappings
These two mappings are mandatory — you can't create a Google Calendar event without a title and a date, so the sync won't activate until both are set:
Title
Name column
Every Google Calendar event needs a title — maps to the item name
Start Date
Date column
Every Google Calendar event needs a date — maps to a date column on your board
Optional mappings
These fields can be mapped for richer sync. All are optional — map only what you need.
Start Time
Hour column
Syncs the event start time. Leave unmapped for all-day events
End Date
Date column
Syncs the event end date (useful for multi-day events). Mainly for Google → monday — for monday → Google, Duration takes priority
End Time
Hour column
Syncs the event end time. An alternative to Duration — map one or the other
Duration (minutes)
Numbers column
Syncs event length in minutes. Defaults to 30 if not specified. An alternative to End Time
Description
Text column
Syncs the event body/description
Location
Location/Text column
Syncs the meeting location or URL
Attendees
Text column
Syncs event attendees as comma-separated email addresses
Per-field sync direction
Each mapping has its own direction control — independent of the overall sync direction you set in step 1. This lets you create nuanced setups:
- Both ways — changes on either side update the other
- Monday → Google Calendar — the monday column is the source of truth; Google Calendar updates to match
- Google Calendar → Monday — the Google Calendar field is the source of truth; monday updates to match
Example: You might set your overall sync to two-way, but make the Description field one-way (monday → Google Calendar only) so calendar edits don't overwrite your board notes.
Common mapping scenarios
Basic meeting sync
Map just the essentials — title, date, time, and location. Good for keeping your calendar and board aligned without over-syncing.
Full project sync
Map everything — title, date, time, duration, description, attendees, location. Use when your board is the central source of truth and you want calendar events to reflect all details.
Read-only calendar mirror
Set all field directions to Google Calendar → monday. Your calendar events create and update items on your board, but board changes don't push back to Google Calendar. Good for dashboards and reporting.
Common gotchas
- Only mapped fields trigger syncs — if you update an unmapped column, nothing happens on the Google Calendar side
- Check the pre-filled columns — the app suggests a column for each field, and the guess can be wrong (e.g., Description pre-filled with an Attendees column). Review every row before you click Next
- You can edit mappings after activation — click the pencil icon in My Syncs to reopen the wizard
- Changing a mapping doesn't retroactively update existing items — only new changes follow the updated mapping
- The Integration Column is created automatically and cannot be mapped — it's used internally to link items to events
- Each Google Calendar field requires a specific monday column type — if your board doesn't have a matching column, add one before mapping (see the table above for which type each field needs)
Next up
Related
- Setting up a Sync — full setup walkthrough
- Board Setup Best Practices — recommended columns and structure
- Understanding Conditional Triggering — filter which events and items sync
- Integration Column explained — the column that links items to events
Still stuck?
If something isn't working as expected, check Troubleshooting or FAQ . You can also reach us at hello@fantasymedia.io .