BugHerd is a visual feedback and bug tracking tool for websites, allowing clients and teams to report issues directly on live sites.
BugHerd is a visual feedback and bug tracking tool for websites, allowing clients and teams to report issues directly on live sites. On Nagent, Bugherd is exposed as a fully-configurable project management integration that any agent can call — 26 actions, and API key authentication. No code is required to wire Bugherd into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Bugherd to automate the kinds of tasks project management teams previously handled manually. Concrete examples — each one is a single agent step in Nagent — include:
Every action and trigger is paired with a structured input/output schema (visible in the sections below), so when you wire Bugherd into Helix — our agentic agent builder — the editor knows exactly what each step expects and produces. Configure once, deploy anywhere across your Nagent agents.
Every operation an agent can call against Bugherd, with input parameters and output schema. Drop these into any step of an agent built in Helix.
BUGHERD_ADD_GUEST_TO_PROJECTTool to add a guest (client) to a project. Use when you want to add an existing client by ID or invite a new client by email.
Input parameters
Email address to invite a new guest (client). Mutually exclusive with 'user_id'.
ID of an existing guest (client) to add. Mutually exclusive with 'email'.
ID of the project to add the guest (client) to.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BUGHERD_ADD_MEMBER_TO_PROJECTTool to add a member to a project in BugHerd. Use when you need to add an existing user to a specific project.
Input parameters
The ID of the existing user to add to the project.
The ID of the project to which the member will be added.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BUGHERD_CREATE_ATTACHMENTTool to add a new attachment to a task using an existing URL. Use when you have project and task IDs and the external file URL ready.
Input parameters
Public URL of the file to attach.
Unique identifier of the task to which the attachment will be added.
Name of the attachment file (e.g., 'resolution.gif').
Unique identifier of the project containing the task.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BUGHERD_CREATE_COLUMNTool to create a new column in a project. Use when you need to add a custom workflow column after identifying the project ID.
Input parameters
Name of the new custom column.
Zero-based position of the new column in the project's column list; defaults to appending if omitted.
ID of the project to which the column will be added.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BUGHERD_CREATE_COMMENTTool to add a new comment to a task. Use when you need to record discussion or feedback on an existing task.
Input parameters
Content of the comment to add.
Email address of the commenter. Used if 'user_id' is not set.
ID of the task to which the comment will be added.
ID of an existing user adding the comment. Mutually exclusive with 'email'.
ID of the project containing the task.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BUGHERD_CREATE_PROJECTTool to create a new project. Use when you need to initialize a project after gathering its name and URL. Example: "Create a new project named 'My Website' with URL 'http://www.example.com'."
Input parameters
Project fields for creating a new BugHerd project.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BUGHERD_CREATE_TASKTool to add a new task in a project. Use when you have the project ID and full task details ready.
Input parameters
Status or column for the task. Use one of the default statuses ('backlog','todo','doing','done','closed') or for custom columns pass the column name. Omit or set to null to send to the Feedback panel.
Priority of the task. Defaults to 'not set' if omitted.
List of tag strings to associate with the new task.
ID of the project to which the task will be added.
Text describing the task or bug to be logged.
API-only field for correlating with external systems. Cannot be set from the BugHerd UI.
ID of an existing requester user. Mutually exclusive with 'requester_email'.
ID of a project member to assign this task to. Mutually exclusive with 'assigned_to_email'.
Email address of the requester. Used if 'requester_id' is not set.
Email of a project member to assign this task to. Must correspond to an existing member in the given project.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BUGHERD_CREATE_WEBHOOKTool to create a new webhook for real-time event notifications. Use when you need to configure a callback endpoint for task or comment events. Example: "Create a webhook for 'task_create' events to be sent to 'https://example.com/webhook'."
Input parameters
Event that triggers the webhook. One of 'task_create', 'task_update', 'comment', or 'task_destroy'.
ID of the project to apply the webhook to. If omitted, applies to all projects.
URL to which webhook payloads will be delivered.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BUGHERD_DELETE_PROJECTTool to delete a project. Use when you need to permanently remove a project and its associated data. This action cannot be undone, so confirm the project ID before calling.
Input parameters
The ID of the project to delete.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BUGHERD_LIST_ACTIVE_PROJECTSTool to list all active projects in your BugHerd account. Use when you need to retrieve the active projects list (e.g., for syncing or reporting).
Input parameters
Page number for pagination (1-based). BugHerd returns up to 100 records per page; omit to fetch the first page.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BUGHERD_LIST_ATTACHMENTSTool to list all attachments for a task. Use when you need to retrieve file attachments after fetching task details.
Input parameters
Page number for pagination (each page returns up to 100 attachments).
Global unique ID of the task to list attachments for (not the local_task_id).
ID of the project containing the task.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BUGHERD_LIST_COLUMNSTool to list all columns for a project. Use when you need the full set of default and custom columns for a project.
Input parameters
The unique identifier of the BugHerd project. Obtain this from the List Projects action.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BUGHERD_LIST_PROJECTSRetrieves a paginated list of all projects in your BugHerd account. Returns project details including ID, name, creation date, owner, task status, and associated website URLs. Results are paginated with up to 100 projects per page. Use the meta.count field to determine the total number of projects.
Input parameters
Page number for pagination. Each page returns up to 100 projects. Defaults to 1 if not specified.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BUGHERD_LIST_PROJECT_TASKSTool to list tasks within a specific BugHerd project with optional server-side filters (status/column, assignee, tag, priority, date filters) and pagination. Use when you need to retrieve tasks scoped to a single project.
Input parameters
Filter by tag name.
Page number for pagination. Each page returns up to 100 tasks. Defaults to 1 if not specified.
Filter by status or column name (e.g., 'backlog', 'todo', 'doing', 'done', 'closed', or custom column name).
Filter by priority level (e.g., 'critical', 'important', 'normal', 'minor', 'not set').
ID of the project to list tasks from.
Filter by external ID for integration with external systems.
Filter tasks created since this timestamp (ISO8601 format).
Filter tasks updated since this timestamp (ISO8601 format).
Filter by assigned user ID.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BUGHERD_LIST_USERSTool to list all users in your account. Use after authenticating to fetch the current user roster. Supports pagination via the `page` parameter.
Input parameters
Page number (1-based) to retrieve.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BUGHERD_LIST_WEBHOOKSTool to list all installed webhooks. Use when you need to audit or verify existing webhooks after setup.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BUGHERD_SHOW_ATTACHMENTTool to retrieve details of a specific attachment. Use after you have project_id, task_id, and attachment_id to get filename, URL, and timestamps.
Input parameters
Unique identifier of the task containing the attachment.
Unique identifier of the project containing the task.
Unique identifier of the attachment to retrieve.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BUGHERD_SHOW_COLUMNTool to show details of a specific column. Use when you need metadata for a particular column within a project.
Input parameters
Unique identifier of the column to retrieve
ID of the project containing the column
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BUGHERD_SHOW_ORGANIZATIONTool to retrieve your BugHerd organization details. Use after authenticating to fetch account metadata.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BUGHERD_SHOW_PROJECTRetrieves full details of a specific BugHerd project by ID. Returns comprehensive project information including name, settings, team members, guests, and kanban columns. Use this when you need detailed project data such as member lists, workflow columns, or project configuration settings. Requires a valid project_id obtained from list_projects or another source.
Input parameters
The unique identifier of the project to retrieve
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BUGHERD_SHOW_USER_PROJECTSTool to list all projects a specific user has access to. Use after obtaining the user's ID.
Input parameters
Page number for pagination. Each page returns up to 100 projects. Defaults to page 1 if not specified.
The unique ID of the user whose accessible projects you want to list.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BUGHERD_SHOW_USER_TASKSRetrieves all tasks created by or assigned to a specific user, grouped by project. Returns task details including ID, description, priority, status, timestamps, and tags. Requires a valid user_id (obtain from List Users action). Supports pagination via page parameter.
Input parameters
Pagination page number (each page returns up to 100 tasks).
Globally unique ID of the user whose tasks to list.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BUGHERD_UPDATE_COLUMNTool to update a column in a project. Use when you have the project and column IDs and need to rename a column. Use after confirming the correct IDs.
Input parameters
Column fields to update
ID of the column to update
ID of the project containing the column
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BUGHERD_UPDATE_PROJECTUpdate settings for an existing BugHerd project. Use this to modify a project's name, URL, visibility settings, or guest permissions. Prerequisites: You need a valid project_id. Use list_projects to find existing project IDs, or create_project to create a new one. Note: Only include fields you want to change - omitted fields will retain their current values.
Input parameters
Object containing the fields to update. Only include the fields you want to change.
The unique numeric ID of the project to update. Get this from list_projects or create_project.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BUGHERD_UPDATE_TASKTool to update a task in a project. Use after confirming the project and task IDs.
Input parameters
Fields to update for the task
Global ID of the task to update (not the local_task_id)
ID of the project containing the task
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BUGHERD_UPLOAD_ATTACHMENTTool to upload a new attachment and add it to a specific task. Use when you have binary file content ready and need to attach it to a BugHerd task.
Input parameters
ID of the task to attach the file to.
Name of the attachment file including extension (e.g., 'screenshot.png', 'report.pdf').
ID of the project containing the task.
Raw binary content of the file to be uploaded. For text files, encode the content as bytes.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
No publicly available marketplace agent is found using this tool yet. There are 41 agents privately built on Nagent that already use Bugherd.
Build on Nagent
Connect Bugherd to any Nagent agent in minutes — no API key management, no boilerplate. Just configure and deploy.
The five questions agent builders ask before adopting a new integration.
Open the External Integrations panel inside Nagent (app.nagent.ai/externalIntegration), find Bugherd, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, Bugherd is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Bugherd is connected, you configure its 26 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop Bugherd steps into any workflow visually. Pick an action (e.g., one of those listed above), fill in the inputs (Helix knows the required vs. optional schema for each parameter), and connect it to upstream/downstream steps. Triggers run as the entry point of an agent, so when a Bugherd event fires, the agent kicks off automatically.
Every Bugherd action and trigger ships with a fully-typed schema — input parameters with name, type, required flag, and description, plus the output payload shape. The schemas are documented in the sections above. Helix uses these schemas to validate your configuration at build time and to type-check the data flowing between steps.
Yes. While Bugherd ships with 26 pre-built project management actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching Bugherd together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Bugherd-based workflows tailored to your business.