Integration Studio
Integration Studio lets you build custom outbound integration workflows that send incident data from BigPanda to your external tools. Instead of manually configuring webhooks and writing JSON payloads, you describe what you want the integration to do and Integration Studio generates a structured workflow that you can visually edit, test, and deploy.
Use Integration Studio when you need to send incident data to external systems such as ticketing platforms, collaboration tools, or custom webhooks, especially when your workflow requires conditional logic, data transformation, or authentication.
Key Features
AI-assisted workflow generation from natural language descriptions
Visual workflow editor with drag-and-drop nodes
Conditional routing based on incident attributes and event types
Built-in support for OAuth authentication
Data transformation using templates and dynamic variables
External ID tracking for linking BigPanda incidents to external records
Import and export workflow configurations as JSON
Before You Start
Make sure you have admin or integration management permissions in BigPanda.
Identify the external system you want to connect to, including its API endpoint, authentication method, and expected payload format.
Set up an auto-share rule if you want incidents to be sent to your integration automatically.
Create an Integration Studio Workflow
1. Add a New Integration
Go toIntegrationsand clickAdd Integration.
Search forIntegration Studioand select it.
Enter a name for your integration and generate an app key.
ClickContinueto open the Workflow Designer.
2. Generate a Workflow with a Prompt
In the Workflow Designer, you can describe what you want the integration to do in plain language. For example:
"Create an integration that checks if an incident is new. If it is new, transform the payload and send it to my webhook endpoint. Save the external ID from the response. If the incident is an update, include the external ID in the update payload and send it to a different endpoint."
After you enter your description and clickContinue, Integration Studio generates a workflow based on your prompt. The generated workflow appears as a visual node graph that you can review and modify.
📘 Prompt Tips
Include specific details in your prompt for better results. Mention target tools, event types you want to handle, field mappings, and any routing logic. The more specific your prompt, the closer the generated workflow will be to your final configuration.
3. Review and Edit the Workflow
The Workflow Designer displays your integration as a series of connected nodes. Each node represents a step in the workflow.
You can:
Add, remove, or reorder nodes on the canvas
Click any node to configure its settings in the side panel
Adjust routing rules and error handling paths
Wire connections between nodes by dragging lines on the canvas
Switch between the visual editor and code view to see the raw JSON configuration
📘 Available Variables
Use theParameterspanel to browse all available variables from the share payload. These include incident metadata, alert tags, and integration-specific values that you can reference in your templates.
4. Save and Activate
When your workflow is ready, clickSave. You can set the workflow status toActiveorInactive:
Active-- the workflow runs when incidents are shared to this integration.
Inactive-- the workflow is saved but does not run. Use this while you are still building or testing.
Node Types
Integration Studio workflows are built from the following node types.
Flow Control
Routes workflow execution based on a condition, similar to a switch statement. You define a source variable and a set of matching values. Each match routes to a different path in the workflow.
Common uses:
Route by event type (for example,
incident#newvs.incident#updated)Branch based on severity, environment, or tag values
Define a default path for unmatched conditions
On the canvas, flow control nodes display one outgoing line per route option. Connect each line to the target node for that path.
Transform
Transforms incoming data into a new payload shape for downstream nodes. Use Handlebars-style templates to reference variables from the share payload or from previous node outputs.
Common uses:
Build a JSON body for an HTTP request
Reshape incident data to match an external system's expected format
Extract and combine fields from multiple sources
Example template:
{
 "event_type": "{{metadata.event_type}}",
 "incident_id": "{{incident.id}}",
 "status": "{{incident.status}}"
}
The output of a transform node is stored as a variable that you can reference in later nodes.
OAuth
Obtains a Bearer token from an OAuth provider for use in downstream HTTP requests.
Configuration:
Client ID-- your OAuth client identifier
Client Secret-- your OAuth client secret
Grant Type-- the OAuth grant type (for example,
client_credentials)Token URL-- the endpoint to request the token from
The token is stored as a variable (for example,access_token) and can be referenced in HTTP request headers.
HTTP Request
Sends an HTTP request to an external endpoint.
Configuration:
Method-- the HTTP method (GET, POST, PUT, etc.)
URL-- the target endpoint
Headers-- request headers as a JSON string
Body-- the request body, which can include template variables
WhenPerform Request Transformationis enabled, the URL, headers, and body are processed as templates before the request is sent. This lets you insert dynamic values from the share payload or previous node outputs.
The response body and status code are stored as variables for use in subsequent nodes.
Save ID
Saves an external ID from a response and links it to the BigPanda incident. This is essential for update workflows where subsequent shares need to reference the external record.
Configuration:
External ID-- the variable containing the ID to save (for example,
createResponse.id)Unlock Shares-- when enabled, allows subsequent shares to proceed after the ID is saved
Flow Control Wiring
When configuring a flow control node, the side panel defines only the source variable and matching values. You wire each outgoing path to its target node directly on the canvas by dragging a connection line.
Import and Export Configurations
You can import and export workflow configurations as JSON files.
Export-- download the current workflow configuration for version control or sharing with your team.
Import-- upload a JSON configuration to create or update a workflow. Integration Studio validates the configuration and surfaces any errors.
🚧 Import Validation
Imported configurations are validated against the supported node types and structure. If the configuration contains errors, Integration Studio displays them so you can correct the file before saving.
Runtime Behavior
When an incident is shared to an Integration Studio workflow:
BigPanda evaluates the workflow starting from the first node.
Each node executes in sequence, following the defined connections and branches.
Transform nodes process templates and store outputs as variables.
HTTP request nodes send data to external endpoints and capture responses.
If a Save ID node is present, the external ID is linked to the incident for future shares.
All node outputs are stored as workflow variables and can be referenced by any subsequent node in the flow.
Example Workflow
A common Integration Studio workflow handles new incidents differently from updates:
Flow Control-- checks
metadata.firstTimeto determine if this is the first share for the incident.Transform (New Path)-- builds a creation payload with incident details.
HTTP Request (New Path)-- sends the payload to the external system's create endpoint.
Save ID-- captures the external ID from the response and saves it.
Transform (Update Path) -- builds an update payload that includes the saved external ID.
HTTP Request (Update Path) -- sends the update payload to a separate endpoint.
Troubleshooting
Symptom | Likely Cause | Solution |
|---|---|---|
Workflow does not execute when an incident is shared | Workflow status is set to Inactive | Open the workflow and set the status to Active. |
Transform node produces unexpected output | Template references an incorrect or missing variable | Check the Parameters panel for available variable names and verify your template syntax. |
HTTP request returns an authentication error | OAuth node is missing or misconfigured | Verify that the OAuth node has the correct Client ID, Client Secret, Grant Type, and Token URL. |
External ID is not saved | Save ID node references an incorrect variable | Verify that the variable name in the Save ID node matches the output variable from the preceding HTTP request or transform node. |
Imported configuration fails validation | JSON structure contains unsupported node types or missing fields | Review the error messages displayed during import and correct the JSON file. |
Next Steps
AutoShare Rules -- set up automatic sharing to trigger your Integration Studio workflow.
Incident Tags -- learn about incident data that you can use in your workflow templates.