AmoCRM Source

Renta supports data export from AmoCRM to following destinations:

  • Google BigQuery
  • Clickhouse
  • SQL Server
  • Google Spreadsheets

Integration creating in data warehouse (DWH)

  1. Go to integrations catalog;
  2. Select AmoCRM;
  3. Add a AmoCRM account that has the necessary data;
  4. Choose the added AmoCRM account;
  5. Specify the destination you want to import the data into;
  6. Go to the settings screen and set necessary configuration:

Report type

Report type consists of the unique set of parameters and metrics available for uploading to DWH. Each Report Type has its own parameters and metrics collection.

NameDescription
LeadsThe method allows you to get a list of leads in the account.
ContactsThe method allows you to get a list of contacts in the account.
CompaniesThe method allows you to get a list of companies in the account.
СustomersThe method allows you to get a list of customers in the account.
TasksThe method allows you to get a list of tasks in the account.
PipelinesThe method allows you to get a list of pipelines in the account.

Parameters

Parameters contains the list of parameters and metrics available for export. Specify the parameters required for uploading.

As a result, Renta will create the table that will contain the selected parameters data. The order of the selected parameters in the Rentas interface will match to the order of the table columns.

Date range type

Choose the inserting period. You can specify any historical time interval.

To select the necessary time, enter the date from which you want to start uploading data in the “From” field, then enter the end date in the “To” field.

If you want the data in the table to be updated daily and supplemented with new days, then enter “Yesterday” in the “To” field.

Detailed instructions for working with a date range.

Integration name

There is an auto generated name for your integration and here you can edit it as much as you like.

Both Cyrillic and Latin are permitted, but not more than 100 symbols.

The integration name is displayed on the Integration List page.

Table name

There is an auto generated name for your table and here you can edit it as much as you like.

Only Latin is permitted, numbers and “_” symbol.

Update time

You can specify any update time that you need. Users choose early morning integration updates most often, for example 5 AM.

In that case your integration will update in period from 5 AM to 6 AM.

Integrations are updating according to the time zone selected in your profile settings.

Integration creating in Google Spreadsheets

Take advantage of the free extension available in the Google Workspace Marketplace. In order to do it:

  1. Install the extension Renta Spreadsheets Add-on.
  2. Then go to Google Sheets and in the Tools tab select Renta
  3. Press the Run button.

After that a workspace with integration settings will open in the right sidebar. Detailed instructions for creating an integration are available at this link. Please note that all integrations created in Google Spreadsheets are also available for management in the web version of Renta.

Data Structure

NameDescriptionType
idThe unique identifier of the new entity.STRING
nameName of the lead.STRING
responsible_user_idid of the responsible user.STRING
created_byid of the user who created the lead.STRING
created_atThe time and date the lead was created.DATE
updated_atDate and time of the lead change.DATE
account_idid of the account on which the lead was created.STRING
is_deletedDeal deleted or not. Deleted leads can be in “deleted”.BIT
main_contact.idid of the main contact of the lead.STRING
group_idid of the group in which the user is responsible for the lead.STRING
company.idid of the company that is attached to this lead.STRING
company.nameThe name of the company that is attached to the lead.STRING
closed_atThe time and date when this lead was completed.DATE
closest_task_atThe time of the nearest task for this lead.DATE
tags.idid of the tag attached to this trade.ARRAY(STRING)
tags.nameThe name of the tag attached to this lead.ARRAY(STRING)
custom_fields.idid of the custom field.STRING
custom_fields.namename of the custom field.STRING
custom_fields.values.valueThe value of the custom field.ARRAY(STRING)
custom_fields.values.enumEarly identifier of the preset option for the list or multisession.ARRAY(STRING)
custom_fields.values.subtypeThe identifier of the values ​​of the additional field “address”.ARRAY(STRING)
custom_fields.is_systemIs the extra field systemic.BIT
contacts.idid of the contact attached to the lead.ARRAY(STRING)
status_idId of the stage of the digital funnel where this transaction is located.STRING
saleBudget of the lead.INTEGER
pipeline.idid of the digital pipeline in which the lead is located.STRING
idThe unique identifier of the new entity.STRING
nameFull contact name.STRING
first_nameFirst contact Name.STRING
last_nameContact last name.STRING
responsible_user_idid of the responsible user.STRING
created_byId of the user who created the contact.STRING
created_atContact creation time and date.DATE
updated_atUpdated contact time and date.DATE
account_idId of the account on which the contact was created.STRING
updated_byId of the user who updated the contact.STRING
group_idid of the group in which the user is responsible for this contact.STRING
company.idid of the company that is attached to this contact.STRING
company.nameThe name of the company that is attached to this contact.STRING
leads.idid of the lead that is attached to this contact.ARRAY(STRING)
closest_task_atThe nearest task for this contact.INTEGER
tags.idId of the tag attached to this contact.ARRAY(STRING)
tags.nameThe name of the tag attached to this contact.ARRAY(STRING)
custom_fields.idId of additional field.STRING
custom_fields.nameAdditional field name.STRING
custom_fields.values.valueThe value of the custom field.ARRAY(STRING)
custom_fields.values.enumEarly identifier of the preset option for the list or multisession.ARRAY(STRING)
custom_fields.values.subtypeThe identifier of the values ​​of the additional field “address”.ARRAY(STRING)
custom_fields.is_systemIs the extra field systemic.BIT
customers.idId of the customer attached to this contact.ARRAY(STRING)
idUnique identifier of the company.STRING
nameCompany name.STRING
responsible_user_idid of the responsible user.STRING
created_byId of the user who created the company.STRING
created_atTime and Date of Company Creation.DATE
updated_atCompany time and date.DATE
account_idid of the account on which the company is established.STRING
updated_byId of the user who updated the company.STRING
group_idid of the group in which the user is responsible for the given company.STRING
contacts.idId of the contact that is attached to this company.ARRAY(STRING)
leads.idid of the lead that is attached to this company.ARRAY(STRING)
closest_task_atTime of the nearest task for this company.DATE
tags.idId of the tag attached to this company.ARRAY(STRING)
tags.nameThe name of the tag attached to this company.ARRAY(STRING)
custom_fields.idId of additional field.STRING
custom_fields.nameAdditional field name.STRING
custom_fields.values.valueThe value of the additional field.ARRAY(STRING)
custom_fields.values.enumEarly identifier of the preset option for the list or multi-selection.ARRAY(STRING)
custom_fields.values.subtypeThe identifier of the values ​​of the additional field “address”.ARRAY(STRING)
custom_fields.is_systemIs the extra field systemic.BIT
customers.idid of the customer attached to this company.ARRAY(STRING)
idThe unique identifier of the new entity.STRING
nameElement name.STRING
responsible_user_idid of the user responsible for the customer.STRING
created_byid of the user who created the customer.STRING
created_atDate and time the customer was created.DATE
updated_atDate and time of the change of the customer.DATE
account_idid of the account in which the customer was created.STRING
updated_byid of the user who changed the customer.STRING
is_deletedThe customer was deleted or not deleted.BIT
main_contact.idid of the main contact of the customer.STRING
tags.idId tag attached to this customer.ARRAY(STRING)
tags.nameThe name of the tag attached to this customer.ARRAY(STRING)
custom_fields.idId of additional field.STRING
custom_fields.nameAdditional field name.STRING
custom_fields.values.valueAdditional field value.ARRAY(STRING)
custom_fields.values.enumEarly identifier of the preset option for the list or multi-selection.ARRAY(STRING)
custom_fields.values.subtypeThe identifier of the values ​​of the additional field “address”.ARRAY(STRING)
custom_fields.is_systemIs the extra field systemic.BIT
contacts.idid of the contact attached to the lead.ARRAY(STRING)
company.idid of the company that is attached to this lead.STRING
company.namethe name of the company that is attached to the lead.STRING
next_priceExpected Amount.INTEGER
closest_task_atThe time of the nearest task for the given customer.DATE
period_idUnique period identifier, digital pipeline of customers.DATE
periodicityPeriodicity.INTEGER
next_dateNext purchase date.DATE
idThe unique identifier of the task.STRING
element_idUnique identifier of a contact or lead (lead or contact is specified in element_type).STRING
element_typeThe type of the element to be attached (1-contact, 2-lead, 3-company, 12-customer).INTEGER
complete_till_atThe date to which you want to complete the task. If the time is 23:59, then “All day” will be displayed in the system interfaces instead of time.DATE
task_typeTask type.INTEGER
textTask text.STRING
created_atDate this task was created (optional).DATE
updated_atDate of the last change of this task (optional parameter).DATE
responsible_user_idUnique identifier of the responsible user.STRING
is_completedTask completed or not.BIT
created_byUnique identifier of the task creator.STRING
account_idUnique Account ID.STRING
group_idId of the group in which the user is related to the task.STRING
idThe unique pipeline identifier.STRING
nameThe name of pipeline.STRING
sortPipeline number for display.INTEGER
is_mainIs pipeline “main”.BIT
statuses.idThe unique identifier of the step.ARRAY(STRING)
statuses.nameThe name of the phase.ARRAY(STRING)
statuses.colorStage color.ARRAY(STRING)
statuses.sortSequence number of the stage when displayed.ARRAY(INTEGER)
statuses.is_editableIs it possible to change or delete this step.ARRAY(BIT)

Quotes and limits

Important note: Renta doesn’t provide any restrictions like amount of accounts, connectors, integrations or inserting date range.

Limits for AmoCRM:

  • Not more than 7 requests per second.

Link to the official documentation