# Monday.com AI employee

Viktor works in Monday.com for you. Ask in Slack or Microsoft Teams.

Viktor is an AI employee that connects to Monday.com and helps you plan, assign, and track work on monday.com boards, running 106 Monday.com actions for you like Search, Get form, and Vibe ask. Ask in plain English from your workspace; Viktor does the work in Monday.com and reports back. Viktor connects natively.

- Tool: Monday.com
- Category: Productivity
- Connection: Managed connector (native integration)
- Actions available: 106
- Currently available in: Slack, Microsoft Teams, and Discord
- Page: https://viktor.com/integrations/monday-com

## What can your AI employee do in Monday.com?

Viktor connects to your Monday.com account and completes work in it. He doesn't just answer questions about Monday.com, he takes the actions on your behalf and delivers the finished result to your workspace.

Unlike workflow builders such as Zapier or Make, there is nothing to configure - no triggers to map, no workflows to maintain. You describe the outcome in plain English, and Viktor picks the right Monday.com actions, chains them with the other 9,800+ tools he connects to, and asks for approval before anything sensitive runs.

### About Monday.com

Manage work, projects, and team workflows

### How a run works

1. **You ask in your workspace** - Describe what you need in plain English
2. **Viktor picks the actions** - Selects from 106 Monday.com actions, chains them together
3. **Runs in Monday.com** - Helps you plan, assign, and track work on monday.com boards - your real data.
4. **Reports back** - Delivers the finished result to your workspace

## Use Monday.com from Slack and Microsoft Teams

Message Viktor in a Slack channel, a Microsoft Teams chat or a direct message. He opens Monday.com, does the work and posts the result in the same thread, so nobody has to switch tabs.

He can also run Monday.com work on a schedule, like a weekly Monday.com summary posted to your team's channel. Anything sensitive waits for your approval before it runs.

## Security and permissions

- Native integration - Viktor handles authorization itself, never sees your password, and you can revoke access at any time.
- Review-first approvals: sensitive Monday.com actions wait for your sign-off before they run.
- Isolated compute per team, encrypted in transit and at rest - and your data is never used to train models.
- SOC 2 Type 1 compliant, with Type 2 and ISO 27001 in progress.
- Viktor is not affiliated with or endorsed by Monday.com.

## What can you ask Viktor to do in Monday.com?

- "Create tasks in Monday.com from the action items in this thread."
- "Summarize what changed in Monday.com this week and post it here every Friday."
- "Find the tasks in Monday.com that are overdue and draft a status update."
- "Keep Monday.com in sync with our roadmap and flag anything at risk."

## How does Viktor work with Monday.com?

1. Open Viktor in a supported workspace.
2. Connect Monday.com natively - Viktor handles authentication.
3. Ask in plain English. Viktor runs the Monday.com actions, chains them with your other tools when needed, and reports back. Sensitive actions wait for your approval.

## What can Viktor do in Monday.com? (106 actions)

- **Agent catalog** - Browse the account-wide catalog of available trigger types and skills for monday platform agents. READ-ONLY — no agentid required.
- **All api read** - Execute read-only GraphQL queries against the monday.com API. Only queries are accepted — mutations are rejected with an error before the request is sent. Use the gettypedetails tool first to understand the schema before crafting your query.
- **All api write** - Execute GraphQL mutations against the monday.com API to create, update, or delete data. Only mutations are accepted — queries are rejected with an error before the request is sent. Use getgraphqlschema and gettypedetails tools first to understand the schema before crafting your mutation.
- **All monday api** - Execute any monday.com API operation by generating GraphQL queries and mutations dynamically. Make sure you ask only for the fields you need and nothing more. When providing the query/mutation - use getgraphqlschema and gettypedetails tools first to understand the schema before crafting your query.
- **All widgets schema** - Fetch complete JSON Schema 7 definitions for all available widget types in monday.com.
- **Board insights** - This tool allows you to calculate insights about board's data by filtering, grouping and aggregating columns. For example, you can get the total number of items in a board, the number of items in each status, the number of items in each column, etc. Use this tool when you need to get a summary of the board's data, for example, you want to know the total number of items in a board, the number of items in each status, the number of items in each column, etc.[REQUIRED PRECONDITION]: Before using this tool, if new columns were added to the board or if you are not familiar with the board's structure (column IDs, column types, status labels, etc.), first use getboardinfo with filters.columns.only to get column metadata without fetching views. This is essential for constructing proper filters and knowing which columns are available.[IMPORTANT]: For some columns, human-friendly label is returned inside 'LABEL<columnid' field. E.g. for column with id 'status123' the label is returned inside 'LABELstatus123' field.
- **Change item column values** - Change the column values of a single item on a monday.com board. [IMPORTANT] If you need to update multiple items in one call, use updateitems instead of calling this tool in a loop. Otherwise: change the column values of a single item in a monday.com board. [REQUIRED PRECONDITION]: Before using this tool, if new columns were added to the board or if you are not familiar with the board's structure (column IDs, column types, status labels, etc.), first use getboardinfo with filters.columns.only to get column metadata without fetching views. This is essential for constructing valid column values. For board-relation linking tasks, call linkboarditemsworkflow before using this tool.
- **Connect external agent** - Connect a custom external agent (an agent running on your own server/infra) to monday.com.
- **Create action** - Use to save a reusable action (a stored code script) for later execution by runaction. Save a reusable action (a stored code script). Variables are injected as environment variables (access via os.environ in Python, process.env in JS/TS).
- **Create agent** - Create a personal/custom agent on the monday.com platform. See getagent for what a monday platform agent is.
- **Create automation** - Creates an automation on a monday board from a structured natural-language description.
- **Create board** - Create a monday.com board. Use creationPrompt to describe how you want the board to be built.
- **Create column** - Create a new column in a monday.com board. [REQUIRED PRECONDITION]: If the column needs type-specific configuration (columnSettings) — e.g. status/dropdown labels, formula definitions, number units — first call getcolumntypeinfo with fetchMode "schema" for that column type to learn the valid settings structure. Do not guess the settings shape. To give the new column AI behavior, create it here first, then call configureaicolumn.
- **Create dashboard** - Use this tool to create a new monday.com dashboard that aggregates data from one or more boards.
- **Create doc** - Create a new monday.com doc either inside a workspace or attached to an item (via a doc column). After creation, the provided markdown will be appended to the document.
- **Create folder** - Create a new folder in a monday.com workspace.
- **Create form** - Create a monday.com form. Also creates a backing board to store responses. Returns the formToken for future mutations.
- **Create form submission** - Submit a response to a monday.com WorkForm. Use getform first to retrieve the WorkForm, then.
- **Create group** - Create a new group in a monday.com board. Groups are sections that organize related items. Use when users want to add structure, categorize items, or create workflow phases. Groups can be positioned relative to existing groups and assigned predefined colors. Items will always be created in the top group and so the top group should be the most relevant one for new item creation.
- **Create item** - Create a single item or subitem on a monday.com board, or duplicate an existing item. [IMPORTANT] If you need to create multiple items in one call, use createitems instead of calling this tool in a loop. Otherwise: create a new item with provided values, create a subitem under a parent item, or duplicate an existing item and update it with new values. Use parentItemId when creating a subitem under an existing item. Use duplicateFromItemId when copying an existing item with modifications. [REQUIRED PRECONDITION]: Before using this tool, if new columns were added to the board or if you are not familiar with the board's structure (column IDs, column types, status labels, etc.), first use getboardinfo with filters.columns.only to get column metadata without fetching views. This is essential for constructing proper column values and knowing which columns are available.
- **Create items** - Create up to 20 new items in a single call. Each item is fully independent - it chooses its own groupId, parentItemId (for subitems), duplicateFromItemId (for bulk templating from an existing item), and createLabelsIfMissing. A single call can therefore span multiple groups, mix regular items with subitems under different parents, and mix fresh creates with duplicates of existing items. Each item returns its own itemid and itemurl on success, or a raw error message on failure. [REQUIRED PRECONDITION]: Before using this tool, if new columns were added to the board or if you are not familiar with the board's structure (column IDs, column types, status labels, etc.), first use getboardinfo with filters.columns.only to get column metadata without fetching views. This is essential for constructing proper column values and knowing which columns are available.
- **Create notification** - Send a notification to a user via the bell icon and optionally by email. Use targettype "Post" for updates/replies or "Project" for items/boards.
- **Create update** - Create a new update (comment/post) on a monday.com item. Updates can be used to add comments, notes, or discussions to items. You can optionally mention users, teams, or boards in the update. You can also reply to an existing update by using the parentId parameter.
- **Create updates** - Create up to 40 updates (comments/posts) in a single call. Each entry is independent - it targets its own item, has its own body and mentions, and can reply to an existing update via parentId - so one call can post on many items, or post several replies. Use this instead of calling createupdate repeatedly when posting more than one update. Each entry returns its own updateid and itemid on success or a raw error message on failure.
- **Create view** - Create a new board view (tab) with optional filters and sorting.
- **Create view table** - Create a new table-type board view with optional filters, sort, tags, and table-specific settings including conditional coloring (highlight rows/cells based on column values).
- **Create widget** - Create a new widget in a dashboard or board view with specific configuration settings.
- **Create workflow** - Creates a new empty workflow in the given workspace and returns its identifiers (workflowObjectId and workflowDraftId).
- **Create workspace** - Create a new workspace in monday.com.
- **Delete action** - Use to permanently delete a saved action by its ID. Delete a saved action.
- **Delete view** - Delete a board view (tab) from a monday.com board. Use getboardinfo to find the view ID before deleting.
- **Execute code** - Use to run arbitrary code (Python, JavaScript, TypeScript, or Bash) in a monday-authenticated sandbox for bulk operations, data transformation, file I/O, or multi-step workflows. Run arbitrary code in a monday-authenticated sandbox, without saving.
- **Explore meetings** - Find which meetings are about a topic, person or project, or list meetings by date; the starting point for questions across meetings. With a query, meetings are ranked by meaning across their AI-generated content (title, AI gist, summary, topics, action items; not the transcript) together with keyword overlap on the title and gist, so a paraphrase can still match. It always returns the closest meetings, even when none is really about the query: judge each by its title and gist. Results are ordered by relevance, not by date. A recurring meeting is several results with one title, one per occurrence. Without a query it lists meetings newest first, filtered by date and access. Read a meeting with getmeetingscontent using its id.
- **Finalize asset upload** - Finalize a file upload and create the asset on monday.com. Call this after uploading the file to the presigned URL from getassetuploadurl. Requires the etag value from the PUT response headers. Automatically attaches the uploaded asset to the specified file column on the item. Returns the created assetid.
- **Form questions editor** - Create, update, or delete a question in a monday.com form. [REQUIRED PRECONDITION]: For update and delete, call getform first to resolve the exact question id and see its current type and settings — never guess a question id. For create, getform shows the existing questions so you do not duplicate one.
- **Get action** - Use to retrieve a saved action by its ID. Retrieve a saved action by ID.
- **Get activity logs** - Use when the user asks what changed, who did something, or what happened on monday.com boards, items or users over a period of time. Reads the monday.com activity log: who changed what, and when. Requires at least one of boardids, userids or correlationids. Narrow the query with itemids, eventtypes, entities, search and a time range (lasthours, or from/to; at most the last 90 days) rather than paging through everything — the tighter the filters, the faster and cheaper the call. Returns newest events first; pass the returned cursor with the same filters to get the next page. Rows are compact by default; set includedata only when you need the event payload, such as column values before and after a change — payloads share a per-call size budget. Only events the user is allowed to see are returned.
- **Get asset upload url** - Get a presigned URL to upload a file to monday.com. Returns an uploadid and uploadurl.
- **Get assets** - Get assets (files) by their IDs. Returns file metadata including name, extension, size, public URL (valid for 1 hour), thumbnail URL, upload date, and who uploaded it.
- **Get automation runs** - Read automation/workflow run history. Read-only.
- **Get automation statistics** - Aggregate automation run statistics. Read-only.
- **Get board activity** - Get board activity logs for a specified time range (defaults to last 30 days). Optionally filter by item ids or user ids to avoid fetching activity for the entire board. [REQUIRED PRECONDITION]: Call this with includeData=true before undoaction — it is the source of the actionrecorduuid that identifies the action to undo.
- **Get board info** - Get comprehensive board information including metadata, structure, owners, and configuration. Set includeKnowledge to true when you need to interpret the board rather than just read its configuration: for example, choosing a status, label or column value from the user's intent instead of an exact name they gave, or explaining what statuses, columns or roles mean. Not needed for structural work such as column ids, types, revisions or views. Adds latency and may be null while knowledge is still being generated. Set includeSubscribers to true to also return the board's subscribers (people and AI agents) and team subscribers. Also returns the board's views (e.g. table views, filter views) — each view includes its id, name, type, and a structured filter object. On large boards, ALWAYS narrow the response: use filters.views.names or filters.views.ids when you only need specific views, and/or filters.columns.ids when you only need specific columns. Set filters.views.only or filters.columns.only when you want just that section — full views[].settings across many views can be multi-MB. The response includes hierarchytype which indicates if the board is a multi-level board ("multilevel") where items can have nested subitems up to 5 levels deep on the same board. On multi-level boards, subitems share the same columns as parent items and subItemColumns will be null. Call this FIRST whenever you are not already familiar with a board structure (column IDs, column types, column revisions, status labels) — before reading or writing its data, or before any tool that declares this as a required precondition (e.g. getboarditemspage, boardinsights, createitem, createitems, updateitems, changeitemcolumnvalues, updatecolumn, createview, createviewtable, updateview, updateviewtable). Also use the views it returns to resolve a view referenced by name (pass that name in filters.views.names), and as the source of view ids for updateview and updateviewtable. Each column's "settings" field is the raw API value for that existing column, shown so you can read current labels/config — it is NOT the format expected by the columnSettings parameter of createcolumn or updatecolumn. Never copy a column's "settings" object verbatim into columnSettings — use getcolumntypeinfo with fetchMode "schema" to get the correct shape for the column type you are creating or updating.
- **Get board items page** - Get items from a monday.com board: list, filter, sort, search and paginate board items with their column values, groups, subitems and item descriptions.
- **Get column type info** - Retrieves comprehensive information about a specific column type. Use fetchMode "schema" (default) to get the JSON schema definition from the API — to understand structure, validation rules, and available properties for column settings. Call this BEFORE any tool that writes column settings: createcolumn, updatecolumn, and manageobjectschemacolumns. Use fetchMode "guidelines" to get only guidelines.filter and guidelines.aggregation (no schema, no GraphQL round-trip). Call this before building any filter rule that uses comparevalue/operator for that column type — e.g. getboarditemspage, boardinsights, or a view's filters (createview, createviewtable, updateview, updateviewtable) — and before building board insights aggregation counts.
- **Get form** - Get a monday.com form by its form token, including its pages, questions, question ids, settings, and conditional showIfRules. Form tokens can be extracted from the form's url. Given a form url, such as the formToken is the alphanumeric string that appears right after /forms/ and before the ?. In the example, the formToken is abc123def456ghi789. Call this FIRST before any tool that acts on an existing form: createformsubmission (to know the questions and their constraints), formquestionseditor (to resolve question ids and current structure), and updateform (to see the current settings before changing them).
- **Get graphql schema** - Fetch the monday.com GraphQL schema structure including query and mutation definitions. This tool returns available query fields, mutation fields, and a list of GraphQL types in the schema. You can filter results by operation type (read/write) to focus on either queries or mutations.
- **Get meetings content** - Fetch full content (summary, topics, action items, transcript) for meetings you already have ids for. Get those ids from exploremeetings or searchmeetingscontent first; this tool is NOT for discovery or listing. Pass several ids in one call, with the include flags for the content you need (defaults to the summary if none are set). Requested ids that are not returned are listed at the end (not found, not accessible, or no completed recording); a meeting whose content was dropped to keep the response within its size limit says so, and can be requested again on its own. The search param is a narrow case-insensitive substring fallback on title, participant name, or email — NOT topic/keyword search.
- **Get monday dev sprints boards** - Discover monday-dev sprints boards and their associated tasks boards in your account.
- **Get monday knowledge** - Ask a question about monday.com and get an AI-generated answer from the official knowledge base.
- **Get run once trigger entities** - Lists the concrete entities (items, boards, docs, ...) the workflow's trigger can be fired on, so the workflow can be run once on one of them.
- **Get sprint summary** - Get the complete summary and analysis of a sprint.
- **Get sprints metadata** - List the sprints of a monday-dev sprints board with their metadata.
- **Get type details** - Get detailed information about a specific GraphQL type from the monday.com API schema, including its fields, input fields, and enum values. Call this with a known type name to confirm its exact fields, arguments, and enum values before referencing that type in an operation for allmondayapi, allapiread, or allapiwrite, so the fields and arguments you send actually exist.
- **Get updates** - Get updates (comments/posts) from monday.com items or a board. Pass the IDs in objectIds and set objectType: up to 25 item IDs for Item, in one call instead of calling once per item, or one board ID for Board. Filter by date range with fromDate and toDate (both required together, ISO8601 format). By default, Board queries return only board discussion. Set includeItemUpdates to true to also include updates on individual items, and add a date range to keep the response small. Returns update text (bodies over 2000 characters are truncated and flagged with textbodytruncated. To read one in full, call again with only that item's ID and includeFullText), creator info, timestamps, and optionally replies and assets.
- **Get user context** - Fetch current user information, account information, and their relevant items (boards, docs, folders, workspaces, dashboards).
- **Get workflow editor link** - Creates the link that opens a workflow in the monday workflow editor, and saves a short summary of this conversation that the editor's chat shows the user, so they can continue there.
- **Get workflow run once status** - Reports how a run started by runworkflowonce ended: whether it succeeded, and if not, which step failed and why.
- **Invoke process planner** - A reasoning-focused process planner with deep knowledge of monday.com workflow architecture. Given a description of a process, it returns a structured textual plan describing one or more related workflows that implement it.
- **Invoke workflow expert** - Workflow expert for a single workflow. Given a prompt, answers questions about the workflow's structure and configuration, or makes changes to it (create, update, delete steps, and configure step fields).
- **List actions** - Use to list all saved actions for the current user. List all saved actions for the current user.
- **List automations** - List all automations on a specific monday.com board, including their ids, titles, active state, and configuration.
- **List users and teams** - Tool to fetch users and/or teams data.
- **List workspaces** - List all workspaces available to the user, ordered by membership (user's workspaces first). Returns workspaces with their ID, name, and description.
- **Manage agent** - Full lifecycle management for monday platform agents — create, read, update, delete, change state, and run.
- **Manage agent jobs** - Manage jobs on a monday platform agent.
- **Manage agent knowledge** - List, grant, update, or revoke a monday platform agent's access to boards and docs.
- **Manage agent skills** - Manage the full skill lifecycle for monday platform agents — create new skills in the catalog, attach skills to an agent, or detach them.
- **Manage agent tools** - Add integration tools (Gmail, Slack, ...) and built-in capabilities (web search, notetaker, ...) to a monday platform agent.
- **Manage agent triggers** - Legacy flat-trigger management for a monday platform agent. When jobs with instructions are enabled, use manageagentjobs so each trigger belongs to an explicit job.
- **Manage automations** - Activate, deactivate, or delete an existing monday.com automation.
- **Move object** - Move a folder, board, or overview in monday.com. Use position for relative placement based on another object, parentFolderId for folder changes, workspaceId for workspace moves, and accountProductId for account product changes.
- **Read docs** - Get information about monday.com documents. Supports two modes.
- **Run action** - Use to execute a previously saved action by its ID, optionally passing variables. Execute a saved action by ID. Optionally pass variables (injected as environment variables, access via os.environ).
- **Run workflow once** - Runs the workflow once: a single execution, right now, on one real entity, without publishing or activating the workflow. When workflowDraftId is given the draft revision runs; otherwise the published live revision runs.
- **Search** - Use when the user asks to find or look up a monday.com board, item, doc, dashboard, folder, workspace, update, or timeline item by name or keyword. Search within monday.com platform. Supported searchType values: BOARD, DOCUMENTS, FOLDERS, WORKSPACES, UPDATES, ITEMS, TIMELINEITEMS, DASHBOARDS.
- **Search meetings content** - Find where specific words appear inside meeting content and return the matching passages, across many meetings at once. Matches keywords only, not meaning, in discussed topics, the AI summary and action items: names, terms, codenames and numbers work best. Each result shows the meeting's title, date and AI overview, then its matching passages. The overview is a short gist for telling meetings apart: it leaves out most figures, owners, quotes and corrections, which are in the passages and in getmeetingscontent. Transcripts are not searched. Without a query it returns content filtered by date/access. Read a meeting with getmeetingscontent using its id.
- **Show assign** - Use for requests to see or use an interactive assignment interface. [UI COMPONENT] Renders an interactive smart assignment interface visualization that the user can see and interact with. IMPORTANT: This is a UI DISPLAY tool - use it to RENDER visual components for the user to see and interact with. Do NOT use data-fetching tools when the user explicitly asks to "show", "display", "visualize", or "see" something visually. Helps assign tasks to the right people. Assignment suggestions are based on task details (like name) and person details (such as title, availability, etc). Always show as much as data possible, while showing the person details like title etc. If you do not have the data available - use the listusersandteams tool.
- **Show battery** - Use when user asks for: battery view, progress indicator, status distribution bar, completion percentage visualization, or Monday.com style status breakdown. [UI COMPONENT] Renders an interactive battery/progress indicator visualization that the user can see and interact with. IMPORTANT: This is a UI DISPLAY tool - use it to RENDER visual components for the user to see and interact with. Do NOT use data-fetching tools when the user explicitly asks to "show", "display", "visualize", or "see" something visually.
- **Show chart** - Use when user asks for: pie chart, bar chart, line graph, data visualization, or any graphical representation of numbers/statistics. [UI COMPONENT] Renders an interactive chart/graph visualization that the user can see and interact with. IMPORTANT: This is a UI DISPLAY tool - use it to RENDER visual components for the user to see and interact with. Do NOT use data-fetching tools when the user explicitly asks to "show", "display", "visualize", or "see" something visually.
- **Show monday** - Open the full monday.com web app in the ChatGPT sidebar. Opens the full monday.com web app for the current account. Launched from the ChatGPT sidebar.
- **Show table** - Use when user asks to: display a board as table, show items in table format, view data in tabular layout, or see a Monday.com board visually. [UI COMPONENT] Renders an interactive table visualization that the user can see and interact with. IMPORTANT: This is a UI DISPLAY tool - use it to RENDER visual components for the user to see and interact with. Do NOT use data-fetching tools when the user explicitly asks to "show", "display", "visualize", or "see" something visually. When asked to update an item, use the currently selected item ID (get it from the widget state, using tools like "getwidgetstate") for deciding which item to update.
- **Stop workflow run once** - Stops the run that runworkflowonce started, so the remaining steps do not execute.
- **Submit bug or feature request** - Report a bug, submit a feature request, or share feedback about the monday.com product or this integration.
- **Update action** - Use to update fields of an existing saved action, such as its code, name, or variables. Update an existing action. Only pass the fields you want to change.
- **Update column** - Update properties of an existing monday.com column (title, description, settings). [REQUIRED PRECONDITION]: Uses optimistic concurrency control via the revision field — fetch the column id, type, and current revision via getboardschema first (preferred), or getboardinfo if you already have it, then call this tool. If the update fails because the revision is stale, re-fetch and try again. After a successful update, use the new revision returned in the response for any further update to this column, not the one you started with. [REQUIRED PRECONDITION]: If you are changing columnSettings, also call getcolumntypeinfo with fetchMode "schema" for that column type first to learn the valid settings structure. columnSettings is the flat payload for that column type (e.g. {"labels": [...]}) — not getboardinfo's column.settings object copied as-is, and not wrapped again as {"settings": {"labels": [...]}}. To edit existing status or dropdown labels (rename, recolor, or reorder): first call getboardinfo with filters.columns.ids for that column (or filters.columns.only) to read its current settings.labels, where each existing label's id lives. Editing an existing label requires sending its id in that label's entry — omitting it fails validation, since only a brand-new label can omit id. Status labels need the full label shape (id, label, color, index, and so on), not just a renamed string. Never invent an id — reuse the ids from getboardinfo and add new labels without one. Flow: getboardinfo for the revision and current settings.labels with ids, getcolumntypeinfo (schema mode) for the valid shape, then build columnSettings.labels reusing existing ids and adding new labels without id.
- **Update doc** - Update an existing monday.com document. Provide docid (preferred) or objectid, plus an ordered operations array (executed sequentially, stops on first failure).
- **Update folder** - Update an existing folder in monday.com.
- **Update form** - Update a monday.com form. Use the action field to specify the operation. [REQUIRED PRECONDITION]: Call getform first to read the current form state — you need it to resolve the formToken, and for actions that reference existing entities (updateQuestionOrder needs the question ids, deleteTag needs the tag id) or that overwrite existing settings (updateAppearance, updateAccessibility, updateFeatures, updateFormHeader).
- **Update items** - Update column values for up to 40 items in a single call. Each update targets one item by itemId and sets one or more column values on it. Each update is independent - it can target its own board via boardId and set its own column values, so a single call can update many items across multiple boards, apply the same value to many items, or apply different values per item. Each update returns its own itemid and itemurl on success or a raw error message on failure. To link board-relation columns, call linkboarditemsworkflow before using this tool. [REQUIRED PRECONDITION]: Before using this tool, if you are not familiar with the board structure (column IDs, column types, status labels), first use getboardinfo with filters.columns.only to get column metadata without fetching views. This is essential for constructing valid column values.
- **Update view** - Update an existing board view (tab) — change its name, filter rules, or sort order. Provide only the fields you want to change.
- **Update view table** - Update an existing table-type board view — change its name, filters, sort, tags, or table-specific settings including conditional coloring (highlight rows/cells based on column values). Provide only the fields you want to change.
- **Update workspace** - Update an existing workspace in monday.com.
- **Upload file to update** - Attach a file to a monday.com update (item comment). Viktor's own tool, sent with the connection's monday sign-in.
- **Validate workflow** - Validates the current workflow's structure and step configuration. Reports issues such as a missing trigger or action block, a delay/wait-trigger block left as a leaf, an empty loop, unknown blocks, missing required inputs, type mismatches between a variable and the field it's bound to, cross-branch node-results references, invalid variable values, or switch steps whose cases are empty, have no matching route, or are missing entirely.
- **Vibe ask** - Ask a read-only question about an existing Vibe app. Blocks for up to 45s (configurable via timeoutms) awaiting the assistant reply. Status: COMPLETED with the reply, TIMEOUT if the workflow did not finish in time (call vibeget later to retrieve it), or FAILED if the workflow errored or was cancelled. Optional model to pick the LLM for the answer.
- **Vibe collaborators** - Manage collaborators on a Vibe app. action=list returns all current collaborators. action=add grants a user editor access (userid required; only the EDITOR role can be granted). action=remove revokes a user's access (userid required). The app owner cannot be removed — use transferownership instead. An editor may remove themselves to leave the app.
- **Vibe create** - Creates a new Vibe app from a natural-language prompt. Returns immediately with appid and editorlink — the URL of the Vibe builder/chat page for the new app ( the user can open it right away to watch generation in progress. Generation itself runs asynchronously — poll vibeget for status. Optional: workspaceid to create the app in a specific workspace, boardids to connect existing boards (omit to auto-create), viewid to host a dashboard widget, and model to pick the LLM.
- **Vibe delete** - Delete a Vibe app and its associated assets. Destructive.
- **Vibe duplicate** - Duplicate an existing Vibe app into a new app, copying the source app's live version. If workspace_id is omitted, the copy goes to the source app's workspace (or the user's default Vibe workspace). Returns the new app, including its editor_link.
- **Vibe get** - Fetch a Vibe app by id. App metadata is always returned, including editorlink — the URL of the Vibe builder/chat page for this app ( usable as soon as the app row exists. Pass include to add expensive slices: status (refreshes status + adds isbusy, default true), messages (with optional fromdate), code (generated files — the current version unless versionid or versionstatus is given), codeversions.
- **Vibe list** - List Vibe apps owned by the authenticated user. Supports pagination, search, status, and ispublished filters.
- **Vibe publication** - Manage the publication state of a Vibe app on the caller account. action=publish requires the app to be deployed and respects the published-apps license limit. action=unpublish removes the app from the account.
- **Vibe rename** - Rename a Vibe app and return the updated app.
- **Vibe update** - Sends a follow-up message to modify an existing app. Fire-and-forget — returns immediately with usermessageid and editorlink (the Vibe builder/chat URL for this app, Returns APPBUSY (409) if the app is currently generating; poll vibeget first. Optional model to pick the LLM for this build.
- **Workspace info** - This tool returns the boards, docs and folders in a workspace and which folder they are in. It returns up to 100 of each object type, if you receive 100 assume there are additional objects of that type in the workspace.

## Viktor uses Monday.com together with

- [Slack](https://viktor.com/integrations/slack)
- [Gmail](https://viktor.com/integrations/gmail)
- [Google Sheets](https://viktor.com/integrations/google-sheets)
- [HubSpot](https://viktor.com/integrations/hubspot)
- [Salesforce](https://viktor.com/integrations/salesforce)
- [Stripe](https://viktor.com/integrations/stripe)

## More Productivity integrations

- [GitHub](https://viktor.com/integrations/github)
- [Jira & Confluence](https://viktor.com/integrations/jira-confluence)
- [Asana](https://viktor.com/integrations/asana)
- [Linear](https://viktor.com/integrations/linear)
- [Notion](https://viktor.com/integrations/notion)
- [Miro](https://viktor.com/integrations/miro)
- [ServiceM8](https://viktor.com/integrations/servicem8)
- [ClickUp](https://viktor.com/integrations/clickup)

## FAQ

### Does Viktor integrate with Monday.com?

Yes. Monday.com is one of the 9,800+ tools Viktor connects to, as one of Viktor's native, deepest integrations. Once connected, anyone on your team can put Viktor to work in Monday.com from their workspace - no workflow builder, no code.

### How do I connect Monday.com to Viktor?

Ask Viktor in your workspace to connect Monday.com. It's one of Viktor's native integrations, so Viktor handles authorization itself and starts working right away. Setup takes about two minutes, and you can revoke access at any time.

### What can Viktor do in Monday.com?

Viktor can run 106 Monday.com actions, including Search, Get form, and Vibe ask - and chain them with other tools in a single request. In practice that means Viktor helps you plan, assign, and track work on monday.com boards. If a task spans several actions, Viktor plans the sequence itself and reports back when the work is done. You connect with Sign in with monday.com: Viktor uses monday.com's official MCP server, and the sign-in runs through monday.com's own OAuth. Viktor reads and changes boards, items, column values, groups, updates and docs, runs GraphQL queries and mutations through monday's API tools, and can attach a file to an update. Changes wait for your approval when your workspace asks for it. monday.com is a trademark of monday.com Ltd.; Viktor is not affiliated with, endorsed by, or sponsored by monday.com.

### Do I need to build workflows for Monday.com?

No. Viktor isn't a workflow builder - there are no triggers to map and nothing to maintain. You ask for the outcome in plain English in your workspace, and Viktor decides which Monday.com actions to take, runs them, and reports back.

### Is my Monday.com data secure with Viktor?

Yes. Viktor connects to Monday.com natively, runs in an isolated environment per team, and never trains models on your data. Sensitive actions wait for your approval, and you can revoke access at any time. Viktor is SOC 2 Type 1 compliant, with Type 2 and ISO 27001 in progress.

### How much does the Monday.com integration cost?

Nothing extra - every integration, including Monday.com, is available on every plan. You can start free with up to $100 in credits, no credit card required; the Team plan is $100 a month.

### Can Viktor use Monday.com together with my other tools?

Yes - that's the point. Viktor connects to 9,800+ tools and works across them in a single run: he can pull data from Monday.com, cross-reference it with another tool - for example Slack or Gmail, and deliver the finished result in your workspace.

## Get started

Viktor is free to start - up to $100 in credits, no credit card required. All 9,800+ integrations are included on every plan. Sign up at https://viktor.com or browse all integrations at https://viktor.com/integrations.