Sellsy

Sellsy is a French suite that puts prospecting, CRM, and billing in the same product, and this integration takes a clear position on where an agent belongs inside it. It manages the commercial layer end to end: companies, contacts, individuals, opportunities, tasks, and catalog items are fully writable, with Search Companies and Search Opportunities doing server side filtering by name, type, status, pipeline, step, and creation date range. Then it stops at the accounting documents. Invoices are read through Get Invoices and Get Invoice, and the only write is Validate Invoice. Estimates are read through Get Estimates, and the only write is Update Estimate Status. This connector does not create invoices and does not create estimates.

That boundary is the interesting part, and it is a feature rather than a shortfall. A billing document is authored where the numbering, the tax treatment, and the accounting rules live, which is inside Sellsy. What an agent is genuinely good at is everything around it: resolving the right third party, opening the deal, keeping the catalog in step, assembling the evidence that an order is real, and moving a prepared document to its next state at the moment that becomes true rather than at the end of the week. Some practical facts that decide whether a flow works. Authentication uses a Sellsy API v2 OAuth client configured on the developer page of your account, and the connector exchanges its Client ID and Client Secret for a bearer token at the Sellsy token endpoint using the client credentials grant, so there is no interactive consent step and no user redirect; tokens carry a 3600 second lifetime and are renewed automatically shortly before expiry, and an optional Scopes setting narrows what the client may do. All calls target the v2 API. Plain Get actions return records sorted but unfiltered, so the Search actions are the ones to reach for when a flow needs a subset. Paging uses offset and limit with a default of 25 per page, and each list returns { data, pagination } where pagination carries limit, total, count, and offset, so the next page is read by adding the number of records already seen to the offset. Required fields on create are specific: a type and name for a company, a last name for a contact, a type and last name for an individual, a name plus a pipeline, a step, and a related third party for an opportunity, a related object for a task, and a type plus a reference for a catalog item. Select the pipeline before the step, because steps belong to a specific pipeline. Opportunities attach to a Company, Individual, or Contact, while tasks accept a wider set including Opportunity, Invoice, Estimate, and Item. Several status values keep Sellsy's original spelling on the wire, for example a Cancelled status travelling as cancelled, and the dropdowns map readable labels to those exact values. Since August 2024 each Sellsy account numbers its own objects independently, so a record id is unique within an account and not across accounts, which matters if a flow spans two of them. Delete Company, Delete Contact, and Delete Opportunity are permanent. This connector ships no triggers and registers no webhook subscription, so change detection is a scheduled Search Companies or Search Opportunities call filtered on a creation date range.