Steady

Steady, formerly Status Hero, runs asynchronous team check-ins, goals and activity. Agents read and post check-ins, track goals and pull team activity so standups and status roll-ups happen without a meeting.

37 actions API key available

Steady website Platform Documentation Capability data verified 2026-08-18

The weekly goal review window opens on a schedule

The agent pulls the current figure from the system that actually holds it

List Goal Updates shows what was last reported on this goal, and when

The agent compares the new figure against the target and against the previous update

The goal owner receives the assembled evidence and the three confidence labels Steady accepts

The owner picks On Track, At Risk or Off Track, and only then does Create Goal Update post it

What This Integration Enables

Steady, which teams may still know as Status Hero, replaces the standup with a written record: check-ins, goals and a digest the team reads instead of attending a meeting. That makes it an unusual integration target, because almost everything an agent writes here is read by colleagues as a statement about their work rather than as data. The connector reflects that. The read surface is wide, covering check-ins, comments, reactions, action items, digests, Echoes and activities, while the write surface is deliberately narrow.

The write worth building flows around is Create Activity. It records work done in a tool Steady does not integrate with, so a deploy from GitHub, a resolved escalation from Zendesk or an overnight batch that finished clean lands in the same digest as everything Steady collects itself. The other write with real weight is Create Goal Update, because a goal's progress and confidence are read-only on the goal and derived entirely from its updates. Steady normalizes confidence to exactly three labels, On Track, At Risk and Off Track, which is precisely the kind of judgment FlowRunner's human-in-the-loop design exists to keep with a person.

Without FlowRunner

Status written twice People report progress in a meeting, then retype it into the tool

Work outside the integrations is invisible A deploy, an escalation or a finished batch job never reaches the team digest

Confidence set by whoever remembers The label on a goal moves when someone thinks to move it, not when the number does

With FlowRunner

Evidence gathered before the ask The numbers arrive with the update request instead of being looked up during it

Every system feeds the digest Work done in tools Steady does not integrate with still shows up beside the ones it does

The label stays a human call The agent proposes and the owner declares, so a public judgment has a named author

Use Case Scenarios

The work nobody logs becomes visible

An agent watches the systems that do the actual work. A release finishes in GitHub, an incident is closed in PagerDuty, a nightly reconciliation completes in the ERP. Each one becomes a Create Activity call with its group, a one-line description and a link back to the source. The team's digest then reads as what the team did, not as what the tools Steady happens to integrate with did. Because Steady fills in the kind, the title, the person and the timestamp itself, the agent supplies only the three fields it genuinely knows.
Blocked people get found the same morning

Each morning the agent calls List Check Ins with Blocked enabled, scoped to the teams that matter. Steady spells its array filters with brackets and silently returns everything when they are sent bare, which is exactly the failure that turns "the Engineering team is blocked" into "the company is blocked"; the connector sends the bracketed form so a team-scoped report stays team-scoped. Whoever is blocked, and what they said they are blocked on, posts to the team lead in Slack alongside the open action items from List Action Items. The lead unblocks people before lunch instead of reading about it on Friday.
A goal moves because a number moved

A goal tracks a metric that lives somewhere else entirely, in a warehouse table or a billing system. Weekly, the agent reads the real figure, calls List Goal Updates to see what was last claimed, and assembles the delta with its source. That package goes to the goal owner with the three confidence labels attached as choices. The owner picks one. Create Goal Update posts it, which is what actually moves the goal's progress and confidence, and the agent adds nothing else. If the owner asks for the previous week's update to be corrected rather than superseded, the agent uses Update Goal Update, because deleting an update quietly changes the progress the goal reports.

Human-in-Loop Highlight

Create Goal Update is the operation that moves a goal, and Steady's confidence field is not a number the agent can average its way into. It normalizes to exactly three values, and the one that gets written appears next to a team's name in a digest the whole company reads. Declaring a goal At Risk is an assertion about colleagues' work, and it is one that lands under the goal owner's name. So the agent stops before it. It posts: "Q3 activation goal: target 4,200, current 3,315 as of this morning, up 190 since last week's update which was labeled On Track. At this rate the target is missed. Post as On Track, At Risk, or Off Track?" The owner answers and the update goes out. The agent did every piece of work that a person would have done badly, which is the lookup, and none of the work only a person can do, which is the judgment. The same reasoning is why the agent never calls Create Echo unattended: an Echo starts asking the entire team a recurring question, and nobody should be able to do that by accident.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via preferred channel

Human decides

Agent resumes with decision

Agent Capabilities

37 actions

Account

Get Current Person Returns the person the access token belongs to. The quickest check that a connection works and that it acts as the right individual.
List People Lists the people in the account, filtered by team where needed. Used to resolve who a check-in or goal actually belongs to.
Get Person Returns one person's profile.
List Teams Lists the teams in the account, which is where the identifiers for every team-scoped filter come from.
Get Team Returns one team with its details.

Check Ins

List Check Ins Lists check-ins, filtered by team, person, date or blocked status. The Blocked filter is the one that turns a status tool into an early warning system.
Get Check In Returns one check-in with what was reported.
Update Check In Changes a check-in. Used to correct or enrich a record rather than to author somebody's status for them.
List Check In Comments Lists the comment thread on a check-in.
Comment On Check In Leaves a comment on a check-in, which notifies whoever wrote it. Worth treating as a message to a colleague, because that is what it is.
List Check In Reactions Lists the reactions on a check-in.
List Digest Returns the rolled-up digest for a period. The read behind any report that answers "what did the team do this week".
List Action Items Lists the action items raised across check-ins, which is where commitments made in writing are tracked.
Get Action Item Returns one action item.

Goals

List Goals Lists goals, filtered by team or owner. The starting read for any goal review flow.
Get Goal Returns one goal with its derived progress and confidence.
Create Goal Creates a goal with its title, dates, owner and teams.
Update Goal Changes a goal's title, dates, owner, teams and archived state. It cannot change progress or confidence, because those are derived from the goal's updates.
Delete Goal Deletes a goal along with its update history.

Goal Updates

List Goal Updates Lists the updates behind a goal, which is what its reported progress is actually calculated from.
Create Goal Update Posts an update to a goal. This is the operation that moves progress and confidence, and the one this page's human gate sits on.
Get Goal Update Returns one goal update.
Update Goal Update Corrects an existing update. The safe way to fix a mistake, because it leaves the goal's history intact.
Delete Goal Update Removes an update, which changes the progress the goal reports because it was one of the inputs. Correcting is usually the better call.
List Goal Update Comments Lists the comment thread on a goal update.
Comment On Goal Update Comments on a goal update, notifying whoever posted it.
List Goal Update Reactions Lists the reactions on a goal update.

Echoes

List Echoes Lists the recurring questions Steady asks the team on a schedule.
Get Echo Returns one Echo with its schedule and question.
Create Echo Creates a recurring question that Steady will start asking the whole team. Consequential enough that flows should treat it as a deliberate act, not a side effect.
Update Echo Changes an Echo's question or cadence.
Delete Echo Stops an Echo and removes it.
List Echo Answers Lists the answers a recurring question has collected, which is the raw material for any sentiment or blocker trend.
Get Echo Answer Returns one answer to an Echo.

Activities

List Activities Lists the activity stream Steady has collected, across its own integrations and anything a flow has contributed.
Get Activity Returns one activity record.
Create Activity Records work done in a tool Steady does not integrate with, so it appears in the team's digest alongside everything else. The write worth designing flows around.

Frequently Asked Questions

What can FlowRunner do with Steady?

FlowRunner agents can run Get Current Person, List People, and Get Person in Steady, plus 34 more actions.

Does connecting Steady to FlowRunner require OAuth?

No. Steady connects to FlowRunner with an API key, no OAuth flow required.

Can Steady trigger a FlowRunner workflow automatically?

Steady doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with Steady

Free plan, no card required. Connect in minutes.

Start Building Free Talk to us