CRM

Log a call, a meeting, a note or a follow-up

Records something against a customer or a deal. Two fields decide what it means and they are never merged: completed_at is when it HAPPENED (a call you are writing up), due_at is when it is PLANNED (a follow-up nobody has done yet). Give one, or both when you are logging a call and booking the next one. A note is completed the moment it is written and takes no due date. A planned activity becomes the deal’s next action, which is what stops it going quiet — so booking one is usually the useful half.

post/api/v1/rest/crm/activities

Request

  • Base URL: https://api.custodo.ai
  • URL: https://api.custodo.ai/api/v1/rest/crm/activities
  • Auth: HTTP bearer

Headers

X-Tenant-Idstring uuid

The organisation to act in. An API key is bound to exactly one, so this is optional for a key and must match the one it was minted for.

Request body

subject_type'party' | 'deal' required

deal for a trattativa, party for a customer with no deal in play.

subject_idstring uuid required

The deal id it hangs off, or the anagrafica id (from anagrafiche_search_parties) for a customer.

kind'task' | 'call' | 'meeting' | 'note' | 'email' | 'document' required

call, meeting, task, note, email or document.

titlestring required

One line, in Italian.

bodystring

What was said, or what has to be done.

due_atstring date-time

When it is planned, ISO-8601 with a timezone: 2026-09-03T15:00:00Z.

completed_atstring date-time

When it actually happened, ISO-8601 with a timezone. Backdating is normal.

direction'inbound' | 'outbound'

Only for a call or an email: who rang whom.

outcomestring

How it went, in a few words.

duration_minutesinteger

Response

Done. data is the tool’s own answer.

oktrue required
dataunknown required

Changes

No recorded changes to this operation across all 1 revision of this API.