Amocrm icon

Amocrm

Consume AmoCRM API
Join our community

Actions28

Overview

This node interacts with the AmoCRM platform to retrieve detailed information about an account. It supports fetching various supplementary data related to the account, such as chat service account ID, user rights in chats, user groups, task types, version, entity names, datetime settings, drive URL, and API filter status. This node is useful for users who want to programmatically access comprehensive account details from AmoCRM for integration, reporting, or automation purposes.

Use Case Examples

  1. Retrieve the AmoCRM account information along with user rights in chats and task types to automate user permission management.
  2. Fetch account details including version and datetime settings to synchronize CRM data with other systems.

Properties

Name Meaning
Authentication Selects the authentication method to connect to AmoCRM, either using a Long Lived Token or OAuth2.
With Specifies additional related data to include in the account information response, such as chat service account ID, user rights, user groups, task types, version, entity names, datetime settings, drive URL, and API filter status.

Output

JSON

  • accountInfo - The main account information retrieved from AmoCRM.
  • amojo_id - Chat service account ID if requested.
  • amojo_rights - User rights in chats if requested.
  • users_groups - Information about user groups if requested.
  • task_types - Task types associated with the account if requested.
  • version - Version information of the AmoCRM account if requested.
  • entity_names - Entity names related to the account if requested.
  • datetime_settings - Datetime configuration settings if requested.
  • drive_url - Drive URL associated with the account if requested.
  • is_api_filter_enabled - Flag indicating if the API filter is enabled if requested.

Dependencies

  • Requires AmoCRM API access with either a Long Lived Token or OAuth2 authentication credentials.

Troubleshooting

  • Authentication failures due to incorrect or expired tokens. Ensure the selected authentication method is correctly configured and tokens are valid.
  • Requesting unsupported or unavailable additional data in the 'With' property may result in incomplete responses. Verify the options selected are supported by the AmoCRM API version in use.
  • Network connectivity issues can prevent successful API calls. Check internet connection and AmoCRM service status.

Links

Discussion