Amocrm icon

Amocrm

Consume AmoCRM API
Join our community

Actions28

Overview

This node allows users to create notes in AmoCRM associated with various entity types such as leads, contacts, companies, or customers. It supports different authentication methods and flexible input formats, including structured note data or raw JSON. This node is useful for automating the addition of notes to CRM records, such as logging calls, messages, or service interactions, enhancing CRM data completeness and workflow automation.

Use Case Examples

  1. Automatically add call logs as notes to a lead after a phone call.
  2. Create service messages or geolocation notes for a customer record.
  3. Log SMS communications as notes on contact records.

Properties

Name Meaning
Authentication Method used to authenticate with AmoCRM API, either Long Lived Token or OAuth2.
Entity Type Type of CRM entity to which the note will be attached, e.g., lead, contact, company, or customer.
JSON Parameters Flag to indicate if the note data 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 with various types (e.g., common, call in/out, service message) and fields such as created date, entity ID, creator, text, and additional metadata.

Output

JSON

  • id - Unique identifier of the created note.
  • entity_id - ID of the entity to which the note is attached.
  • entity_type - Type of the entity (lead, contact, company, customer).
  • created_at - Timestamp when the note was created.
  • created_by - User who created the note.
  • text - Content text of the note.
  • note_type - Type/category of the note (e.g., common, call_in, service_message).

Dependencies

  • Requires AmoCRM API access with either OAuth2 or Long Lived Token authentication.

Troubleshooting

  • Ensure correct authentication method and valid credentials are used to avoid authorization errors.
  • Verify that the entity ID and entity type are valid and exist in AmoCRM to prevent not found errors.
  • When using JSON input, ensure the JSON string is correctly formatted to avoid parsing errors.
  • If loading user options fails, check API permissions and connectivity.

Links

Discussion