Workflows: from a low score to a Jira ticket

Most low scores are read by someone, eventually. Workflows make sure they are acted on, on time, by the right person.

Build it on the canvas

A workflow starts with a trigger — a response arriving, a score dropping, a schedule. Add a condition (“Workload under 6”), a wait (“24 hours, skip weekends”) and an action (“Create a Jira issue in OPS”). Each step comes from the integrations your workspace has installed.

Every run is on record

Open Runs to see each execution step by step: what triggered it, which branch it took, and what the connected system answered. A failed step is retried and the failure is kept, so nothing disappears silently.

Start from a recipe

Seven recipes ship ready to copy: escalate low scores, follow up on low scores, post tool complaints to Slack, thank people who answered, a weekly comments digest, check in with new people, and close the loop. Or describe the workflow to Ask Polzy and it drafts one on the canvas for you to review.