Overview
The Baresquare node for n8n allows you to retrieve incident tickets from the Baresquare API. It supports fetching either newly created tickets (since the last poll) or the most recent X tickets, making it suitable for automating workflows that respond to new incidents or require regular ticket data synchronization.
Common scenarios:
- Triggering a workflow when new incident tickets are created in Baresquare.
- Periodically fetching the latest tickets for reporting, monitoring, or further processing in n8n.
Practical examples:
- Automatically send notifications or create tasks in another system when a new Baresquare ticket is detected.
- Aggregate and analyze recent incident data for dashboards or reports.
Properties
Name | Type | Meaning |
---|---|---|
Select Server | options | Choose which Baresquare server to connect to (US or EU). Determines the API endpoint. |
Get Data | options | Selects whether to fetch only new tickets ("New Tickets") or the last X tickets ("Last X Tickets"). |
Ticket Limit | number | Maximum number of tickets to return per request. Minimum value is 1. |
Output
The node outputs an array of JSON objects, each representing a ticket with the following fields:
Field | Description |
---|---|
ID | Unique identifier of the ticket |
Title | Title of the incident |
Impact Score | Numeric impact score |
Sentiment | Sentiment analysis result |
Incident date | Date and time of the incident |
Description | Detailed description of the incident |
Assignee email address | Email address of the assigned user |
Priority | Priority level of the ticket |
Author email address | Email address of the ticket's author |
Granularity | Granularity information |
Volume index value | Volume index metric |
Deviation index value | Deviation index metric |
Status | Current status of the ticket |
Creation date | When the ticket was created |
Last updated | Last update timestamp |
Number of comments | Count of comments on the ticket |
Archive status | Whether the ticket is archived |
Ticket URL | Direct link to the ticket in Baresquare |
Dependencies
- External Service: Requires access to the Baresquare API.
- API Key: You must provide valid Baresquare API credentials (
baresquareApi
) in n8n. - Environment: No special environment variables required beyond standard n8n credential configuration.
Troubleshooting
Common issues:
- Invalid API Key: If the provided API key is incorrect or expired, the node will fail to authenticate.
- Network Issues: Connectivity problems may prevent reaching the Baresquare API endpoints.
- Unsupported Option: If an unsupported value is selected for "Get Data", the node will throw an error.
Error messages:
Could not fetch data from API with following error:...
Resolution: Check your API credentials, network connection, and ensure the Baresquare service is available.The defined option "..." is not supported
Resolution: Ensure you select a valid option for "Get Data" (either "New Tickets" or "Last X Tickets").
Links and References
- Baresquare Website
- n8n Documentation
- For API details, refer to your Baresquare account documentation or contact Baresquare support.