0.9.0

Fergus runs on a connector we build and maintain ourselves, with 86 tools covering jobs, quotes, site visits, materials, customers and sites, enquiries, invoices, pricebooks, the calendar, tasks and notes.

It follows the shape of the work rather than the shape of the API: an enquiry becomes a quote, the quote becomes a job, the job splits into site visits that carry the labour and the materials, and those become an invoice.

Connecting is a pasted key

Fergus does not offer integrations like ours a sign-in-and-approve flow, so you create a personal access token in your own Fergus account and paste it into FloConnector. The token acts as the person who created it, so if a tool comes back refused for permissions, it is that person's access you need to widen.

Quoting, end to end

A quote can be built, priced, published, marked as sent, then accepted or declined or voided, and superseded by a new version when the customer asks for a change. You can price a selection of optional sections without changing anything, which is the question customers actually ask, and you can build a section from a saved favourite instead of typing the lines out again.

What Fergus does not let anyone write

Two things are read only, and neither is our choice. Fergus publishes no way to create, edit or delete a time entry, so hours cannot be pushed in from any integration. Invoices are the same: you can read one in full, down to the line items, but raising, sending and paying stay in Fergus.

Notes are a smaller version of the same story. They attach to jobs, customers, quotes, sites, tasks, enquiries and works orders, but not to a site visit.

Tasks answer with an error even when they work

Fergus currently reports a server error on every task write except deleting one, then applies the change anyway. Left alone that is worse than a plain failure, because the natural response is to try again and you end up with three copies of the same task.

So we do not report it as a failure. You are told the change almost certainly went through, told not to retry, and pointed at the tool that confirms it. We have raised it with Fergus.

Rate limits are per company, and shared

Fergus allows one hundred requests a minute per company, counted across every integration on the account rather than per key. We stay inside it for you, and when it genuinely runs out you are told when it clears instead of the request hanging.