CRM v1 current
crm.
Logs what was discussed in a call on a client's record, naming the client; optionally creates the follow-up with its date. Reads nothing and calls no one.
Last updated
POST /api/v1/actions/crm.call_logged- Key scope
crm.call_logged@1- Workspace permission
api.crm.call_loggedoff by default
Two permissions, not one
Both are needed: a key with that scope, and the workspace owner having switched the permission on. Holding the key is not enough — they are two decisions made by different people.
Request
| field | type | rules | |
|---|---|---|---|
client | string | required | min 1 · max 200 |
summary | string | required | min 1 · max 4000 |
followUp | object | optional |
followUp
| field | type | rules | |
|---|---|---|---|
what | string | optional | min 1 · max 500 |
dueAt | string (date-time) | required |
Response — output when status is done
| field | type | rules | |
|---|---|---|---|
clientId | string | required | |
clientName | string | required | |
activityId | string | required | |
followUpId | string | null | required |
Example
# One request, one idempotency key: retrying with the same key never runs twice.
curl -X POST https://niiko.org/api/v1/actions/crm.call_logged \
-H "Authorization: Bearer nk_…" \
-H "Idempotency-Key: $(uuidgen)" \
-H "Content-Type: application/json" \
-d '{
"client": "…",
"summary": "…"
}'
# 200 → done · 202 → pending_approval (a person signs later) · 4xx → refused, with a named reasonWhy it may refuse
Each reason names who can fix it and how. With reason stale, detail.message says what to do.
cliente_no_encontradocliente_ambiguodemasiados_clientessin_permiso
In the clients
| @vorluno/niiko-sdk | niiko.loggedCall() |
| niiko (Python) | niiko.logged_call() |
| niiko-cli | niiko run crm.call_logged |
| n8n-nodes-niiko | crmCallLogged |
| niiko-mcp-server | crm_call_logged |