pub struct UpdateActivityRequest {Show 18 fields
pub due_date: Option<String>,
pub due_time: Option<String>,
pub duration: Option<String>,
pub deal_id: Option<i32>,
pub lead_id: Option<Option<Uuid>>,
pub person_id: Option<i32>,
pub project_id: Option<Option<i32>>,
pub org_id: Option<i32>,
pub location: Option<String>,
pub public_description: Option<String>,
pub note: Option<String>,
pub subject: Option<String>,
pub type: Option<String>,
pub user_id: Option<i32>,
pub participants: Option<Vec<Value>>,
pub busy_flag: Option<bool>,
pub attendees: Option<Vec<Value>>,
pub done: Option<Done>,
}
Fields§
§due_date: Option<String>
The due date of the activity. Format: YYYY-MM-DD
due_time: Option<String>
The due time of the activity in UTC. Format: HH:MM
duration: Option<String>
The duration of the activity. Format: HH:MM
deal_id: Option<i32>
The ID of the deal this activity is associated with
lead_id: Option<Option<Uuid>>
The ID of the lead in the UUID format this activity is associated with
person_id: Option<i32>
The ID of the person this activity is associated with
project_id: Option<Option<i32>>
The ID of the project this activity is associated with
org_id: Option<i32>
The ID of the organization this activity is associated with
location: Option<String>
The address of the activity. Pipedrive will automatically check if the location matches a geo-location on Google maps.
public_description: Option<String>
Additional details about the activity that is synced to your external calendar. Unlike the note added to the activity, the description is publicly visible to any guests added to the activity.
note: Option<String>
The note of the activity (HTML format)
subject: Option<String>
The subject of the activity
type: Option<String>
The type of the activity. This is in correlation with the key_string
parameter of ActivityTypes.
user_id: Option<i32>
The ID of the user whom the activity is assigned to
participants: Option<Vec<Value>>
List of multiple persons (participants) this activity is associated with. It requires a structure as follows: [{\"person_id\":1,\"primary_flag\":true}]
busy_flag: Option<bool>
Set the activity as ‘Busy’ or ‘Free’. If the flag is set to true
, your customers will not be able to book that time slot through any Scheduler links. The flag can also be unset by never setting it or overriding it with null
. When the value of the flag is unset (null
), the flag defaults to ‘Busy’ if it has a time set, and ‘Free’ if it is an all-day event without specified time.
attendees: Option<Vec<Value>>
The attendees of the activity. This can be either your existing Pipedrive contacts or an external email address. It requires a structure as follows: [{\"email_address\":\"mail@example.org\"}]
or [{\"person_id\":1, \"email_address\":\"mail@example.org\"}]
done: Option<Done>
Implementations§
Source§impl UpdateActivityRequest
impl UpdateActivityRequest
pub fn new() -> UpdateActivityRequest
Trait Implementations§
Source§impl Clone for UpdateActivityRequest
impl Clone for UpdateActivityRequest
Source§fn clone(&self) -> UpdateActivityRequest
fn clone(&self) -> UpdateActivityRequest
1.0.0 · Source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source
. Read more