ActivitiesAttendees
Get all Activities attendees
Select
The add-in will use the Pipedrive API to process WHERE clause conditions built with the following columns and operators. The rest of the filter is executed client side within the add-in.
- ActivitiesId supports the '=' operator.
- FilterId supports the '=' operator.
- OwnerId supports the '=' operator.
- DealId supports the '=' operator.
- LeadId supports the '=' operator.
- PersonId supports the '=' operator.
- OrgId supports the '=' operator.
- Done supports the '=' operator.
For example, the following query is processed server side:
SELECT * FROM ActivitiesAttendees WHERE ActivitiesId = 246 SELECT * FROM ActivitiesAttendees WHERE Done = false SELECT * FROM ActivitiesAttendees WHERE PersonId = 1 SELECT * FROM ActivitiesAttendees WHERE DealId = 2 SELECT * FROM ActivitiesAttendees WHERE OrgId = 1
Columns
| Name | Type | References | Description |
| ActivitiesId [KEY] | Integer |
Activities.Id | Activities ID. |
| EmailAddress [KEY] | String | EmailAddress. | |
| IsOrganizer | Boolean | IsOrganizer. | |
| Name | String | Name. | |
| AttendeePersonId | Integer | AttendeePersonId. | |
| Status | String | Status. | |
| UserId | Integer | UserId. |
Pseudo-Columns
Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.
| Name | Type | Description | |
| FilterId | Integer | The ID of the Filter to use. | |
| OwnerId | Integer | The id of the owner of the activity. | |
| DealId | Integer | The id of the deal corresponding to the activity | |
| LeadId | String | The Id of the lead corresponding to the activity. | |
| PersonId | Integer | The id of the person corresponding to the activity. | |
| OrgId | Integer | The id of the organisation corresponding to the activity. | |
| Done | Boolean | Whether the Activity is done or not. If omitted, returns both Done and Not done activities. |