Renta supports data export from AmoCRM to following destinations:
- Google BigQuery
- Clickhouse
- SQL Server
- Google Spreadsheets
Integration creating in data warehouse (DWH)
- Go to integrations catalog;
- Select AmoCRM;
- Add a AmoCRM account that has the necessary data;
- Choose the added AmoCRM account;
- Specify the destination you want to import the data into;
- 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.
Name | Description |
---|---|
Leads | The method allows you to get a list of leads in the account. |
Contacts | The method allows you to get a list of contacts in the account. |
Companies | The method allows you to get a list of companies in the account. |
Сustomers | The method allows you to get a list of customers in the account. |
Tasks | The method allows you to get a list of tasks in the account. |
Pipelines | The 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:
- Install the extension Renta Spreadsheets Add-on.
- Then go to Google Sheets and in the Tools tab select Renta
- 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
Name | Description | Type |
---|---|---|
id | The unique identifier of the new entity. | STRING |
name | Name of the lead. | STRING |
responsible_user_id | id of the responsible user. | STRING |
created_by | id of the user who created the lead. | STRING |
created_at | The time and date the lead was created. | DATE |
updated_at | Date and time of the lead change. | DATE |
account_id | id of the account on which the lead was created. | STRING |
is_deleted | Deal deleted or not. Deleted leads can be in “deleted”. | BIT |
main_contact.id | id of the main contact of the lead. | STRING |
group_id | id of the group in which the user is responsible for the lead. | STRING |
company.id | id of the company that is attached to this lead. | STRING |
company.name | The name of the company that is attached to the lead. | STRING |
closed_at | The time and date when this lead was completed. | DATE |
closest_task_at | The time of the nearest task for this lead. | DATE |
tags.id | id of the tag attached to this trade. | ARRAY(STRING) |
tags.name | The name of the tag attached to this lead. | ARRAY(STRING) |
custom_fields.id | id of the custom field. | STRING |
custom_fields.name | name of the custom field. | STRING |
custom_fields.values.value | The value of the custom field. | ARRAY(STRING) |
custom_fields.values.enum | Early identifier of the preset option for the list or multisession. | ARRAY(STRING) |
custom_fields.values.subtype | The identifier of the values of the additional field “address”. | ARRAY(STRING) |
custom_fields.is_system | Is the extra field systemic. | BIT |
contacts.id | id of the contact attached to the lead. | ARRAY(STRING) |
status_id | Id of the stage of the digital funnel where this transaction is located. | STRING |
sale | Budget of the lead. | INTEGER |
pipeline.id | id of the digital pipeline in which the lead is located. | STRING |
id | The unique identifier of the new entity. | STRING |
name | Full contact name. | STRING |
first_name | First contact Name. | STRING |
last_name | Contact last name. | STRING |
responsible_user_id | id of the responsible user. | STRING |
created_by | Id of the user who created the contact. | STRING |
created_at | Contact creation time and date. | DATE |
updated_at | Updated contact time and date. | DATE |
account_id | Id of the account on which the contact was created. | STRING |
updated_by | Id of the user who updated the contact. | STRING |
group_id | id of the group in which the user is responsible for this contact. | STRING |
company.id | id of the company that is attached to this contact. | STRING |
company.name | The name of the company that is attached to this contact. | STRING |
leads.id | id of the lead that is attached to this contact. | ARRAY(STRING) |
closest_task_at | The nearest task for this contact. | INTEGER |
tags.id | Id of the tag attached to this contact. | ARRAY(STRING) |
tags.name | The name of the tag attached to this contact. | ARRAY(STRING) |
custom_fields.id | Id of additional field. | STRING |
custom_fields.name | Additional field name. | STRING |
custom_fields.values.value | The value of the custom field. | ARRAY(STRING) |
custom_fields.values.enum | Early identifier of the preset option for the list or multisession. | ARRAY(STRING) |
custom_fields.values.subtype | The identifier of the values of the additional field “address”. | ARRAY(STRING) |
custom_fields.is_system | Is the extra field systemic. | BIT |
customers.id | Id of the customer attached to this contact. | ARRAY(STRING) |
id | Unique identifier of the company. | STRING |
name | Company name. | STRING |
responsible_user_id | id of the responsible user. | STRING |
created_by | Id of the user who created the company. | STRING |
created_at | Time and Date of Company Creation. | DATE |
updated_at | Company time and date. | DATE |
account_id | id of the account on which the company is established. | STRING |
updated_by | Id of the user who updated the company. | STRING |
group_id | id of the group in which the user is responsible for the given company. | STRING |
contacts.id | Id of the contact that is attached to this company. | ARRAY(STRING) |
leads.id | id of the lead that is attached to this company. | ARRAY(STRING) |
closest_task_at | Time of the nearest task for this company. | DATE |
tags.id | Id of the tag attached to this company. | ARRAY(STRING) |
tags.name | The name of the tag attached to this company. | ARRAY(STRING) |
custom_fields.id | Id of additional field. | STRING |
custom_fields.name | Additional field name. | STRING |
custom_fields.values.value | The value of the additional field. | ARRAY(STRING) |
custom_fields.values.enum | Early identifier of the preset option for the list or multi-selection. | ARRAY(STRING) |
custom_fields.values.subtype | The identifier of the values of the additional field “address”. | ARRAY(STRING) |
custom_fields.is_system | Is the extra field systemic. | BIT |
customers.id | id of the customer attached to this company. | ARRAY(STRING) |
id | The unique identifier of the new entity. | STRING |
name | Element name. | STRING |
responsible_user_id | id of the user responsible for the customer. | STRING |
created_by | id of the user who created the customer. | STRING |
created_at | Date and time the customer was created. | DATE |
updated_at | Date and time of the change of the customer. | DATE |
account_id | id of the account in which the customer was created. | STRING |
updated_by | id of the user who changed the customer. | STRING |
is_deleted | The customer was deleted or not deleted. | BIT |
main_contact.id | id of the main contact of the customer. | STRING |
tags.id | Id tag attached to this customer. | ARRAY(STRING) |
tags.name | The name of the tag attached to this customer. | ARRAY(STRING) |
custom_fields.id | Id of additional field. | STRING |
custom_fields.name | Additional field name. | STRING |
custom_fields.values.value | Additional field value. | ARRAY(STRING) |
custom_fields.values.enum | Early identifier of the preset option for the list or multi-selection. | ARRAY(STRING) |
custom_fields.values.subtype | The identifier of the values of the additional field “address”. | ARRAY(STRING) |
custom_fields.is_system | Is the extra field systemic. | BIT |
contacts.id | id of the contact attached to the lead. | ARRAY(STRING) |
company.id | id of the company that is attached to this lead. | STRING |
company.name | the name of the company that is attached to the lead. | STRING |
next_price | Expected Amount. | INTEGER |
closest_task_at | The time of the nearest task for the given customer. | DATE |
period_id | Unique period identifier, digital pipeline of customers. | DATE |
periodicity | Periodicity. | INTEGER |
next_date | Next purchase date. | DATE |
id | The unique identifier of the task. | STRING |
element_id | Unique identifier of a contact or lead (lead or contact is specified in element_type). | STRING |
element_type | The type of the element to be attached (1-contact, 2-lead, 3-company, 12-customer). | INTEGER |
complete_till_at | The 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_type | Task type. | INTEGER |
text | Task text. | STRING |
created_at | Date this task was created (optional). | DATE |
updated_at | Date of the last change of this task (optional parameter). | DATE |
responsible_user_id | Unique identifier of the responsible user. | STRING |
is_completed | Task completed or not. | BIT |
created_by | Unique identifier of the task creator. | STRING |
account_id | Unique Account ID. | STRING |
group_id | Id of the group in which the user is related to the task. | STRING |
id | The unique pipeline identifier. | STRING |
name | The name of pipeline. | STRING |
sort | Pipeline number for display. | INTEGER |
is_main | Is pipeline “main”. | BIT |
statuses.id | The unique identifier of the step. | ARRAY(STRING) |
statuses.name | The name of the phase. | ARRAY(STRING) |
statuses.color | Stage color. | ARRAY(STRING) |
statuses.sort | Sequence number of the stage when displayed. | ARRAY(INTEGER) |
statuses.is_editable | Is 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