BugHerd

BugHerd is a visual website feedback and bug tracker. Agents create and update tasks, move them across columns, add comments and attachments, manage projects and members, and react to new tasks and comments in real time.

Verified 5 triggers 41 actions Basic auth available

BugHerd website Platform Documentation Capability data verified 2026-08-25

On Task Created fires when a client pins feedback on the staging site

Agent reads the description, the element it was pinned to, and the browser and operating system BugHerd captured with it

List Feedback Tasks confirms this is untriaged guest feedback rather than a task the team filed

Agent matches the report against open work so a third report of the same issue joins the first

Update Task sets the column, priority, and assignee, attributed with Updater Email so it does not read as the API key's owner

The delivery channel receives the pin, the screenshot, and the duplicate count

The account manager approves any reply that will be visible to the client

What This Integration Enables

BugHerd exists because the people who find most website problems cannot describe them. A client, a stakeholder, or a customer sees something wrong and their natural report is a sentence with no URL, no browser, and no way to reproduce. BugHerd changes the input rather than the reporter: they point at the thing on the rendered page, and the report arrives with the element, the page, the screen size, and the environment already attached. Everything interesting about automating it follows from that. This is an intake surface for non-technical people, and the connector's shape reflects it, with guests as first-class members, a feedback queue that is deliberately separate from the board, and privacy settings that decide what a client can see.

FlowRunner agents work that queue. They read untriaged feedback, deduplicate it against open tasks, set status by column name, assign work with real attribution rather than as the API key's owner, attach evidence, move tasks between projects, and mirror the result into whichever tracker engineering actually lives in. Five realtime triggers mean this happens as feedback lands rather than on a schedule. What stays with a person is the part a client will read, because BugHerd's comment API can create and delete but cannot edit, and FlowRunner's human-in-the-loop design is built for precisely that kind of one-way door.

Without FlowRunner

Feedback arrives as prose "The button looks wrong on the pricing page" reaches the team without a browser, a URL, or a way to reproduce it

The triage queue is invisible Guest feedback sits in a list the board never shows, so reports age until somebody thinks to look

Two trackers, one project Client feedback lives in one tool and engineering work in another, and keeping them aligned is a standing meeting

With FlowRunner

Feedback arrives attached to the page Every report carries the element, the URL, and the environment it came from, because the client pointed at it

Triage runs continuously Untriaged feedback is read, deduplicated, prioritized, and routed as it lands rather than in a weekly sweep

One tracker feeds the other Reports become engineering tickets automatically and status flows back, without either team leaving their tool

Use Case Scenarios

The triage queue that empties itself

A client pins three pieces of feedback on a staging site during a review call. On Task Created fires for each, and the agent reads them out of List Feedback Tasks, which is where untriaged guest feedback lives and where List Tasks will never show it. For each report it compares the description and the pinned element against open tasks, links duplicates rather than filing them again, reads List Columns to learn the project's real column names, and calls Update Task to set status, priority, and assignee. Because status is matched by column name rather than id, the agent reads the names instead of assuming them, which is also what keeps the flow working after somebody renames a column. Genuinely new issues are mirrored into Jira or Linear with the BugHerd task id carried as an external reference, so status can flow back later.
Reporting that counts everything, including what the board hides

BugHerd keeps four task lists that do not overlap: the taskboard the team sees, the feedback queue nobody has triaged, the archive of closed work, and the filterable general view. A weekly report built from one of them under-reports, and the shortfall is always in the same place, which is the untriaged queue. So the agent reads all four, writes the counts and ages to Google Sheets, and posts the delivery summary to Slack with the oldest untriaged report named. It also reads List Webhooks, because a webhook that has quietly started failing looks exactly like a project where nothing is happening, and the error counts and last error timestamp are right there in the response.
Evidence attached without a download

A support conversation in Zendesk turns out to be a real defect, and the customer sent a screen recording. Rather than asking an engineer to reproduce it from a description, the agent files the task with Create Task, attributing it with Requester Email so the reporter is the customer rather than the integration, then attaches the evidence. Which attachment operation it uses depends on the file. Create Attachment From URL has BugHerd fetch the address itself, which needs a publicly reachable link and can fail later when a signed URL expires. For a private or expiring file the agent uses Upload Attachment and posts the bytes directly.

Human-in-Loop Highlight

BugHerd's comment API publishes create, list, and delete. There is no update route. That single omission decides how an agent should behave here, because a comment on a task is a message to a client, and the Is Private flag is what separates an internal note from something the client reads in their own sidebar. A note posted with Is Private off does not fail, does not warn, and cannot be edited afterward. The only correction available is deleting it, which happens after the client has already read it and leaves a visible gap in the thread. The same shape appears in project settings, where Is Public means anyone with the link can submit feedback without an account, and Guests See Guests means two clients reviewing the same site read each other's remarks about it.

So the agent does everything up to the client-visible word and then stops. It triages, deduplicates, assigns, attaches evidence, and drafts the response, then posts to the account manager: "Task 214, pinned by the client on the checkout page, is a duplicate of task 189 which shipped a fix yesterday. Draft reply: 'This was fixed in yesterday's release, please hard-refresh and let us know.' Posting this with Is Private off puts it in the client's sidebar, and BugHerd has no route to edit a comment afterward. Send as written, revise, or keep it internal?" Internal notes, status moves, and assignment all run unattended, because none of them reach the client. The one action that cannot be taken back is the one a person authorizes.

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

41 actions

Organization and people

Get Organization Reads the BugHerd organization the API key belongs to.
List Users Lists everyone on the account, members and guests together.
List Members Lists internal members, which is the set an assignment can target.
List Guests Lists guest accounts, which is how clients and external reviewers appear.
List User Tasks Lists the tasks associated with one user, for workload and handover checks.
List User Projects Lists the projects a user has access to.

Projects

List Projects Lists every project on the account.
List Active Projects Lists only active projects, which is the working set for a reporting sweep.
Get Project Reads one project including its visibility settings.
Create Project Creates a project. Its Is Public and Guests See Guests settings decide who can submit feedback and who can read whose.
Update Project Changes a project's settings, including the two visibility flags that determine what a client sees.
Delete Project Permanently deletes a project and the work inside it.
Add Project Member Adds an internal member to a project. The v2 API publishes no matching remove.
Add Project Guest Adds a guest, which is how a client is given access to review a site.

Tasks

List Tasks The filterable view, by status, priority, tag, assignee, external id, or time. It does not include the feedback queue or the archive.
List Feedback Tasks Untriaged guest feedback. The triage queue, and invisible to List Tasks, which is where most under-reporting comes from.
List Taskboard Tasks What the team actually sees on the board.
List Archived Tasks Closed work, which every other listing excludes.
Get Task Reads a task by its globally unique id.
Get Task Globally Finds a task across projects when the project is not known in advance.
Get Task By Local ID Reads a task by the small per-project number people say out loud. It needs the project too, because that number is unique only within one.
Create Task Creates a task. Requester Email and Assigned To Email attribute it to real people rather than to the API key's owner.
Update Task Changes a task's column, priority, assignee, tags, or text. Tag Names replaces the whole tag list rather than adding to it, and Unassign User ID is the only way to clear an assignment.
Delete Task Permanently deletes a task.
Move Tasks Moves tasks between projects. Local task numbers are per-project, so a move changes them.

Columns

List Columns Lists a project's columns. Their names are what a task's status is matched on, so this is also the answer to which statuses a project has.
Get Column Reads one column.
Create Column Adds a column to a project's board.
Update Column Renames or changes a column. Renaming changes the value status matches on, so a flow setting the old name stops working silently.
Delete Column Removes a column from the board.

Comments

List Comments Lists the comments on a task, including whether each one is private.
Create Comment Adds a comment. With Is Private off it is visible to the client, and BugHerd publishes no route to edit a comment afterward.
Delete Comment Permanently deletes a comment. The only correction available for a comment that should not have been public.

Attachments

List Attachments Lists the files attached to a task.
Get Attachment Reads one attachment's details.
Create Attachment From URL Has BugHerd fetch a file from a URL, which requires an address reachable from the public internet and can fail after a signed link expires.
Upload Attachment Posts the bytes directly, which is what a private or expiring file needs.
Delete Attachment Removes an attachment from a task.

Webhooks

List Webhooks Lists every webhook on the account with its success count, error count, and last error. A webhook that has quietly started failing is worth alerting on, because it looks like a project where nothing is happening.
Create Webhook Registers a webhook for a BugHerd event.
Delete Webhook Removes a webhook. This listing includes the ones FlowRunner's triggers created, and deleting one of those stops the trigger firing.

Triggers

5 triggers

Event Triggers

On Task Created Fires when a task is created in the chosen project, whether it came through the sidebar or the API. A flow that creates tasks can therefore trigger itself, so filter on the requester or the external id where that matters.
On Task Updated Fires when a task changes: its column, priority, assignee, tags, or text. BugHerd does not say what changed, only that the task did, so a flow reacting to a move into Done compares against its own record of the previous state.
On Task Deleted Fires when a task is deleted. Deletion is not archiving, and a task closed into the final column fires On Task Updated instead, so a flow watching for finished work wants that one.
On Comment Created Fires when a comment is added, including private ones. Check the private flag before republishing a comment anywhere a customer can see it.
On Project Created Fires when a project is created. It is account-wide by nature and takes no project parameter, which makes it the hook for onboarding a new client engagement end to end.

Frequently Asked Questions

What can FlowRunner do with BugHerd?

FlowRunner agents can run Get Organization, List Users, and List Members in BugHerd, plus 38 more actions.

Does connecting BugHerd to FlowRunner require OAuth?

No. BugHerd connects to FlowRunner with basic authentication (a username and password), no OAuth flow required.

Can BugHerd trigger a FlowRunner workflow automatically?

Yes. BugHerd supports 5 triggers that can start a FlowRunner workflow automatically.

Start building with BugHerd

Free plan, no card required. Connect in minutes.

Start Building Free Talk to us