In breve
Sellsy: CRM e fatturazione francesi: aziende, contatti, opportunità, fatture, preventivi, articoli e pagamenti. REST API v2, credenziali client OAuth 2.0.
Configurazione guidata
Collega Sellsy a Microsoft Copilot in 2 minuti
Avvia la prova gratuita su AnythingMCP Cloud, collega Sellsy con la configurazione guidata e aggiungi il tuo URL MCP a Microsoft Copilot. Senza codice e senza server da gestire.
Nessuna carta di credito · 7 giorni di prova · Alternativa self-host disponibile
Prova a chiedere
Prompt di esempio per Sellsy
Clicca su un prompt per copiarlo. Incollalo in Claude, ChatGPT, Cursor, Gemini, Copilot o OpenClaw per eseguirlo contro questo connettore.
Claude è un'AI e può sbagliare. Verifica sempre le risposte.
💡 Niente installazione? Vai direttamente su cloud.anythingmcp.com. Accedi, clicca Connectors → Sellsy, inserisci le credenziali, genera una MCP API key — fatto. Niente Docker, niente
git clone, niente server locale.
Sellsy + Microsoft Copilot
Sellsy: CRM e fatturazione francesi: aziende, contatti, opportunità, fatture, preventivi, articoli e pagamenti. REST API v2, credenziali client OAuth 2.0.
Prerequisiti
Le istruzioni di setup complete sono incluse nel connettore stesso (visibili nello store quando lo selezioni). Le variabili d'ambiente richieste sono:
SELLSY_CLIENT_ID, SELLSY_CLIENT_SECRET
Step 1 — Ottieni le credenziali
Getting credentials
- Sign in to Sellsy, open Paramètres → API and create an application in the developer area.
- Choose the client credentials flow — it authorises the application against your own account with no browser consent step. You receive a client id and client secret.
- Set
SELLSY_CLIENT_IDandSELLSY_CLIENT_SECRET. AnythingMCP mints and refreshes the access token on its own.
This is API v2, at https://api.sellsy.com/v2. Sellsy's v1 was an entirely different, single-endpoint RPC API — if you find an example that POSTs everything to one URL with a request parameter, that is v1 and it does not apply here.
…(continued in the in-app connector instructions)
Step 2 — Installa l'adapter
curl -fsSL https://raw.githubusercontent.com/HelpCode-ai/anythingmcp/main/docker-compose.quickstart.yml -o docker-compose.yml
printf 'JWT_SECRET=%s\nENCRYPTION_KEY=%s\n' "$(openssl rand -hex 32)" "$(openssl rand -hex 32)" > .env
docker compose up -d
Step 3 — Aggiungi il connettore in Microsoft Copilot
L'URL del tuo server: in AnythingMCP apri MCP Servers → il server su cui si trova questo connettore e copia il suo URL (
https://cloud.anythingmcp.com/mcp/…). Usalo ovunque questa guida mostraYOUR_SERVER_ID.
Microsoft Copilot usa i server MCP tramite gli agenti creati in Copilot Studio: aggiungi AnythingMCP a un agente come strumento, poi pubblichi l'agente in Microsoft 365 Copilot e in Teams. Copilot Studio si collega dal cloud di Microsoft via Streamable HTTP, che AnythingMCP supporta.
- In Copilot Studio apri il tuo agente (o creane uno), vai su Tools e scegli Add a tool → New tool → Model Context Protocol.
- Inserisci un Server name (per esempio
AnythingMCP), una Server description che dica cosa fa il connettore e il Server URLhttps://cloud.anythingmcp.com/mcp/YOUR_SERVER_ID. Copilot Studio usa la descrizione per decidere quando chiamare il server. - Come autenticazione scegli API key, imposta Type su Header e come nome dell'header
X-API-Key, poi seleziona Create. - In Add tool scegli Create a new connection, incolla una chiave API MCP di AnythingMCP (MCP Servers → il tuo server → API keys) e seleziona Add to agent.
- Provalo nel riquadro Test dell'agente: chiedi qualcosa che richiede i tool di
Sellsy. - Seleziona Publish, poi Channels → Microsoft 365 and Microsoft Teams, lascia selezionato Make agent available in Microsoft Copilot e scegli Add channel. See agent in Teams lo installa per te; in Microsoft 365 Copilot scrivi @ e scegli l'agente.
Preferisci un accesso per ogni utente? Al posto della chiave API scegli OAuth 2.0 → Dynamic discovery: ogni persona accede ad AnythingMCP la prima volta che l'agente lo chiama.
Usi il self-hosting? Usa l'indirizzo HTTPS pubblico della tua istanza al posto di https://cloud.anythingmcp.com. Copilot Studio si collega dal cloud di Microsoft, quindi localhost non funziona.
Tool disponibili
| Tool | What it does |
|---|---|
sellsy_list_companies | List client companies with their name, SIRET, VAT number, address and owner |
sellsy_search_companies | Search companies with Sellsy's filter object — far more expressive than the plain list |
sellsy_get_company | Read one client company in full: addresses, contacts, tax identifiers, rating and the notes recorded against it |
sellsy_list_contacts | List individual contacts with their name, e-mail, phone, position and the company they belong to |
sellsy_list_invoices | List invoices with their number, date, due date, client, net and gross totals and payment status — the receivables view |
sellsy_search_invoices | Search invoices with Sellsy's filter object — by status, date range, client or amount |
sellsy_get_invoice | Read one invoice in full: every row with its quantity, unit price, discount and VAT, the totals and the payments applied against it |
sellsy_list_estimates | List estimates (devis) with their number, date, client, total and acceptance status — what is out with prospects and not yet won |
sellsy_list_opportunities | List CRM opportunities with their name, client, amount, funnel step and expected close date — the pipeline view |
sellsy_list_items | List catalogue items with their reference, name, unit price, VAT rate and stock tracking flag |
sellsy_get_contact | Read one contact (person) in full: name, email and phone numbers, position, note, addresses, owner, archive state and custom fields |
sellsy_list_contact_companies | List the companies a contact is linked to |
sellsy_edit_contact | Change fields of a contact |
sellsy_edit_company | Change fields of a company |
sellsy_create_company | Create a company (a client, prospect or supplier) |
sellsy_list_company_contacts | List the contacts (people) linked to a company, with name, e-mail, phones, position and their roles at the company |
sellsy_link_contact_to_company | Link an existing contact to a company, optionally with roles (e.g. ["main", "invoicing", "dunning"]) |
sellsy_list_company_addresses | List the addresses of a company (invoicing, delivery and others) with their ids, for use as invoicing_address_id or delivery_address_id on… |
sellsy_create_company_address | Add an address to a company |
sellsy_get_company_custom_fields | Read the custom field values of a company: field id, name, type and value |
sellsy_update_company_custom_fields | Set custom field values on a company |
sellsy_list_company_files | List the directories and files attached to a company (contracts, scans, exports), with file ids for sellsy_get_file |
sellsy_list_individuals | List individuals (private persons who are clients, prospects or suppliers in their own right, unlike contacts who belong to a company) with… |
sellsy_search_individuals | Search individual with Sellsy's filter object (a POST that only reads) |
sellsy_get_individual | Read one individual in full: name, contact details, type, addresses, owner and notes |
sellsy_create_individual | Create an individual (a private person as client, prospect or supplier) |
sellsy_edit_individual | Change fields of an individual |
sellsy_search_contacts | Search contact with Sellsy's filter object (a POST that only reads) |
sellsy_create_contact | Create a contact (a person, usually working at a company) |
sellsy_get_opportunity | Read one opportunity: name, status, pipeline and step, amount, probability, due date, source, related company or individual, contacts… |
sellsy_search_opportunities | Search opportunity with Sellsy's filter object (a POST that only reads) |
sellsy_create_opportunity | Create an opportunity in a pipeline step for a company or individual |
sellsy_update_opportunity | Partly update an opportunity, e.g. mark it won or lost, change its amount or due date |
sellsy_move_opportunity_step | Move an opportunity to another step of its pipeline (the kanban move), optionally placing it before another opportunity |
sellsy_list_opportunity_pipelines | List the opportunity pipelines (sales funnels) with their ids and names |
sellsy_list_pipeline_steps | List the steps of one pipeline in order, with id, name, rank and default probability. embed opportunities_number adds how many… |
sellsy_list_opportunity_sources | List the opportunity sources (where leads come from: website, trade fair, referral...) with their ids |
sellsy_list_opportunity_categories | List the categories that group opportunity sources; embed sources returns the sources of each category |
sellsy_get_estimate | Read one estimate (devis) in full: number, date, expiry date, status, related parties, rows with quantity, price and VAT, totals and the… |
sellsy_search_estimates | Search estimate with Sellsy's filter object (a POST that only reads) |
sellsy_create_estimate | Create an estimate (devis) as a draft |
sellsy_update_estimate_status | Change the status of an estimate, e.g. to accepted when the client signed or refused when they declined |
sellsy_create_invoice | Create an invoice as a draft (it gets its final number when validated with sellsy_validate_invoice) |
sellsy_validate_invoice | Validate a draft invoice: it gets its definitive number, can no longer be edited and is due |
sellsy_list_invoice_payments | List the payments recorded on one invoice: amount, date, payment method and status |
sellsy_list_invoice_credit_notes | List the credit notes linked to one invoice (refunds and corrections), with number and amounts |
sellsy_list_invoice_files | List the directories and files attached to one invoice, with file ids for sellsy_get_file |
sellsy_list_credit_notes | List credit notes (avoirs) with number, date, client, amounts and status (draft, stored, partialspend, spent, cancelled) |
sellsy_search_credit_notes | Search credit note with Sellsy's filter object (a POST that only reads) |
sellsy_get_credit_note | Read one credit note in full: rows, totals, status, related parties and the invoices it refers to |
sellsy_list_orders | List sales orders (bons de commande) with number, date, client, amount, status and delivery status (order_status: none, wait, picking… |
sellsy_search_orders | Search order with Sellsy's filter object (a POST that only reads) |
sellsy_get_order | Read one sales order in full: rows, totals, status, delivery status and related parties |
sellsy_list_deliveries | List delivery notes (bons de livraison) with number, date, client and delivery status |
sellsy_list_payments | List payments received or made, with amount, currency, paid date, payment method, status and the documents they settle |
sellsy_search_payments | Search payment with Sellsy's filter object (a POST that only reads) |
sellsy_get_payment | Read one payment: amount, date, method, status, number and the documents it is allocated to |
sellsy_list_payment_methods | List the payment methods of the account (transfer, card, cheque, direct debit...) with their ids for payment_method_ids on documents |
sellsy_get_item | Read one catalogue item: type, reference, name, description, reference price, purchase price, VAT, unit and accounting codes |
sellsy_search_items | Search item with Sellsy's filter object (a POST that only reads) |
sellsy_create_item | Create a catalogue item (product or service) |
sellsy_edit_item | Change fields of a catalogue item |
sellsy_get_item_prices | Read the prices of an item per rate category (price lists), with amounts with and without tax |
sellsy_list_taxes | List the VAT rates (taxes) of the account with id, rate and label, for tax_id on items and document rows |
sellsy_list_units | List the units of measure (piece, hour, day, kg...) with their ids, for unit_id on items and rows |
sellsy_list_currencies | List the currencies available on the account, with code and symbol |
sellsy_list_payment_terms | List the payment terms of the account (on order, 30 days, end of month...) with their ids, for payment_terms on invoices and estimates |
sellsy_list_rate_categories | List the rate categories (price lists such as retail or wholesale) with their ids |
sellsy_list_custom_fields | List the custom field definitions of the account: id, name, code, type, options and which objects they apply to |
sellsy_list_tasks | List tasks (to-dos) with title, due date, status (todo or done), label, priority, assignees and the record they belong to |
sellsy_search_tasks | Search task with Sellsy's filter object (a POST that only reads) |
sellsy_get_task | Read one task: title, description, due date, status, label, priority, reminders, assignees and the related record |
sellsy_create_task | Create a task (to-do) on a record, e.g. a follow-up call on a company |
sellsy_update_task | Update a task, e.g. set status done, move the due date or reassign it |
sellsy_list_task_labels | List the task labels (types such as call, e-mail, meeting) with their ids, for label_id when creating tasks |
sellsy_list_comments | List comments (notes left on companies, contacts, opportunities and documents) with text, author, date and related record |
sellsy_search_comments | Search comment with Sellsy's filter object (a POST that only reads) |
sellsy_create_comment | Add a comment (note) to a record, e.g. a summary of a call on a company or opportunity |
sellsy_list_calendar_events | List calendar events (meetings, appointments) with title, start and end, label, participants and related record |
sellsy_search_calendar_events | Search calendar event with Sellsy's filter object (a POST that only reads) |
sellsy_get_calendar_event | Read one calendar event: title, description, start and end, all-day flag, label, participants and related record |
sellsy_create_calendar_event | Create a calendar event (meeting or appointment), optionally linked to a record and with participants |
sellsy_update_calendar_event | Update a calendar event, e.g. move it or change its title |
sellsy_list_calendar_event_labels | List the calendar event labels (meeting, call, demo...) with their ids, for label_id when creating events |
sellsy_list_crm_activity | Read the CRM activity feed: e-mails, calls, meetings, comments and other events logged on records, with date, author and label |
sellsy_list_staffs | List the staff members (users of the Sellsy account) with id, name, e-mail and status |
sellsy_get_staff | Read one staff member |
sellsy_list_teams | List the teams of the Sellsy account (groups of staff members) with their ids and members |
sellsy_get_file | Read one file attached in Sellsy: name, size, type, the record it belongs to and its download link |
sellsy_list_subscriptions | List subscriptions (recurring invoicing plans) with client, frequency, amounts and next invoice date |
sellsy_get_subscription | Read one subscription (recurring invoicing plan); embed payment_installments adds its installments |
sellsy_search | Search the whole account by text, like the search bar: companies, individuals, contacts, opportunities, items, documents and staff |
sellsy_get_quotas | Read the API quotas of the account: requests allowed and used in the current windows |
FAQ
Per quale Copilot vale? Per Microsoft 365 Copilot in azienda, tramite gli agenti di Copilot Studio. L'app Microsoft Copilot per account personali non permette di aggiungere un proprio server MCP.
Cosa mi serve? Un account di lavoro con accesso a Copilot Studio (licenza o prova) per creare l'agente. Chi lo usa in Microsoft 365 Copilot o in Teams deve avere accesso all'agente: condividilo, oppure chiedi a un amministratore di pubblicarlo per l'organizzazione. Se la tua organizzazione applica criteri sui dati ai connettori di Power Platform, valgono anche per i server MCP.
L'agente non chiama i tool. Controlla che il nome dell'header sia esattamente X-API-Key e che la chiave appartenga allo stesso server MCP dell'URL, e scrivi una Server description precisa: Copilot Studio la usa per decidere quando chiamare il server. Dopo ogni modifica pubblica di nuovo l'agente; in una chat già aperta scrivi "start over" per passare alla nuova versione.
Prossimi passi
- Landing del connettore
- Collegare a Claude
- Collegare a ChatGPT
- Collegare a Cursor
- Collegare a Gemini
- Collegare a Meta Muse
Questa guida ti è stata utile?
