SlimCRM

SlimCRM is a Vietnamese product for small and medium businesses that decided not to be only a CRM. Customers, contacts, and leads sit next to projects, tasks, milestones, support tickets, expenses, and invoices, which means the same system holds the deal, the delivery, and the money. That is a genuinely useful shape for a business too small to run three tools and too organised to run none, and it makes SlimCRM one of the better places for an agent to work, because the record it needs next is usually already there.

The thing to understand before designing a flow is that the write surface narrows as you move through that lifecycle, and the connector reflects that faithfully rather than papering over it. Customers, contacts, and leads have the full set, create, read, update, and delete. Projects, tasks, support tickets, and milestones can be created and deleted but not updated through this connector. Expenses can be created and searched. Invoices and staff are read only. So an agent here is very good at getting things started and at reading the whole picture, and deliberately limited at revising delivery records in flight, which is worth designing around rather than discovering halfway through a rollout. Operationally, authentication uses an API token created inside SlimCRM under System, then Settings, then API Management, sent on every request as the authtoken header rather than as a bearer token or a query parameter. The API Management menu is hidden by default and SlimCRM support enables it per account, and each token carries an expiry set when it is created. The API is bound to a whole installation, so one token covers the account, and because SlimCRM is tenant hosted you supply your own instance base URL, for example https://crm.slimsoft.vn/your-account, with every route built under /api. Create, update, and delete requests submit fields as multipart form data, and optional or account specific fields that are not exposed as named parameters go through the Additional Fields object. Delete operations use the /api/delete/{resource}/{id} path shape, which the connector handles for you. Reads return the record or an array directly while writes return a {status, message} envelope, and a logical failure can arrive as an HTTP 200 body with status:false or as an HTTP 404, both of which this connector inspects and raises so an automation exception surfaces rather than passing as a quiet success. Fields such as lead source, lead status, task priority, project status, department, and billing type are numeric ids configured per account, so they are plain inputs and the Customers, Staff, Expense Categories, Payment Modes, and Tax Rates dictionaries resolve related ids where your instance exposes them. This connector ships no triggers and registers no webhook subscription with SlimCRM, so change detection is a scheduled Search call on the resource you care about. A flow written on the assumption that SlimCRM will notify FlowRunner when a ticket is raised will never run.