Actions360
- Access Review Actions
- Access Review Source Actions
- AI System Actions
- Asset Actions
- Attachment Actions
- Audit Actions
- Audit Log Actions
- Business Function Actions
- Compliance Portal Actions
- Activate Access
- Create
- Create Access
- Create Commitment
- Create Commitment Group
- Create Custom Link
- Create Reference
- Deactivate Access
- Delete
- Delete Audit
- Delete Commitment
- Delete Commitment Group
- Delete Custom Link
- Delete Document
- Delete File
- Delete Reference
- Delete Third Party
- Get
- Get Many
- Get Many Commitment Groups
- Get Many Commitments
- Get Many Files
- Get Many References
- Update
- Update Audit Visibility
- Update Commitment
- Update Commitment Group
- Update Document Visibility
- Update Third Party Published
- Connector Actions
- Control Actions
- Cookie Banner Actions
- Cookie Category Actions
- Cookie Consent Record Actions
- Data Actions
- Device Actions
- Document Actions
- Archive
- Cancel Signature
- Create
- Delete
- Delete Draft Version
- Get
- Get Approval Decision
- Get Approval Quorum
- Get Latest Published Version ID
- Get Many
- Get Many Approval Decisions
- Get Many Approval Quorums
- Get Many Signatures
- Get Many Versions
- Get Signature
- Get Version
- Publish
- Request Signature
- Unarchive
- Update
- Update Version
- Void Approval
- DPIA Actions
- Employee Portal Actions
- Evidence Actions
- Execute Actions
- Finding Actions
- Framework Actions
- Internal Control Actions
- Obligation Actions
- Organization Actions
- Organization Context Actions
- Processing Activity Actions
- Resource Alias Actions
- Rights Request Actions
- Risk Actions
- Risk Analysis Actions
- Create
- Create Boundary
- Create Diagram
- Create Node
- Create Process
- Create Scenario
- Create Threat
- Delete
- Delete Boundary
- Delete Diagram
- Delete Node
- Delete Process
- Delete Scenario
- Delete Threat
- Fork
- Get
- Get Boundary
- Get Diagram
- Get Diagram Mermaid Chart
- Get Many
- Get Many Boundaries
- Get Many Diagrams
- Get Many Nodes
- Get Many Processes
- Get Many Scenarios
- Get Many Threats
- Get Node
- Get Process
- Get Scenario
- Get Threat
- Link Scenario Risk
- Link Scenario Threat
- Publish
- Unlink Scenario Risk
- Unlink Scenario Threat
- Update
- Update Boundary
- Update Diagram
- Update Node
- Update Process
- Update Scenario
- Update Threat
- Statement of Applicability Actions
- Task Actions
- Task Activity Actions
- Task Comment Actions
- Third Party Actions
- Create
- Create Contact
- Create Risk Assessment
- Create Service
- Delete
- Delete Business Associate Agreement
- Delete Compliance Report
- Delete Contact
- Delete Data Privacy Agreement
- Delete Service
- Get
- Get Business Associate Agreement
- Get Contact
- Get Data Privacy Agreement
- Get Many
- Get Many Child Third Parties
- Get Many Compliance Reports
- Get Many Contacts
- Get Many Risk Assessments
- Get Many Services
- Get Risk Assessment
- Get Service
- Link Third Party
- Publish List
- Unlink Third Party
- Update
- Update Business Associate Agreement
- Update Contact
- Update Data Privacy Agreement
- Update Service
- Vet
- TIA Actions
- Tracker Pattern Actions
- Treatment Plan Actions
- User Actions
- Webhook Actions
Compliance Portal → Update Third Party Published
AI-generatedSummary
Update the published status of a third party on a specified compliance portal to control its visibility.
Inputs
- Authentication (required) — Select API Key for authenticating requests.
- Compliance Portal ID (required) — Specify the ID of the compliance portal where the third party publication status is to be updated.
- Third Party ID (required) — Provide the ID of the third party whose published status is to be updated on the compliance portal.
- Published (required) — Boolean to set whether the third party should be published (true) or unpublished (false). Use the Delete Third Party operation to remove the third party entirely.
Output shape
a single JSON object containing the updated third party publication information or response from the API
The operation returns data reflecting the new published status of the third party. Errors or unsuccessful updates will return error messages through the node execution. No pagination applies for this operation.