0.11.0

AroFlo runs on a connector we build and maintain ourselves, with 72 tools covering jobs, clients and sites, quotes, invoices, bills, purchase orders, work orders, scheduling, timesheets, inventory, assets and the people on your site.

Every one of those tools has been run against a live AroFlo site, and every tool that writes was checked by reading the record back afterwards. Several of the notes below exist because of what that turned up.

Connecting is four pasted values

AroFlo does not offer integrations like ours a sign-in-and-approve flow, so you copy four values from Site Administration, Settings, General, AroFlo API and paste them into FloConnector. They act as the AroFlo user they belong to, so if a tool comes back refused, it is that person's access you need to widen.

If someone changes that user's AroFlo username, the credentials stop working and have to be copied again. You are told that specifically rather than being shown a generic failure.

Asking for a date now includes that date

A filter like "invoices dated on or after 1 July" was quietly leaving out 1 July itself, and everything else you asked for on the day you named. Ask for jobs due from today and you got nothing back, with no sign that anything had gone wrong.

AroFlo has no way to express "on or after" directly, so the connector now works around it. All 24 date filters that say "on or after" include the day you name. This is a change in results, not just wording: if you had been asking for the day before to work around it, you will now get one extra day.

Reading a busy site without exhausting it

AroFlo allows 2,000 requests a day per site, counted across every integration on the account rather than per connection. Re-reading everything to find what changed is the one habit that will spend it.

So the tools carry a "changed since" filter, and there is a separate feed that lists what has changed across the whole site and costs nothing against the daily allowance. Each response tells you how much of the day's budget is left. Related records come back in the same request rather than a second one, so pulling a job's labour, materials and totals costs one request, not four.

What AroFlo does not let anyone write

Quotes are readable in full, down to the line items, but building, sending and approving one stays in AroFlo. Timesheets are the same: hours can be read, sorted and totalled, but not pushed in. Payments, contacts and site locations are read only.

Nothing can be deleted through this connector, because AroFlo's API provides no way to delete anything at all. Saved message templates can be created but not edited.

Two things AroFlo does that we tell you about

Updating a work order requires a status, even when the status is not what you are changing. Send the one it already has, and the rest of your change applies.

A work order's required-by date reads back a day earlier than you set it, because AroFlo records it against your site's local midnight and returns it in UTC. The date is right; the way it reads is not. We do not quietly adjust it, since the correction depends on where your site is, and a silent adjustment would be harder to spot than a visible one. Purchase order delivery dates are unaffected.