> 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/faq.md).

# FAQ

<details>

<summary>Do I need to install anything in monday.com before connecting?</summary>

Yes. You must install the Coupler.io app from the monday.com marketplace before you can authorize the connection in Coupler.io. Attempting to connect without this step is the most common reason the OAuth flow fails.

</details>

<details>

<summary>What's the difference between Replace and Append mode for monday.com?</summary>

**Replace** wipes all previously imported data from the board and replaces it with the latest data from your source. Use this when you only care about current values — for example, live campaign metrics.

**Append** adds new rows below the existing ones on each run. Use this when you want to build a historical record — for example, logging daily performance snapshots over time.

</details>

<details>

<summary>Can I send data from multiple sources into a single monday.com board?</summary>

Yes. Coupler.io supports multiple sources in a single data flow. You can use the **Join** or **Append** transformation to combine data from different sources—for instance, merging Google Ads and Facebook Ads data—and send the unified result to a single monday.com board.

</details>

<details>

<summary>Can Coupler.io create a new monday.com board automatically?</summary>

Yes. During destination setup, instead of selecting an existing workspace and board, you can type a new name, and Coupler.io will create the board for you on the first run.

</details>

<details>

<summary>Why do I keep getting an "invalid scope param" error?</summary>

This error is almost always caused by third-party cookies being blocked in your browser. Try enabling third-party cookies in your browser settings, or attempt the connection in an incognito window with both your Coupler.io and monday.com sessions active. See the Common Issues article for a full step-by-step fix.

{% hint style="info" %}
For detailed troubleshooting steps, refer to the [Common Issues](/destinations/categories/dashboards/monday_com/common-issues.md) article for this destination.
{% endhint %}

</details>

<details>

<summary>Can I share the monday.com connection with my teammates?</summary>

Yes. When connecting your monday.com account, you'll see an optional toggle to share the connection with your team. Enabling this lets other team members in your Coupler.io workspace use the same monday.com authorization without each person needing to authenticate separately.

</details>

<details>

<summary>How often can Coupler.io update my monday.com board?</summary>

Once your data flow has completed a successful manual run, you can set up an automatic schedule. You can configure the interval, specific days of the week, time of day, and timezone to match your reporting cadence.

</details>

<details>

<summary>What data sources can I send to monday.com?</summary>

Any source that Coupler.io supports can be sent to monday.com — including Facebook Ads, Google Ads, Google Sheets, LinkedIn, and many others. The monday.com destination works the same way regardless of which source you've configured in your data flow.

</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/faq.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.