Actions28
- Unsorted Actions
- Lead Actions
- Account Actions
- Catalog Actions
- Note Actions
- Company Actions
- Task Actions
- Contact Actions
Overview
This node interacts with the AmoCRM platform to retrieve a list of tasks based on specified filters and options. It is useful for automating workflows that require task management data from AmoCRM, such as fetching tasks assigned to specific users, filtering by completion status, or sorting tasks by creation date or due date. Practical examples include generating reports on pending tasks, syncing task data with other systems, or triggering actions based on task attributes.
Use Case Examples
- Fetch all incomplete tasks assigned to a particular user.
- Retrieve tasks related to specific leads or contacts within a date range.
- Get a limited number of tasks sorted by their creation date in ascending order.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method used to authenticate with AmoCRM, either via a long-lived token or OAuth2. |
| Return All | Determines whether to return all matching tasks or limit the results to a specified number. |
| Filter | Criteria to filter the tasks retrieved, including responsible users, completion status, task types, entity types, specific entity IDs, task IDs, and update date range. |
| Options | Additional options for sorting the task list, including the field to sort by and the sort order. |
| Page | Page number of results to retrieve when not returning all tasks. |
| Limit | Maximum number of tasks to return when not returning all. |
Output
JSON
id- Unique identifier of the task.responsible_user_id- ID of the user responsible for the task.task_type- Type of the task.entity_type- Type of the related entity (lead, contact, company, customer).entity_id- ID of the related entity.is_completed- Boolean indicating if the task is completed.created_at- Timestamp when the task was created.updated_at- Timestamp when the task was last updated.complete_till- Due date for task completion.
Dependencies
- Requires authentication credentials for AmoCRM, either a long-lived token or OAuth2 credentials.
Troubleshooting
- Ensure authentication credentials are valid and have the necessary permissions to access task data.
- Verify that filter values such as user IDs, task types, and entity IDs are correct and exist in AmoCRM.
- If no tasks are returned, check that the filter criteria are not too restrictive.
- When using pagination, ensure the page number and limit are set correctly to avoid empty results.