/v1/calendar/events/linkPut an existing meeting on a record
Files a meeting the person ALREADY HAS on their own calendar on a record, instead of booking a second one. Body: providerEventId (the entry's providerEventId from get_calendar_events with from/to), definitionKey + rowId (the record), and account to read one connected calendar only (left out, each connected calendar is tried in turn, past one that needs reconnecting). The calendar is only read: the meeting stays the person's, so moving or renaming it is done in Google or Outlook (patch_calendar_events_id refuses a linked meeting) and delete_calendar_events_id takes it OFF THE RECORD without touching their calendar. Linking the same meeting to the same record again answers the existing link; one already on another record, or on a colleague's, is a 409.
Access class: workspace.
Send request
Use the documented inputs to call this endpoint directly.
Request body
application/jsonrequiredResponses
the action's answer
{
"data": {
"attendees": [
"string"
],
"calendarId": "",
"cancelledAt": "2026-01-01T00:00:00Z",
"createdAt": "2026-01-01T00:00:00Z",
"definitionId": "",
"definitionKey": "string",
"endsAt": "2026-01-01T00:00:00Z",
"id": "",
"meetingUrl": "string",
"memberUserId": 1,
"origin": "string",
"provider": "string",
"providerEventId": "",
"rowId": "",
"startsAt": "2026-01-01T00:00:00Z",
"status": "string",
"taskId": 1,
"title": "string",
"updatedAt": "2026-01-01T00:00:00Z"
}
}a refusal: {"error": "<what a person needs to read>"}. 401 no credential, 402 the plan does not include this, 403 the seat does not, 404 the thing does not exist or is not yours to see.
{
"error": "string"
}