Amocrm icon

Amocrm

Consume AmoCRM API
Join our community

Actions28

Overview

This node updates leads in AmoCRM, allowing users to modify multiple lead records with various attributes such as name, price, pipeline, status, responsible user, dates, custom fields, and tags. It supports two authentication methods (Long Lived Token and OAuth2) and offers flexibility in input format, either as structured fields or raw JSON. This node is useful for automating lead management workflows, such as bulk updating lead statuses or assigning leads to different users.

Use Case Examples

  1. Updating multiple leads' statuses and responsible users in bulk.
  2. Modifying lead details like price and pipeline based on external triggers.
  3. Using JSON input to update leads with complex custom fields and embedded tags.

Properties

Name Meaning
Authentication Method used to authenticate with AmoCRM API, either Long Lived Token or OAuth2.
JSON Parameters Toggle to specify if the leads data is provided as raw JSON string or structured fields.
Stringifyed Array of Objects A JSON string representing an array of lead objects, used when JSON Parameters is true.
Leads Collection of lead records to update, each with properties like ID, name, price, pipeline, status, users, dates, loss reason, custom fields, embedded tags, and a request ID.

Output

JSON

  • id - The unique identifier of the updated lead.
  • name - The name of the updated lead.
  • price - The price associated with the lead.
  • pipeline_id - The pipeline ID or name the lead belongs to.
  • status_id - The status ID or name of the lead.
  • created_by - User who created the lead.
  • updated_by - User who last updated the lead.
  • responsible_user_id - User responsible for the lead.
  • closed_at - Date and time when the lead was closed.
  • created_at - Date and time when the lead was created.
  • updated_at - Date and time when the lead was last updated.
  • loss_reason_id - Reason for lead loss, if applicable.
  • custom_fields_values - Custom fields and their values associated with the lead.
  • _embedded
    • tags - Tags associated with the lead.
  • request_id - An optional request identifier returned unchanged in the response.

Dependencies

  • AmoCRM API access with either Long Lived Token or OAuth2 credentials

Troubleshooting

  • Ensure correct authentication method and valid credentials are used to avoid authorization errors.
  • Verify that lead IDs exist in AmoCRM before attempting updates to prevent not found errors.
  • When using JSON input, ensure the JSON string is properly formatted to avoid parsing errors.
  • Check that referenced pipeline, status, user, and custom field IDs are valid and accessible.
  • If updates fail, review API rate limits and ensure the node respects them.

Links

Discussion