Integrations · Automation

Build visual automations on Aptoria events with Make.

Aptoria connects to Make (formerly Integromat) so an event in the building — rent paid, work order created, lease signed — kicks off a scenario you draw on the canvas and fans out to anything Make can reach. Every trigger rides a signed webhook.

Beta

Beta, verify before relying

Make (Integromat) is conditional. Aptoria may prepare or stage the workflow, but a live external action should not be represented as complete until the provider has accepted it and the record has a receipt.

Review Make (Integromat) setup

All integrations

Visual scenario builder

Triggers + actions

Signed webhooks

Make · connected

Trigger

Work order created

Then

Notify + log row

Direction

Two-way

Delivery

Signed webhook

Illustrative — you draw the scenario from Aptoria’s triggers and actions.

Start a scenario from what happens in Aptoria

Aptoria exposes its domain events as Make triggers, so the moment something happens in the building a scenario can fire — no polling, no glue code. Each event carries the record it came from onto the canvas.

Rent paid, work order created, lease signed, and more

Fires the instant the event lands — no polling

Payload carries the unit, lease, and record link

Route and filter by property inside the scenario

Trigger module

Event

Work order created

Unit

Priority

Standard

Sent to

Make

Fan one event out to every app you run

Because a Make scenario chains modules on a canvas, a single Aptoria event can branch to many places at once — post to a chat channel, append a spreadsheet row, and open a ticket in your help desk from the same run.

Multi-step scenarios that branch and merge

Reach anything Make connects to or any webhook

Map and transform fields between the steps

Handle each event without writing code

Scenario

Work order created

Branch 1

Message vendor

Branch 2

Append to Sheets

Run

One trigger

Run actions back in Aptoria, logged like everything else

A Make scenario can also call into Aptoria to stage a maintenance ticket, add a note, or log a task. Every inbound action is delivered over an HMAC-signed webhook and recorded to the audit ledger with available verification context.

Create tickets, notes, or tasks from a scenario

HMAC-signed delivery with automatic retries

Actions respect the same permissions as the app

Every inbound action recorded to the audit ledger

Inbound action

From

Make scenario

Action

Stage ticket

Unit 4B

Logged

Audit ledger

Trust without theater

Verifiable, not vibes.

Three things you can check yourself — without a sales call, without a logo carousel.

Review cancellation and reversal scope before relying on it.

Eligible irreversible autonomous actions using Aptoria’s soft-commit workflow have a 15-minute cancellation window before execution. Undo is available only for actions marked reversible; completed provider or external actions may need a separate remedy.

Soft-commit scope

Decision records with available hash verification.

For organization-scoped decisions recorded through the current decision ledger, Aptoria can verify hash-chain structure and available content hashes. It is not an immutable external archive, complete legal record, or compliance certification.

Ledger scope

Human review remains part of consequential work.

Supported policy blocks keep defined action classes, including eviction filing, applicant denial, lease termination, and security-deposit deductions, out of autonomous execution. Product controls do not replace legal review or jurisdiction-specific advice.

Human-required floor

See exactly how we measure it

More integrations

Connect Make and automate the busywork visually.

Free for your first unit. Draw scenarios off Aptoria events and route reviewable actions back in Aptoria — over signed, logged webhooks.

Start free