Aptli

The service hub

The service hub is your organization's own Aptli instance. Once the website is paired with it, three things happen.

  • Events go to the hub. Every published event with a date or a location goes to the hub's community map and its timeline. Places can go too.
  • Hub forms come to your pages. Editors place the hub's forms, its forms directory and its community map on any page or post, as sections.
  • Residents get answers. A question box on a page answers from your website's own published content, written by the hub's AI.
  • Hub sections: the six section kinds that bring the hub onto a page.
  • AI answers: the question box, and the summary suggestion in the editor.
  • Community map: the website's public map and the map feeds behind it.

Pairing the website with the hub

Pairing takes one code from the hub. An administrator does it from Hub connection in the admin menu.

  1. Under Hub address, type your Aptli instance's address, such as https://yourtown.aptli.io. The address starts with https://.
  2. Press Open your hub. Your Aptli instance opens on its Service portal page.
  3. In Aptli, sign in as an administrator and run Connect a website/CMS. Aptli shows a 16-character pairing code. The code works once, for about ten minutes.
  4. Back in the CMS, paste the code under Pairing code and press Connect.

The website and the hub exchange a key between themselves, and it stays with them. A green box then reads Connected, with the hub's name.

How to set this up on the same screen opens these steps as a panel.

What the website sends

Two switches decide what goes to the hub.

  • Sync published content to the hub sends every published event with a date or a location. A change to the event, a restore or a bulk action sends it again.
  • Also sync places (visitor listings with locations) sends your places as well.

Only published content goes. A draft stays on the website. Each item keeps the result of its last delivery.

Checking the connection

Test connection sends one test event to the hub and reports the answer: Test ping delivered or the error the hub returned. The screen keeps the time and result of the last test.

The dot beside Hub connection in the admin menu shows the state at a glance:

  • not paired to a hub;
  • paired, with sending switched off;
  • the last delivery test failed;
  • connected and sending.

Entering the connection by hand

Advanced holds the connection's fields, for a hub you set up yourself. The API key comes from the hub, under Automations → API keys. The Ingest path is the hub address the website posts its events to. Press Save after changing either.

Who does what

Only administrators open Hub connection and change it. Editors place hub sections on the pages they edit. Residents need no account for anything a hub section offers.