Weekdone

Weekdone is the OKR and weekly status reporting tool. Agents post plans, progress, and problems with comments and likes, create and update objectives and key results, log KPIs, and read the weekly report for any team or user.

Verified 37 actions OAuth available

Weekdone website Capability data verified 2026-08-24

The weekly reporting deadline approaches and the reporting run opens

Search Items reads what each team has already written for the current week

Get Report and List Users show which people and teams have filed nothing yet

Update Key Result writes the progress figures that come from systems rather than from people

Agent pulls this week's metric values from the source systems

Agent compares each value against the recent history of its KPI and flags what does not fit

The metrics owner confirms the outliers before any value is recorded into the series

What This Integration Enables

Weekdone is where a company writes down what it believes about itself. The plans, progress and problems in a weekly report are claims made by people, and the objectives and key results above them are commitments. That distinction matters more here than in a task tool, because the whole value of the product is that leadership reads it as the team's own account of the week. An agent that writes into it is speaking in somebody else's voice, and the design of every workflow on this page follows from that.

FlowRunner agents post and update report items across the built-in and custom columns, comment and react on them, hand work over through the assignment route, maintain objectives and their key results, keep tag status lines current for whole workstreams, and read the full period report for any team or person. They also do the mechanical work the product is bad at making people do: writing progress that a system already knows, and surfacing who has not filed while there is still time to file. Every one of these operations is built and verified against the Weekdone official API.

Two structural details shape how a flow should be written. Weekdone identifies reports by period code rather than by date, in week form for items and quarter form for objectives, so a flow that passes a date is usually accepted silently as the current period. And the reordering route takes the complete new order for a column, not a change to it, which makes it a full-replacement write dressed up as a sort.

Without FlowRunner

Status assembled by hand People retype numbers they already reported elsewhere, and the report is late because of it

OKRs drift from the systems Key result progress is updated when somebody remembers, so the review discusses a stale number

Chasing is a manual round Somebody works out who has not filed and messages them individually every week

With FlowRunner

Numbers arrive from their source Metrics and key result progress are written from the systems that hold them

Reviews open on current data The objective reflects where the work actually is, because the progress write runs on a schedule

Gaps surface before the deadline The people with nothing filed are known while there is still time to file

Use Case Scenarios

Key results that update themselves

An objective's key result is "reduce median first response time to under 4 hours". That number lives in the helpdesk, not in anyone's head. An agent reads it on a schedule, calls Update Key Result with the current progress, and adds a short objective comment naming the window the figure covers so the number in the review has provenance. When a key result has not moved for three weeks, the agent flags it to the objective owner rather than deciding anything about it. Weekdone's own company settings decide whether company, team and personal objectives are even switched on, so the agent reads Get Company Settings first rather than failing on a creation the account does not allow.
The Monday report that is already half written

Before the deadline, an agent reads Search Items for the current week and Get Report for the team, then compares against what the systems already know: shipped work from the engineering board, closed deals, resolved tickets. It drafts the progress column as items through Create Item, attributed to the person who did the work, and posts each person a summary in Slack asking them to confirm or edit before the report closes. The person still writes their own report. They just do not start from an empty column.
Workstream status without a status meeting

Set Tag Status writes a single line against a tag, which is how Weekdone summarizes a whole workstream rather than an item at a time. An agent maintains those lines from the underlying systems: the migration tag carries its current phase, the hiring tag carries open roles against target. Set Tag Priority marks the ones that need attention this week. A weekly rollup of the tag lines and the KPI values goes into Google Sheets for the board pack, so the same sentence appears in the tool and in the deck without anyone copying it across.

Human-in-Loop Highlight

Record KPI Value appends a number to a series, and that is the only thing it does. There is no operation that edits a recorded value and no operation that removes one. The only way to take a wrong number out of a KPI is Delete KPI, which deletes the KPI and its entire history along with it. A single bad write costs the whole series, and the series is what leadership has been reading trend lines from all year.

So a FlowRunner metrics agent does not record blindly on a schedule. It pulls the value, compares it against the KPI's recent history, and writes only when the number is plausible. When it is not, it stops and asks the metrics owner: "The revenue source returned 0 for week 202536, against a trailing average of 41,200. The source may have failed. Record it, hold this week, or investigate first?" A zero recorded on Monday morning because an upstream export was empty is not a small mistake in Weekdone. It is a permanent notch in the chart, and removing it means deleting everything. This is the digital andon cord working the way it should: the agent notices that something is wrong before the write, and pulls it.

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

Report Items

Search Items Reads the plans, progress and problems people write each week, for a given period.
Create Item Adds an item to somebody's weekly report. The type decides which column it lands in, and the priority is a traffic light rather than a scale.
Update Item Changes an item. Moving one between columns needs the period alongside the new type, because the move happens within a specific week's report.
Assign Item Moves an item onto another person's report, which is how work is handed over in Weekdone.
Delete Item Removes an item from a report.
Sort Items Reorders a whole column of one week's report. The list submitted is the complete new order, so anything omitted is not simply left where it was.

Item Comments

List Item Comments Reads the comments on one item.
Add Item Comment Comments on an item as the connected user, which is how a flow leaves context where the discussion already is.
Delete Item Comment Removes a comment from an item.

Item Likes

List Item Likes Reads who has liked an item.
Like Item Likes an item as the connected user, which is Weekdone's lightweight recognition.
Unlike Item Takes back the connected user's like on an item.

Objectives and Key Results

List Objectives Reads objectives with their key results for a quarter.
Create Objective Creates an objective at company, team or personal level. Whether each level is available is an account setting, so a flow reads the settings before assuming.
Update Objective Changes an objective's description.
Delete Objective Deletes an objective and every key result under it.
Add Key Result Adds a key result to an objective. Setting its progress is what keeps an OKR current without anyone opening Weekdone.
Update Key Result Changes a key result's description or its progress. The scheduled write behind an OKR that reflects the systems rather than somebody's memory.
Delete Key Result Removes a key result from an objective.

Objective Comments

List Objective Comments Reads the comments on an objective.
Add Objective Comment Comments on an objective as the connected user. Useful for recording where an automated progress figure came from.
Update Objective Comment Rewrites a comment on an objective.
Delete Objective Comment Removes a comment from an objective.

KPIs

List KPIs Reads the account's KPIs with their current values.
Create KPI Creates a KPI, with display type and precision as presentation settings rather than validation.
Update KPI Changes a KPI's description or display settings. It does not set the value.
Record KPI Value Records a new value for a KPI. This is the operation a metrics flow calls on a schedule, and the one this page's human gate exists for, because a recorded value cannot be edited or removed on its own.
Delete KPI Deletes a KPI and its history. The only way to remove a bad value, and the reason a bad value is worth preventing.

Account and Structure

Get Report Returns a whole period's report: every team, every person in it, their items, their weekly rating and the reviews left on them. The single read that answers what the company did this week.
List Teams Reads the account's teams, each carrying the address its report copies are emailed to.
List Users Reads the account's users with the teams they belong to and whether they administer them.
List Item Types Reads the report columns, built in and custom, which is how a flow learns the ids of a team's own types.
Get Company Settings Returns when reports are due, where they are emailed, the timezone, and which objective levels are switched on. Those flags decide whether an objective can be created at all.

Frequently Asked Questions

What can FlowRunner do with Weekdone?

FlowRunner agents can run Search Items, Create Item, and Update Item in Weekdone, plus 34 more actions.

Does connecting Weekdone to FlowRunner require OAuth?

Yes. Weekdone connects to FlowRunner with OAuth 2.0, so agents authenticate without handling raw credentials.

Can Weekdone trigger a FlowRunner workflow automatically?

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

Start building with Weekdone

Free plan, no card required. Connect in minutes.

Start Building Free Talk to us