Amocrm icon

Amocrm

Consume AmoCRM API
Join our community

Actions28

Overview

This node operation allows users to reject an unsorted item in AmoCRM. It is useful for managing and organizing incoming unsorted data by explicitly rejecting items that are not needed or are irrelevant. For example, a user can reject a specific unsorted lead or contact by providing its UID, helping to keep the CRM data clean and relevant.

Use Case Examples

  1. Reject an unsorted lead by specifying its UID and optionally assigning the rejection action to a specific user by their ID or username.
  2. Use the node to automate the cleanup of unsorted items that do not meet certain criteria, improving data quality in AmoCRM.

Properties

Name Meaning
Authentication Method used to authenticate with AmoCRM API, either Long Lived Token or OAuth2.
Unsorted UID The unique identifier of the unsorted item to reject.
User Name or ID Optionally specify the user by name or ID who is associated with the rejection action.

Output

JSON

  • rejectedItemId - The UID of the unsorted item that was rejected.
  • status - The status or result of the reject operation, e.g., success or failure.

Dependencies

  • Requires authentication credentials for AmoCRM API, either a long-lived token or OAuth2 credentials.

Troubleshooting

  • Ensure the provided Unsorted UID is correct and exists in AmoCRM; otherwise, the reject operation will fail.
  • Authentication errors may occur if the token or OAuth2 credentials are invalid or expired; refresh or reauthenticate as needed.
  • If specifying a user ID or name, ensure it matches an active user in AmoCRM to avoid errors.

Links

Discussion