ProofHub

Manage ProofHub projects from FlowRunner. Agents create tasks from inbound events, update dates, assignees, and completion status, organize work into task lists, review discussion topics, and resolve account members for assignment.

9 actions API key available

ProofHub website ↗ Platform Documentation ↗ Capability data verified 2026-07-28

A new work request lands from the intake form or the ticket queue

List People resolves the assignee's user id from the account roster

List Task Lists finds the right list in the client's project, or Create Task List opens one for a new phase of work

Create Task opens the task with title, description, start and due dates, assignees, and labels

The assignee gets a chat message with the ticket number and due date

A nightly sweep compares status in the external systems against List Tasks and stages the differences

The project lead reviews staged bulk updates, because assignee and label writes replace the existing lists outright

Update Task applies the approved changes, and only the approved changes

What This Integration Enables

ProofHub's pitch is one place for project work: projects hold task lists, task lists hold tasks, and the team stops living in five tools. The catch is that work does not arrive in ProofHub; it arrives in forms, inboxes, and ticket queues, and the gap between "requested" and "on the board" is where things get lost. FlowRunner agents work that gap. They turn inbound events into properly filed tasks, keep dates and completion status synchronized with the systems where work actually happens, and pull the whole picture into reports. - Create tasks from form submissions, tickets, and other inbound events, filed to the right project and task list - Keep tasks in sync with external systems: dates, labels, and completion status - Gate bulk task rewrites with [human-in-the-loop](/concepts/human-in-the-loop) review before assignments change hands - Organize incoming work by creating task lists that group related tasks within a project - Report on projects, lists, and tasks in spreadsheets and dashboards

Without FlowRunner

Requests arrive everywhere but the tool Work comes in through forms, email, and chat, and someone has to retype it into ProofHub before it officially exists

Status synced by standup The task board says what it said last time somebody remembered to update it, so standups spend their time reconciling

Assignments resolved by asking Figuring out who should own a task means knowing the team roster by heart or interrupting the person who does

With FlowRunner

Every request becomes a task at arrival Inbound work lands in the right project and task list with dates, labels, and a resolved assignee, within minutes

The board tracks the other systems External completions and date changes flow into ProofHub on a schedule, with a person approving anything that rewrites assignments

Reporting reads from live tasks Projects, lists, and task status flow into standing reports without anyone compiling them

Use Case Scenarios

The intake form that files its own work

Client requests arrive through [Typeform](/integrations/typeform). For each submission, the agent calls List People to resolve the right owner's user id, finds the client's project and the active task list, and opens the task with Create Task: title from the request, due date from the SLA, labels for the request type. The requester's form confirmation and the assignee's [Slack](/integrations/slack) notification reference the same ticket number. Nothing waits for a human to transcribe it.

Completion status that crosses tool boundaries

The development work tracked in ProofHub actually happens in the engineering tool. When a deliverable ships there, the agent finds the matching task via List Tasks and calls Update Task to mark it complete, touching only the completion field so assignees and labels stay exactly as a human set them. The team channel gets the done notice. Client-facing status stops depending on an engineer remembering to update a second board.

The project report assembled from the source

Each Friday, the agent walks List Projects, then List Task Lists and List Tasks for each active project, and writes the state of play to [Google Sheets](/integrations/google-sheets): open tasks by project, overdue items with assignees, completions this week. Get Project fills in managers and end dates. The Monday client calls start from a report generated Sunday night by nobody.

Human-in-Loop Highlight

Update Task has a sharp edge: when you supply assignees or labels, they are replacement lists, not additions. A sync run that writes an assignee field does not add a name to the task, it overwrites everyone a project lead deliberately put there. Run that logic across a few hundred tasks and you have silently reassigned a project, erasing decisions no system recorded anywhere else. So FlowRunner draws the line exactly there: agents freely update dates and completion status, the fields where external systems hold the truth, but any staged change that rewrites assignees or labels queues for the project lead with a before-and-after diff. The sweep runs at machine speed. The right to reassign people's work stays with a person.

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

9 actions

Projects

List Projects Retrieves all projects visible to the API key's user, with each project's id, title, description, status, category, dates, and assigned members. The starting point for every sweep and report.
Get Project Retrieves a single project by id, including title, description, status, category, start and end dates, assigned members, and manager.

Task Lists

List Task Lists Retrieves all task lists within a project, each with id, title, and description. Task lists group related tasks; their ids are required for task operations.
Create Task List Creates a new task list inside a project with a title and optional description. Used to open a home for a new phase or category of incoming work.

Tasks

List Tasks Retrieves all tasks within a specific task list, with each task's id, ticket number, title, description, start and due dates, assigned members, labels, and completion status. Requires both a project id and a task list id.
Create Task Creates a new task inside a task list with a title and optional description, start date, due date, assignee user ids, and labels. Dates use YYYY-MM-DD format. The write that turns an inbound request into filed work.
Update Task Updates an existing task; only supplied fields change, but assignees and labels are replacement lists when provided. The operation this page's human gate exists for.

Discussions

List Discussions Retrieves all discussion topics within a project, each with id, title, description, and metadata. Used to read the collaboration context around a project's work.

People

List People Retrieves all users in the account with id, name, email, and role. The roster lookup that resolves assignee ids before tasks are created or updated.

Frequently Asked Questions

What can FlowRunner do with ProofHub?

FlowRunner agents can run List Projects, Get Project, and List Task Lists in ProofHub, plus 6 more actions.

Does connecting ProofHub to FlowRunner require OAuth?

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

Can ProofHub trigger a FlowRunner workflow automatically?

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

Start building with ProofHub

$100 in credits. No card required. Connect in minutes.

Start Building Free Talk to us