Claude Coupler.io connectorWhat Claude can do in your Coupler.io account.
The Claude Coupler.io connector exposes 4 tools. 3 read your data sets and data flows, 0 write, and 1 is named on the directory sheet with no description anywhere. Below: what Claude can query, what you must set up in Coupler.io first, and a known loading bug.
Verified Trustpilot reviews · AI, automation & growth agency
What changes once Claude can query Coupler.io
Coupler.io pulls data from ad platforms, CRMs and finance tools into data sets on a schedule. With this web connector, a marketing manager asks Claude a question about that data in plain English, and Claude reads the columns and runs the query itself. No export, no spreadsheet formula, and no need to know SQL.
Answer a performance question on the spot. Ask which campaigns spent the most last month and get-data runs the query on Coupler.io's side, so a large data set does not have to fit into the conversation.
Read a data set correctly. Before querying, get-schema gives Claude each column's name, type, description and any business context saved on it, which keeps it from mixing up a cost column and a revenue column.
Check that the numbers are fresh. get-dataflow reports a flow's sources, destinations and last run, so you know whether the figures date from this morning or last week.
What it will not do: Coupler.io says queries are read-only and cannot edit, delete or overwrite the rows it imported. Claude also sees only data flows that have Claude set as a destination, nothing else in the workspace. And no refresh happens on its own because Claude asked a question: refresh schedules live in Coupler.io. Pushing data on a timer is the job of an automation tool, which the Integrations hub covers.
Five words to know
The Claude vocabulary this page relies on.
- Connector
- A link you set up once between Claude and an account you already have, so Claude can work in it while it answers you.
- Tool
- One named action a connector gives Claude. Claude chooses which to call by itself, and the directory sheet lists each name.
- Authorization
- The service's own sign-in screen, where you hand Claude the access it will use. Given once per person, and it can be taken back.
- Approval
- The confirmation Claude asks for before an action that changes your account, displayed in the conversation when it comes up.
- MCP
- The common standard connectors are built on: it is what lets an assistant such as Claude talk to an outside service like Coupler.io.
Connect Coupler.io to Claude in three steps
- 01
Open the connector list
In Claude's settings, open Customize, then Connectors, and find Coupler.io. On a Team or Enterprise workspace, an Owner or Primary Owner enables the connector before members can each authenticate.
- 02
Connect and sign in
Click Connect on the Coupler.io row and log in to Coupler.io in the window it opens. That window is Coupler.io's, not Claude's. If the connection goes stale, Disconnect and connect again.
- 03
Check the authorization
Read the authorization screen before you accept: it belongs to Coupler.io and decides what the access covers. Coupler.io adds that Claude asks permission to use its tools the first time it needs them in a conversation.
The 4 tools on the directory sheet
Coupler.io gives Claude 4 tools: 3 that read your account, 0 that change something in it, and 1 no official source describes.
Three read, one has no published description. Names stay exactly as Claude shows them.
- 3 read
- 1 not documented
What Claude reads (3)
3 toolsTools that look at your data sets and flows without changing them.
get-data
Runs a SQL query against one data set and returns the result, which is what actually answers your question. The work happens on Coupler.io's servers, so a big table never has to fit inside the chat.
get-schema
Returns the structure of a data set: column names, types, descriptions and the business context saved on it. Claude reads it before querying so it interprets each column the way you do.
get-dataflow
Describes where a data flow stands: its sources, its destinations and its last run. It tells you how recent the figures are and where they come from.
Undocumented (1)
1 toolThe directory gives this name and nothing else, and Coupler.io's tool reference does not mention it. We do not guess from a name.
list-dataflows
This name appears in the directory's tool list and that is all. Coupler.io's own tool reference does not include it, and no Claude page mentions it, so this page says nothing about what it does. The general approval rule below is the only reference for it.
What Claude asks you first
By default, Claude stops and asks for confirmation before each action it takes on an account for someone.
Coupler.io's FAQ describes the prompt you will meet: the first time Claude needs to fetch or process data in a session, it asks permission to use the tools, and choosing Always allow stops the question for that conversation. No source describes a prompt specific to one tool. On Team and Enterprise, owners decide whether members may let some actions through without asking and can restrict a connector for the whole organization. Claude reaches only what the connected person reaches.
Which Claude plans can use it
No official source publishes plan availability connector by connector. That is a real gap in the catalog, not in our research.
The published rule is general: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile, and on Team and Enterprise an Owner or Primary Owner opens a connector for the organization before members connect. Coupler.io's own documentation reports a plan-related loading issue, quoted with its date in the limits section below. The connector's sheet in the official directory remains the only page showing its live state.
Where this connector stops
A connector is not an automation. Claude calls these tools while it answers, so nothing runs when a data flow refreshes.
Only Coupler.io documents this connector: no Claude help article covers it. By default its sheet exposes only reading, an observed floor rather than a promise, since an administrator can open actions no public sheet lists. Coupler.io's tool reference describes many more tools than the four on the sheet; this page sticks to the sheet. The directory badge is not a security audit, and Anthropic states on every sheet that it neither picks a publisher's tools nor guarantees their behavior. For a very different case, see the Claude agility-cms connector.
Does the directory's Coupler.io connector work on every Claude plan?
- Claude help center, general connector rule ↗September 2026Remote connectors are available to all users on Claude, Cowork, Claude Desktop and mobile; on Team and Enterprise an Owner enables them first.
- Coupler.io documentation, troubleshooting page ↗undated, read October 2026The publisher reports that on individual Free and Pro plans the official connector may connect while its tools fail to load, says Team and Enterprise are unaffected, and suggests a custom connector as a workaround.
What this page followsThe two do not clash on availability as such: Anthropic states the general rule, Coupler.io reports a known bug it says it is tracking with Anthropic. Neither settles it for your account, so check the directory sheet and whether the tools actually appear once you connect.
Need help connecting Coupler.io to Claude?
A person reads every message.