How can we help?
Searching in {{docApp.searchFilterBySpecificBookTitle}}
{{docApp.searchResultFilteredItems.length}} results for: {{docApp.currentResultsSearchText}}
in {{docApp.searchFilterBySpecificBookTitle}}
Search results have been limited. There are a total of {{docApp.searchResponse.totalResultsAvailable}} matches.
You have an odd number of " characters in your search terms - each one needs closing with a matching " character!
-
{{resultItem.title}}
{{resultItem.url}}
{{docApp.libraryHomeViewProduct.title || docApp.libraryHomeViewProduct.id}}
{{docApp.libraryHomeViewProduct.description}}
{{group.title || group.id}}
{{group.description}}
Operation Information
Retrieves information about a Pipedrive Activity.
This is a Premium Integration.
Authentication
This operation requires authentication, the details of which can be securely stored on your instance in a KeySafe Key of type API Key.
To create a key of this type:
- In the Configuration area of your Hornbill instance, navigate to Platform Configuration > Security > KeySafe;
- Click on the + Create New Key button;
- On the resulting Create New Key form, choose API Key in the Type pick list;
- Give the API Key KeySafe key a Title (this is the name / identifier for the API Key account as you will see it when using the cloud automation node in your workflows);
- Optionally populate the Description field;
- Populate the following fields accordingly, then click the Create Key button to create your new key:
Name | Type | Description |
---|---|---|
ApiKey | string |
Authentication Key |
API Endpoint | string |
Optional API Endpoint |
Tip
The API Endpoint field is not required to be populated for this integration - just an API Key for your Pipedrive account.
Revoking Access
If at any point you wish to revoke access to any of the above accounts from your Hornbill instance, just delete the relevant KeySafe key(s) from the KeySafe list.
Warning
This will revoke the rights of any existing Cloud Automation Node in your Hornbill Workflows that are using the revoked API Key account, so you will need to manage these workflows accordingly.
Input Parameters
Display Name | ID | Type | Description | Required | Supported Values |
---|---|---|---|---|---|
Activity ID | id |
number |
None provided | Yes | None provided |
Output Parameters
Display Name | ID | Type | Description |
---|---|---|---|
Active? | active_flag |
boolean |
None provided |
Add Time | add_time |
string |
None provided |
Assigned to User ID | assigned_to_user_id |
number |
None provided |
Company ID | company_id |
number |
None provided |
Created by User ID | created_by_user_id |
number |
None provided |
Deal Dropbox BCC | deal_dropbox_bcc |
string |
None provided |
Deal ID | deal_id |
number |
None provided |
Deal Title | deal_title |
string |
None provided |
Done | done |
boolean |
None provided |
Due Date | due_date |
string |
None provided |
Due Time | due_time |
string |
None provided |
Duration | duration |
string |
None provided |
Google Calendar Event ID | gcal_event_id |
string |
None provided |
Google Calendar ETag | google_calendar_etag |
string |
None provided |
Google Calendar ID | google_calendar_id |
string |
None provided |
Activity ID | id |
number |
None provided |
Marked As Done Time | marked_as_done_time |
string |
None provided |
Note | note |
string |
None provided |
Organization ID | org_id |
number |
None provided |
Organization Name | org_name |
string |
None provided |
Owner Name | owner_name |
string |
None provided |
Person Dropbox BCC | person_dropbox_bcc |
string |
None provided |
Person ID | person_id |
number |
None provided |
Person Name | person_name |
string |
None provided |
Reference ID | reference_id |
number |
None provided |
Reference Type | reference_type |
string |
None provided |
Subject | subject |
string |
None provided |
Type | type |
string |
None provided |
Update Time | update_time |
string |
None provided |
User ID | user_id |
number |
None provided |
- Version {{docApp.book.version}}
- Node {{docApp.node}} / {{docApp.build}}