The "Create One Incident" database component in workflows fails to create incidents, returning an empty {} response and triggering the Error port. #364

Closed
opened 2026-04-05 16:19:28 +02:00 by MrUnknownDE · 0 comments
Owner

Originally created by @vivek-dodia on 9/29/2025

Description:
The "Create One Incident" database component in workflows fails to create incidents, returning an empty {} response and triggering the Error port.

Steps to Reproduce:

  1. Create a workflow with webhook trigger receiving Alertmanager payloads
  2. Parse alert data with JavaScript component
  3. Add "Create One Incident" component with the following JSON arguments:
{
  "projectId": "10620f90-3148-4b62-8ac1-810f36a8c2bd",
  "title": "Test Incident",
  "description": "Test description",
  "incidentSeverityId": "c262c774-09b3-4b82-96b5-e9e8aa17309b"
}
4. Trigger the workflow

Expected Behavior:
Incident should be created successfully

Actual Behavior:
- Component returns empty {}
- Workflow executes Error port
- No incident is created
- Component logs show no error message (just empty object)

Environment:
- OneUptime: Latest version
- Component: Create One Incident (incident-create-one-1)
- Workflow: Custom webhook-triggered workflow

Additional Context:
The component appears to be missing API authentication headers (ApiKey and ProjectID) required by the /api/incident endpoint. Workaround is to use "Make an HTTP Request" component instead with manual authentication headers.

Is the database component supposed to automatically use project credentials, or should authentication be configurable?
*Originally created by @vivek-dodia on 9/29/2025* **Description:** The "Create One Incident" database component in workflows fails to create incidents, returning an empty `{}` response and triggering the Error port. **Steps to Reproduce:** 1. Create a workflow with webhook trigger receiving Alertmanager payloads 2. Parse alert data with JavaScript component 3. Add "Create One Incident" component with the following JSON arguments: ```json { "projectId": "10620f90-3148-4b62-8ac1-810f36a8c2bd", "title": "Test Incident", "description": "Test description", "incidentSeverityId": "c262c774-09b3-4b82-96b5-e9e8aa17309b" } 4. Trigger the workflow Expected Behavior: Incident should be created successfully Actual Behavior: - Component returns empty {} - Workflow executes Error port - No incident is created - Component logs show no error message (just empty object) Environment: - OneUptime: Latest version - Component: Create One Incident (incident-create-one-1) - Workflow: Custom webhook-triggered workflow Additional Context: The component appears to be missing API authentication headers (ApiKey and ProjectID) required by the /api/incident endpoint. Workaround is to use "Make an HTTP Request" component instead with manual authentication headers. Is the database component supposed to automatically use project credentials, or should authentication be configurable? ```
Sign in to join this conversation.
No Label
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github/oneuptime#364