- Home
- Resources
- Integrations
- Datarails FinanceOS
Claude Datarails FinanceOS connectorWhat Claude can do in your Datarails FinanceOS account.
The Claude Datarails FinanceOS connector exposes 24 tools, all 24 of them read tools. 0 write, 0 undocumented. Below: what Claude can query in your consolidated finance data, who has to switch it on in Datarails, and what the publisher explicitly keeps off limits.
Verified Trustpilot reviews · AI, automation & growth agency
What it changes for an FP&A team
Instead of exporting a table, building a pivot and double-checking the filters, you ask Claude for spend by vendor over the quarter. It queries Datarails, has the totals computed server-side and answers you. According to the publisher, none of the 24 tools creates, edits or deletes anything.
Answer with your own definitions. list_business_metrics returns the KPIs exactly as your organization defined them, and list_aliased_fields the business names of each column.
Compute without pulling everything. start_aggregation_by_alias starts a grouping on the server, then get_aggregation_result_by_alias brings back the totals. Raw rows arrive 100 per page through get_data_by_alias. The figures stay within what your Datarails role lets you see.
Vet a table before trusting it. profile_numeric_fields and profile_categorical_fields return counts, sample values and SUM, AVG, MIN, MAX statistics, so you can judge a table before a board pack goes out.
What Claude will not do: Datarails spells it out, the connector writes no data, formulas, models or users, and cannot switch itself on. It does not fire when a month closes either. For scheduled processing you need an automation tool, a different job gathered on the Integrations hub.
The vocabulary in one minute
Five words before you connect Datarails FinanceOS.
- Connector
- The link you set up once between Claude and an account you already have, so Claude can work with it while it answers you.
- Tool
- One named action a connector opens to Claude. Claude picks the ones it needs by itself; the directory lists them by name.
- Authorization
- The service's own sign-in screen, where you hand Claude the access it will use. Granted once per person, and revocable.
- Approval
- The confirmation Claude waits for before an action that changes your account, shown in the chat at the moment it matters.
- MCP
- The shared standard connectors are built on: it is what lets an assistant like Claude talk to an outside service at all.
Connect Datarails FinanceOS to Claude in three steps
- 01
Find the connector
In Claude's settings, open Customize, then Connectors, and look for Datarails FinanceOS. On a Team or Enterprise workspace, an Owner or Primary Owner enables it first, then each member connects individually.
- 02
Sign in to Datarails
Click Connect on its row. Datarails opens its own login page, through your SSO if one is set up, and asks you to pick your environment. If the link breaks, Disconnect and connect again.
- 03
Approve the consent screen
Read Datarails' authorization screen before accepting. It is that screen, not Claude, that defines what the access covers. You can withdraw it later from Claude or from your Datarails account.
The 24 tools, all read-only
Datarails FinanceOS gives Claude 24 tools: 24 that read your account, 0 that change something in it.
Tables, fields, KPIs, company profile, filebox, FX rates and aggregations: Datarails labels all 24 tools as reads. Names stay as Claude shows them.
- 24 read
Tools index
- get_aggregation_result_by_alias
- get_aggregation_result_by_id
- get_company_profile_sections
- get_connector_status
- get_currency_rates
- get_data_by_alias
- get_data_by_id
- get_distinct_values_result_by_alias
- get_distinct_values_result_by_id
- get_fields_by_id
- get_org_users
- get_workflow_guide
- list_aliased_fields
- list_business_metrics
- list_company_profile_sections
- list_data_models
- list_filebox
- list_xl_functions
- profile_categorical_fields
- profile_numeric_fields
- start_aggregation_by_alias
- start_aggregation_by_id
- start_distinct_values_by_alias
- start_distinct_values_by_id
What Claude reads (24)
24 toolsTwenty-four reads, including pairs that start a calculation and then collect its result.
get_aggregation_result_by_alias
Collects the result of an aggregation started earlier on a table named by its business alias. It is the second half of a pair: the query goes out first, the figures come back here.
get_aggregation_result_by_id
Picks up the totals of an aggregation submitted on a table identified by its technical ID, once Datarails has finished computing them.
get_company_profile_sections
Returns the text of named sections from your company profile in Datarails. You name the sections; their titles come from list_company_profile_sections.
get_connector_status
Reports whether the connector is switched on for your organization.
get_currency_rates
Gives your organization's current exchange rate snapshot, based on the US dollar. Claude can then convert an amount with the rates Datarails holds.
get_data_by_alias
Brings back rows from a table you name by its business label, with the columns and filters you choose. Handy when nobody remembers the technical ID.
get_data_by_id
Returns rows from a table addressed by its ID, keeping only the columns and filters that matter. The technical twin of the alias lookup.
get_distinct_values_result_by_alias
Hands back the list of different values found in a field, after a lookup started on a table referenced by alias.
get_distinct_values_result_by_id
Delivers the unique values of a field once the lookup is done, when the table was referenced by its identifier.
get_fields_by_id
Describes a table's columns: their names, types and descriptions. Claude then knows what to ask for before it queries any rows.
get_org_users
Provides the list of organization users with their role and department. Datarails flags that it includes those people's names and email addresses.
get_workflow_guide
Returns guidance written by Datarails for common analysis tasks, with no customer data in it. Datarails authors this material itself, so nothing from your own tables appears in it.
list_aliased_fields
Shows a table's business-friendly field aliases along with what each field means. In other words, the readable names your team gave its columns, nothing technical.
list_business_metrics
Lists the KPIs and metric definitions your organization has set up in Datarails. They come back as your organization defined them, not as generic finance terms.
list_company_profile_sections
Lists the sections that make up your company profile, without their content. Use it before get_company_profile_sections, which then returns the text of the ones you name.
list_data_models
Lists the tables and data models your account is allowed to see.
list_filebox
Shows how the filebox is organized: folders, files, templates and lookup tables, by name and structure only.
list_xl_functions
Lists the named XL functions that Excel DR.GET formulas rely on. Only the function names come back; the workbooks themselves stay in Excel.
profile_categorical_fields
Profiles categorical fields with distinct counts and sample values. Like every data tool, it only covers tables your Datarails role lets you see.
profile_numeric_fields
Computes sum, average, minimum, maximum and count for numeric fields. As with the other data tools, Datarails checks each call against your role and permission groups.
start_aggregation_by_alias
Asks the server for a grouped aggregation on a table named by its business alias and returns a tracking handle. Datarails states this query stores nothing.
start_aggregation_by_id
Kicks off a grouped aggregation (sum, count, average, min, max and similar) on a table identified by ID. The query runs server-side and keeps nothing.
start_distinct_values_by_alias
Asks for the list of distinct values in a field of a table called by its business name. The answer is fetched in a second step.
start_distinct_values_by_id
Launches the search for a field's unique values on a table referenced by ID, for a deferred read of the result.
What Claude asks before it acts
By default, Claude stops and asks for your go-ahead before each action it takes on an account for you. Here, all 24 tools are reads.
No source describes a confirmation specific to Datarails. On a Team or Enterprise workspace, owners decide whether a member may let certain actions through without being asked again, and can cap what a connector does for the whole organization. On the Datarails side, every call is checked against your role (Super Admin, Admin, Contributor, Viewer) and permission groups, just as in the web app. Claude therefore sees nothing you could not see yourself.
Which plans it is available on
None of the 819 sheets in the directory shows plan availability. That information is not published anywhere, connector by connector.
The general rule is published: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner turns the connector on for the organization first. The Datarails AI connector subscription is a separate matter, covered under limits. For the current state on your account, the sheet in the official directory remains the reference.
Where this connector stops
A connector is not an automation. Claude calls these tools while it answers you; nothing kicks off by itself when a period closes.
Only the publisher documents this connector. Neither Claude's help center nor Anthropic's developer docs have a page on it. Datarails stresses one point: read-only is a property of the tools published today, not an enforced restriction, and write tools sit on its roadmap. If someone must not change a data set, their Datarails permissions have to guarantee it. The directory badge is not a security audit, and Anthropic does not choose the tools a publisher exposes.
Need help connecting Datarails FinanceOS to Claude?
A person reads every message.