Amocrm icon

Amocrm

Consume AmoCRM API
Join our community

Actions28

Overview

This node updates notes in AmoCRM for various entity types such as leads, contacts, companies, and customers. It supports different note types including common notes, call-in, call-out, service messages, geolocation, SMS, attachments, and more. Users can update notes by specifying detailed properties like creation date, creator, text content, and additional metadata. The node supports authentication via long-lived tokens or OAuth2 and allows input either as structured fields or as a JSON string for flexibility.

Use Case Examples

  1. Updating a lead's note with a text message and specifying the user who created it.
  2. Adding a call-in note with details like duration, source, and phone number to a contact.
  3. Updating an attachment note for a company with file UUID and version information.

Properties

Name Meaning
Authentication Method used to authenticate with AmoCRM API, either Long Lived Token or OAuth2.
Entity Type Type of entity the note is associated with, e.g., leads, contacts, companies, or customers.
JSON Parameters Flag to indicate if the notes input is provided as a JSON string instead of structured fields.
Stringifyed Array of Objects A JSON string representing an array of note objects, used when JSON Parameters is true.
Notes Collection of note entries to update, supporting multiple note types with detailed fields such as ID, creation date, creator, text, and other metadata.

Output

JSON

  • id - ID of the updated note.
  • created_at - Timestamp when the note was created.
  • entity_id - ID of the entity the note is associated with.
  • created_by - User who created the note.
  • text - Text content of the note.
  • request_id - Optional request identifier returned unchanged in the response.

Dependencies

  • Requires AmoCRM API access with either a long-lived token or OAuth2 credentials.

Troubleshooting

  • Ensure correct authentication method is selected and credentials are valid to avoid authorization errors.
  • When using JSON Parameters, ensure the JSON string is properly formatted to prevent parsing errors.
  • Required fields like note ID must be provided; missing these will cause the update to fail.
  • If user selection fields fail to load, verify the method to fetch active users is functioning and the API has necessary permissions.

Discussion