Monday.com support

Last updated date:

Connect, reconnect, and troubleshoot Monday.com without sharing credentials or customer content through support channels.

1. Before you start

  • Create a personal API token from a dedicated Monday.com admin or service account.
  • List workspace or board IDs when the connection should not ingest every board visible to the token.
  • Use the displayed API version and review Monday.com's complexity and request limits.
  • Do not send Monday.com credentials, customer content, personal information, or private record data by email or through an ordinary support ticket.
Monday.com authenticationMonday.com's API authentication guidance.

2. Connect Monday.com

  1. In Seedling, open Connections and choose Monday.com.
  2. Connect from workspace scope as a current Seedling workspace administrator.
  3. Enter the API token, optional account label, workspace and board IDs, and pinned API version.
  4. Seedling verifies the token against the intended account and uses cursor-based items_page traversal for each selected board.
  5. Allow the first Monday.com synchronization to finish, then verify the expected resource population and member access policy.

3. Authorization and connection problems

Monday.com API token rejected
Confirm the monday.com api token is active, was entered without surrounding whitespace, and belongs to the intended Monday.com account and environment.
Missing permission or resource
Restore the exact read permission or provider-side resource access described in this guide. Seedling does not substitute a broader credential or silently treat a forbidden Monday.com population as empty.
Wrong account or scope
Disconnect before retrying with the intended Monday.com identity, account, and Seedling connection scope. Seedling does not infer account ownership from a display name or email address.

4. Missing or delayed data

  1. Confirm the board belongs to the selected workspace or board allowlist and is visible to the token owner.
  2. Check private-board membership, archive/deletion state, and the boards:read or updates:read permission.
  3. Allow complexity-limit and request-limit retries to complete before treating data as absent.
  4. Allow incremental synchronization and provider retry handling to complete. A temporary provider failure does not delete previously synchronized data.
  5. If the issue remains, contact support@tryseedling.ai with the Seedling workspace, safe timestamps, and non-sensitive provider record identifiers. Do not include credentials or record contents.

5. Rotate or replace access

Never use email or an ordinary support ticket to transfer the old or replacement credential.

  1. Create replacement monday.com api token for the same Monday.com account with the same or narrower released permissions.
  2. Replace the credential on the exact Seedling connection and repeat identity, scope, and capability verification.
  3. After Seedling confirms the replacement, revoke the old monday.com api token in Monday.com.