Relay one finished meeting note to the connector's service as the signed-in person [write]
Changed onThe Mac app's meeting-note.v1 facts for a recorded call (source, app, start and end, the matched calendar event's id and attendees, what each side said, the workspace file ids of the note), or the platform's for a settled cloud recording (source recall). Relayed exactly like ../ingest/messages — the person's workspace role picks the connector's vault, whose credential goes on POST {origin}/v1/ingest/meeting-notes and never reaches the caller — and the service decides what the note becomes (the CRM keeps only notes with a counterpart it knows and stores the transcript as a file). The body is one JSON object of at most 1 MiB; Idempotency-Key passes through, defaulting to meeting-note:<shared file id>, else the start time and app. The answer is the service's status and body as they were, with x-agentsky-relay naming the audit record. The same refusals as ../ingest/messages.
Request
- Base URLhttps://api.agentsky.dev/v1
- URLhttps://api.agentsky.dev/v1/workspace-connectors/{id}/ingest/meeting-notes
- AuthHTTP bearer
Path parameters
Headers
Request body
One meeting-note.v1 facts object
Response
The service's answer, as it was
Changes
- info
endpoint added
- info