Bloom Growth

Bloom Growth, formerly Traction Tools, runs the meeting and accountability rhythm of teams on the EOS / Traction methodology. Agents manage rocks, to-dos, issues, scorecards and meeting agendas so weekly Level 10 meetings reflect what actually happened.

97 actions Session available

Bloom Growth website Platform Documentation Capability data verified 2026-08-18

The scorecard week turns over, ahead of the leadership team's weekly meeting

Get Current Week returns the week identifier every score has to be recorded against

Agent pulls the week's actual numbers from the systems that hold them

Record Score writes each measurable's number for the week

List Measurable Scores compares the week against the target and the direction it is measured in

The misses and the rocks now off track are posted to the leadership channel before the meeting

The team lead decides which misses become issues on the list, and who gets added to the room

What This Integration Enables

Bloom Growth, formerly Traction Tools, encodes a methodology rather than offering a blank canvas. Level 10 meetings, rocks, issues, headlines, the scorecard, and the accountability chart are the objects, and their meanings are not negotiable. That opinionated shape is the reason teams choose it, and it is also the reason automating it is worth doing: when the vocabulary is fixed, an agent can be held to it precisely.

FlowRunner agents keep the inputs of that rhythm true. They read the scorecard week and write the week's numbers from the systems that actually produced them, keep rocks and milestones honest about their status, raise issues on the right meeting's list, assign the seven-day commitments the methodology calls todos, and read the accountability chart to work out who owns what. The point is not to run the meeting. The point is that the ninety minutes goes to the discussion instead of to reading numbers aloud.

Two properties of this API deserve to be in the design rather than discovered at runtime. Every operation runs as the person whose sign-in the connection uses, with their permissions, so what a flow can see is exactly what that person can see. And several routes have no inverse: an attendee can be added to a meeting but not removed, a todo cannot be reassigned after it is created, and a measurable's owner cannot be changed. Those gaps are where the human gate belongs, and they are named on each capability below rather than left to be found.

Without FlowRunner

The first twenty minutes go to data entry Numbers are read out and typed in while the meeting waits

Scores arrive from memory A measurable gets whatever number somebody recalls, because the source system is elsewhere

Rocks drift quietly A quarterly priority slips for six weeks before anybody notices at a meeting

With FlowRunner

The scorecard is filled before the meeting starts Numbers come from the systems that produced them, written against the right week

Misses arrive already framed The team sees which measurables missed, by how much, and which rocks moved off track

The rhythm holds without policing Milestones, todos, and issue lists are kept current by a flow rather than by a facilitator

Use Case Scenarios

The scorecard fills itself before the meeting

An hour before the weekly leadership meeting, the agent calls Get Current Week, because Bloom Growth records scores against a week identifier rather than a date and getting that wrong writes a real number into the wrong column. It then pulls each measurable's actual figure from where it lives: pipeline from HubSpot, cash and receivables from QuickBooks Online, delivery counts from a sheet in Google Sheets. Record Score writes each one. List Measurable Scores then reads the trend rather than the single week, because a measurable that has missed three weeks running is a different conversation from one that missed once. The summary posts to Slack with the misses named and the direction of travel attached.
Rocks that report their own status

Each rock is a quarterly priority owned by one person, broken into milestones with due dates. The agent reads List Rock Milestones weekly and compares each milestone against the delivery evidence in Jira Issues. Where the evidence says a milestone is complete and the milestone says otherwise, it proposes the update rather than making it, because the owner's judgment of done is the one the methodology cares about. Where a milestone's due date has passed with no movement, the agent uses Create Meeting Issue to raise the concern on the right meeting's list so it gets discussed rather than noticed later. At quarter end, Set Rock Archived closes the quarter cleanly, which keeps the history readable through List Archived Rocks instead of deleting it.
Commitments that survive the room

During the meeting, todos are agreed and typed. Afterward, the agent reads List Meeting Todos and mirrors each one into the tool its owner actually works in, then watches for completion evidence there. When a todo is done, Set Todo Complete ticks it off in Bloom Growth so next week's meeting starts from a true list. When a todo has been open past its seven days, the agent does not silently reassign it, because this API publishes no way to reassign a todo at all. It surfaces the aging commitment to the owner and to the team lead, and lets them decide whether it becomes an issue, gets recommitted, or gets dropped.

Human-in-Loop Highlight

Add Meeting Attendee is a one-way door. This API publishes no route to take an attendee back out, so removing somebody from a Level 10 meeting has to be done by hand in the Bloom Growth interface. That makes adding a person to a leadership meeting one of the few genuinely unrecoverable writes on the connector, and it is a write with social weight: who sits in the room is a statement about who is accountable, and an agent inferring it from an org sync will eventually infer it wrong.

So a FlowRunner agent keeps every meeting's issues, headlines, todos, rocks, and scores current without asking, and stops at the door: "The HR feed shows two new directors reporting into Operations. Adding them to the Ops Leadership L10 cannot be undone through the API, only in the Bloom Growth interface. Add both, add one, or leave the attendee list alone?" The team lead answers. The same discipline covers Delete Meeting, which takes the issues, headlines, and todos hanging off it, and Delete Rock, which takes its milestones and where Set Rock Archived is almost always the operation actually wanted. What makes this safe is not that the agent is cautious in general. It is that the gate sits precisely where the API stops offering a way back.

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

97 actions

People and orientation

Get Current User Returns the person the sign-in details belong to. Every operation that scopes to mine means this person.
Get User Returns one person by their identifier.
List Viewable Users Returns everyone the signed-in person is allowed to see. It is the widest people list the API offers and the source a picker is built from.
List Direct Reports Returns the people reporting to someone, defaulting to the signed-in person's own reports.
List User Seats Returns the seats a person holds on the accountability chart. A seat carries a position and the roles under it.
List My Positions Returns the positions the signed-in person holds on the accountability chart.
Get Current Week Returns the scorecard week the account is currently in. Scores are recorded against a week identifier, so this is read before any score is written.
Search Searches across everything the signed-in person can see, which is the quickest way to turn a name into an identifier.
Search Users Searches only the people the signed-in person can see.

Level 10 meetings

List Meetings Returns the Level 10 meetings someone attends, defaulting to the signed-in person's own. The meeting is the container everything else hangs off.
Get Meeting Returns one Level 10 meeting by its identifier.
Create Meeting Creates a Level 10 meeting. Adding yourself while creating it is usually what is wanted, since a meeting you cannot see is difficult to fill.
Update Meeting Renames a Level 10 meeting.
Delete Meeting Deletes a Level 10 meeting. A meeting owns its issues, headlines, and todos, so what still hangs off it is worth checking first.
List Meeting Attendees Returns the people attending a meeting.
Add Meeting Attendee Adds a person to a meeting. This API publishes no route to take an attendee back out, so removal has to be done in the Bloom Growth interface, which is why this operation sits behind the human gate.
List Meeting Issues Returns the issues on a meeting's list, optionally narrowed to one attendee.
Create Meeting Issue Raises an issue directly on a meeting's list.
Remove Meeting Issue Takes an issue off a meeting's list. The issue itself survives and can be placed elsewhere.
List Meeting Headlines Returns the headlines shared at a meeting, optionally narrowed to one attendee.
Create Meeting Headline Shares a headline at a meeting. A headline is a short piece of good or bad news that does not need discussion.
Remove Meeting Headline Takes a headline off a meeting.
List Meeting Todos Returns the todos assigned at a meeting, optionally narrowed to one attendee.
Create Meeting Todo Assigns a todo at a meeting. In this methodology a todo is a seven-day commitment, so a due date inside the week is the norm.
List Meeting Rocks Returns the rocks tracked at a meeting, optionally narrowed to one attendee. A rock is a quarterly priority.
Create Meeting Rock Creates a rock directly on a meeting, owned by one person.
Set Rock On Meeting Attaches an existing rock to a meeting, or takes it off. A rock can be tracked at more than one meeting.
Set Rock On Business Plan Puts a rock on the meeting's business plan, or takes it off. The business plan is the long-term view a quarterly rock can be promoted onto.
List Meeting Measurables Returns the measurables on a meeting's scorecard, optionally narrowed to one attendee.
Set Measurable On Meeting Puts an existing measurable on a meeting's scorecard, or takes it off. A measurable can appear on more than one scorecard.

Issues

List Issues Returns the issues someone owns across every meeting, defaulting to the signed-in person's own.
Get Issue Returns one issue by its identifier.
Create Issue Raises an issue on a meeting's list. Every issue belongs to a meeting, so one has to be named.
Update Issue Changes an issue's title, owner, or compartment. Short-term issues are worked at the weekly meeting; long-term ones are parked for the quarter.
Set Issue Complete Marks an issue solved, or reopens it.
Move Issue To Meeting Moves an issue onto a different meeting's list.
Set Issue On Vision Moves an issue onto the vision document's issues list, or brings it back to the meeting.
Get Issue Notes Returns the notes attached to an issue, as a rendered editor document rather than plain text.

Rocks and milestones

List Rocks Returns the rocks someone is accountable for this quarter, defaulting to the signed-in person's own.
List Archived Rocks Returns the rocks someone has archived, which is how earlier quarters are reviewed.
Get Rock Returns one rock by its identifier.
Create Rock Creates a rock without attaching it to any meeting. Attaching it afterward, or creating it on a meeting directly, are the two ways it becomes visible in the rhythm.
Update Rock Changes a rock's title, owner, or status. On track and at risk are the two statuses that carry the week-to-week signal.
Delete Rock Permanently deletes a rock with its milestones. Archiving is almost always the operation actually wanted when a quarter simply ends.
Set Rock Archived Archives a rock at the end of a quarter, or restores it. Archived rocks stay readable through the archived listing.
Get Rock Notes Returns the notes attached to a rock, as a rendered editor document rather than plain text.
List Rock Milestones Returns the milestones on a rock, which are how a quarterly priority is broken into checkable steps.
Create Milestone Adds a milestone to a rock. Both the title and the due date are required, because a milestone without a date cannot be tracked.
Get Milestone Returns one milestone by its identifier.
Update Milestone Changes a milestone's title, due date, or status. Setting the status to done is how a milestone is ticked off.
Delete Milestone Removes a milestone from its rock.

Todos

List Todos Returns the todos someone owns across every meeting, defaulting to the signed-in person's own.
Get Todo Returns one todo by its identifier.
Create Todo Creates a todo without attaching it to any meeting. Raising one on a meeting's list is the other route.
Update Todo Changes a todo's title or due date. This API publishes no way to reassign a todo, so its owner is fixed once it is created.
Set Todo Complete Ticks a todo off, or reopens it.
Get Todo Notes Returns the notes attached to a todo, as a rendered editor document rather than plain text.

Headlines

List Headlines Returns the headlines someone has shared, defaulting to the signed-in person's own.
Get Headline Returns one headline by its identifier.
Update Headline Rewrites a headline.
Delete Headline Permanently deletes a headline.
Get Headline Notes Returns the notes attached to a headline, as a rendered editor document rather than plain text.

Scorecard

Get Scorecard Returns a scorecard for a meeting or for a person, defaulting to the signed-in person's own. It is the weekly numbers view.
List Measurables Returns the measurables someone owns. A measurable is one tracked number with a weekly target.
Get Measurable Returns one measurable by its identifier.
Create Measurable Creates a measurable. The direction and the target together decide whether a week's number counts as a hit.
Update Measurable Changes a measurable's name, target, direction, or units. Unlike the create route it has no owner field, so reassigning a measurable has to be done in the Bloom Growth interface.
List Measurable Scores Returns every week's number for one measurable, which is how a trend is read rather than a single week.
Get Score Returns one week's score by its identifier.
Record Score Records a week's number, either against a known score identifier or against a measurable and a week. Reading the current week first is what keeps a number out of the wrong column.

Accountability chart

Get Seat Returns one seat on the accountability chart, which is a place in the structure rather than a person.
Delete Seat Removes a seat from the accountability chart.
List Seat Users Returns the people sitting in a seat. More than one person can share one.
Set Seat User Puts a person in a seat, or takes them out.
Add Seat Direct Report Makes a person report into a seat, which is how the chart's hierarchy is built.
Get Seat Position Returns the position a seat holds. A position is the job title; the roles under it are what the job actually owns.
Set Seat Position Names the position a seat holds.
Delete Seat Position Removes the position from a seat, leaving the seat itself in place.
List Seat Roles Returns the roles a seat owns. In this methodology a seat should own about five.
Add Seat Role Adds a role to a seat.
Get Role Returns one role by its identifier.
Update Role Renames a role.
Set Role Deleted Deletes a role, or restores one that was deleted.

Teams

Create Team Creates a team.
Get Team Returns one team by its identifier.
Update Team Renames a team.
List Team Members Returns the people in a team.
Set Team Member Adds a person to a team, or takes them out.

Documented processes

List Processes Returns the documented processes, optionally within one folder. A process is a written procedure that can be run as a checklist.
List Process Folders Returns the folders processes are filed under.
Get Process Returns one process by its identifier.
List Process Steps Returns the steps a process is made of, as written rather than as run.
Execute Process Starts a run of a process, turning the written procedure into a live checklist somebody works through.
List Execution Steps Returns the steps of a running process with their completion state, which is how progress through a live checklist is read.
Set Process Step Complete Ticks a step of a running process off, or reopens it.

Quarterly conversations

List Quarterly Conversations Returns the quarterly conversations, which are the scheduled reviews between a person and their manager.
Get Quarterly Conversation Returns the recorded content of one quarterly conversation.

Frequently Asked Questions

What can FlowRunner do with Bloom Growth?

FlowRunner agents can run Get Current User, Get User, and List Viewable Users in Bloom Growth, plus 94 more actions.

Does connecting Bloom Growth to FlowRunner require OAuth?

No. Bloom Growth connects to FlowRunner with session-based authentication, no OAuth flow required.

Can Bloom Growth trigger a FlowRunner workflow automatically?

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

Start building with Bloom Growth

Free plan, no card required. Connect in minutes.

Start Building Free Talk to us