Update note in Planhat
CRM API · write, waits for approval · 100% field coverage
Your agent can update note in Planhat through Apideck's CRM API, the same call it makes for every CRM app. It changes data in the customer's Planhat account, so it stops with the exact request until a person approves it. Apideck adds the customer's Planhat credentials, so no token ever reaches the agent.
The call
PATCH https://unify.apideck.com/crm/notes/{id}
Headers: x-apideck-service-id: planhat, plus your app id and the customer's consumer id. Apideck MCP tool: crm-notes-update. Agent operation id: unified.crm.notesUpdate.
| Parameter | In | Description |
|---|---|---|
| id · required | path | ID of the record you are acting upon. |
Body fields
| Field | Type | Description |
|---|---|---|
| title | string | The title of the note |
| content | string | The content of the note. |
| owner_id | string | The user that owns the note. |
| contact_id | string | The contact that is related to the note. |
| company_id | string | The company that is related to the note. |
| opportunity_id | string | The opportunity that is related to the note. |
| activity_id | string | The activity that is related to the note. |
| lead_id | string | The lead that is related to the note. |
| active | boolean | Whether the Note is active or not. |
More for notes in Planhat
Update note in other CRM apps
The same call works for each of these; only the service id changes.
CloseFolkFreshworks CRMHubSpotMicrosoft Dynamics CRMOdooPipedriveSalesforceZoho CRM