Amocrm icon

Amocrm

Consume AmoCRM API
Join our community

Actions28

Overview

This node updates company records in AmoCRM. It supports updating multiple companies with various fields such as name, responsible user, creation and update timestamps, custom fields, and tags. It is useful for automating CRM data management, ensuring company information is current and accurate. For example, it can be used to update company details after a sales call or to synchronize company data from another system.

Use Case Examples

  1. Updating the name and responsible user of a company after a sales interaction.
  2. Adding or modifying custom fields for multiple companies in bulk.
  3. Tagging companies based on recent activity or status changes.

Properties

Name Meaning
Authentication Selects the authentication method to use for connecting to AmoCRM, either a long-lived token or OAuth2.
JSON Parameters Determines whether the input data is provided as JSON string or as structured fields.
Stringifyed Array of Objects A JSON string representing an array of company objects to update, used when JSON Parameters is true.
Companies A collection of company objects to update, each with fields like ID, name, responsible user, creation and update info, custom fields, embedded tags, and a request ID for tracking.

Output

JSON

  • id - The unique identifier of the updated company.
  • name - The name of the updated company.
  • responsible_user_id - The ID of the user responsible for the company.
  • created_by - The ID of the user who created the company.
  • updated_by - The ID of the user who last updated the company.
  • created_at - The timestamp when the company was created.
  • updated_at - The timestamp when the company was last updated.
  • custom_fields_values - Custom fields and their values associated with the company.
  • _embedded
    • tags - Tags associated with the company.
  • request_id - An optional field returned unchanged in the response for tracking purposes.

Dependencies

  • AmoCRM API with authentication via long-lived token or OAuth2

Troubleshooting

  • Ensure the authentication credentials (long-lived token or OAuth2) are valid and have the necessary permissions to update companies.
  • If using JSON Parameters, verify the JSON string is correctly formatted and represents an array of company objects.
  • Check that company IDs provided exist in AmoCRM; updates will fail for non-existent IDs.
  • Custom fields and tags must exist in AmoCRM; otherwise, the update may fail or ignore those fields.
  • Error messages related to authentication failures usually indicate expired or invalid tokens; re-authenticate as needed.

Links

Discussion