Common Issues

Connection issues

The agent doesn't call the Coupler.io tool

If your agent ignores the Coupler.io tool or says it can't access the data, check the following:

• Confirm generative orchestration is turned on for the agent — without it, the agent won't decide to call MCP tools on its own.
• Verify the tool was added under Tools → Add a tool → New tool → Model Context Protocol with the correct Coupler.io MCP server URL.
• Make sure at least one data flow with the Microsoft Copilot Studio destination has completed a successful run.

Authentication or consent fails when using the tool

The Coupler.io MCP tool uses OAuth 2.0 with Dynamic discovery, so Copilot Studio registers itself automatically — you don't add a client ID or secret. If sign-in fails:

• Confirm the tool's authentication is set to OAuth 2.0 with Dynamic discovery, not a manual client ID/secret setup.
• When the consent card appears in chat, sign in to Coupler.io to authorize the tool. Each user signs in once.

If you re-created the tool or changed its authentication settings, users may need to sign in again through a fresh consent card.

The agent can't see a data flow I just created

Only data flows that use the Microsoft Copilot Studio destination are available to the agent. If a data flow uses a different destination, the agent won't see it. Confirm the destination and that the flow has completed a successful run.

Data issues

The agent sees fewer rows than the Coupler.io preview shows

A mismatch between the Preview in Coupler.io and the data the agent receives can occur when the same identifier appears multiple times and deduplication affects the export differently than the preview.

Don't rely on the Preview tab alone to confirm what the agent will receive. Always verify the actual row count after running the flow. You can also configure a Google Sheets export to cross-check the number of rows and see what's missing.

If specific rows are missing, note the relevant IDs and contact Coupler.io support with the data flow details — this type of discrepancy requires engineering investigation.

Permission errors

"You've reached your destination limit" or AI usage is restricted

Coupler.io plans have limits on destination type. If you're using Microsoft Copilot Studio as a destination and also sending data elsewhere (for example, Google Sheets), you may hit this limit.

To resolve this, either:

• Remove the other destination and use only Microsoft Copilot Studio, or
• Upgrade to a higher Coupler.io plan that supports multiple destination types.

Each active data flow counts toward your plan limits. If you created a test flow with a different destination, delete it to free up your destination slot or upgrade to a higher plan.