> ## Documentation Index
> Fetch the complete documentation index at: https://docs.blinkops.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Case Linked

> Trigger a workflow automatically when cases are linked together in Blink case management.

<Note>
  **Note**
  For `long-text` fields (e.g., `Summary`), the returned value will be a substring of the full content. To obtain the complete value, retrieve the entire case.
</Note>

<Note>
  **Note**
  Workflows based on this trigger will search for new events **every minute**.
</Note>

## Sample Event

```json theme={"dark"}
{
	"case_record": {
		"alert_ids": null,
		"attachment_ids": null,
		"auto_id": 1,
		"case_id": "INC-00001",
		"case_ids": null,
		"case_manager": null,
		"case_tags": null,
		"close_reason": null,
		"closed_at": null,
		"closed_by": null,
		"closed_by_automation": false,
		"collaborators": null,
		"created_at": 1732194432630,
		"created_by": "test@blinkops.com",
		"id": "bb2a5fcc-423b-4536-8b7a-63a547216579",
		"observable_ids": null,
		"mitre_attack": null,
		"name": "New Case",
		"observable_ids": null,
		"overview": null,
		"severity": 1,
		"sla": null,
		"sla_expiry": null,
		"status": "OPEN",
		"summary": null,
		"task_ids": [
			"a4be5ac6-399f-4b0c-b04e-ed323148c5de"
		],
		"type": null,
		"updated_at": 1732194441635,
		"updated_by": "test@blinkops.com",
		"vendors": null
	},
	"linked_record": {
		"alert_ids": null,
		"assigned_to": null,
		"attachment_ids": null,
		"auto_id": 1,
		"case_ids": [
			"bb2a5fcc-423b-4536-8b7a-63a547216579"
		],
		"closed_at": null,
		"created_at": 1708250747614,
		"created_by": "test@blinkops.com",
		"description": null,
		"due_date": null,
		"id": "a4be5ac6-399f-4b0c-b04e-ed323148c5de",
		"is_blocking": false,
		"name": "New Task",
		"observable_ids": null,
		"priority": 1,
		"task_id": "Task-00001",
		"status": "OPEN",
		"task_ids": null,
		"updated_at": 1732194441635,
		"updated_by": "test@blinkops.com"
	},
	"linked_record_table_name": "tasks"
}
```

***

## Testing Workflows Triggered by a Case Event

When building a workflow triggered by a case event, the testing parameters include a “Fetch event” button. This button retrieves a recent case ID for testing purposes.

However, it’s important to note that the returned case ID may reference a case that has been deleted since the last polling interval. This behavior is expected and by design.

As a result, the fetched ID may not always return valid case data when used in subsequent steps.

**Recommendation:**
Builders should account for this scenario by implementing appropriate error handling in their workflows to manage cases where the retrieved ID is no longer valid.