Use cases
Incident response automation
Trigger an n8n workflow from a Bronto monitor alert webhook. The workflow queries Bronto for recent errors or anomalies around the alert window, formats a summary, and creates a ticket in Linear, Jira, or PagerDuty — with log context already attached.AI-assisted log investigation
Use the Bronto node as an AI tool node inside an n8n AI agent workflow. The agent calls Bronto search at runtime to look up relevant logs, then synthesizes findings and posts a summary to Slack or email.Scheduled health checks
Run a recurring n8n workflow that queries Bronto for error rates, latency distributions, or specific log patterns on a schedule. Compare results against thresholds and notify your team when something drifts.Log-driven data pipelines
Extract structured fields from Bronto log events and push them to a data warehouse, spreadsheet, or analytics tool. Useful for compliance exports, capacity planning, or building custom dashboards outside of Bronto.Cross-tool correlation
Combine Bronto log data with data from other systems in the same workflow — query deployment events from GitHub, pull error counts from Bronto, and correlate them to detect regressions after releases.Minimal install
The Bronto node is a verified community node hosted on npm and the n8n community node registry. Requirements- n8n v0.187.0 or later (self-hosted or n8n Cloud)
- Instance owner access to install community nodes
- Open Settings → Community nodes
- Click Install a community node
- Enter the package name:
n8n-nodes-bronto - Confirm and restart n8n if prompted
Credential setup
After installing the node, create a Bronto API credential in n8n:- Go to Credentials → Add credential → Bronto API
- Enter your Bronto API key — create one under Account Management → API Keys with search permissions
- Select your region: EU or US
https://api.eu.bronto.io or https://api.us.bronto.io).
Node reference
The Bronto node has a single Search operation that queries the Bronto search API.Source
Choose how to identify which logs to search:| Source type | Description |
|---|---|
| Logs | Select one or more log datasets from a dropdown populated from your Bronto account |
| Tags | Filter by tag key:value pairs (e.g. env:production service:api) |
Search parameters
| Parameter | Description | Example |
|---|---|---|
| Time range | Relative time window | Last 1 hour, Last 2 days |
| Where | SQL-like filter expression | level:error AND duration_ms>2000 |
| Select | Fields or aggregate functions to return | *, @raw or count(), avg(duration_ms) |
| Groups | Fields to group aggregate results by | service, region |
| Limit | Maximum number of results (1–6666) | 50 |
Additional options
| Option | Description |
|---|---|
| From / To timestamp | Absolute time bounds in Unix milliseconds |
| Most recent first | Sort order — newest events first (default: true) |
| Number of slices | Time buckets for time-series aggregate queries |
| Paginate | Automatically follow next_page_url to fetch all matching results |
Output
The node maps the API response to n8n items in one of three shapes depending on the query:events[]— individual log events from a raw searchgroups[]— grouped rows from an aggregate queryresult[]— other result arrays
Use as an AI tool node
The Bronto node supports n8n’susableAsTool flag, meaning it can be connected directly to an AI agent node without wrapping. When used this way, the agent decides at runtime when and how to call the Bronto search — passing a query, time range, and filter based on context from the conversation or workflow.
This is the recommended pattern for AI-assisted log investigation workflows where the query is not known in advance.