--- title: "Blue Integration" description: "Blue is project and work management built around records on workspaces, with custom fields and views per project. Agents create and update records, manage projects, tags and assignees, and keep Blue in step with the systems where work originates." url: https://flowrunner.ai/integrations/blue date_modified: 2026-09-04T14:21:17-07:00 --- # Blue [Project Management](https://flowrunner.ai/integrations/category/project-management-productivity) Blue is project and work management built around records on workspaces, with custom fields and views per project. Agents create and update records, manage projects, tags and assignees, and keep Blue in step with the systems where work originates. 51 actions · API key · available [Blue website](https://blue.cc/) · [Platform Documentation](https://blue.cc/) · Capability data verified 2026-08-18 1. An order, ticket or signup lands in the system that owns it 2. Agent reads the fields the Blue board tracks for that kind of work 3. Search Records looks for a record already covering it, so the board does not gain a duplicate 4. Create Record opens it in the intake list, or Update Record refreshes the one that exists 5. Move Record advances it into the list its current state belongs in 6. Agent reports which of the board's own automation rules fired on that move 7. When a rule moved the record somewhere nobody expected, the board owner decides whether to pause it ## What This Integration Enables Blue is work management built around records on workspaces, where a workspace is a board and a list is a column. The connector's shape says something about what Blue is for. Fifty-one operations cover the record lifecycle you would expect, but a large share of them are reads over Blue's own reporting and governance layer: dashboards and their charts, saved reports that can be run on demand and return rows, saved views, forms that let somebody outside the account create a record, and the board's automation rules. Blue expects the board to be looked at, not just worked in. FlowRunner agents write into that board from the systems where work actually starts, and they read out of the reporting layer so a number that used to require someone opening a dashboard can drive a decision instead. What deserves attention when you build here is that a Blue board acts on its own. Rules move records without an agent asking, which means an agent is never the only actor on the board. That is the reason this connector's [human-in-the-loop](https://flowrunner.ai/concepts/human-in-the-loop) step sits over Blue's own automation rules rather than over its records. Every action is built and verified against the Blue API. ### Without FlowRunner **Boards fed by copy and paste**: A record exists in the source system and again on the board, kept in step by whoever remembers **Reporting runs on a schedule nobody controls**: A dashboard shows what it last computed, and refreshing it means opening the interface **Automation rules are invisible until they misfire**: Nobody knows which rules will act on a record until one of them already has ### With FlowRunner **The board is written from the source**: Records are created, updated and moved by the system that owns the work **Reports run when the answer is needed**: Saved reports and charts are recomputed on demand and their rows read straight into the flow **Rule effects are reported alongside the write**: Every automated move the board makes on an agent's write is named in the same summary ## Use Case Scenarios ### The board reflects the system of record without anyone retyping A support escalation is raised in [Zendesk](https://flowrunner.ai/integrations/zendesk), or a pull request is opened in [GitHub](https://flowrunner.ai/integrations/github). The agent calls Search Records to see whether Blue already carries it, then Create Record or Update Record accordingly, and Set Custom Field Value to write the request type. Because which parameter carries a custom field value depends entirely on the field's type, the agent reads List Custom Fields first rather than guessing. Get GitHub Integration and List Record GitHub Links let it show the linked pull requests on the record, so the board says what state the work is in without a status meeting. ### Reporting that answers rather than displays The operations lead needs a number, not a dashboard. On a schedule, the agent calls Get Report Data to run a saved report and return its rows, uses Count Records to check volume on a large board cheaply rather than fetching every record, and calls Recalculate Chart where a chart needs to be current rather than waiting for its own schedule. It writes the results into [Google Sheets](https://flowrunner.ai/integrations/google-sheets) for trend history and posts the movers into [Slack](https://flowrunner.ai/integrations/slack). Anyone who wants the underlying view still has it, but the decision no longer waits for someone to look. ### Intake through a form, triaged before anyone sees it Blue's forms let people outside the account create records. The agent reads List Forms and Get Form to know the fields a form collects, then watches the intake list. New records get a first pass: Set Record Tags applies the classification, Create Checklist and Create Checklist Item add the steps that request type always needs, and Set Record Dependency links it to the work it is waiting on. Anything the agent cannot classify confidently is left in triage with a comment through Add Comment explaining what it could not decide, which is a better outcome than a confident wrong tag. ## Human-in-Loop Highlight An automation rule in Blue is somebody's process, written once and then relied on silently. When an integration agent starts writing records into a board, those rules fire on its writes, and the first sign of trouble is usually a record that moved somewhere nobody asked for. The agent can stop that immediately, because Blue ships the reversible option: Set Automation Enabled pauses a rule without touching its configuration. Delete Automation is the other one, and it is permanent, with no route anywhere in this API to read a deleted rule back or reconstruct what it did. So the sync agent pauses and reports rather than cleaning up. It posts: "Since this morning's import, 46 records I created in Intake were moved to Client Review within seconds. Rule Auto-advance new intake is doing it. I have paused it and the records are where I put them. Should I re-enable it, adjust the import to land in a different list, or does its owner want it deleted?" Somebody answers. The rule that gets deleted, if any, is deleted by the person who knows why it existed. 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 51 actions ### Organization and Workspaces 6 - **List Organizations** Retrieves the organizations the token can reach. Read first to find the identifier every other operation is scoped to. - **List Workspaces** Retrieves the workspaces in the organization. A workspace is a board, and almost everything else in Blue is scoped to one. - **Create Workspace** Creates a workspace, optionally from a template and inside a folder. Used to provision a per-client or per-initiative board on demand. - **List Lists** Retrieves the lists in a workspace. A list is what a board column is, and a record sits in exactly one. - **Create List** Adds a list to a workspace, which is how a stage is added to a board. - **List Users** Retrieves the people in the organization, or in one workspace. The read behind resolving an assignee. ### Records 13 - **List Records** Retrieves records, which are Blue's unit of work, filtered by list, assignee, tag or done state. - **Count Records** Counts records without fetching them, which is much cheaper on a large board and is what a threshold check should use. - **Search Records** Searches a workspace's records by free text. Narrower than the filtered listing, and the read that prevents duplicate creation. - **Get Record** Retrieves one record in full, which is the read a flow makes before a decision. - **Create Record** Creates a record. Supply either plain text or HTML for the description rather than both, because Blue stores one rendering. - **Update Record** Updates a record's title, description, dates, color, assignees or done state. Supplying assignees replaces the whole set, so a flow that means to add reads the current set first. - **Move Record** Moves a record into a different list, which is how progress is recorded on a Blue board. - **Delete Record** Permanently deletes a record with its comments, checklists and custom field values. - **Set Record Dependency** Links two records so one blocks or relates to the other, or removes that link. - **Add Comment** Adds a comment to a record. Used to record what an agent decided, or what it declined to decide and why. - **Set Record Tags** Sets which tags a record carries. This replaces the whole set rather than adding to it, so an empty list clears every tag. - **List Record Activity** Retrieves what has happened on one record, which is its audit trail. - **List Activity** Retrieves the activity feed of a workspace, optionally narrowed to one person or a date range. ### Checklists 3 - **Create Checklist** Adds a checklist to a record. A record can carry several, each with its own items. - **Create Checklist Item** Adds an item to a checklist, which is how a request type's standard steps land on the record automatically. - **Update Checklist Item** Renames a checklist item, ticks it off, or moves it. ### Tags and Custom Fields 4 - **List Tags** Retrieves the tags defined in a workspace. - **Create Tag** Creates a tag in a workspace. - **List Custom Fields** Retrieves the custom fields defined on a workspace, with their types and options. Read before writing a value, because the type decides which parameter carries it. - **Set Custom Field Value** Sets a custom field's value on a record. Which parameter to fill depends on the field's type, from plain text through numbers, checkboxes, single and multiple choice, and dates. ### Documents and Files 3 - **List Documents** Retrieves the documents in a workspace, optionally just the wiki ones. - **Get Document** Retrieves one document with its content. - **List Files** Retrieves the files uploaded to a workspace. ### Forms 2 - **List Forms** Retrieves the forms in a workspace. A form lets somebody outside the account create a record, which is how external intake reaches the board. - **Get Form** Retrieves one form with its fields, so a flow knows what an inbound record will carry. ### Dashboards and Reporting 9 - **List Dashboards** Retrieves the dashboards, optionally just one workspace's. - **Get Dashboard** Retrieves one dashboard with its charts. - **List Charts** Retrieves the charts on a dashboard. - **Recalculate Chart** Recomputes a chart's data on demand rather than waiting for its schedule, which is what makes a chart usable inside a flow. - **List Reports** Retrieves the saved reports. - **Get Report** Retrieves one report's definition. - **Get Report Data** Runs a saved report and returns its rows, optionally filtered and sorted further. The operation that turns a Blue report into an input rather than a screen. - **List Saved Views** Retrieves a workspace's saved views, which are the filters people switch between. - **Get Saved View** Retrieves one saved view with its filter, so a flow can reuse the team's own definition of a segment. ### Automations 3 - **List Automations** Retrieves a workspace's automation rules. The read that tells an agent what else will act on the records it writes. - **Set Automation Enabled** Turns an automation rule on or off without deleting it. The reversible way to stop a rule that is misbehaving. - **Delete Automation** Permanently deletes an automation rule. This is the operation the human gate on this page exists for, because nothing in the API reads a deleted rule back. ### Integrations 2 - **Get GitHub Integration** Retrieves how a workspace is connected to GitHub, if it is. - **List Record GitHub Links** Retrieves the GitHub issues and pull requests linked to a record, which is how a board shows engineering state without a status update. ### Webhooks 6 - **List Webhooks** Retrieves the organization's webhooks. - **Get Webhook** Retrieves one webhook by its identifier. - **Create Webhook** Subscribes an address to the organization's events. Leaving the event list empty subscribes to every event, which is a great deal of traffic on a busy organization. - **Update Webhook** Changes a webhook's address, name, events or workspaces, and is also how a disabled webhook is switched back on. - **Disable Webhook** Stops a webhook delivering without deleting it. - **Delete Webhook** Permanently removes a webhook. Disabling is the reversible alternative. ## Frequently Asked Questions ### What can FlowRunner do with Blue? FlowRunner agents can run List Organizations, List Workspaces, and Create Workspace in Blue, plus 48 more actions. ### Does connecting Blue to FlowRunner require OAuth? No. Blue connects to FlowRunner with an API key, no OAuth flow required. ### Can Blue trigger a FlowRunner workflow automatically? Blue doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger. **Work at Blue?** This integration exposes Blue to AI agents on every FlowRunner plan, including through MCP, at no cost to you. [See what FlowRunner offers integration partners](https://flowrunner.ai/integrations/partners), including how to keep this page current. --- Markdown version of https://flowrunner.ai/integrations/blue. Site index: https://flowrunner.ai/llms.txt