Actions120
- Activity Actions
- API Token Actions
- Assessment Actions
- Assessment Comment Actions
- Assessment Phase Actions
- Assessment Section Actions
- Assessment Section Event Actions
- Assessment Section Template Actions
- Assessment Task Set Actions
- Assessment Template Actions
- Assessment Template Checklist Actions
- Assessment User Actions
- Checklist Actions
- Checklist Category Actions
- Checklist Category Template Actions
- Checklist Template Actions
- Client Actions
- Custom Field Actions
- Document Actions
- Finding Actions
- Finding Event Actions
- List finding events
- Create a finding comment
- Update a finding comment
- Create a finding retest
- Update a finding retest
- Create a finding retest inquiry
- Update a retest inquiry
- Create a finding retest cancelled event
- Update a retest cancelled event
- Create a finding review event
- Create a finding retest review event
- Create a remediation status change
- Update a remediation status change
- Finding Layout Actions
- Finding Template Actions
- Language Actions
- Notification Actions
- Output File Actions
- Reaction Actions
- Role Actions
- Snippet Actions
- Tag Actions
- Target Actions
- Task Actions
- Task Set Actions
- Team Actions
- Team User Actions
- Test Case Actions
- Test Case Template Actions
- Theme Actions
- Tool Finding Actions
- Tool Target Actions
- User Actions
Finding → Create a finding
AI-generatedSummary
Create a new finding within a specified assessment and assessment section, defining its details such as title, vulnerability status, review status, publication status, and various optional attributes.
Inputs
- Assessment id (required) — The ID of the assessment under which to create the finding.
- Title (required) — The title of the finding (max 191 characters).
- Assessment section id (required) — The ID of the assessment section within the assessment where the finding will be placed. The section must belong to the assessment and allow findings.
- Is vulnerability (required) — Boolean indicating if the finding is a vulnerability with associated severity metrics.
- Review status (required) — The current review status of the finding; valid options are Draft, Under Review, Revision Requested, or Approved.
- Is published (required) — Boolean indicating if the finding is published.
- Additional Fields — Optional additional fields such as tool findings linked, resolvers, severity metrics, severity (required if not vulnerability), draft documents, assignees, teams, remediation status (only if vulnerability), priority, complexity, recommended action, targets, found at date, description, risk, recommendation, proof, references, classifications, and test cases.
- Custom Fields — Custom field values to set for the finding using the node's custom fields interface.
Output shape
a single record representing the newly created finding with all submitted and assigned properties
The operation requires certain fields depending on whether the finding is marked as a vulnerability. Severity metrics are required if the finding is a vulnerability; severity is required if it is not. Parent IDs (assessment and assessment section) must be valid and consistent. The response returns the created finding resource directly.