Claude Trussi AI connectorWhat Claude can do in your Trussi AI account.
The Claude Trussi AI connector exposes 32 tools: 16 read, 4 write, 12 undocumented. The read side covers projects, customers, pipeline, revenue, schedules and reports of your Trussi roofing CRM; the write side adds comments, calendar events, quotes and pipeline moves.
Verified Trustpilot reviews · AI, automation & growth agency
What changes when Claude can work in Trussi AI
With this connector, you ask Claude about your Trussi roofing CRM in plain language. Claude reads projects, customers, the sales pipeline, finances and schedules while it answers, and, if you granted the write scope when connecting, it adds a comment, creates a calendar event or a quote, or moves a project to another pipeline stage.
The state of sales in one answer. trussi_get_pipeline, trussi_get_dashboard and trussi_get_leaderboard sit behind Trussi's promise of checking your pipeline, dashboard and leaderboard without opening them.
Money in and money owed. trussi_get_revenue_trend, trussi_get_collections and trussi_get_marketing_channels map to month-by-month revenue, receivables and marketing-channel performance, and trussi_get_profit_analysis to profit analysis.
Small actions without leaving the chat. trussi_create_comment, trussi_create_calendar_event, trussi_create_quote and trussi_update_pipeline_stage cover the four write actions Trussi lists.
What it will not do: no source describes deleting records, and Trussi's page mentions messaging customers without any listed tool matching it. Twelve tools have no description at all, so the page does not guess what they do. Nothing runs on its own either: Claude calls these tools while it answers you. A scheduled weekly report belongs to an automation platform; see the Integrations hub for the ones we cover.
Five words before you connect
Claude's vocabulary around this connector, in one minute.
- Connector
- The link you set up once between Claude and an account you already have, so Claude can use it while it answers you.
- Tool
- One named capability a connector opens to Claude. Claude picks the ones it needs; the directory sheet lists all 32 by name.
- Authorization
- Trussi's own sign-in screen, where you grant the access Claude will use, read and write as separate scopes. Per person, revocable.
- Approval
- The confirmation Claude waits for before it changes something in your Trussi account, shown in the chat at that moment.
- MCP
- The shared standard connectors run on: it is what lets an assistant like Claude talk to a business tool such as Trussi.
Connect Trussi AI to Claude in three steps
- 01
Find Trussi AI in the connector list
Open Claude's settings, go to Customize, then Connectors, and look for Trussi AI. On a Team or Enterprise workspace, an Owner or Primary Owner enables it for the organization before members connect individually.
- 02
Sign in to Trussi
Click Connect on its row and sign in with your Trussi account in the window that opens. If the connection breaks later, Disconnect it and connect it again to repair it.
- 03
Choose the scopes on Trussi's screen
On Trussi's side, reading and acting are two distinct permissions, each granted on this screen. Read it before you accept: it belongs to Trussi, not to Claude, and it decides whether Claude can only read or can also act.
The 32 tools, sorted by what they do
Trussi AI gives Claude 32 tools: 16 that read your account, 4 that change something in it, and 12 no official source describes.
Three groups: 16 tools that read, 4 that write, and 12 that no source describes. Trussi's directory description covers the first two groups by family; the names stay as Claude shows them.
- 16 read
- 4 write
- 12 not documented
What Claude reads (16)
16 toolsSixteen tools tied to the data Trussi lists as readable: projects, customers, pipeline, finances, schedules, timelines and reports.
trussi_get_activity
One of two tools attached to Trussi's mention of project and per-user activity timelines: Claude reads an activity timeline instead of you opening the record.
trussi_get_collections
Brings receivables and collections figures, part of the finance views Trussi says you can pull from the chat, next to month-by-month revenue and marketing-channel performance.
trussi_get_dashboard
Pulls up your Trussi dashboard in the conversation, one of the three sales views the publisher names alongside the pipeline and the leaderboard.
trussi_get_leaderboard
Shows the sales leaderboard that Trussi lists next to the pipeline and dashboard among the things you can check from the conversation.
trussi_get_marketing_channels
Reports marketing-channel performance, which Trussi groups with month-by-month revenue and receivables in its list of financial views you can request from Claude in plain language.
trussi_get_pipeline
Reads your sales pipeline as Trussi holds it, the first of the three sales views the publisher says you can check from Claude.
trussi_get_profit_analysis
Returns the profit analysis Trussi says you can review from the chat, in the same sentence as worksheets and insurance supplements, the three job finance views it names.
trussi_get_project
Opens one project with its full job detail, which Trussi describes as status, quotes, files and measurements, all brought into the conversation at once.
trussi_get_project_worksheets
Gives a project's worksheets, which Trussi describes as signed value, collected amount and balance due, inside the conversation rather than in the CRM's own screens.
trussi_get_revenue_trend
Provides month-by-month revenue, the first item of the financial views Trussi says you can pull without leaving the chat, ready to compare one period with another.
trussi_list_calendar_events
Lists calendar events, tied to Trussi's mention of calendar, labor and delivery schedules that Claude can read for any single day or for a whole date range.
trussi_list_customers
Lists the customers in your Trussi account, part of the publisher's promise to find and open projects and customers from the chat.
trussi_list_project_activity
Second tool attached to the activity timelines Trussi mentions, alongside the general activity tool: Claude reads a project's timeline instead of you scrolling the record.
trussi_list_project_supplements
Lists insurance supplements, which Trussi names with profit analysis and worksheets among the job finance views available in the chat.
trussi_list_saved_reports
Lists your saved reports, tied to Trussi's statement that you can run them from Claude, so you can pick the right one by name.
trussi_run_saved_report
Runs one of your saved reports, as Trussi's description promises, and brings the result back into the conversation, where you can ask Claude about it like any other answer.
What Claude can add or move (4)
4 toolsFour tools tied to the actions Trussi lists. No source describes a confirmation specific to them, so the general rule below applies.
trussi_create_calendar_event
Approval: see the ruleAdds an event to the Trussi calendar, one of the four actions Trussi lists for Claude.
trussi_create_comment
Approval: see the rulePosts a comment in Trussi, the first action the publisher lists among what Claude can do with your permissions.
trussi_create_quote
Approval: see the ruleCreates a quote in Trussi, part of the actions the publisher says Claude can take with your permissions.
trussi_update_pipeline_stage
Approval: see the ruleMoves a project to another stage of the pipeline, the last of the four actions Trussi lists.
Not documented (12)
12 toolsThe directory publishes these names and nothing else. No source says whether they read or change anything, so nothing is claimed about them here.
trussi_list_company_documents
No official source describes this tool: the directory sheet publishes its name only, and Trussi's pages never mention it. Nothing is claimed here about what it returns or whether it reads or acts.
trussi_list_dead_lead_reasons
Undocumented. Neither the directory description nor Trussi's connector page has a sentence about this name, so the page leaves it without a capability.
trussi_list_job_catalog
Nothing published explains this one. The sheet lists the name, no Trussi text covers it, and guessing from a name is exactly what this page refuses to do.
trussi_list_locations
Here too, no source: Trussi's description lists families of data and actions, and none of its sentences names this tool. It stays in the undocumented group.
trussi_list_production_orders
This name appears on the directory sheet with no description attached anywhere. Neither Trussi's directory text nor its connector page says what it returns or whether it changes anything.
trussi_list_project_comments
Not described by any official source. The directory sheet carries the name, and no sentence from Trussi covers it, so the page claims nothing about what it does.
trussi_list_project_files
No description exists for it. The name is on the directory sheet, yet no sentence from Trussi is tied to it, so whether it reads or acts stays unknown here.
trussi_list_projects
Missing from every source as a named tool. No sentence in Trussi's directory description or on its connector page is tied to this name, so it gets no capability here.
trussi_list_quote_templates
Without any source sentence, this tool keeps an unknown status. The directory gives its name; Trussi's directory description and connector page are both silent on it.
trussi_list_quotes
Undocumented as a tool. The directory sheet lists it by name, but no sentence from Trussi names this one, and the page does not assume a link with any other.
trussi_list_team
No official text describes this tool, on the directory sheet or on Trussi's site. Its name is all that is published.
trussi_search_projects
Absent from the sources as well. The sheet lists it by name and no sentence from Trussi is tied to it, so it is left undocumented rather than described by guesswork.
What Claude asks before acting
Claude's default is to stop and ask before any action it takes on an account for you. Four documented tools write here, and no source describes a confirmation specific to them, so that default is what applies.
On Team and Enterprise workspaces, owners decide whether members may let some actions through without a new prompt, and they can restrict what a connector does for the whole organization, keeping reads and blocking writes. No member overrides that alone. Claude works with the rights of the person who connected it, and Trussi adds that access is scoped by role and branch. The official per-tool label only shows inside a connected account's settings.
Which plans include it
None of the 819 sheets in the official directory shows availability by plan. Connector by connector, that answer is not published anywhere.
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 turns a connector on before members connect. For this connector's current state, open its sheet in the official directory, the only place that shows it.
Where the Claude Trussi AI connector stops
A connector is not an automation. Claude works in Trussi while it answers you; nothing fires when a job changes stage or a payment comes in.
The public tool list is an observed floor, not a ceiling: an admin can open actions that no sheet shows. The verification badge is not a security audit, and Anthropic says on every sheet that it does not decide a publisher's tools. Only Trussi documents this connector, in its directory description and its own connector page; no Claude help article or Anthropic developer page covers it, so every detail here is the publisher's word.
Need help connecting Trussi AI to Claude?
A person reads every message.
