Actions113
- Activity Actions
- Analytics Actions
- Asset Actions
- Asset Tag Actions
- Automation Actions
- Credential Actions
- Credential Inquiry Actions
- Email Actions
- HAI (AI) Actions
- Organization Actions
- Program Actions
- Add Structured Scope
- Archive Structured Scope
- Create CVE Request
- Get
- Get Balance
- Get Many
- Get Audit Log
- Get Common Responses
- Get Integrations
- Get Payment Transactions
- Get Reporters
- Get Triage Reviews
- Get Weaknesses
- Invite Hacker
- List CVE Requests
- List Hacker Invitations
- List Structured Scopes
- List Team Members
- List Awarded Swag
- List Thanks
- Mark Swag Sent
- Send Message
- Update Policy
- Update Structured Scope
- Report Actions
- Add Comment
- Add Participant
- Assign
- Award Bounty
- Award Swag
- Change State
- Close Comments
- Create
- Delete Attachment
- Export PDF
- Get
- Get Many
- Mark Ineligible
- Manage Disclosure
- Manage Retest
- Set Custom Fields
- Update Bounty Suggestion
- Update CVEs
- Update Inboxes
- Update Reference
- Update Scope
- Update Severity
- Update Tags
- Update Title
- Update Weakness
- Upload Attachment
- Write Summary
- User Actions
Report → Upload Attachment
AI-generatedSummary
Upload a file attachment to a specific HackerOne report identified by its numeric Report ID, using binary data provided in the workflow's input.
Inputs
- Report ID (required) — The numeric ID of the report to which the attachment will be uploaded.
- Binary Data (required) — The binary file content to upload as the attachment. Must be provided via n8n's standard binary input handling.
Output shape
a single JSON object containing the uploaded attachment's details as returned by the HackerOne API
The operation requires binary data to be present on the node's input under the specified binary property name. The response is the JSON representation of the created attachment resource from the HackerOne API.