Amocrm icon

Amocrm

Consume AmoCRM API
Join our community

Actions28

Overview

This node interacts with the AmoCRM system to retrieve a list of notes associated with various entity types such as leads, contacts, companies, or customers. It supports filtering notes by IDs, entity IDs, note types, and update date ranges. Users can choose to return all notes or limit the number of results, and sort the results by update date or ID in ascending or descending order. This node is useful for scenarios where users need to fetch and analyze notes related to CRM entities for reporting, auditing, or integration purposes.

Use Case Examples

  1. Fetch all notes related to leads updated within a specific date range for detailed analysis.
  2. Retrieve a limited number of notes of type 'call_in' and 'sms_out' for a specific contact to review communication history.
  3. Get notes sorted by their update date in descending order for a company to monitor recent activities.

Properties

Name Meaning
Authentication Method used to authenticate with AmoCRM, either Long Lived Token or OAuth2.
Entity Type Type of entity to which the notes belong, such as leads, contacts, companies, or customers.
Return All Whether to return all matching notes or limit the results to a specified number.
Filter Criteria to filter the notes, including note IDs, entity IDs, note types, and update date range.
Options Additional options for sorting the notes by a specified field and order.
Page Page number to retrieve when not returning all results.
Limit Maximum number of notes to return when not returning all results.

Output

JSON

  • id - Unique identifier of the note.
  • entity_id - Identifier of the entity to which the note belongs.
  • entity_type - Type of the entity (lead, contact, company, customer).
  • note_type - Type of the note (e.g., call_in, sms_out).
  • updated_at - Timestamp when the note was last updated.
  • content - Content or text of the note.
  • attachments - Any attachments associated with the note.

Dependencies

  • AmoCRM API authentication via Long Lived Token or OAuth2

Troubleshooting

  • Authentication failures due to incorrect or expired tokens. Ensure valid credentials are provided.
  • Invalid filter parameters such as malformed date ranges or unsupported note types may cause errors. Verify filter inputs.
  • Pagination issues when 'Return All' is false and page or limit values are out of range. Adjust page and limit accordingly.

Links

Discussion