Update a Meeting activity
Most commonly this can be used to update a meetings’s user_note_html or outcome_id.
Authentication
Bearer authentication of the form Bearer <token>, where token is your auth token.
Path parameters
Request
Response
Type of the activity, e.g. Call, Email or Note.
When the activity happened, e.g. when an Email or SMS was sent. Defaults to date_created.
ID of the Contact the activity is with, or null if it isn’t with a particular Contact.
How the value was chosen: user-selected by a user, or autodetected by AI.
ID of the user who created the activity, or null if it wasn’t created by a user.
ID of the activity, e.g. acti_abc123.
ID of the Lead the activity is on. Can be null for Calls and SMS with phone numbers that don’t match any Contact.
How the Outcome was set: autofilled by AI, user-selected by a user, or voicemail-dropped automatically after a voicemail drop.
How the value was chosen: user-selected by a user, or autodetected by AI.
How the Meeting got into Close: calendar if it was synced from a connected calendar, manual if it was created in Close.
Status of the Meeting. canceled means it was removed from the synced calendars or has no Lead participants left. declined-by-org means every Close user declined it, declined-by-lead that a Lead participant declined it and none accepted.
ID of the user who last updated the activity, or null if it wasn’t updated by a user.
ID of the user the activity belongs to, e.g. who made the Call or sent the Email. Can be null, e.g. for an incoming SMS to a group number.
Name of the user in created_by.
Name of the user in updated_by.
Name of the user in user_id.
Deprecated. Use created_by_agent_id instead.