NagentArtefacts
Dev & Technology
Enterprise and White Glove
Company
Honeybadger connects to a Nagent workspace with an API key. Once it is connected, agents can call 7 Honeybadger actions, such as "Report Check-In", "Report Check-In With Payload" and "Report Deployment". Nothing is enabled on connect: each action is allowed one at a time, and an action with side effects runs or waits for a person according to the agent's level.
Every operation an agent can call against Honeybadger, with input parameters and output schema.
HONEYBADGER_REPORT_CHECK_INReports a check-in (ping) to Honeybadger for uptime monitoring. Check-ins are used to monitor scheduled tasks, cron jobs, and background processes. By pinging this endpoint regularly, you signal that your task is running on schedule. If Honeybadger doesn't receive a ping within the expected timeframe, it will alert you that the task may have failed or stopped running. Use this action at the end of successful task executions to notify Honeybadger the task completed as expected.
Input parameters
The unique identifier of the check-in to report. Provide this OR `project_api_key` and `slug`.
The slug identifier of the check-in. Required when reporting by slug instead of `id`.
The API key of the project. Required when reporting by `slug` instead of `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
HONEYBADGER_REPORT_CHECK_IN_WITH_PAYLOADReport a check-in with additional payload data to Honeybadger. Use when monitoring scheduled tasks or cron jobs and need to send metrics, status, or metadata (up to 20KB).
Input parameters
Check-in payload data containing metrics, status, or other metadata (max 20KB total)
The unique identifier of the check-in to report. This acts as authentication for the check-in endpoint.
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
HONEYBADGER_REPORT_DEPLOYMENTReport a new deployment to Honeybadger for deployment tracking and error correlation. Use this tool after deploying code to notify Honeybadger, which allows you to: - Track deployment history on your project's Deployments page - Correlate errors with specific deployments - Automatically resolve errors when deploying to an environment All deployment fields are optional, but providing environment and revision is recommended for better tracking.
Input parameters
Deployment details including environment, revision, repository, and username. All fields are optional but providing more details helps track deployments.
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
HONEYBADGER_REPORT_EVENTSend custom events to Honeybadger Insights for tracking, monitoring, and analytics. Use this action to record any structured event data such as: - User activity and behavioral events (logins, page views, feature usage) - Application errors and exceptions with context - Performance metrics and timing data - Custom business events and audit trails - System health and operational metrics Events are sent as newline-delimited JSON (NDJSON) and can include any custom fields. The API returns tracking IDs for each successfully recorded event.
Input parameters
List of event objects to send to Honeybadger Insights. Each event is a flexible dictionary that can contain any fields relevant to your tracking needs (e.g., event name, user_id, timestamps, custom metadata). Common patterns include: error events with error_type/message fields, user activity events with user_id/action fields, or performance metrics with timing data. Size constraints: each event < 100 kB, total payload < 5 MB.
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
HONEYBADGER_REPORT_EXCEPTIONTool to report an exception notice to Honeybadger. Use when sending error details (stack trace, context) for diagnostics.
Input parameters
Exception details including backtrace
Server and process context for the exception.
HTTP request context at the time of the exception.
Client library information for Honeybadger notifier.
Breadcrumb trail leading up to the exception.
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
HONEYBADGER_UPLOAD_FILE_TO_S3Tool to upload a local file to a managed S3 bucket. Use when preparing files for source-map uploads.
Input parameters
The file to upload to S3.
Optional filename to use in S3. Defaults to the uploaded file's name.
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
HONEYBADGER_UPLOAD_SOURCE_MAPUpload JavaScript source maps to Honeybadger for error stack trace de-minification. Use this tool after deploying minified JavaScript assets to enable Honeybadger to display un-minified, readable stack traces when errors occur. Source maps allow Honeybadger to map minified code back to your original source code with proper file names, function names, and line numbers. The tool uploads: (1) the minified JS file, (2) its corresponding .map file, and optionally (3) additional source files referenced by the map, all associated with the production URL.
Input parameters
Deploy revision identifier (e.g., Git commit SHA, version tag) for tracking which deployment this source map applies to. Should match the revision configured in honeybadger.js. Defaults to 'master' if not provided.
The corresponding source map file (.map).
Absolute production URL of the minified JS file in production; supports '*' wildcard for domain/protocol matching. Query strings are ignored. Example: 'https://cdn.example.com/app.min.js' or 'https://*/assets/app.min.js'
The minified JavaScript file to upload.
Additional original source files referenced by the source map. Each filename must match the source file's production URL path. Used when source map references files not embedded inline.
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
Agents can call 7 Honeybadger actions on Nagent, including "Report Check-In", "Report Check-In With Payload" and "Report Deployment". Report Check-In: Reports a check-in (ping) to Honeybadger for uptime monitoring. Each action is listed on this page with its input parameters and its output.
Honeybadger connects with an API key, under your workspace's own connection. Nothing is enabled on connect: each action is allowed one at a time and can be scoped to the agents that need it.
It also takes 3 optional inputs: id, slug and project_api_key. It returns data, error and successful.