> For the complete documentation index, see [llms.txt](https://docs.coupler.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coupler.io/destinations/categories/dashboards/monday_com/common-issues.md).

# Common Issues

## Connection issues

<details>

<summary>"Invalid scope param" error when connecting monday.com</summary>

This is the most frequently reported issue with the monday.com destination. The error `{"error":"invalid_scope","error_description":"Invalid scope param"}` appears during the OAuth authorization step.

**Most likely cause:** Third-party cookies are blocked in your browser.

**Fix 1 — Allow third-party cookies:**

1. Open your browser's cookie settings and allow third-party cookies.
2. Reload the Coupler.io page and retry the connection.

**Fix 2 — Use two tabs (if Fix 1 doesn't help):**

1. Open two browser tabs.
2. Log in to Coupler.io in one tab and monday.com in the other.
3. With both sessions active, retry installing and authorizing the Coupler.io app from within monday.com.

**Fix 3 — Try incognito mode:** Open Coupler.io in an incognito/private window, where cookie restrictions are often different, and attempt the connection again.

{% hint style="warning" %}
If none of the above resolves the issue, contact Coupler.io support and include a screenshot of the exact error message. The scope issue can occasionally be caused by a configuration problem on the platform side that requires investigation.
{% endhint %}

</details>

<details>

<summary>Coupler.io app not appearing during monday.com authorization</summary>

If the Coupler.io authorization prompt doesn't appear or the connection silently fails, the Coupler.io app may not be installed in your monday.com account.

**Fix:** Go to the monday.com app marketplace and install the Coupler.io app before attempting to connect from Coupler.io. Authorization will not work without this step completed first.

</details>

## Data issues

<details>

<summary>New columns are created on every Append run instead of reusing existing ones</summary>

This is expected behavior for Append mode. On the very first run, Coupler.io creates the board columns. On subsequent runs in Append mode, new rows are added to those existing columns correctly.

However, if your source schema changes between runs (e.g., a new field appears or a column is renamed), Coupler.io will create additional columns for the new fields rather than overwriting old ones.

**Fix:** Keep your source column names consistent across runs. If you need to restructure your data, consider switching to Replace mode, which rebuilds the board from scratch on each run.

</details>

<details>

<summary>Data appears in the wrong board or workspace</summary>

This can happen if you selected the wrong workspace or board during setup, or if a new board was created unintentionally.

**Fix:** Open your data flow, go to the destination settings, and verify the workspace and board selected. Update them if needed and run the data flow again. If Replace mode is active, the correct board will be populated on the next run.

</details>

## Permission errors

<details>

<summary>Authorization fails with a permissions error in monday.com</summary>

If your monday.com account doesn't have sufficient permissions to install apps or connect third-party integrations, the OAuth flow will fail.

{% hint style="danger" %}
Only monday.com account admins can install apps from the marketplace. If you're not an admin, ask your monday.com administrator to install the Coupler.io app on your behalf before you attempt to connect.
{% endhint %}

</details>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.coupler.io/destinations/categories/dashboards/monday_com/common-issues.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.