Actions125
- Ticket Actions
- Ticket Note Actions
- Ticket Attachment Actions
- Company Actions
- Company Note Actions
- Company Attachment Actions
- Contact Actions
- Resource (Employee) Actions
- Contract Actions
- Contract Note Actions
- Project Actions
- Project Note Actions
- Task Actions
- Task Note Actions
- Time Entry Actions
- Configuration Item Actions
- Configuration Item Note Actions
- Product Actions
- Opportunity Actions
- Quote Actions
- Quote Item Actions
- Service Call Actions
- Invoice Actions
- Subscription Actions
- Inventory Item Actions
- Purchase Order Actions
- Purchase Order Item Actions
Project Note → Update Project Note
AI-generatedSummary
Update an existing project note in Autotask.
Inputs
- parentId (required) — Numeric ID of the parent project.
- entityId (required) — Numeric ID of the project note to update.
- payloadJson (required) — Fields to update. The note ID is automatically merged into the request body as Autotask expects the id in the body, not the URL. Defaults to an empty JSON object.
- requestOptions — Optional header overrides for the request, such as impersonation settings. Defaults to an empty collection. Contains a single sub‑option: impersonationResourceId (string) – numeric Autotask resource ID to impersonate for this request, overriding the credential default.
Output shape
The raw Autotask response body for the updated project note (typically the updated note object).
The operation sends a PATCH request to the endpoint
/Projects/{parentId}/Notes/{entityId}with a body that merges the supplied payload with{ id: <entityId> }. On success, the node returns the response as‑is. If the request fails, an error is thrown unless the node’s continueOnFail option is enabled.
Examples
Example 1: Change the description of a project note.
Set parentId to the project’s numeric ID, entityId to the note’s numeric ID, and payloadJson to { description: 'Updated note text' }.
