Guide
Connecting Claude to itinovo
How to enable the connector for the agency, connect your Claude account, what Claude can and cannot do in itinovo, where the data goes and how to disconnect.
Before you start
- An itinovo account, on trial or with an active subscription. Claude is included in every plan and its actions do not use up the plan's AI requests.
- A Claude account. To work on client data use a Team or Enterprise plan: it has a data processing agreement and does not use conversations to train models.
- The agency's account holder or an administrator enables Claude once for everyone (step 1).
Connect in three steps
- 1
Enable it for the agencyaccount holder or administrator
In itinovo open Settings → Integrations → Claude, read what happens to the data and press Enable for the agency. itinovo records who enabled it, when and on which text.
- 2
Add itinovo in Claudeeach person
From the same card press Continue with Claude: Claude opens.
From the directory: search for itinovo CRM among the connectors and press Connect.
Custom connector: add a custom connector with this address and leave the advanced settings empty.
https://api-crm.itinovo.com/mcpWith Claude Team or Enterprise, the owner of the Claude organisation adds the connector once; then each person presses Connect.
- 3
Sign in with your itinovo accounteach person
itinovo's sign-in page opens: sign in with email and password or with Google. From then on Claude works with your role, only when you ask it in chat.
Three examples
- 1
Loading a hotel's price list
Attach the PDF or spreadsheet and write: “Load Villa Clementina's 2027 rates.” Claude uses
import_supplier: the hotel becomes a supplier with its card and its rates by season, room and board. It asks you before saving and at the end says what it created, updated or left out. - 2
From the client's email to a quote
Paste the request: “Prepare a quote from this email.” Claude uses
prepare_quote: client, booking and draft quote with days, services and prices. You send the quote from the app. - 3
The week at a glance
“Which departures do I have next week, and what is missing?” Claude uses
get_overviewandget_lead: departures, deadlines, missing confirmations and payments, booking by booking. Read only, nothing to confirm.
What it can do
Claude sees and changes only what you see and change in the app. Tools marked “asks first” go through your confirmation in Claude before each use.
| Tool | What it does | — |
|---|---|---|
| Reading | ||
search | Searches bookings, clients, suppliers and quotes by name, email or reference. | read only |
list_leads · get_lead | Bookings by stage, dates or destination; a booking with its quotes, travellers, tasks, documents and history. | read only |
list_quotes · get_quote | Quotes by status; a quote with its days, services, prices, versions and change requests. | read only |
list_clients · get_client | Clients; a client with details, travel companions, bookings and documents. | read only |
list_suppliers · get_supplier | Suppliers, tour operators' products and services; a supplier with rates, allotments and terms. | read only |
list_tasks · list_confirmations | Tasks and suppliers' confirmations, open or overdue. | read only |
get_overview | Departures, deadlines, notifications and unread messages. | read only |
get_money | Invoices, payments and payment plans, read only. | read only |
get_analytics | Sales, margin and payments received in the period, as on the Analytics page. For administrators. | read only |
get_agency_info · get_campaigns · get_reference | The agency's details, team and templates; campaigns and their results; allowed values (stages, currencies, boards). | read only |
search_flights | Searches flights with the agency's flight account, without booking them. | read only |
| Creating | ||
prepare_quote | From a request: client, booking and draft quote with days, services and prices. | creates |
create_lead · create_quote | A new booking, also for a group; a new quote, from a template, duplicated or as a new version. | creates |
save_travellers | Adds travellers to a booking. | creates |
generate_document · save_as_template | Generates a booking document, without sending it; saves a quote as a template. | creates |
| Changing | ||
update_lead | A booking's details and stage. | asks first |
edit_quote_texts · edit_quote_items · edit_quote_settings | Texts; days and services, costs, mark-ups and prices; quote settings. On drafts, recalculated as in the editor. | asks first |
save_client · save_supplier · save_task · save_group | Creates or updates clients, suppliers with products and rates, tasks, groups and series. | asks first |
update_confirmation | Records what a supplier confirmed: code, price, due dates, cancellation fees. | asks first |
import_supplier · import_clients | Loads a supplier with its rates, or a list of clients: updates what is there, never duplicates. | asks first |
mark_read | Marks notifications and messages as read. | asks first |
| With effects outside itinovo, or final | ||
ask_suppliers | Asks suppliers for availability or confirmations, with the agency's template. | asks first |
set_lead_state · delete | Booking lost, reactivated or with a complaint; deletes an item. | asks first |
What it never does
- Send quotes, documents or messages to clients
- Book or pay on outside systems
- Take payments, request payments, issue invoices
- Change the agency's settings and team
- Read identity documents and health data
These actions stay in the app, done by a person at the agency.
Importing data
Attach the file to Claude or paste the text: a supplier's price list or contract, the clients' spreadsheet or an export of your old software, a client's email, a supplier's voucher, the programme of a tour operator you work with, an old quote.
- Loading again updates, never duplicates: suppliers, rates and clients already there are recognised.
- Every detail the source gives goes in; what it does not say stays empty. At the end Claude says what was created, updated and left out, and why.
- A hotel is a supplier with its rates by room, board and occupancy.
Only import data you have the right to use. Photos do not go through Claude: you upload them in the Media tab of the supplier's card, confirming you have the rights.
Data and privacy
- What Claude reads from itinovo goes to Anthropic under your agency's contract with Anthropic.
- Identity documents (numbers and images) and health data never leave itinovo through the connector.
- Every action of Claude is in the agency's AI Log for 90 days, and the booking's history reads “via Claude”.
- References: Privacy notice · Terms, art. 19-bis · Data processing agreement · Sub-processors
Disconnecting
- Disconnect Claude in Settings → Integrations → Claude stops your own connection.
- Disable for the agency stops it for everyone; after a new activation each person connects again.
- In Claude you can also remove itinovo from your connectors.
- itinovo is published in Claude's connectors directory: Anthropic may remove it from the directory at any time.
Common problems
Claude says the connection is not complete
Check in Settings → Integrations → Claude that the agency has enabled Claude and that you pressed Continue with Claude.
Claude asks for a Client ID or a Client Secret
Leave the fields empty: itinovo recognises Claude by itself.
Claude says I don't have permission
Claude has your role: ask an administrator for the permission in the app, in Team › Roles.
Claude stops after many changes in a row
The connector accepts up to 120 changes a minute: wait a moment and try again, or split a long list into several requests.
Does it work with Claude Code?
Not yet: the connector is for claude.ai and the Claude desktop and mobile apps.
Need help?
Write to us, we answer in your language. To report a security vulnerability: security@itinovo.com.
Claude is a trademark of Anthropic, PBC. The connector is by Itinovo S.r.l.