iqavaiqava
Sign inGet started

By module

Automations & AI

No-code rules that react to what happens across your modules: when an event fires, check conditions, then raise an alert. Start from a sample, tweak it, and it's live.

Best use case

Catching the things a human would otherwise have to watch for — a large binding that needs reinsurance confirmed, a claim reserve that should be escalated, a bordereaux posted and awaiting review.

How an automation works

Every automation follows the same shape — a trigger, optional conditions, and an action:

Trigger (when)Conditions (if)Action (then)

The trigger is a domain event — a policy bound, a claim registered, a treaty bound, a bordereaux posted, an assignment completed. The conditions narrow it down (e.g. only when the premium is at least a threshold); all conditions must match. The action raises an alert with a severity, a title and a message. Titles and messages can include {tokens} from the event — like {reference} or {insuredName} — which are filled in when the rule fires.

Build a rule

  1. New automation
    Open Automation Studio and choose New automation.
  2. Pick the trigger
    Choose the event to listen to; the available tokens update to match it.
  3. Add conditions (optional)
    Add one or more field / operator / value rows. Leave empty to fire on every event.
  4. Compose the alert
    Set severity (Info, Warning, Critical), a title and a message, using tokens.
  5. Enable and save
    Enable it to go live, or save disabled to review first.

Start from a sample

You don't have to start from scratch. Start from a sample opens a gallery of ready-made automations spanning underwriting, claims, reinsurance and service delivery — flag large policy bindings, prioritise high-value claims, escalate high reserves, trigger recovery on large settlements, and more. Pick one, adjust the few values (like the threshold), and save. It becomes a normal rule you can edit or disable.

Tip

Samples are seeded disabled so you can review the threshold and wording before enabling them.

Export & import

Any automation can be exported to a portable JSON file from its row in the studio, and importedback into any workspace. This is how you move a rule you've refined into another workspace, share it with a colleague, or keep a versioned copy. Imported rules arrive disabled for review, and the file is validated on import — only recognisable iqava automation files are accepted.

Export → .automation.jsonMove / edit / storeImport → reviewEnable

The AI copilots

Alongside the rules engine, AI copilots are grounded on your data — claims triage, reconciliation assistance, and the intake and marketplace agents. Automations and the AI copilots are available as a paid add-on on any plan; see pricing.

Best practice

Keep alert messages specific and actionable — name the record and the next step (“confirm reinsurance”, “notify reinsurers”) so the person who receives it knows exactly what to do.

Documentation overview