Resources · Claude connector

Claude Orion by Gravity connectorWhat Claude can do in your Orion by Gravity account.

The Claude Orion by Gravity connector exposes 21 tools. 15 read your projects, metrics, workflows and deliverables, 5 start an analysis, a metric run or a workflow, or delete a deliverable, and 1 has no source describing it. Here is what each does and what needs your go-ahead.

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What changes when Claude talks to Orion

Gravity says its server lets assistants such as Claude work directly with your Orion projects, metrics, workflows and knowledge base. From Claude you hand Orion an analysis question, read its decks, dashboards and reports, follow your KPIs or start a workflow, and the result comes back in the same conversation.

Ask Orion a question. Claude passes a plain-language question on with ask_orion, then reads the answer through get_conversation_history; Gravity says a multi-step analysis takes a minute or two.

Follow a project's KPIs. list_metrics lists them, get_metric_results gives their past results and get_metric_insights surfaces the significant changes and anomalies Orion detected on its own.

Read an existing deliverable. get_artifact returns a deck, dashboard or report as markdown, which Claude can then quote in its answer.

Start from what Orion suggests. list_recommendations returns the AI-generated recommendations for a project with suggested analysis prompts, and search_wiki looks through the knowledge base, so a question can start from what your team already wrote down.

What the sheet does not list: a tool that builds a dashboard or edits a project, and nothing runs in the background between two of your questions. For other platforms the team has documented, start from the Integrations hub.

Vocabulary

Five words to get started

The Claude vocabulary you will run into here, in plain terms.

Connector
The link you set up once between Claude and an account you already have, so Claude can work in it while answering you.
Tool
One named action the connector opens to Claude. Claude decides which to call; the directory sheet lists them by name.
Authorization
Orion's sign-in screen, where you give Claude the access it will use. Granted once per person, and you can revoke it.
Approval
The confirmation Claude waits for in the chat before it runs or deletes something in your account.
MCP
The shared standard behind connectors: it is what lets an assistant like Claude talk to an outside service.
Connect

Set up the Claude Orion by Gravity connector

  1. 01

    Find Orion in the list

    In Claude's settings, open Customize, then Connectors, and search for Orion. On a Team or Enterprise workspace, an Owner or Primary Owner enables it for the organization first, then each member connects.

  2. 02

    Sign in with your Orion credentials

    Click Connect on its row. Orion opens its own sign-in window: you log in with your Orion account, and Gravity points out there is nothing to install on your side.

  3. 03

    Review the authorization screen

    Read what Orion's screen lists before you approve. Gravity says you sign in with your Orion credentials; the access is granted once, for you, and can be taken back the same way.

Tools

All 21 tools in the Claude Orion by Gravity connector

Orion by Gravity gives Claude 21 tools: 15 that read your account, 5 that change something in it, and 1 no official source describes.

Three groups: what Claude reads, what it runs or deletes, and one tool no source describes. Names stay exactly as Claude shows them.

  • 15 read
  • 5 write
  • 1 not documented

What Claude reads (15)

15 tools

Fifteen tools that look up projects, chats, metrics, workflows and deliverables without changing anything.

list_projects

Lists the Orion projects you have access to. Most other tools work on a project, so this is where its reference comes from. The list only covers projects your Orion account can open.

When it helps
you don't remember the exact name of the project you want to question.

Sourcedocs.runorion.com · October 1, 2026 ↗

list_conversations

Lists a user's Orion chat conversations, so an earlier exchange can be found again from Claude. Gravity pairs it with conversation history to read what was said in each one.

When it helps
you want to pick up an analysis thread started in Orion rather than start over.

Sourcedocs.runorion.com · October 1, 2026 ↗

get_conversation_history

Reads the messages of an existing Orion conversation. Gravity says it is also how the final answer is collected after a question sent with ask_orion.

When it helps
an analysis was launched a moment ago and its result has not come back yet.
Watch out
Gravity asks for at least 30 seconds between polls.

Sourcedocs.runorion.com · October 1, 2026 ↗

list_artifacts

Lists the slide decks, dashboards and reports of a project, the deliverables Orion keeps for it. Each one can then be opened with get_artifact, which returns its content.

When it helps
you need to know which deliverables exist in a project before reading one of them.

Sourcedocs.runorion.com · October 1, 2026 ↗

get_artifact

Returns the content of a deck, dashboard or report as markdown. Claude can then quote it or compare it with another one in the conversation. Gravity names markdown as the format, whatever the deliverable type.

When it helps
you want the substance of a report without opening Orion.

Sourcedocs.runorion.com · October 1, 2026 ↗

search_wiki

Searches the Orion wiki, the knowledge base attached to your organization's projects. Gravity describes it simply as a search of the Orion wiki and knowledge base, with no further detail on results.

When it helps
a definition or a piece of documentation already written in the wiki should frame the answer.

Sourcedocs.runorion.com · October 1, 2026 ↗

list_users

Lists every user in the Orion organization and returns, for each one, an ID, a name and a role. Those three fields are the only ones Gravity lists for this tool.

When it helps
you need to know who holds which role in Orion.

Sourcedocs.runorion.com · October 1, 2026 ↗

list_metrics

Lists the metrics, meaning the KPIs, defined for a project. It is the inventory, before any detail or result. For the definition and code of one of them, get_metric takes over.

When it helps
you want to see which KPIs a project tracks.

Sourcedocs.runorion.com · October 1, 2026 ↗

get_metric

Brings back the full record for a single metric: its definition, its Python code, its data sources and its latest result. It is the most detailed view of a KPI that the sheet exposes.

When it helps
you want to check how a number is computed before relying on it.

Sourcedocs.runorion.com · October 1, 2026 ↗

get_metric_results

Returns the historical execution results of a metric, run after run, rather than its latest value alone. For the most recent value alone, get_metric is enough.

When it helps
you want to see how a KPI has moved over its past runs.

Sourcedocs.runorion.com · October 1, 2026 ↗

get_metric_insights

Surfaces the metric insights Orion detected on its own for a project: significant shifts and anomalies, across the KPIs it tracks. Claude reads them as Orion stored them, without recomputing anything.

When it helps
you want to know which numbers moved enough to deserve a closer look before you ask Orion why.

Sourcedocs.runorion.com · October 1, 2026 ↗

list_workflows

Lists the workflows defined for a project in Orion. Each workflow found here can then be read in detail with get_workflow, which shows its steps and schedule.

When it helps
you are looking for a workflow before reading its detail or starting it.

Sourcedocs.runorion.com · October 1, 2026 ↗

get_workflow

Exposes a workflow's detail: its definition, with its steps and outputs, and its schedule. The schedule is part of what Gravity says this tool returns.

When it helps
you want to know what a workflow produces and when it is scheduled before starting it.

Sourcedocs.runorion.com · October 1, 2026 ↗

get_workflow_results

Still listed on the sheet, but Gravity says three other tools replaced it and calling it now returns an error. Those replacements are not on the sheet.

When it helps
no longer, according to the publisher.
Watch out
if Claude hits an error here, that is expected behavior.

Sourcedocs.runorion.com · October 1, 2026 ↗

list_recommendations

Returns the AI-generated recommendations Orion produced for a project, each with suggested analysis prompts. Gravity describes these recommendations as generated by AI.

When it helps
you don't know where to start in a project and would like questions already phrased.

Sourcedocs.runorion.com · October 1, 2026 ↗

What Claude runs or deletes (5)

5 tools

Five tools Gravity files under actions: they create, trigger or delete. No source describes their confirmation step, so the general rule below applies.

ask_orion

Approval: see the rule

Sends a plain-language question to Orion, which returns an AI-powered data analysis. Gravity calls it the primary tool for working with Orion.

What Claude asks for
no source describes a confirmation specific to this tool; the general rule below applies.
When it helps
a question about your data needs a multi-step analysis.
Watch out
expect a minute or two before the answer lands.

Sourcedocs.runorion.com · October 1, 2026 ↗

create_conversation

Approval: see the rule

Starts a new Orion conversation, separate from the existing ones.

What Claude asks for
nothing specific is documented here, so the default rule covers it.
When it helps
a new subject deserves its own thread rather than an existing one.

Sourcedocs.runorion.com · October 1, 2026 ↗

execute_metric

Approval: see the rule

Triggers the execution of a metric to refresh its current value, instead of reading the last stored result.

What Claude asks for
Gravity documents no particular check; rely on the general approval rule.
When it helps
the latest stored value is not recent enough for your question.

Sourcedocs.runorion.com · October 1, 2026 ↗

run_workflow

Approval: see the rule

Triggers a workflow run and returns the created run with its ID. Gravity says runs take minutes and their outputs land as they are ready.

What Claude asks for
no tool-specific confirmation is documented; the general approval rule holds.
When it helps
you want a fresh run of an existing workflow without opening Orion.

Sourcedocs.runorion.com · October 1, 2026 ↗

delete_artifact

Approval: see the rule

Deletes a slide deck, dashboard or report artifact from Orion. Gravity itself labels this a destructive action.

What Claude asks for
no source details a confirmation specific to this tool; the general rule covers it.
When it helps
a deliverable is no longer needed in a project.
Watch out
no source mentions a trash bin or a restore option.

Sourcedocs.runorion.com · October 1, 2026 ↗

Undocumented (1)

1 tool

A tool the sheet publishes by name only: no official source says what it does, or whether it reads or changes anything.

get_company

The directory sheet publishes this tool by name only, and Gravity's tool reference doesn't mention it. No official source describes it.

No public page classifies it either way. The general approval rule further down is all there is to go on for this one.

Approvals

What Claude asks before acting

By default, Claude stops and asks for your go-ahead before every action it takes on an account for you. The request shows up in the conversation, at the moment it matters.

Gravity says each tool carries annotations telling the assistant which ones are safe to call without confirmation, and puts its read tools in that bucket. For the five action tools, no source describes a specific confirmation, so the general rule applies. On Team and Enterprise, owners decide whether a member can let some actions through without a fresh prompt, and they can cap what the connector does organization-wide. And Claude works with your Orion rights, nothing more.

Plans

Which plans include it

None of the 819 sheets in the official directory shows availability by plan. For a given connector, that information is not published anywhere: it is a real gap in the catalog.

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 before members connect. For Orion by Gravity's current status, check its sheet in the official directory. Worth knowing: only Gravity and the sheet document this connector; no Claude help article covers it.

Limits

Where this connector stops

A connector is not an automation. Claude calls these tools while it answers you: nothing fires when a metric slips or a workflow finishes.

The tool list is an observed floor, not a promise: an admin can open actions no sheet shows. The partner badge is not a security audit, and Anthropic notes on every sheet that it does not choose a publisher's tools or guarantee how they behave. Here, Gravity even documents more tools than the sheet publishes, hence the mismatch below.

One more point: only Gravity and the sheet describe this connector, and their lists differ. Trust what Claude shows once you are connected.

Two official sources disagree

Which tools does the Orion by Gravity connector expose to Claude?

  • Claude directory sheet ↗October 1, 202621 tools, including get_workflow_results and get_company, and no wiki write tool.
  • Gravity's tool reference ↗undated page27 tools, including creating and editing wiki pages; get_workflow_results is replaced and returns an error; get_company is not listed.

What this page followsThe two lists don't match. The sheet is dated, Gravity's reference is not, and neither settles it alone: the list actually exposed is the one you see once the connector is plugged in. This page follows the sheet for the count and flags the gaps.

Need help

Need help connecting Orion by Gravity to Claude?

A person reads every message.

FAQ

Questions about the Claude Orion by Gravity connector

01What can Claude do with the Orion by Gravity connector?
Claude can hand analysis questions to Orion and read what Orion produces. Fifteen tools look up your projects, conversations, users, metrics and their anomalies, workflows, deliverables, recommendations and the wiki. Five take action: asking Orion a question, opening a conversation, refreshing a metric, running a workflow and deleting a deliverable. One more, get_company, has no source describing it. Gravity is a verified partner in the directory. Orion runs the analyses itself; Claude relays the question and reads the result back.
02Can Claude run or delete things in Orion?
Yes, five tools act on your account. ask_orion starts an analysis, create_conversation opens a conversation, execute_metric refreshes a KPI and run_workflow starts a workflow run. delete_artifact removes a deck, dashboard or report, which Gravity itself calls destructive. No source mentions restoring a deleted item. Gravity also documents wiki writes, but those tools do not appear on the directory sheet, so the count here leaves them out. Check the directory sheet to see whether its list has changed.
03Does Claude ask before deleting a deliverable?
By default, yes: Claude asks for confirmation before each action it takes on an account for you. No source describes a check specific to delete_artifact or the four other action tools, so that rule covers them. Gravity only says its read tools are safe to call without confirmation. On Team and Enterprise, owners can also shut off actions for everyone while keeping reads open, and members can't override that. Read a deletion request carefully before you approve it.
04Which Claude plans is this connector available on?
No official source publishes plan availability connector by connector, and none of the 819 directory sheets shows it. The general rule says remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner enables them for the organization first. Gravity names no Claude plan. Only the Orion by Gravity sheet in the directory shows its current status for your account.
05Does Claude see every Orion project in the company?
No, Claude works with your rights and nothing more. The project tool only returns projects you can access, and Gravity notes that wiki writes follow your own permissions, limited to Admin, Analyst and Group Analyst roles. A colleague with different rights will see different things. A Team or Enterprise owner can also restrict what the connector does on the Claude side, which narrows it further. Your role stays the limit.
06Why doesn't Claude answer right away after asking Orion?
Because Orion runs multi-step analyses that, per Gravity, take a minute or two. Claude sends the question with ask_orion, then rereads the conversation with get_conversation_history until the answer lands, leaving at least 30 seconds between polls. A workflow run takes minutes. When Warp Drive is on for a project, Gravity says a question its approved content can't answer is declined, and a longer Full Analysis may be offered if the project's access policy allows it.
07Claude or an automation tool for Orion by Gravity?
They serve different needs, so the choice depends on the task, not on a ranking. Claude suits questions asked in a conversation: explaining a change, reading a deck, starting a workflow on request. It only acts while you talk to it, and nothing fires when a metric moves or a run finishes. An automation tool handles repeated sequences that run without you. Workflows do carry a schedule inside Orion, which get_workflow shows. Nothing stops you from using both.