New Secret Detected

Data Element for a New Secret

Overview

The tables below define the data elements available in the Workflow action for a New Secret Detected trigger.

Please note you will need to prepend all data elements with data.

Example: data.secret.id

---

Event Metadata

Name	Example value	Description
workflow_execution_id	6823	Unique identifier for the workflow execution
workflow_id	11	Unique identifier for the workflow definition
tenant_id	demo	Tenant identifier where the event originated
resource_id	h4r>>github>>github_repository>>acme>>demo-tracker	Heeler resource identifier for the repository
repository_id	911827810	Repository numeric identifier
repository_url	https://github.com/acme/demo-tracker	Repository URL

---

Secret

Name	Example value	Description
secret.id	1949	Unique identifier for the secret finding within Heeler
secret.repository_id	h4r>>github>>github_repository>>acme>>demo-tracker	Heeler repository identifier where the secret was detected
secret.rule_id	openai.2	Detector rule identifier that matched the secret
secret.confidence	medium	Confidence level of the match (as determined by the detector)
secret.validation_status	Active Credential	Validation status for the secret (e.g., whether it appears usable/active)
secret.validation_response	{...}	Validator output/details (when available). May include provider-specific response data.
secret.exception_status	NO_EXCEPTION	Indicates whether the secret is exempted by policy
secret.language	Java	Programming language associated with the file containing the secret
secret.path	src/main/java/com/example/bugtracker/service/AiTriageService.java	Path within the repository where the secret was detected
secret.file_path	src/main/java/com/example/bugtracker/service/AiTriageService.java	File path where the secret was detected (may mirror secret.path)
secret.file_url	https://github.com/acme/demo-tracker/blob/.../AiTriageService.java#L18	Deep link to the file and line in the SCM (when available)
secret.column_start	50	Start column of the match within the line (when available)
secret.column_end	213	End column of the match within the line (when available)
secret.git_command	git show f8f6268...:src/main/java/.../AiTriageService.java	Git command that can be used to retrieve the file contents at the relevant commit
secret.git_commit_id	f8f62683228a034f32be4722163f94166473d64f	Commit SHA where the secret was detected
secret.git_commit_date	2026-02-09	Commit date for the detected secret
secret.git_comitter_name	demo-hai	Name/handle of the committer for the commit containing the secret
secret.git_comitter_email	[email protected]	Email address of the committer for the commit containing the secret
secret.created_at	2026-02-10T04:11:42.591081	Timestamp when the secret finding was created in Heeler
secret.updated_at	2026-02-10T04:11:42.686057	Timestamp when the secret finding was last updated in Heeler
secret.repository_url	https://github.com/acme-demo/demo-tracker	Repository URL (when included on the secret object)

---

Resource (Repository)

Name	Example value	Description
resource.id	911827810	Internal identifier for the repository
resource.org	acme-demo	Organization that owns the repository
resource.name	demo-tracker	Repository name
resource.full_name	acme-demo/demo-tracker	Fully qualified repository name
resource.description	Bug tracker for acme	Repository description (when available)
resource.language	Java	Primary programming language
resource.default_branch	main	Default branch of the repository
resource.created_at	2025-01-04T00:35:04	Repository creation timestamp
resource.pushed_at	2026-02-10T04:07:57	Timestamp of the most recent push to the repository
resource.updated_at	2026-02-10T04:08:00	Last update timestamp
resource.html_url	https://github.com/acme-demo/acme-tracker	Repository URL
resource.clone_url	https://github.com/acme-demo/acme-tracker.git	Git clone URL
resource.ssh_url	[email protected]:acme-demo/acme-tracker.git	SSH clone URL
resource.private	true	Indicates whether the repository is private
resource.visibility	internal	Visibility level of the repository in Heeler
resource.custom_properties	{"BU":"Engineering"}	Custom repository metadata ingested from the SCM (when available)
resource.tech_lead.email	[email protected]	Assigned technical lead (when available)
resource.security_lead.email	[email protected]	Assigned security lead (when available)
resource.url	https://demo.heeler.com/.../repositories/...acme-tracker	Direct link to the repository in the Heeler UI

---

Team (Optional Context)

Name	Example value	Description
team.id	6	Internal identifier for the team (when included)
team.name	Raiders	Team name (when included)