Integrations and Automations

Admin › Integrations holds everything that moves data in and out of Aptli, and every rule that acts on its own. It is one tree with two sides:

• Outside systems: each system you connect, its connections, and under each connection the rules and devices that use it.
• Inside Aptli: each module's built-in behaviours and the rules you add to them.

Any · Outside · Inside, the first button in the toolbar, shows one side or both. A name opens its editor in a window: a rule, a connection, a system or a built-in behaviour.

Status and health

A row's Status says whether it is on. Health reports the worst problem on the row: runs that failed in the last 24 hours, open alarms, or a push connection with no key. A problem in a row further down shows outlined on the rows above it. Press a chip for the actions that deal with what it reports, such as Show activity or Show alarms. Filters can show Only problems.

Connecting a system

New connection walks through connecting an outside system, in either direction.

• Coming in: an inbound source reads from another system, such as a JSON feed over HTTP, an RSS feed, an ArcGIS or OGC service, or a PostgreSQL or SQL Server database, on a schedule. Devices and sensors send their readings to a connection of their own.
• Going out: a connection sends Aptli's changes to another system, by calling its web address, writing to its database, or delivering a file.

The arrow beside the create button adds an inbound source directly, or Connect a website or CMS to pair a website with Aptli.

Your plan includes a number of connections. Each connection counts once, and so does an API key that stands on its own. The count menu shows how many are in use.

Rules

A rule has three parts:

1. When: what starts it. A record is created or changes status, a timer runs out, a schedule comes round, a reading or an inbound event arrives.
2. If: conditions on the record or the event, such as priority is high or status is completed.
3. Then: what it does. Rules can create a job, a work order, an assignment or a help request, update a field, run a calculation, start a response timer, send a notification, call another system, write to a database, or deliver a file.

A delivered file can be JSON, CSV, GeoJSON, PDF, Excel or XML, sent to a folder, S3-compatible storage, SFTP, an email address or a web address. It can carry the record that started the rule, or a saved report run at that moment.

New rule opens an empty rule. New rule here, in a row's ⋯, starts one already attached to that connection or behaviour. A row's ⋯ also holds History, Changes, Send a test, Clone, Turn on, Turn off and Delete.

Tick rules to turn them on or off together, or to delete them.

Keys, sources and activity

The count menu shows the totals and opens three windows:

• Activity: every run, what started it, what it did and whether it worked.
• Keys and credentials: the API keys other systems use to send data in, and the stored passwords, tokens and database logins Aptli uses to reach them. A stored secret never shows again once saved. It can only be replaced.
• Inbound sources: every feed Aptli reads from.

Access, in the same menu, sets who can use automations.

Other pages' rules

Some pages carry rules of their own, built in a window on that page, such as reminders set on a work order. They appear here too, under Inside Aptli, with everything else that runs by itself.