AroFlo Booking Forms

Choose the AroFlo credential bookings use, test it and watch the request limit

4 min read AroFlo booking form

Settings in the AroFlo Bookings menu opens AroFlo Bookings settings, and its first page, AroFlo Credentials, is the AroFlo account every form books into. The credential is used to read your calendar and create clients, locations and tasks from bookings.

Before you start

You need an AroFlo credential. The token is made in AroFlo, under Site Admin, AroFlo API, and saved on the AroFlo integration. Connecting AroFlo with Formpiece covers making it. AroFlo shows a token once, and it ends on the day chosen when it was made.

Step by step

  1. Open Settings, then AroFlo Credentials.
  2. Under AroFlo Credential, pick the credential. Create new AroFlo credential adds another one on the integrations page.
  3. Click Update AroFlo credential. The page says "AroFlo credential updated". If the credential was already chosen it says "The AroFlo credential is already set to this one."

A credential that has lapsed is listed with "(needs connecting again)" after its name.

AroFlo API token details

Once a credential is chosen, this card summarises its token. The saved token is never shown. To replace it, click Manage token and paste a new one on the AroFlo integration.

  • A badge beside the credential name reads Connected, Not confirmed, Needs connecting again or Token expired. Connected is shown only when the booking service has confirmed the token works.
  • Token ends shows the end date and how many days are left, or how long ago it expired. AroFlo doesn't tell Formpiece when a token ends, so the date is the one entered on the integration. The days left turn red within 30 days, and Needs attention on the dashboard warns at the same point. If no date was entered the page says "No end date was given."
  • Test Connection asks AroFlo whether it accepts the token and shows the answer. If AroFlo can't be reached the page says "The AroFlo API could not be reached."

What this token is allowed to do

A token has the same access as the AroFlo user who made it. Test Connection checks view access only (clients, locations, tasks, scheduling, users, invoices and payments), and lists each as Allowed or Not allowed.

Create rights are not tested, because that would make a record in AroFlo. A booking needs to create clients, contacts, locations and tasks, edit scheduling and add documents and notes. Payments need Invoices and Payments create. Bookings never set a price on the task, so pricing visibility isn't needed.

AroFlo request limit

AroFlo allows 120 requests a minute and 5,000 a day for the whole AroFlo site. Bookings share that with lead forms and any other tool that uses the AroFlo API. A booking uses about 8 requests.

The card shows how many requests have been used today, when the day's count starts again and how many are left this minute. It shows a dash until AroFlo has reported a count, which happens on its next call. Limit near appears at 80% of the day's requests and Almost reached at 95%. Needs attention on the dashboard says the same, and at 95% adds that bookings stop until the count starts again.

When it goes wrong

Test Connection says AroFlo did not accept the token

The token was revoked, mistyped or has ended. Make a new token in AroFlo and replace it under Manage token.

The badge says Token expired

The end date entered on the integration has passed. Nothing can be sent to AroFlo until a new token is made in AroFlo. AroFlo can't renew a token.

A permission shows Not allowed

The AroFlo user who made the token can't view that kind of record. Make the token as a user who can.

Bookings stop with the limit used up

Lead forms and every other tool on the AroFlo site count towards the limit as well. Bookings carry on when the count starts again. The time is shown under Request limit.

"Could not update the AroFlo credential."

The choice could not be saved. Try again.

"Your AroFlo settings could not be loaded."

Reload the page. Nothing has been changed.