Integrate with Biggy
You can set up integrations so that Biggy can access information from your tools in real-time. Integrations enable you to retrieve on-call schedules, create Jira artifacts or Zoom rooms, and more.
Manage Biggy Integrations
You can enable and manage integrations from the Biggy Settings page at Configuration > Integrations.
To integrate with Biggy:
Navigate to Configuration > Integrations.
Select an integration from the list and click Configure.
In the configuration screen, populate the required fields for your integration. See the Standard Integrations section for more information about specific configuration requirements.
Select the Enable toggle.
Click Save.
Once an integration has been set up, it will appear in the list with a green Enabled icon.
To edit or disable an integration, you can click the Configure button and make any desired changes.
Standard Biggy Integrations
Biggy has standard integrations available with the following tool categories:
Tool categories
Some Biggy integrations may fall into multiple categories.
On-Call
On-call tools are incident response and on-call management platforms. These integrations enable automated paging, escalations, notifications, and coordination during critical incidents.
You can integrate Biggy with the following on-call tools:
Jira Service Management
Use the Jira Service Management (JSM) integration to retrieve on-call schedules, rotations, and contacts.
The following JSM operations permissions must be enabled to use the integration:
read:ops-config:jira-service-managementread:jira-userread:meoffline_access
To set up the integration, click Connect JSM. You'll be redirected to the Atlassian page where you will need to grant Biggy access to your Atlassian account. Click Accept to enable the integration.
OpsGenie
The OpsGenie integration is used for alerting and on-call management.
To configure the OpsGenie integration, enter your OpsGenie API Key.
PagerDuty
The PagerDuty integration is used for incident response and alerting.
In PagerDuty, generate a user token API key with the following permissions granted:
schedules.readservices.readusers.readusers.contact_methods.readincidents.writeincidents.read
To configure the PagerDuty integration, enter your PagerDuty Email address and a user token API Key.
Paging Targets
You can set up paging targets in Managed Incident Channels escalation workflows. These paging targets will receive a notification during an incident.
To add a paging target, go to the Search Query box and type the name of a service. Matching services will appear in the menu to the right. Select a service to add it to the configuration.
You can also click + Add Manual Target to manually add a target without searching for it.
After selecting the service, populate the following information in the Configured Targets section:
Service ID - the ID of the targeted service in PagerDuty.
Display Name - the display name that will appear in the managed incident channel.
Description - description of the PagerDuty target.
Click Save Targets to add it to your configuration.
ITSM
ITSM tools are used for ticket management, SLA tracking, and workflow automation. These integrations enhance service desk efficiency and incident handling.
The following ITSM integrations are available:
BMC Remedy
The BMC Remedy integration is used for IT service management.
To configure the BMC Remedy integration, enter your BMC Remedy API Key and click Save.
Jira
The Jira integration is used for issue tracking and project management.
To configure the Jira integration, populate the following fields:
Field | Description |
|---|---|
Jira URL | Jira endpoint URL. |
Username and Password | Username and Password of the Jira account that Biggy should use for API interactions. |
System/Schema Nuances | List any special field mappings, naming conventions, custom tables/fields, or other knowledge that helps Biggy more effectively interact with your tool. We highly recommend configuring this field, as it allows you to enter organization-specific information that enables Biggy to provide more accurate and consistent results. For example, you can include explanations of any custom fields and when or how they should be used to handle certain types of user queries. |
ServiceNow
The ServiceNow integration is used for managing incidents and requests.
Configuration management
The ServiceNow integration is also part of the Configuration Management integration category.
Biggy and ServiceNow Context Sync
For information on installing the Biggy ServiceNow Data Connector app, see Biggy and ServiceNow Unified Data Connector.
To configure the ServiceNow integration, populate the following fields:
Field | Description |
|---|---|
ServiceNow URL | Base URL of your ServiceNow instance. (For example, https://[company].service-now.com) |
Username and Password | Username and Password of the ServiceNow account that Biggy should use for API interactions. |
System Time Zone | Select the time zone configured in your ServiceNow instance. This ensures that ServiceNow correctly interprets dates and times to maintain consistency. |
System/Schema Nuances | List any special field mappings, naming conventions, custom tables/fields, or other knowledge that helps Biggy more effectively interact with your tool. We highly recommend configuring this field, as it allows you to enter organization-specific information that enables Biggy to provide more accurate and consistent results. For example, you can include explanations of any custom fields and when or how they should be used to handle certain types of user queries. |
ITSM Ticket Configuration Settings
Configure the mandatory or allowed fields and values for ServiceNow tickets.
For certain interactions, like creating a ticket upon creation of a Biggy-managed incident channel, these settings control which fields or values are displayed to users during auto-population.
Configure the following sections:
Field Configuration
Add ServiceNow fields in the Field Configuration section:
Click + Add ServiceNow Field .
Select a field from the drop-down menu and click + Add.
Enter or edit the following information for the field:
Field
Description
Display Name
A user-friendly name that will appear in the UI. This field is prepopulated, but can be edited.
Field Name
The ServiceNow field name, also known as the API name. This field is prepopulated, but can be edited.
Field Type
Select how this field should be processed and displayed. Options include:
Text - plain text field extracted by Biggy based on prompt instructions.
Choice - a choice field in ServiceNow that has defined values in this table.
Choice (Reference) - a choice field in ServiceNow where the choices are referenced from a different table.
Constant - the value configured for this field will always be used, and cannot be updated by users when creating a ticket.
Field Requirement
Determine whether or not the field must be filled out when creating tickets.
Select Optional to allow the field to be left blank when creating tickets.
Select Mandatory if the field must be filled out when creating tickets.
Reference Table
This field will appear if you select Choice (Reference) for the Field Type.
Select the ServiceNow table to reference for choice options.
Reference Table Display Field
This field will appear if you select Choice (Reference) for the Field Type.
Select the ServiceNow column used for display value in reference table. The column used is typically
name.For Text fields, configure AI Extraction Guidance.
For Choice or Choice (Reference) fields, configure Choice Configuration.
For Constant fields, configure Constant Values.
Click Save Mappings.
All Active Field Configurations appear at the top of the section. Click any field to expand the configuration. You can click the Pencil icon to edit the configuration, or the Trash icon to delete it.
AI Extraction Guidance
The AI Extraction Guidance section will appear if you select Text for the Field Type. Use the Suggestion Prompt to help Biggy understand how to extract and populate the field.
The following is an example of a Suggestion Prompt:
Extract the affected service name from the incident description. Look for keywords like system, service, application, or proper names of services.
The Default Value section appears if you select Text for the Field Type.
You can optionally enter a Default Text Value to pre-populate the field with a default value. This value will be used when no specific value can be extracted or determined.
Choice Configuration
The Choice Configuration section will appear if you select Choice or Choice (Reference) for the Field Type. In this section, configure available options for the field.
Use the Search Query box to find values within the reference table.
Select an option within the Add to Configuration field. Your selection appears in the Configured Choices section below.
(Optional) In the Configured Choices section, click + Add Manual Choice to manually add a value.
The Default Value section will appear if you select Choice or Choice (Reference) for the Field Type.
(Optional) In the Default Value section, you can configure a pre-selected option for new tickets.
In the drop-down menu, select a value. If this field is left blank, manual selection will be required for each ticket.
The AI Auto Population section will appear if you select Choice or Choice (Reference) for the Field Type.
(Optional) Guide Biggy on how to automatically select values in the AI Auto-Population section.
In the Suggestion Prompt field, provide clear instructions for when and how to auto-select different options.
For example, you can instruct Biggy to select High for urgent incidents, Medium for standard issues, and Low for minor problems based on the incident description and urgency keywords.
Constant Value
The Constant Value section will appear if you select Constant for the Field Type.
Enter a Fixed Value that will always be used for the field. This value will be used for every ticket created, regardless of the incident details.
Observability
Observability tools provide real-time system insights, metric analysis, and automated troubleshooting capabilities.
Integrated observability tools can be utilized as part of an agent team using the Observability Agent action plan.
The following observability integrations are available:
AppDynamics
The AppDynamics integration is used for full-stack/APM monitoring.
To configure the Datadog integration, populate the following fields:
Field | Description |
|---|---|
AppD Controller URL | Enter the controller URL for your AppDynamics instance. (For example, |
Client ID | Your AppDynamics Client ID is a combination of the client name and account name in this format: |
Client Secret | Auto-generated AppDynamics client secret. |
Agent Notes | Add notes to help Biggy understand your AppDynamics environment. We highly recommend configuring this field, as it allows you to enter organization-specific information that enables Biggy to provide more accurate and consistent results. For example, if your logs contain a specific field that is used to identify the type of application or service, provide that information here. |
Datadog
Beta integration
The Datadog integration is currently in Beta release status.
The Datadog integration is used for full-stack monitoring.
In Datadog, ensure the following permissions/scopes have been enabled:
apm_api_catalog_read
apm_read
apm_remote_configuration_read
apm_retention_filter_read
apm_service_catalog_read
apm_service_ingest_read
audience_management_read
continuous_profiler_pgo_read
continuous_profiler_read
debugger_read
error_tracking_read
events_read
incident_read
logs_read_data
logs_read_index_data
metrics_read
monitors_read
reference_tables_read
rum_apps_read
rum_retention_filters_read
rum_session_replay_read
synthetics_global_variable_read
synthetics_private_location_read
synthetics_read
timeseries_query
To configure the Datadog integration, populate the following fields:
Field | Description |
|---|---|
Datadog Region | The region of your Datadog instace. If you access Datadog via datadoghq.eu, select EU. If not, choose your US region. Select from US, US3, or US5. |
API Key | Your Datadog API key. |
Application Key | Your Datadog application key with required read-only scopes. |
Agent Notes | Add notes to help Biggy understand your Datadog environment. We highly recommend configuring this field, as it allows you to enter organization-specific information that enables Biggy to provide more accurate and consistent results. For example, if your logs contain a specific field that is used to identify the type of application or service, provide that information here. |
Dynatrace
The Dynatrace integration is used for application performance monitoring.
Ensure the following Dynatrace scopes/permissions have been enabled:
API v1 Scopes
DataExport
ReadConfig
ExternalSyntheticIntegration
ReadSyntheticData
API v2 Scopes
entities.read
events.read
metrics.read
problems.read
settings.read
logs.read
syntheticLocations.read
syntheticExecutions.read
To configure the Dynatrace integration, populate the following fields:
Field | Description |
|---|---|
Dynatrace URL | The URL of your Dynatrace instance. |
API Key | Your Dynatrace API key. |
Agent Notes | Add notes to help Biggy understand your Dynatrace environment. We highly recommend configuring this field, as it allows you to enter organization-specific information that enables Biggy to provide more accurate and consistent results. For example, if your logs contain a specific field that is used to identify the type of application or service, provide that information here. |
Elasticsearch
Beta integration
This integration is currently in beta release status.
The Elasticsearch integration is used for metrics monitoring. Populate the following fields to set up the integration:
Field | Description |
|---|---|
Elasticsearch Instance URL | Enter the base URL of the inbound Elasticsearch instance. Include the port if applicable. (For example, |
Username | Username of the Elasticsearch account that Biggy will use for API interactions. |
Password | Password of the Elasticsearch account that Biggy will use for API interactions. |
Validate SSL | Enable this option to send secure traffic over HTTPS with SSL validation. Disable this option to turn off SSL validation. |
Deployment | Select whether your Elasticsearch deployment is Cloud or On Prem. |
Elasticsearch Agent Notes | Add notes to help Biggy understand your Elasticsearch environment. We highly recommend configuring this field, as it allows you to enter organization-specific information that enables Biggy to provide more accurate and consistent results. For example, if your logs contain a specific field that is used to identify the type of application or service, provide that information here. |
Prometheus
Beta integration
This integration is currently in beta release status.
The Prometheus integration is used for metrics monitoring. Configure the following fields to set up the integration:
Field | Description |
|---|---|
Prometheus Instance URL | Enter the base URL of the inbound Prometheus instance. Include the port, if applicable. (For example, |
Username and Password | Add credentials of the Prometheus account that Biggy should use for API interactions. |
Validate SSL | Enable this option to send secure traffic over HTTPS with SSL validation. Disable this option to turn off SSL validation. |
Splunk
Beta integration
This integration is currently in beta release status.
The Splunk integration is used for log monitoring. Configure the following fields to set up the integration:
Field | Description |
|---|---|
Splunk Instance URL | Enter the Base URL and Port of the inbound Splunk instance. (For example, |
Username and Password | Add credentials of the Splunk account that Biggy should use for API interactions. |
Validate SSL | Enable this option to send secure traffic over HTTPS with SSL validation. Disable this option to turn off SSL validation. |
Agent Notes | Add notes to help Biggy understand your Splunk environment. We highly recommend configuring this field, as it allows you to enter organization-specific information that enables Biggy to provide more accurate and consistent results. For example, if your logs contain a specific field that is used to identify the type of application or service, provide that information here. |
Conferencing
Conferencing integrations enable automated meeting management, transcription analysis, and action item tracking.
The following Conferencing integrations are available:
Microsoft Teams
The Microsoft Teams integration is used for collaboration and communication.
Chat
The Microsoft Teams integration is also part of the Chat integration category.
To configure the Microsoft Teams integration, enter your Tenant ID and the Default User ID (GUID) of the user that your organization will use for meeting creation.
Slack
The Slack integration is used for collaboration and communication.
Chat
The Slack integration is also part of the Chat integration category.
Due to rate limitations of the Slack API, retrieving all channels is done through a channel sync mechanism. Once synced, all channels are then available for selection in relevant settings and action plan configuration screens of the web app.
Click the Sync Channels button to sync or resync your Slack channels. We recommend syncing periodically to ensure your channel selection stays up to date.
Private channels
If you'd like to sync private Slack channels, be sure to add Biggy to those channels first.
Rate limitations
Syncing may take some time given the throttling required to stay within the Slack rate limitations.
Webex
The Webex integration is used for team collaboration and meetings.
Chat
The Webex integration is also part of the Chat integration category.
To configure the Webex integration, enter your Webex API Key.
Zoom
The Zoom integration is used for Biggy Scribe (AI Transcription) as well as creating bridge calls.
Zoom admin
To set up the Zoom integration, you must have administrator rights in the Zoom application.
To set up the Zoom integration, click the Connect Zoom button and sign in with your administrator credentials.
Configuration requirements
To complete the integration for this app, do not populate the Account ID, Client ID, or Client Secret fields.
Configuration Management
Configuration management tools enable automated system changes, compliance checks, and configuration analysis.
The following Configuration Management integrations are available:
OpsLevel
The OpsLevel integration is used for service ownership and maturity tracking.
To configure the OpsLevel integration, enter your OpsLevel API Key.
Chat
Chat tools enable direct user interaction, automated notifications, and contextual assistance within team communication channels.
The following chat integrations are available: