Hive
Project ManagementManage Hive projects from AI agent workflows. Agents create projects and actions (Hive's tasks), update statuses, assignees, and due dates, and look up workspace members to route work across a Hive workspace.
What This Integration Enables
A Hive board is a set of promises with names and dates on them, and its usefulness collapses the moment it stops matching reality. Keeping it matched is exactly the work nobody was hired to do. FlowRunner agents take that job: they feed the board from every system where work actually originates, move actions as the work progresses elsewhere, and publish the board's state to the people who need it without anyone compiling a report. - Create actions from form submissions, support tickets, and CRM records, assigned and dated on arrival - Keep projects and boards in sync with external systems by listing and creating projects programmatically - Update an action's status, assignees, title, or due date as work moves through a pipeline - Resolve workspace members to user IDs so routing lands on people, not guesses - Export project and action data into spreadsheets and push progress notifications to chat Every operation scopes to a workspace, and a single connection can work across several by overriding the workspace per call, which suits agencies running one flow across many client workspaces. One intake flow, one reporting sweep, one completion gate, applied uniformly across every client without duplicating the automation per workspace. The status writes that announce progress are where FlowRunner's [human-in-the-loop](/concepts/human-in-the-loop) step stands guard.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Bug reports that arrive already triaged
A [Typeform](/integrations/typeform) bug report form fires. The agent classifies the report, resolves the right project with List Projects and the on-call owner with List Users, and calls Create Action with the title, severity in the description, the assignee, and a due date derived from the severity. The reporter's submission becomes a routed board item in under a minute, and reports the classifier is unsure about go to the project lead instead of guessing.
The board that follows the work
Delivery happens across systems: a pull request merges, a document gets client approval, an invoice is paid. Each event reaches the agent, which finds the linked action via List Actions and patches exactly the fields that changed with Update Action, a status ID from List Statuses, a new due date, an added assignee. Moves into a Done column post a completion note to [Slack](/integrations/slack). The standup opens a board that is already true.
The Friday snapshot without the Friday ritual
On a schedule, the agent walks each project with List Actions, joins statuses from List Statuses, and writes the full board state into [Google Sheets](/integrations/google-sheets): open items per column, overdue actions with owners, items untouched for two weeks. The digest posts to the leadership channel with the exceptions on top. The ops lead reads the outliers instead of assembling the report.
Human-in-Loop Highlight
Update Action moving a task into a Done status looks like bookkeeping, but on a client-facing board it is a public claim: this deliverable is finished. In FlowRunner delivery flows that move is wired to consequences, a completion note in the client's channel, the next dependent action starting its clock, so a false Done does not just mislabel a column, it tells a customer something untrue and sets downstream work in motion on a fiction. The agent therefore treats Done differently from every other column. It can move work into To Do and In Progress on signal alone, but when the evidence says finished, it posts: "PR merged and deploy succeeded for 'Migrate checkout API'. Mark Done on the Acme board and notify the client channel?" The delivery owner confirms, because they know what merged code does not: whether the client considers it delivered. Machine speed for the bookkeeping, human judgment for the claim.
Agent Capabilities
8 actionsProjects
3- List Projects Lists a workspace's projects, each grouping related actions with its own statuses. The routing step for intake flows.
- Create Project Creates a project in a workspace, returning its generated ID. Used when new engagements or clients need their own board.
- List Statuses Lists the workspace's action statuses, the board columns such as To Do, In Progress, and Done. The lookup that turns a column name into a status ID for updates.
Actions
4- List Actions Lists actions in a workspace, optionally filtered to one project, with title, assignees, status, and due date. The sweep behind snapshots and matching.
- Get Action Retrieves one action in full, including description, assignees, status, due date, and project. The context read before any update.
- Create Action Creates an action in a project with a title, optional assignee user IDs, and a due date. The intake write that turns requests into board items.
- Update Action Updates only the fields supplied: title, assignees, status, and due date. The status write this page's human gate exists for when the destination is Done.
Users
1- List Users Lists workspace members with ID, name, and email. The resolution step that turns a name into an assignable user ID.
Frequently Asked Questions
What can FlowRunner do with Hive?
FlowRunner agents can run List Projects, Create Project, and List Actions in Hive, plus 5 more actions.
Does connecting Hive to FlowRunner require OAuth?
No. Hive connects to FlowRunner with an API key, no OAuth flow required.
Can Hive trigger a FlowRunner workflow automatically?
Hive doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with Hive
$100 in credits. No card required. Connect in minutes.