Amocrm icon

Amocrm

Consume AmoCRM API
Join our community

Actions28

Overview

This node allows users to create tasks in AmoCRM. It supports creating multiple tasks at once, either by providing task details through a structured form or by inputting a JSON string representing an array of task objects. This node is useful for automating task creation in AmoCRM workflows, such as assigning follow-up tasks to sales leads, scheduling reminders, or logging activities related to contacts, companies, or customers.

Use Case Examples

  1. Create a single task to follow up with a lead, specifying the responsible user, due date, and task type.
  2. Batch create multiple tasks by providing a JSON array of task objects, each with different properties like text, completion status, and associated entity.
  3. Use the node to assign tasks to different users based on dynamic workflow conditions, automating task distribution.

Properties

Name Meaning
Authentication Method used to authenticate with AmoCRM, either Long Lived Token or OAuth2.
JSON Parameters Flag to indicate if tasks are provided as a JSON string array instead of individual form fields.
Stringifyed Array of Objects A JSON string representing an array of task objects, used when JSON Parameters is true.
Tasks A collection of task objects to create, each with properties like text, completion date, responsible user, entity type and ID, task type, duration, completion status, result text, creator and updater user IDs, and timestamps.

Output

JSON

  • id - The unique identifier of the created task.
  • text - The text or description of the task.
  • complete_till - The due date and time by which the task should be completed.
  • responsible_user_id - The ID of the user responsible for the task.
  • entity_type - The type of entity the task is associated with (e.g., leads, contacts).
  • entity_id - The ID of the associated entity.
  • task_type_id - The type or category of the task.
  • duration - The duration of the task in seconds.
  • is_completed - Indicates whether the task is marked as completed.
  • resultText - Text describing the result or outcome of the task.
  • created_by - The user ID who created the task.
  • updated_by - The user ID who last updated the task.
  • created_at - Timestamp when the task was created.
  • updated_at - Timestamp when the task was last updated.

Dependencies

  • AmoCRM API 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 create tasks in AmoCRM.
  • If using JSON Parameters, verify that the JSON string is correctly formatted and represents an array of valid task objects.
  • Check that required fields such as task text and responsible user ID are provided to avoid validation errors from the API.
  • If loading options for users or task types fails, verify that the API connection is active and the user has access rights.

Links

Discussion