Connect monday.com
Connect monday.com with a personal API token, see which boards and items Gurusup reads, how changes arrive, and how to bring in older items.
Admins only. Gurusup joins each item with what was said in Slack and meetings about it. It only reads monday.com: the only things it creates there are its own webhooks, which tell it when an item changes.
At a glance
| Topic | Details |
|---|---|
| Who can connect | Admins |
| What you need | A monday.com personal API token |
| What Gurusup reads | Public boards in open workspaces that the token's owner can see, and their items |
| How changes arrive | Within minutes through webhooks, plus a check every 6 hours |
| Past content | Import history, from last week to last year |
| Knowledge access | Default access, Restricted or Private. See Who can read it. |
Before you start
- You are an admin in Gurusup.
- You have a monday.com personal API token. In monday.com, click your profile picture, then Developers, then API token > Show.
- Gurusup reads the boards the token's owner can see, and of those only public boards in open workspaces. A token from someone who sees few boards brings in few boards.
- One monday.com account takes one connection.
Connect monday.com
Open the monday.com connector
In the sidebar, open Sources, then Catalog, find monday.com (use Search sources if you need to) and click Connect on its row. Its page opens. Next to Organization accounts, click Connect for the organization. The dialog Connect monday.com for the organization opens.
Create the token
Under the Personal access token field, the hint reads "In monday, open your avatar → Developers → My access tokens." and Show steps adds "Create a personal API token. Gurusup reads the boards this person can see." monday.com now labels that page API token. Copy the token.
Paste the token
Paste it in Personal access token. Gurusup says "Reading the boards this token reaches in monday…" and lists them under Boards Gurusup will read in with your monday.com account name. A line says how many boards stay out, for example "3 private or shareable boards stay out." If monday.com does not list the boards within 10 seconds, or does not answer, the list is replaced by "Counting is taking too long right now, usually because the account is large. You can still connect." and Connect stays available.
Choose who can read it
Under Who can read it, Access mode starts as Default access. Choose Restricted or Private to limit the source to the people you pick.
Connect
Click Connect (it stays off until Gurusup has checked the token). A message says "monday.com connected." and the connection appears under Organization accounts with a Connected badge.
What Gurusup reads
Gurusup creates one document per board and one per item.
| Document | What it holds |
|---|---|
| A board | Its name, workspace, owners and description, its groups, and its columns with their type |
| An item | Its name, board and group, the value of each field, its active subitems with their fields, and its comments with their replies, each with who wrote it and when |
Changes to a subitem refresh the item it belongs to. Archived subitems are left out.
What Gurusup does not read
| Left out | Why |
|---|---|
| Private and shareable boards | Gurusup only reads public boards. |
| Boards in closed workspaces | Only boards in open workspaces, or with no workspace, come in. |
| monday Docs and anything that is not a board | Gurusup only reads boards. |
| Archived and deleted boards | Only active boards are read. |
| Boards the token's owner cannot see | Gurusup sees what that person sees. |
How changes arrive
- Gurusup starts from now. Items that change after you connect come in. Items that do not change stay out until you import them.
- Within minutes. Right after you connect, Gurusup adds its own webhooks to each board it reads. monday.com then tells Gurusup when an item is created, renamed, archived or deleted, when a field changes, and when someone posts a comment.
- Every 6 hours. Gurusup goes over your boards and finds new boards, boards that stopped being public, and edited or deleted comments, which monday.com does not report on its own. A board or item it finds this way comes in only if it changed after you connected or since the last pass, never just because it exists.
- Withdrawn content. If a board becomes private, is archived or moves to a closed workspace, Gurusup withdraws it and its items at the next check. Archiving or deleting an item withdraws it too. What Gurusup learned only from them leaves; anything other sources also back stays.
- monday.com's daily API limit. If your account reaches it, Gurusup stops reading until midnight UTC and then picks up where it left off.
Import past work
Open Import history
On Sources, open the monday.com page. Under History, click Import history.
Pick how far back
Pick Last week, Last month, Last 3 months, Last 6 months or Last year. Gurusup counts the items changed in that window, up to 500 (shown as "500+ items" past that), and shows what the import would use out of what you have left this month. If counting takes more than 10 seconds, the dialog says "Counting is taking too long right now, usually because the account is large. You can still import." without figures, and Import stays available.
Import
Click Import. It runs in the background. See How connectors keep Gurusup in sync for the rest of the import flow.
Who can read it
monday.com is one source.
| Knowledge access | Who reads it in Brain |
|---|---|
| Default access | Everyone, according to what they are already allowed to see: admins every category, members and agent accounts the categories an admin granted them. |
| Restricted | Only the people you pick. Administrators are not included unless you pick them. |
| Private | Only you. Administrators are not included. |
You can change it later under Knowledge access on the monday.com page, and it saves as soon as you change it; set it before you click Connect so it applies before Gurusup reads anything. See Restrict a source to specific people.
Check that it worked
- On Sources, a monday.com row is there.
- Change an item on a board Gurusup reads, for example its status.
- Open Ingest and pick the monday.com source in the source filter. The item moves from Queued to Learning to Learned. See Follow ingestion.
Reconnect
Open the monday.com page from Sources. Under Organization accounts, the account shows its status and when it last synced. The page does not list the boards Gurusup reads; you see them in the Connect monday.com for the organization dialog before you connect, and again when you reconnect.
To swap the token, click Reconnect on the account's row, paste a new one from the same monday.com account and click Reconnect again. Gurusup keeps the source, its access settings and what it learned, and replaces its webhooks with ones made with the new token.
If monday.com stops accepting the token, for example because it was regenerated, the status reads Needs reconnect. Click Reconnect on the account's row and paste a new token. Until you reconnect, Gurusup reads no changes.
Disconnect
On Sources, open the monday.com page. Under Danger zone, open the menu on Disconnect and choose Disconnect. A dialog titled "Disconnect [name]?" says "Gurusup stops reading from monday.com. What it already learned stays." Click Disconnect again to confirm, or Cancel. Gurusup deletes the webhooks it created on your boards and forgets the token, but does not revoke it in monday.com; see Remove, disconnect and what stays.
monday.com has no separate revoke for a personal token. If you no longer want it to work, regenerate it in monday.com under Developers > API token > Regenerate, which invalidates the old one at once. Anything else that uses that token needs the new one.
If it does not work
When Connect fails, the message starts with "Could not connect monday.com."
| Message | What to do |
|---|---|
| "monday no longer accepts this connection's token. Reconnect monday with a new personal access token." | monday.com refused the token. When connecting for the first time, check you copied the whole token. On a connected source, create a new token and click Reconnect. |
| "monday didn't accept this token. Create a new one under your avatar → Developers → My access tokens and paste it here." | Create a new token and paste it. |
| "This token can't read the monday boards. Use a token from a member who can open them." | Use a token from someone who can open your boards. |
| "This token belongs to a different monday account. Use a token from the account already connected." | Paste a token from the connected account. To switch accounts, disconnect and connect again. |
| "monday's daily API limit was reached; Gurusup resumes at 00:00 UTC." | Nothing. Gurusup picks up again after midnight UTC. |
| "No public boards in open workspaces yet" | The token's owner sees no public board in an open workspace. Make the boards public, or use a token from someone who sees them. |
| "We couldn't read monday because of a problem on our side. Your saved content is safe. We've recorded the problem; reading resumes when it is resolved. You can contact support for help." | Contact support if it lasts. |
| "Gurusup couldn't read monday. Your saved content is safe. Contact support for help." | Contact support. |
| "Ingestion is paused for this organization. Ask your organization admin to resume ingestion before adding content." or "Demo Mode prevents changing external sources. Ask your organization admin to turn off Demo Mode to continue." | Connecting, reconnecting and changing what a source brings in are off, and gurusup ignores monday.com changes. Disconnect still works while ingestion is paused, but not in Demo Mode. See Connectors overview. |
Nothing coming in and no message? See Connector troubleshooting.