Retrieve all activities from Pipedrive.
Application
Pipedrive
Inputs (what you have)
Name | Description | Data Type | Required? | Example |
Connected account | The connected account to use for the request | Connected Account | Yes | |
Resolve properties? | By default do custom properties get returned only as ID instead of their actual name. Also option fields contain only the ID instead of their actual value. If this option gets set they get automatically resolved | True/False | No | |
Return all? | Whether to return all results or only up to a given limit | True/False | No | |
Limit | Max number of results to return | Number | No | |
Done? | Whether the Activity is done or not. 0 = Not done, 1 = Done. If omitted returns both Done and Not done activities | True/False | No | |
End date | Use the Activity due date where you wish to stop fetching Activities from. Insert due date in YYYY-MM-DD format | Datetime | No | |
Predefined filter ID | The ID of the Filter to use (will narrow down results if used together with user_id parameter) | Text (Short) | No | |
Start date | Use the Activity due date where you wish to begin fetching Activities from. Insert due date in YYYY-MM-DD format | Datetime | No | |
Type ID 1 | Type of the Activity | Text (Short) | No | |
Type ID 2 | Type of the Activity | Text (Short) | No | |
Type ID 3 | Type of the Activity | Text (Short) | No | |
User ID | The ID of the User whose Activities will be fetched. If omitted, the User associated with the API token will be used. If 0, Activities for all company Users will be fetched based on the permission sets | Text (Short) | No |
Outputs (what you get)
Name | Description | Data Type | Required? | Example |
JSON Output | JSON output returned by the API | Text (Long) | No |
Outcomes
Name | Description |
Success | This status is selected if the job has successfully completed. |
Unsuccessful | This status is selected if the job has completed unsuccessfully. |
Requirements
N/A