monday.com Work Management Core Certification flashcards

32 cards. Read the term and the definition here. The deck at the top of this page is optional.

Board vs workspace

A workspace is a container that groups boards and folders and controls who can access them; a board holds items and columns and is the unit automations and dashboards read from.

Subitem structure

Subitems are a second level of rows nested under a parent item. They have their own columns, separate from the parent board's columns, and can be summarized back to the parent with a rollup.

Connect Boards column

A column that stores a live link between an item and one or more items on another board. The link is saved on the source board and enables Mirror columns and cross-board automations.

Mirror column behavior

A Mirror column displays a column value pulled from a connected item on another board. It is read-only on the receiving board and refreshes when the source value changes.

Formula column limits

A Formula column computes values from other columns on the same item using arithmetic and functions. It cannot write to other columns and cannot read columns from a different board directly.

Guest vs member access

A member belongs to the account and can be added to boards; a guest is invited to specific boards only, sees nothing else, and cannot browse the account's workspace structure.

Item ID vs item name

The item ID is an immutable numeric identifier assigned per board and used in URLs and API calls. The item name is editable text, so it is unreliable as a unique key.

Board duplication effects

Duplicating a board copies its groups, columns, items, and automations. External integration connections and some app settings are not carried over and must be reconnected.

Chart widget aggregation

Each chart widget chooses an aggregation: item count, count per group, count per status label, or sum/average/min/max of a Numbers column. Changing aggregation changes the displayed values.

Widget-level filters

Filters set inside one widget apply only to that widget. Two widgets on the same dashboard can therefore show different subsets of the same source board.

Dashboard filter stacking

Dashboard-level filters apply to every compatible widget, and widget-level filters apply on top of them. The visible result is the intersection of both filter sets.

Multi-board widget matching

A widget combining several boards merges rows only where the boards share the charted column by title and type. Missing or differently named columns yield empty or partial charts.

Workload widget inputs

The Workload widget sums effort per person using the People column assignments and configured capacity. Subitem assignments are counted only when the widget includes subitem data.

Public dashboard link

A dashboard can be shared as a view-only public link. Anyone with the URL can see the widget data without logging in, so sensitive boards should not be shared this way.

Dashboard refresh timing

Dashboards read board data when rendered rather than storing a snapshot. A board edit appears after the dashboard reloads, and exported files never update on their own.

Numbers widget use

The Numbers widget displays a single aggregated figure, such as total revenue or open item count, and optionally compares it to a goal or previous period.

Integration run ownership

An integration runs under the account of the user who created it, using that user's board permissions. Deactivating that user or removing board access stops the recipe.

Outbound vs inbound recipe

Outbound recipes start in monday.com and act in another app; inbound recipes start in the other app and create or update monday.com items. Direction determines which app holds the trigger.

Webhook payload delivery

The webhook integration sends an HTTP POST with a JSON body to a chosen URL when the selected event occurs. The endpoint must accept POST and return a 2xx status.

Integration failure logging

Failed integration runs, such as expired authentication or a deleted target, are recorded in the integration's activity log. They are not retried automatically after the cause is fixed.

Calendar sync integration

A calendar integration maps a monday.com date or timeline column to an external calendar event. Edits sync in the configured direction and can overwrite manual changes on the other side.

Integration Center scope

The Integration Center lists recipes installed on a board or account. Disabling a recipe prevents future runs but leaves items it already created or changed untouched.

Automation trigger vs condition

A trigger is the event that starts a recipe, such as a status change to Done. A condition is checked at run time and can block the action without being the starting event.

Custom automation builder

The custom builder combines one trigger, multiple and/or conditions, and several actions in a single recipe. It covers logic that the prebuilt one-line recipes cannot express.

Automation cascade risk

If an automation's action changes a value that triggers another automation, runs can chain. monday.com limits recursion, so design triggers so they cannot re-fire each other.

Date-arrives automation

A date-based automation fires when the date column reaches its value, evaluated in the account time zone. It fires once per item per date unless the date is changed.

Automation action quota

Plans that meter automations share a monthly action quota across all boards in the account. Exceeding it pauses automation runs until the quota resets or the plan changes.

Notify action targeting

A notify action sends an in-app or email notification to a person column value or a fixed user, depending on the recipe wording. The recipient must have access to the board.

AI agent output target

An AI step writes its result to a chosen destination, such as a text column, a status label, or a new subitem. The destination determines what downstream automations can read.

Non-deterministic AI output

AI steps generate text or classifications that can vary between runs on identical input. Validate critical fields with a human review step before automations depend on them.

Constrained prompt labels

To map AI output to a status column, list the allowed values in the prompt and use a fixed mapping. Unconstrained output can produce labels that do not exist on the board.

Human-in-the-loop review

A review pattern adds a pending status and a notification after the AI step, so a person confirms the result before the item advances to a final state.