Automations

An automation in BNDRY is a runnable unit of compliance work — a job the platform executes on your behalf so that checks, orchestrations, and downstream integrations don't sit on a person's to-do list. Automations live alongside workspaces and forms in your tenant configuration, and you can see what's available to run from the platform's Automations area.

An automation is the definition; an automation execution is the running instance. When you run an automation, BNDRY creates an execution and tracks its state from start to finish. Executions can take longer than a single request to complete and may pause part-way through to request input from a human.

Why automations exist

Compliance work is repetitive, sequenced, and easy to get wrong when it's done by hand. Screening a new customer, recalculating a risk rating after a change of circumstances, verifying an identity document, kicking off a periodic review — each of these is a series of steps that has to happen the same way every time, with a defensible record of what ran and why.

Automations exist to operationalise those workflows. They run the checks, orchestrate the sequence, and feed the outcomes into the rest of the platform — into the entity's risk rating, into tags, into the audit trail. Because each execution is tracked as its own resource with a clear state and timestamps, you also get the answer to the question every auditor eventually asks: when did this run, what did it do, and what was the outcome.

How automations relate

Automations are the "doing" layer of the platform. They run checks, orchestrate sequences, and produce outcomes that show up elsewhere: a risk rating on an entity, a tag applied to an individual or company, an event emitted to your downstream systems.

When it finishes, the result is recorded against the individual, company, or other resource it was acting on, and the execution itself remains queryable as part of that resource's history.