monday.com app guide
Last updated on June 27, 2026
OOMOL lets you connect monday.com once, then make authorized monday.com tools available to supported AI agents, reusable Skills, and workflows. This guide explains how to add the monday.com app, what permissions OOMOL uses, what agents can do with monday.com, how to troubleshoot common issues, and how to remove the app.
OOMOL requires users to sign in before connecting external accounts. To install the monday.com app, sign in to OOMOL, open Connections, search for monday.com, and choose Connect to start the monday.com OAuth authorization flow.
Prerequisites
- An OOMOL account.
- A monday.com account that you are allowed to authorize for third-party apps.
- Access to the OOMOL Console at https://console.oomol.com/.
- Permission in monday.com to authorize apps with the requested monday.com scopes.
- If your monday.com account is managed by an organization, your monday.com administrator may need to approve the OOMOL app before you can authorize it.
- Department administration tools require a monday.com Enterprise account with departments enabled. Depending on the action, the connected user must have the department administration rights required by monday.com, such as department owner access for the relevant department or account-level permission to manage users.
Adding the app
- Sign in to the OOMOL Console.
- Open Connectables or go directly to Connections.
- Search for monday.com.
- Select monday.com, then choose Connect.
- OOMOL redirects you to monday.com. Sign in to monday.com if prompted.
- Review the monday.com authorization screen, including the requested permissions.
- Select the account or workspace you want to connect if monday.com asks you to choose one.
- Select Authorize, Allow, or the equivalent authorization action shown by monday.com.
- After monday.com redirects you back to OOMOL, confirm that monday.com appears as connected in your OOMOL connections.
If any step fails, see Troubleshooting.
After authorization, OOMOL stores the connection needed to call monday.com tools on your behalf. You can then use monday.com tools from OOMOL-supported agents, reusable Skills, and workflows.
What OOMOL does in monday.com
OOMOL makes monday.com actions available after you connect an account. Depending on the action you run, agents can read account context, boards, items, updates, docs, assets, workspaces, users, teams, and departments. Agents can also write back to monday.com when a user asks them to create or update board data, post updates, create or update docs, organize workspaces, or manage departments.
OOMOL does not start using monday.com on its own after installation. A monday.com tool runs when an authorized user, reusable Skill, supported agent action, or approved OOMOL tool call provides the required input.
Typical uses include:
- Board automation: read board data, create or update items, and post results back to monday.com.
- Project updates and reporting: summarize item updates, generate status reports, and write reports into monday.com docs or item updates.
- File and document tasks: read monday.com assets, extract information from files, and create or update monday.com docs.
- Team routing: use monday.com users, teams, and departments to route work to the right owner or group.
- Workspace and department administration: help authorized users organize workspaces and manage monday.com departments through explicit administration actions.
After installation
After monday.com redirects you back to OOMOL, check that the monday.com connection is marked as connected in the OOMOL Console. From there, you can:
- Configure
oo-cliif you want connected monday.com tools inside a supported AI agent environment. - Use demo boards, items, updates, docs, assets, and workspaces to test read and write actions.
- Use demo departments only if your monday.com account supports department administration and your connected user has the department administration rights required by monday.com, such as department owner access for the relevant department or account-level permission to manage users.
Usage
monday.com tools are available only after you connect a monday.com account. The exact tool list shown in OOMOL may change as the connector is updated, but the current monday.com connector includes tools for reading the connected user, account, boards, workspaces, users, teams, updates, docs, assets, and departments, plus tools for writing boards, workspaces, updates, docs, and departments when the required scopes are granted.
Use monday.com tools with oo-cli
To make connected monday.com tools available in a supported AI agent environment, install and configure oo-cli after you sign in to OOMOL.
- Sign in to the OOMOL Console.
- Open the oo-cli installation page.
- Follow the instructions on that page. The page provides a one-click copy prompt for installing and configuring
oo-cliin a supported AI agent environment. - After
oo-cliis configured and monday.com is connected in OOMOL, ask the agent to use the connected monday.com tools with demo boards, docs, updates, and departments.
The exact agent prompt can vary by environment. For example, you can ask the agent to confirm the connected account, summarize a demo board, create a test item, post a status update, generate a monday.com doc, list departments, or create a demo department if your account supports department administration.
Permissions used
OOMOL uses monday.com permissions to let an authorized monday.com user connect monday.com as an App in OOMOL, then make approved monday.com tools available to agents, reusable Skills, and workflows.
The exact scopes shown during monday.com OAuth are the source of truth for your installation. The current monday.com connector may request these scopes depending on the tools enabled for your account:
| monday.com scope | Used by | Why OOMOL uses it |
|---|---|---|
me:read | Get Current User | Identify the monday.com user who authorized the connection and display the connected account in OOMOL. |
account:read | Account read tools | Read basic account information so users and agents can confirm which monday.com account is connected before running tools. This helps when a user has access to more than one monday.com account. |
boards:read | Board read tools | Let agents read boards, items, columns, groups, and board structure needed for user requests or workflows. |
boards:write | Board write tools | Let agents create or update board data when a user, Skill, or workflow asks OOMOL to write results back to monday.com. |
workspaces:read | Workspace read tools | Let agents find the right workspace, board, or folder before reading, organizing, or writing monday.com data. |
workspaces:write | Workspace administration tools | Let agents create, update, or organize workspaces when an authorized user explicitly asks for workspace administration. |
users:read | User read tools | Let agents resolve monday.com users for assignment, routing, mentions, ownership, and audit context. |
teams:read | Team read tools | Let agents understand monday.com team membership and route work to the right team. |
updates:read | Update read tools | Let agents read item updates for summaries, reports, follow-up tasks, and context gathering. |
updates:write | Update write tools | Let agents post comments, summaries, workflow results, or follow-up notes to item updates. |
docs:read | Doc read tools | Let agents read monday.com docs that a user selects or that a workflow uses as input. |
docs:write | Doc write tools | Let agents create or update monday.com docs, such as reports, briefs, generated documentation, and tool outputs. |
assets:read | Asset read tools | Let agents read files and asset metadata attached in monday.com when those assets are used as workflow input. |
departments:read | Department read tools | Let agents list departments and understand department ownership, membership, or routing context. |
departments:write | Department administration tools | Let authorized users manage monday.com departments through explicit agent actions and administration tasks. |
If a monday.com administrator does not grant a required permission, the monday.com connection can fail, or tools that depend on that permission may be unavailable until the permission is granted. Department write actions also require the department administration rights required by monday.com, such as department owner access for the relevant department or account-level permission to manage users.
Supported monday.com tools
| Tool area | Supported function | Typical use case | Prerequisites |
|---|---|---|---|
| Current user | Read the authorized monday.com user’s profile information. | Confirm which monday.com user is connected before an agent or workflow uses monday.com. | monday.com is connected in OOMOL and the connected account is active. |
| Account | Read basic information about the connected monday.com account. | Confirm the account context before running a workflow, especially when a user belongs to more than one monday.com account. | monday.com is connected in OOMOL and the connected account is active. |
| Boards | Read and write board data that the connected account can access. | Summarize a board, create or update items, copy task results into columns, or prepare a project report. | The connected account has access to the target board and the workflow has valid board or item identifiers. |
| Updates | Read and post item updates. | Summarize recent activity, extract action items, or post a generated status update to an item. | The connected account can access the target item or board, and the workflow has the target update or item context. |
| Docs | Read, create, or update monday.com docs. | Turn board activity into a project report, meeting note, brief, or reusable documentation. | The connected account can access the target doc or location, and the workflow has the required doc content. |
| Assets | Read files and asset metadata available to the connected account. | Use attachments as workflow input for extraction, summarization, reporting, or document generation. | The connected account can access the target asset. |
| Users and teams | Read monday.com users and teams. | Resolve assignees, owners, reviewers, mentions, team routing, and escalation paths. | The connected account can access the relevant user or team information. |
| Workspaces | Read, create, update, or organize workspaces. | Set up a project area, organize boards or folders, or support workspace administration tasks. | The connected account has the monday.com permissions needed for the workspace action. |
| Departments | Read, create, update, delete, assign, or clear department information. | Maintain department structure and user department assignments through explicit administration tasks. | The connected account is a monday.com Enterprise account with departments enabled, and the connected user has the department administration rights required by monday.com, such as department owner access for the relevant department or account-level permission to manage users. |
Read account context, boards, updates, docs, assets, users, teams, and departments
Use case: let an agent gather monday.com context before summarizing work, generating a report, preparing a follow-up, routing a task, or taking a requested action.
Prerequisites:
- monday.com is connected in OOMOL.
- The connected monday.com account has access to the requested account information, board, item, update, doc, asset, user, team, workspace, or department.
- The agent, Skill, or workflow has the required identifier, search input, or selected monday.com object.
What the tools do:
- Read monday.com data available to the connected account and granted OAuth scopes.
- Return monday.com data needed for the requested agent action or workflow.
- Do not modify monday.com during read-only actions.
Write boards, updates, docs, and workspaces
Use case: let an agent write the result of a user request or workflow back to monday.com, such as creating or updating board data, posting a status update, generating a doc, or organizing a workspace.
Prerequisites:
- monday.com is connected in OOMOL.
- The connected monday.com account has permission to modify the target object.
- The user, Skill, or workflow provides the target and the content to write.
- The values are valid for monday.com, such as valid board IDs, item IDs, doc IDs, column values, workspace IDs, and required fields.
What the tools do:
- Create or update supported monday.com objects based on the provided inputs.
- Return the result made available by monday.com after the action completes.
- Do not write to unrelated monday.com objects unless the active workflow provides those targets.
Manage departments
Use case: let an authorized user manage monday.com departments through explicit department administration actions, such as maintaining department structure or aligning monday.com departments with an internal organization workflow.
Department administration tools use departments:write and include:
Each account member can belong to only one department at a time. Assigning a user to a department replaces that user’s existing department assignment, and clearing a user’s department removes the user’s current department assignment.
| Tool | Supported function | Required input | Result |
|---|---|---|---|
create_department | Create a department. | data with name; reserved_seats is optional. | Returns the created department, including id, name, reserved_seats, assigned_seats, members, and owners. |
update_department | Update an existing department. | department_id and data with at least one of name or reserved_seats. | Returns the updated department. |
delete_department | Delete a department. | department_id. | Returns the deleted department information made available by monday.com. |
assign_department_members | Assign users to one department, replacing any existing department assignment for those users. | department_id and user_ids. | Returns successfulUsers and failedUsers from monday.com. |
clear_users_department | Clear users’ current single department assignment. | user_ids. | Returns clearedUsers. |
Prerequisites:
- monday.com is connected in OOMOL.
- The connected monday.com account is on an Enterprise plan with departments enabled.
- The connected monday.com user has the department administration rights required by monday.com, such as department owner access for the relevant department or account-level permission to manage users.
- The user, Skill, or workflow provides the required department ID, user IDs, and update data.
What the tools do:
- Run only when a user, Skill, agent action, or workflow explicitly requests department administration.
- Create, update, delete, assign, or clear department data based on the provided inputs.
- Replace a user’s current department assignment when assigning that user to a new department.
- Return the monday.com result, including successful and failed user assignment results when monday.com provides them.
delete_department and clear_users_department can affect organization-level structure and user assignments. Review the target department and user IDs before running these actions, and use demo departments when testing.
Testing the app
You can test the monday.com app with an account where you are allowed to authorize apps. Use demo boards, demo docs, demo updates, demo assets, and demo departments so you can safely test read and write actions.
Customer onboarding demo flow
This flow creates its own demo item and then reuses the returned IDs. It does not depend on an existing item, doc, or asset with a specific name.
Before you start:
- Choose a demo board where the connected monday.com account can create items.
- Prepare a small demo file, such as
acme-demo-requirements.txt. - Use only demo data. Do not use real customer, employee, project, or confidential content.
-
Confirm the connected monday.com context and find the demo board:
Use Monday to confirm the connected user and account, then list available workspaces and boards. Keep the output concise and include ids. -
Create a demo item in the target board. Replace
<BOARD_ID>with the board ID returned in the previous step:Use Monday to create a new item in board ID <BOARD_ID> named "Customer onboarding - Acme Demo". Then post an update on the new item explaining that it tracks the demo customer's onboarding work. Return the new item id and update id. Keep the output concise. -
Open the newly created item in monday.com and upload the demo file to the item’s Files tab. Confirm that the file appears in monday.com before continuing.
-
Read the demo item, updates, and attached assets. Replace
<NEW_ITEM_ID>with the item ID returned when the item was created:Use Monday to read item ID <NEW_ITEM_ID>, including item details, recent updates, and attached assets. Summarize the item status, updates, and asset metadata such as file name, asset id, file type, and file size. Keep the output concise. -
Create a demo doc and read it back. Replace
<WORKSPACE_ID>with the workspace ID returned in the first step:Use Monday to create a Monday doc named "Acme Demo onboarding status report - video demo" in workspace ID <WORKSPACE_ID>. After creating it, read the newly created doc by its returned id and confirm its id and title. Do not add body content to the doc. Keep the output concise. -
Post a status report back to the demo item:
Use Monday to post an update on item ID <NEW_ITEM_ID> with a concise status report based on the item updates and attached asset metadata. Keep the output concise.
This flow exercises the core connector behavior used by agents: confirming the account context, reading boards and item context, reading updates and assets, creating docs, and writing updates back to monday.com. Department and workspace administration can be tested separately with demo data when those admin tools are enabled for the connected account.
Sample test prompts
- Get the current connected monday.com user and account.
- List monday.com boards visible to the connected account.
- Summarize a demo board and post the summary as an item update.
- Create a demo item in a test board.
- Read recent updates from a demo item.
- Create a monday.com doc from a demo project summary.
- Read a demo asset attached to a test item.
- Create a demo workspace named
OOMOL Demo Workspace, then rename it toOOMOL Demo Workspace Archive. - List monday.com users and teams visible to the connected account.
- List monday.com departments.
- Create a demo department named
OOMOL Demo Department. - Update the demo department’s reserved seats.
- Assign a test user to the demo department, replacing any current department assignment for that user.
- Clear the test user’s current department assignment.
- Delete the demo department.
Use only demo data during testing. Do not use real customer, employee, project, or confidential monday.com content in test prompts.
Troubleshooting
I cannot add the monday.com app
- Make sure you are signed in to the correct OOMOL account.
- Make sure you are signing in to the monday.com account you want to connect.
- Confirm that the monday.com account allows third-party apps and the requested OAuth scopes.
- If your monday.com account belongs to an organization, ask a monday.com administrator whether the OOMOL app requires approval.
- Try disconnecting any failed or partial monday.com connection in OOMOL, then connect again.
- If the issue continues, contact OOMOL support and include the OOMOL account email, the monday.com account or organization if available, the time of the attempt, and any error message or screenshot.
A monday.com tool cannot find a board, item, update, doc, asset, workspace, user, team, or department
- Confirm that the connected monday.com account has access to the requested object.
- Confirm that the workflow is using the correct monday.com ID, search input, board, item, doc, asset, workspace, user, team, or department.
- Check whether the object exists in the monday.com account connected to OOMOL.
- If you recently changed monday.com permissions or app scopes, reconnect monday.com in OOMOL so the authorization state is refreshed.
A monday.com tool cannot write data
- Confirm that the connected monday.com account can make the same change directly in monday.com.
- Confirm that the tool call includes all required inputs.
- Check that provided values are valid for monday.com, such as column values, item IDs, board IDs, workspace IDs, doc content, department IDs, and user IDs.
- If monday.com returns a policy or permission error, ask a monday.com administrator to review the connected account’s permissions and app authorization.
A department action fails
- Confirm that the connected monday.com account is on an Enterprise plan and has departments enabled.
- Confirm that the connected user has the department administration rights required by monday.com, such as department owner access for the relevant department or account-level permission to manage users.
- Confirm that the department ID and user IDs are valid.
- Remember that each user can belong to only one department. Assigning a user to a department replaces any existing department assignment.
- For
assign_department_members, reviewsuccessfulUsersandfailedUsersto see which users monday.com accepted or rejected. - For
update_department, include at least one editable field:nameorreserved_seats. - For
delete_departmentandclear_users_department, confirm that you are targeting demo or intended production data.
Removing the app
You can remove the monday.com app from either OOMOL or monday.com. We recommend removing it from both places if you no longer want OOMOL to access monday.com.
Remove monday.com from OOMOL
- Sign in to the OOMOL Console.
- Open Connections.
- Find monday.com in your connected apps.
- Open the monday.com connection details.
- Choose Disconnect, Remove, or the equivalent removal action shown in OOMOL.
- Confirm the removal.
Remove OOMOL from monday.com
- Sign in to monday.com.
- Open monday.com app management, admin, or connected apps settings for your account.
- Find OOMOL.
- Open the app details.
- Choose the action to uninstall, disconnect, or remove the app.
- Confirm the removal.
If you cannot remove apps in monday.com, ask a monday.com administrator to remove the app.
What happens after removal
- OOMOL can no longer use monday.com tools for your account after the monday.com connection is removed or de-authorized.
- Workflows, agents, Skills, or other tasks that depend on monday.com may fail until you reconnect monday.com.
- Existing monday.com boards, items, updates, docs, assets, workspaces, departments, and assignments created or updated before removal remain in monday.com unless you change or delete them in monday.com.
- Removing the app does not delete your OOMOL account.
Data handling
OOMOL accesses monday.com data only after a monday.com user authorizes the app and a user, Skill, approved agent action, or workflow requires monday.com. OOMOL uses monday.com data only to provide the monday.com tools requested through OOMOL-supported agents, reusable Skills, and workflows.
- monday.com OAuth tokens are stored encrypted.
- monday.com OAuth tokens are not exposed to AI agents, prompts, project files, or end users.
- OOMOL may process monday.com account, user, team, department, workspace, board, item, update, doc, and asset metadata when a monday.com tool is called.
- monday.com data may be stored only as needed in user-visible tool results, usage records, execution history, or operational records.
- Stored data is encrypted at rest and transmitted over TLS/SSL.
- OOMOL does not sell your monday.com data.
- OOMOL does not use monday.com data for advertising.
- OOMOL does not use private customer content to train AI models.
- OOMOL does not continuously sync or replicate monday.com account data in the background as part of this connector. monday.com data is accessed when an authorized user, Skill, approved agent action, or workflow calls a monday.com tool.
- When you remove or de-authorize the monday.com app, OOMOL stops using the revoked monday.com authorization. OOMOL deletes or invalidates the stored monday.com authorization tokens according to its normal connection removal process.
- Some logs, support records, security records, or billing-related records may be retained as described in the Privacy Policy.
FAQ
Do I need a paid monday.com account?
Most OOMOL monday.com tools require a monday.com account that can authorize the requested scopes. Some monday.com features, app approval controls, department administration tools, workspace permissions, or account policies may depend on your monday.com plan and organization settings.
Can I connect more than one monday.com account?
Use the OOMOL Console to check the current connection options available to your account or workspace. If you need help with multiple monday.com accounts, contact support.
Can an agent use monday.com automatically after I connect it?
Connecting monday.com makes monday.com tools available in OOMOL, but tool use still depends on the agent, workflow, Skill, permissions, and approvals you choose. Account-based services still require your authorization.
Does OOMOL continuously sync monday.com data?
No. OOMOL does not continuously sync or replicate monday.com data in the background as part of this connector. monday.com data is accessed when an authorized user, Skill, approved agent action, or workflow calls a monday.com tool.
Can OOMOL delete monday.com data?
The current monday.com connector includes delete_department for explicit department administration actions. OOMOL does not delete monday.com data unless a user, Skill, approved agent action, or workflow uses a supported delete tool with the required target information.
Does department administration work on every monday.com plan?
No. monday.com department APIs are available only for Enterprise accounts that support departments. Write actions also require the department administration rights required by monday.com, such as department owner access for the relevant department or account-level permission to manage users.
Contact support
If you need help adding, using, testing, or removing the monday.com app, contact OOMOL support:
- Email: support@oomol.com
- Support page: https://oomol.com/en/support/
Please include your OOMOL account email, the connected monday.com account or organization if relevant, the action you were trying to perform, and any error message or screenshot.