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 Note.
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 |
---|---|---|---|---|---|
Note ID | noteId |
number |
ID of the Note | Yes | None provided |
Output Parameters
Display Name | ID | Type | Description |
---|---|---|---|
Active? | active_flag |
boolean |
Is the Note active |
Time Added | add_time |
string |
The time added of the Note |
Company ID | company_id |
number |
The company ID associated with the Note |
Content | content |
string |
Content of the Note |
Deal ID | deal_id |
number |
The deal ID of the Note |
Deal Title | deal_title |
string |
Deal title |
Note ID | id |
number |
The ID of the Note |
Last Update User ID | last_update_user_id |
number |
The ID of the last user who updated the Note |
Organization ID | org_id |
number |
The organizaiton ID of the Note |
Organization | organization |
number |
The organization associated with the Note |
Person ID | person_id |
number |
The Person ID associated with the Note |
Person Name | person_name |
string |
The Person name associated with the Note |
Pinned to Deal? | pinned_to_deal_flag |
boolean |
Is the note pinned to a Deal |
Pinned to Organization? | pinned_to_organization_flag |
boolean |
Is the note pinned to an Organization |
Pinned to Person? | pinned_to_person_flag |
boolean |
Is the note pinned to a Person |
Update Time | update_time |
string |
The last update time of the Note |
User Email | user_email |
string |
The email address of User user associated with this note |
User ID | user_id |
string |
The user ID of the User associated with this note |
User is You? | user_is_you |
boolean |
Is this a self referring change |
User Name | user_name |
string |
User name |
- Version {{docApp.book.version}}
- Node {{docApp.node}} / {{docApp.build}}