0.8.0

Connecteam runs on a connector we build and maintain ourselves, with 109 tools covering scheduling, the time clock, quick tasks, forms, jobs, users and smart groups, time off, pay rates, sales and chat.

It is the deskless side of a business that AI has been worst at reaching: who is rostered this week, who clocked what hours, which safety forms came back, what is still outstanding on the board.

Connecting is a pasted key

Connecteam does not offer integrations like ours a sign-in-and-approve flow, so an admin on your account creates an API key under Settings, API Keys, and pastes it into FloConnector. The key does not expire, and it carries full account access, so treat it accordingly.

That is the whole of it. Connecteam runs two data regions, global and Australia, and we work out which one your account is on from the key itself rather than asking you to know. If the key is refused, it is the key.

Your Connecteam plan decides which tools work

This is the one thing worth reading before you connect. Connecteam sells three separate hubs, Operations, Communications, and HR and Skills, and prices each one independently. Its API is opened per hub, by that hub's plan.

So if you have Operations on Expert and the others on a lower plan, the scheduling, time clock, jobs and task tools work, while the chat and time off tools are refused. That holds even when the feature is fully set up and you use it every day, because the gate is the hub's plan and not whether the feature is switched on.

When a tool is refused for that reason, the error now names the hub to raise, so you are not left guessing which of the three it is.

Rate limits are per account, and shared

Connecteam counts API requests per account rather than per key, and the allowance is small on its Small Business plan: five requests a minute and one hundred a day, shared with every other integration you run. Expert plans raise that considerably.

We stay inside it for you rather than letting calls fail, and when the allowance genuinely runs out you are told what the limit is and when it clears, instead of the request hanging.