Actions28
- Unsorted Actions
- Lead Actions
- Account Actions
- Catalog Actions
- Note Actions
- Company Actions
- Task Actions
- Contact Actions
Overview
This node operation retrieves a list of leads from AmoCRM. It is useful for scenarios where users need to fetch lead data for analysis, reporting, or integration with other systems. For example, a sales team might use it to get all leads created within a specific date range or filter leads by status or responsible user.
Use Case Examples
- Fetch all leads created in the last month for sales performance review.
- Retrieve leads filtered by specific pipeline and status to prioritize follow-ups.
- Get a limited number of leads with detailed contact information for targeted marketing campaigns.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method used to authenticate with AmoCRM API, either Long Lived Token or OAuth2. |
| Return All | Whether to return all lead results or limit the number of results. |
| Filter | Collection of filters to narrow down the lead list, including search query, lead IDs, names, price range, pipelines, statuses, users involved, and date ranges for creation, update, closure, and closest task. |
| Options | Additional options for sorting and including related data in the response. |
| Page | Page number to retrieve when not returning all leads. |
| Limit | Maximum number of leads to return when not returning all. |
Output
JSON
id- Unique identifier of the lead.name- Name of the lead.price- Price associated with the lead.pipeline_id- Identifier of the pipeline the lead belongs to.status_id- Identifier of the lead's status.created_at- Timestamp when the lead was created.updated_at- Timestamp when the lead was last updated.closed_at- Timestamp when the lead was closed.responsible_user_id- Identifier of the user responsible for the lead.contacts- Associated contacts information if requested.loss_reason- Reason for loss if the lead was lost.source_id- Source identifier of the lead.
Dependencies
- AmoCRM API authentication (Long Lived Token or OAuth2)
Troubleshooting
- Ensure correct authentication method and valid credentials are used to avoid authorization errors.
- Check filter values for correct formats, especially date ranges and comma-separated lists.
- If no leads are returned, verify that the filter criteria are not too restrictive.
- Pagination parameters (page and limit) must be positive integers; otherwise, the node may return errors or no data.
Links
- AmoCRM Leads API Documentation - Official documentation for AmoCRM Leads API endpoints and parameters.