# Workflows (https://riska.io/platform/workflows)

_Workflows_

## Your underwriting guidelines, enforced on every file.

Turn appetite, referral and pricing rules into workflows that run on every submission, endorsement and renewal. Underwriters see the exceptions. Clean risks move straight to quote at the rate you released.

## Your guidelines, written as a workflow.

A workflow is a trigger, a graph of steps, and the values each step hands to the next. The referral rules and renewal checklist your team is meant to follow become something that runs.

- **Start on the event that matters.**: Nine trigger kinds, from a new submission or one watched attribute changing value to a cron schedule or a signed webhook.
- **Branch the way your guidelines do.**: Drop blocks on the canvas and connect them. Filter, if / else and switch split the run into the paths a risk actually takes, so clean files go one way and referrals another.
- **Wire the values through.**: Every block publishes typed outputs. The picker offers only the steps that already ran, so a reference cannot point at a branch that never happened.
- **Runaway cycles, caught.**: The editor walks every workflow in the workspace and flags any whose own writes would re-fire its own trigger. You learn that before you enable it.

> "“The renewal chase used to be a calendar reminder and a spreadsheet. It is four blocks now, and nobody thinks about it.”" — Operations lead, Regional MGA · 12 states

## Start it from what your book already does.

Use an event your book already produces, such as a new submission, a changed limit or an approaching expiry, instead of building a new one.

### Record events.

A submission is created, a record is deleted, a single watched attribute flips value. The run receives the record and the change that caused it.

### Schedules.

Daily, weekly, monthly, or a cron expression in the timezone you name. The renewal sweep runs at six without anyone opening the app.

### Webhooks.

A signed URL your carrier or vendor can post to. Every environment gets its own secret, so a leaked test key cannot sign a production call.

### On demand.

Run it by hand while you are building it, or put it behind a command on the record so an underwriter fires it from the account in front of them.

## Thirty blocks, ten groups.

Enough to automate a referral, an endorsement or a renewal without writing a script.

- **Records**: Create, find, update or upsert, including a whole product record validated against the product.
- **Conditions**: Filter, if / else and switch send the run down the path this account actually takes.
- **Delays**: Pause for a fixed interval or hold until a date, then pick the run back up.
- **AI and agents**: Classify a record, summarize it, or hand it to an agent that gathers what it needs before it answers.
- **External calls**: Send an HTTP request and read the status, headers and body in the step after it.
- **Human steps**: Stop for an approval, a choice or a typed answer, then carry on with what the person said. A referral waits for the underwriter’s decision, not for someone to remember it.

## Every run, on the record.

Every run leaves a record of what it did, so a question about last Tuesday’s renewals has an answer.

### Every step, recorded.

One row per block, with its inputs, its outputs, its status and its duration. Loop iterations are recorded one by one, so you can see which of the forty went wrong.

### Resume at step four.

A failed run rewinds to the step that broke and carries on from there, on the definition it started with. It keeps its id, so the whole history stays in one place.

### Or start over on the fix.

Retry as new replays the original trigger against the current release, so a workflow you just corrected runs the corrected way. The new run points back at the one it came from.

## Workflows that read the live book.

Workflows read and write the same records your underwriters do. Nothing is exported, and nothing is a day old.

## Bring the process you run by hand.

The renewal checklist, the stale submission chase, the carrier email nobody remembers to send. We will build one of them on the call.