Skip to main content

Monday.com Sync

Once your Monday.com account is connected to Gravity Rail, you can configure how data flows between your Monday boards and your workspace. This guide covers board mappings, sync rules, automations, member linking, and monitoring.

How It Works​

Sync is built on three layers:

  1. Board mappings define which Monday boards connect to which Gravity Rail data — either workspace members or Data Type records.
  2. Sync rules within each mapping control which columns map to which fields and how values are transformed.
  3. Automations trigger actions in Gravity Rail (notifications, new conversations) when data arrives from Monday.

Sync runs in one or both directions:

  • Outbound (Gravity Rail to Monday) pushes member or Data Type values to Monday items. Useful for writing back data collected by AI agents — call notes, outreach status, screening results — so your Monday board stays current.
  • Inbound (Monday to Gravity Rail) pulls Monday item data into member profiles or Data Type records. Useful for keeping Gravity Rail in sync with enrollment data, referral information, or status changes made by your operations team in Monday.

You can start with one direction and add the other later.

Setting Up Board Mappings​

Board mappings tell Gravity Rail which Monday boards to sync and how. Each mapping connects one Monday board to either your workspace members or a specific Data Type.

Choosing a Target Type​

The target type determines what kind of Gravity Rail data syncs with the Monday board:

TargetWhen to use itExample
MembersThe Monday board tracks people who should exist as workspace members — patients, enrollees, referrals. Each Monday item maps to one member.An enrollment board where each row is a patient with name, phone, email, and status columns
Data TypeThe Monday board tracks records that should be stored as Data Type records on existing members — assessments, outreach logs, intake answers. Each Monday item maps to one Data Type record.A voicemail queue board where each row is a call record linked to a patient

Most teams start with a member-target mapping for their primary enrollment or patient board. Add Data Type-target mappings later for boards that represent activities or records tied to those members.

Adding a Board Mapping​

  1. Go to the Settings tab.
  2. Click Add Board Mapping.
  3. Choose a Target — Members or Data Type. Choose it first: which boards you can pick depends on it.
  4. Select a Board from the dropdown. This shows all boards accessible to your connected Monday account. A board already mapped for the chosen Target is greyed out and says which Target adds the other direction; a board mapped for both Targets is greyed out for either.
  5. Set the Sync Direction:
    • Bidirectional — Data flows both ways. Best when both teams actively update the same records.
    • Outbound only — Data flows from Gravity Rail to Monday. Best when Gravity Rail collects data (via AI conversations, Data Types, or workflows) that your operations team needs to see in Monday.
    • Inbound only — Data flows from Monday to Gravity Rail. Best when your operations team manages data in Monday and Gravity Rail needs to stay current.
  6. Click Save Sync Settings. If the save shows Sync settings were not saved, see When a Save Is Refused.

The Settings tab showing a board mapping with board selector, target type, sync direction, inbound filter, and create unmatched toggle

You can add multiple board mappings to sync different boards or to sync the same board to different targets.

Board Mapping Options​

Depending on your target type and sync direction, additional options appear:

  • Create new members for unmatched items (member targets only) — When enabled, inbound sync creates new workspace members for Monday items that don't match any existing member. Enable this if your Monday board is the authoritative source of new enrollees. Disable it if members should only be created through other channels (voice, SMS, web).
  • Inbound Filter — A CEL expression that limits which Monday items are synced inbound. For example, source.status == "Active" would only sync items with an Active status, ignoring archived or pre-screening records.
  • Acting Member for Data Type Writes (required for inbound sync with Data Type targets) — Select a workspace admin whose permissions authorize writing to Data Type records during inbound sync.
  • Group for new items (Data Type targets with outbound sync) — The Monday group new items are created in. Leave it on Board default group to let Monday choose. Updates never move an item to another group. Changing the board clears the choice. A saved group that was deleted from the board shows as no longer on this board; Gravity Rail keeps sending that group rather than picking another one, and Monday's refusal, if it refuses, shows in the Sync tab. Choose a current group to fix it.

Conflict Policy​

When at least one board targets Members, the Member Entity Settings card appears below your board mappings. Its Conflict policy applies to member sync on every board and decides what inbound operations do when a Gravity Rail field already has a value:

Conflict policyInbound behavior
Remote winsReplaces the Gravity Rail value with the Monday value. This is the default.
Keep localWrites only where no value is set. An empty Monday value still clears a Synced field; Member properties and Data Type fields keep their own handling of empty values.

Outbound writes and boards mapped to a Data Type are not affected.

Configuring Sync Rules​

Sync rules define how individual fields map between Monday columns and Gravity Rail. Each rule has a name and contains one or more operations in each direction.

Default Rules​

When you add a board mapping targeting members, three default rules are created:

RuleOutbound (GR to Monday)Inbound (Monday to GR)
NameMember name to Monday "Name" columnMonday "Name" to member name
EmailMember email to Monday email columnMonday email to member email
PhoneMember phone to Monday phone columnMonday phone to member phone

For Data Type targets, default rules are generated based on the Data Type's fields.

Adding a Sync Rule​

  1. In a board mapping card, find the Sync Rules section.
  2. Click Add Sync Rule.
  3. Name the rule descriptively (e.g., "Referral Date" or "Enrollment Status").
  4. Add outbound operations, inbound operations, or both.

Outbound Operations (Gravity Rail to Monday)​

An outbound operation writes data from a Gravity Rail member or Data Type record to a Monday column.

  • Source (left side) — Select from member properties, Data Type fields, labels, Member fields, or write a custom CEL expression.
  • Monday column (right side) — Search and select the target column. The picker shows each column's name, type, and ID.

For example, a care coordination team might create an outbound rule that writes the member's profile URL to a "Gravity Rail Profile" link column in Monday, giving the operations team one-click access to conversation history and Data Type values.

An expanded sync rule showing outbound and inbound field mappings between Gravity Rail and Monday columns

Status and Dropdown Columns: Label Matching​

When an outbound rule writes to a Monday status or dropdown column whose source is a Gravity Rail enum field, Gravity Rail sends the field's display label (e.g. Scheduled) — not the stored value (e.g. scheduled). For Monday to accept the write, the label set on the Gravity Rail option must exactly match the label set on the Monday column.

  • Saving a board mapping rejects with an actionable error if any Gravity Rail enum option label is missing from the Monday column's labels. Rename the option in the field editor or the label on the Monday column so they match exactly, then save again.
  • Saved mappings that drift later (label renamed in Monday after save) surface as a yellow warning at the top of the Settings tab and fail closed locally on the next sync run with a missing_remote_label error in the Sync tab — Gravity Rail does not call Monday with a value Monday would reject.
  • Comparison is exact: Scheduled and scheduled are different labels; trailing whitespace counts. There is no fuzzy match.
  • A fixed value typed as a Custom Expression (for example "Yes") is checked the same way when you save: it must be one of the column's labels exactly, or the save is refused with the board, column and rule position. An empty value "" clears the column and is always allowed.
  • Any other expression (a condition or a combination) cannot be checked at save. A non-empty result is checked against the column's labels before every write; a value that is not a label fails locally with missing_remote_label, and Monday is not called. A result that renders as an empty template artifact (the text None or null) is left out of the write instead, so the column keeps its current value.
  • When the column's labels cannot be read (the board reports an empty label list for the column, or its settings cannot be parsed), neither check can prove a mismatch: the value is sent and Monday decides. If Monday rejects it, the Sync tab shows Monday's own error code (remote_api_error:<Monday code>), not missing_remote_label.

Inbound Operations (Monday to Gravity Rail)​

An inbound operation writes data from a Monday column to Gravity Rail.

  • Monday source (left side) — Select a column or write a custom expression.
  • GR field (right side) — Choose where to store the value:
    • Core Properties — Name, email, phone, external ID.
    • New Managed Field… — a Synced field the Monday connection writes to its Synced fields Data Type, by key. The value shows on the member's Data tab under that Data Type.
    • Data Type Fields — Write to a specific field on a Data Type record (requires an acting member to be set).

The choices depend on the board's target. On a board that targets a Data Type, inbound operations can write only fields of that Data Type.

For example, an enrollment team tracking referral dates and referring organizations in Monday can map those columns to Data Type fields in Gravity Rail, so AI agents have that context when engaging with the member.

Record identifiers belong in real Data Type fields. If your Data Type represents a clinical record keyed by an MRN or other upstream identifier, model that identifier as a dedicated Data Type field (e.g. a medical_record_number DataField) — not as DataRecord.external_id. The Data Type's external_id column exists to idempotently bind one Monday item to one record; using it for MRNs silently collapses to "one record per Data Type per MRN" and reuses a non-PHI integration column for PHI.

Expressions​

Sync rule sources use CEL (Common Expression Language). Most of the time, you'll use the dropdowns and never write CEL directly. But for custom transforms — splitting names, formatting values, conditional logic — select Custom Expression and write your own. See the Developer CEL reference for context-specific variables and functions.

The expression context is the same as described in the HubSpot Sync guide: source.name, source.email, source.phone, source.form_data, source.labels, and all available transform presets.

On a board mapped to a Data Type, an outbound expression reads the Data Type record's fields as source.<field> and the member who owns the record as member.<field>: member.name, member.phone, member.email, member.date_of_birth, member.age, member.external_id, member.id, member.uuid and member.profile_url. Select Custom Expression to enter one. A record with no owner has no member data: a rule that reads the member is skipped for that record, and the other rules are still sent.

The same boards also read the record itself:

  • record.update_url — a link to the record on its member's page in Gravity Rail (empty for a record with no member). Map it to a Monday link column. The link contains the member's ID, so saving a rule that reads it needs permission to read members as well as the form's records.
  • record.created_at — when the record was created. It never changes, so a Monday date column fed from it (for example a referral date) keeps its value when the record is edited later.

To send only records created after a moment — for example when moving from an older automation to sync — set the board's Outbound Filter to timestamp(record.created_at) >= timestamp("2026-11-06T18:00:00Z") with your own time in UTC. Older records are never sent, even when edited later, so keep the filter in place.

Item names. A rule whose Monday column is the item Name sets the item's name when it is created and renames it on later updates. Without one, a new item is named after the record's name field, or Record <id>.

Member board or Form board? Pick the board mapping by what the Monday item represents. If a form update should change a column on the member's existing item, add the rule to the Members board mapping and read the form as source.form_data.<form>.<field> — saving it makes changes to that form sync the member. If each form record is its own Monday item, use a Form board mapping.

Importing from a Board​

If you want to do a one-time import of Monday items into Gravity Rail (rather than ongoing sync), use the import feature. This is useful for initial setup — importing your existing Monday roster as workspace members before enabling ongoing sync.

  1. On the Settings tab, click Import from Board.
  2. Select the Board to import from.
  3. Choose Import As: Members or Data Type.
  4. Optionally add a Filter Expression to limit which items are imported.
  5. Check Dry run to preview what would be imported without making changes.
  6. Click Preview Import (dry run) or Start Import.

The import continues in the background; keep the stream key the dialog shows to identify the run. Always run a dry run first on large boards.

Post-Sync Automations​

Board mappings support automations that trigger after an inbound sync completes. These bridge the gap between data arriving from Monday and action happening in Gravity Rail.

To add an automation:

  1. Expand a board mapping on the Settings tab.
  2. Find the Automations section and click Add automation.
  3. Choose an action:
    • Notify Staff — Send a notification when an item syncs. Configure the message template, recipient (target member, acting member, or a specific person), and optional delay. Useful for alerting a care coordinator when a new referral arrives from Monday.
    • Create Chat — Start a conversation in a workflow when an item syncs. Select the workflow, channel (SMS, Phone Call, or Web Chat), and optional opening message (what the member receives). Useful for automatically kicking off an enrollment outreach when a new patient appears in Monday.
  4. Optionally add a Condition (CEL expression) to limit when the automation fires.

A Notify Staff automation card with message template, recipient selector, delay, and condition fields

Linking Members to Monday Items​

The Members tab shows which workspace members are linked to Monday items. Links are created automatically during sync, but you can also manage them manually.

The Members tab showing linked Members and the action that opens the matching tool

Finding Matches​

If you have existing members in Gravity Rail and existing items in Monday that represent the same people, use the matching tool to link them:

  1. Go to the Members tab.
  2. Click Link Members.
  3. In the dialog, click Find matches. Gravity Rail searches your Monday boards for items that match existing Members by email or phone.
  4. Review the matches and click Link on individual matches, or Link All to link them all at once.

A match is proposed only when the search of a board finishes completely and finds exactly one item for the Member across the columns the board's match strategy uses, and never for an item already linked to another Member on that board or proposed to two Members. A Member with an ambiguous or unfinished search gets no proposal on that board and can still be linked manually, for example through the Gravity Rail API.

This is especially useful when connecting Monday to a workspace that already has members from other channels (SMS, voice, web).

The member-matching dialog, showing its search control and the match criteria

Unlinking​

To remove a link between a member and a Monday item, click Unlink next to the member on the Members tab. This doesn't delete the member or the Monday item — it just removes the association so they won't sync.

Seeing Where Monday Keeps Its Data​

The read-only Data tab shows how the connection recognizes a member, which Data Types it keeps data in, and where every mapped field lives. The Data Type that holds your Synced fields is listed under Datasets. In Field map, rows are grouped under Monday board rules. A Data Type you chose for a board is marked Customer-selected Data Type: Monday writes the Data Types your boards name, but it does not own them, so they are not listed as its datasets. For what each dataset state and Field map column means, see Seeing Where a Connection Keeps Its Data.

Viewing Sync Logs​

The Sync tab shows sync activity. You'll see:

  • Live progress during an active sync, with counts for synced, failed, and skipped items.
  • Per-item status showing which members or records succeeded or failed.
  • Error details — click a failed item to see the specific error message.
  • Sync history — a list of past sync runs with timestamps and status.

Test on Small Batch​

When configuring a new board or changing rules, full syncs can take a long time and touch thousands of records. The Test on small batch button next to each entity-type's sync controls runs a capped dry-run preview:

  • Default sample size: 20 records. Adjust with the number input next to the button (1–200).
  • Always a dry run: writes are not persisted, regardless of whether Full resync is checked.
  • Doesn't move the checkpoint: the sync's resume position is unchanged, so the next real sync still picks up where it left off.

Use it to validate field mappings, filters, or a new match strategy on a small slice before committing to a full sync. The Sync tab shows the same per-item status as a normal run, so you can spot mapping or compatibility issues without waiting for thousands of records to process.

Troubleshooting​

Inbound Sync Not Receiving Updates​

Inbound sync requires a Signing Secret to verify webhooks from Monday.com. Open Setup and choose Update credentials to add the signing secret.

Items Not Matching Existing Members​

By default, inbound sync matches Monday items to existing members by email. If your Monday board doesn't have email data, items won't match and will be skipped (or created as new members if "Create new members for unmatched items" is enabled). Check that your sync rules include an inbound email mapping.

If you need to match on a stable identifier that isn't email, open the board mapping's Member Match Strategy dropdown and choose Match by custom field. Two pickers appear:

  • Match On (Local field) — A grouped combobox with two sections:
    • Properties — A Member built-in column: Name, Email, Phone, or Description.
    • Custom fields — A key this Monday connection already holds a value for: a Synced field it writes to the connection's Data Type (for example through an inbound rule on another board that targets it) or a Connection ID (a board's item link). To match on a key the list doesn't show yet, choose Use key…, type the key and select Use key. This only chooses the key to match on — it creates no field. The matcher resolves Members whose value for that key on this connection equals the column value.
  • Match Column (Monday) — Which Monday column carries the remote value. Select any real column on the board.

The intended flow for multi-board workflows is:

  1. Board A writes a stable identifier (for example an MRN) to a Synced field — add an inbound rule whose target is New Managed Field…, key medical_record_number (or your chosen key), source the MRN column.
  2. Board B matches on that same key — pick Match by custom field, select medical_record_number from the Custom fields group (or type it with Use key… if it isn't listed yet), and pick the Monday column that carries the same value.

Every board scoped to this Monday connection can match on the same key without overloading Gravity Rail's Member.external_id column.

If multiple Members share the same key+value pair the inbound item is skipped with "Multiple members matched the selected custom field key" in the run-item detail — the raw value is never logged. Resolve by archiving the duplicate Member or by narrowing the key.

Data Type Field Writes Failing​

Inbound rules targeting Data Type fields require an Acting Member to be set on the board mapping. This must be a workspace admin. Check the board mapping configuration on the Settings tab.

Monday Column Types​

Not all Monday column types are supported for sync. The column picker shows which columns are available. If a column doesn't appear, its type may not yet be compatible with the sync framework.

Outbound Sync Not Updating Monday​

Check the Sync tab for errors. Common causes include expired OAuth tokens (use Reconnect in the connection header), column type mismatches (e.g., writing text to a date column), or missing board permissions on the Monday.com app.

When Monday refuses a write, the failure shows Monday's own error code after remote_api_error: — for example remote_api_error:ColumnValueException or remote_api_error:InvalidColumnIdException. A code Gravity Rail does not recognize shows as UNKNOWN_VENDOR_ERROR. The code tells you the kind of problem, not which column caused it.

Save Rejected: "form option label(s) ... are not present on the Monday status column"​

The save-time validator enforces that every Gravity Rail enum option label exists exactly on the Monday status or dropdown column it maps to. If the labels diverge (e.g. the Data Type has In Progress but the Monday column only has In progress), saving the mapping returns an HTTP 400 with the offending labels listed.

To fix: open the field editor for the Gravity Rail field, rename the option's label to match the Monday column exactly, save the Data Type, then save the sync mapping again. Alternatively, rename the Monday column label to match Gravity Rail. Stored values (option values) are unaffected — only display labels need to match.

"Sync configuration warnings" Banner​

A yellow banner at the top of the Settings tab listing label mismatches means a saved mapping has drifted: the Gravity Rail option labels and the Monday column labels no longer agree. The next outbound sync for those rows will fail closed with missing_remote_label (visible in the Sync tab) until the labels are realigned.

Save Warning: "More formula columns are referenced … than Monday … serve in one request"​

Monday reads the values of at most five formula columns in one request. If a board mapping reads more than five different formula columns — counting the columns its inbound rules use, its inbound filter and the columns it matches Members on — the save still succeeds but shows a warning. The warning starts with the board mapping positions it is about (for example, "Board mappings at position(s) 0, 2:", counting from 0 in the order the mappings appear) and says that some formula values will not be read. It does not say how many formula columns were found. Several mappings on the same board can trip it together: when changes arrive from Monday, the columns of every mapping on that board are read in one request, so two mappings that each read three formula columns also get the warning, naming both positions.

To resolve: split the mapping across multiple boards if possible, drop formula references you don't actually consume downstream, or precompute the formula in Monday into a non-formula column (text/number) and reference that column instead. The warning is informational — Gravity Rail will not block the save, but you should expect some formula values to arrive empty, with no error from Monday, until the mapping reads five formula columns or fewer.

Archived or Deleted Monday Items​

When a Monday item is archived or deleted, Gravity Rail retires the linked DataRecord. A retired DataRecord is hidden from automation evaluation — it will not trigger EventRules, pass CEL gates, match saved Member filters or Member Match conditions, appear in the Members list for those filters, or appear in workflow queues. The underlying data is not deleted. All field values are preserved in Gravity Rail.

If the item is later restored in Monday (un-archived or recovered), re-running sync will reactivate the DataRecord and it will resume participating in automations normally. You can also manually relink the record from the Members tab.

Members linked to archived Monday items are not affected unless the board mapping has Archive member on remote archive enabled. When that option is off (the default), the member remains active in Gravity Rail regardless of the Monday item's state. When it is on, archiving the Monday item archives the member — they will no longer receive messages or participate in workflows until manually unarchived.

Tips​

  • Start with one board and one direction. Get a single board mapping working before adding more. If you're migrating from an existing integration, start with inbound to verify field mappings before enabling outbound.
  • Use the dry run import to preview before committing. This is especially useful for large boards or when you're unsure about column type compatibility.
  • Check the Sync tab after your first sync to catch mapping issues early. Most errors come from column type mismatches or missing fields.
  • Name your rules after the data they carry. With many columns on a Monday board, descriptive rule names ("Referral Date," "Enrollment Status," "Caregiver Phone") make configuration much easier to review and maintain.
  • Use filters to limit scope. If your Monday board has test rows, archived items, or records in early stages that shouldn't sync yet, add an inbound or outbound filter to keep your workspace clean.
  • Monday.com Setup — Create a Monday.com app and connect it to Gravity Rail
  • App Connections — Overview of all available connections
  • HubSpot Sync — Detailed guide on sync rules, CEL expressions, and filters (same concepts apply to Monday.com)
  • Members — Managing member profiles and data
  • Data Types — Structured data collection used in sync rules