# Welcome Use Erathos to move and orchestrate your data in minutes. ## What is Erathos Erathos is an ELT software that extracts data from multiple sources through instant integrations. With plug-and-play connectors, it centralizes all your data into a single analytical environment, allowing you to build a Data Warehouse in minutes. ## Getting started To set up the Erathos platform as quickly as possible, follow the tutorial provided in the [**Quickstart**](/introduction/quickstart) section. This step-by-step guide is designed to help you integrate and configure your data workflows efficiently, enabling you to get started in minutes. ## Connectors
APIs/pages/tjtpMCpmxJ56pJLKLeyB/pages/tjtpMCpmxJ56pJLKLeyB
Databases/pages/LIxCeK0Uy0kLHHhfBJSm/pages/LIxCeK0Uy0kLHHhfBJSm
## Integrate with your Data Stack
Airflow/pages/mla7iPIFlMUSTMUKZ40e/pages/mla7iPIFlMUSTMUKZ40e
Dbt Cloud/pages/joD1YKTeUUREnlNtU7xA/pages/joD1YKTeUUREnlNtU7xA
Prefect/pages/v1cFjvTDIXeBvXpRiQGm/pages/v1cFjvTDIXeBvXpRiQGm
## Settings
Workspace settings/pages/KEpRFzrGgUFpnqVscYfQ
User Settings/pages/d2iQy1I1Qtb52ZEq4vOn
# Quickstart There are two main actions required to configure the Erathos platform effectively: {% stepper %} {% step %} ### Connect your data sources Erathos can seamlessly connect to various data sources, including **SaaS platforms** (via APIs) and **databases**. Pipelines define how the Extract and Load (EL) process is executed. You can configure the frequency and method of updates, as well as select the specific tables or endpoints to sync. {% endstep %} {% step %} ### Connect to your Data warehouse Connect to the Data Warehouse that will serve as the destination for Erathos integrations. {% endstep %} {% endstepper %} ## 1. Connect your data sources To connect to a data source, navigate to **Connections** and select **+ New connection**. Choose the relevant connector (if you're unsure, refer to the [connector's documentation page](/connectors/apis) for guidance) and enter your credentials. Finally, create the jobs that will define the data movement routines, setting up the frequency and method of synchronization. {% embed url="" %} ## 2. Connect to your Data warehouse To connect to your Data Warehouse, navigate to **Settings > Data Warehouse** in Erathos and select your desired option. Erathos supports integration with several major Data Warehouses, including: * [**BigQuery**](/destinations/what-is-a-destination/bigquery) * [**PostgreSQL**](/destinations/what-is-a-destination/postgresql) * [**Redshift**](/destinations/what-is-a-destination/redshift) * [**Databricks**](/destinations/what-is-a-destination/databricks) {% embed url="" %} {% hint style="info" %} If you dont have a Google BigQuery, we can host for you. Referer to [Hosted by Erathos](/destinations/what-is-a-destination/bigquery/hosted-by-erathos) {% endhint %} # Connections Connect data sources to your warehouse. Connections are the bridge linking your data sources to your data warehouse, enabling seamless data integration and processing. Each connection can manage one or multiple jobs, which define specific data extraction, transformation, and loading tasks. To learn more about how jobs work and their role in the data pipeline, refer to the [Jobs Documentation](/platform/connections/jobs). ## How to create a connection {% embed url="" %} {% hint style="info" %} Each connector requires specific credentials for its setup. For detailed information about the credentials needed for a particular connector, refer to its [corresponding documentation](/connectors/apis). {% endhint %} # Jobs A **job** defines how the **Extract and Load (EL)** process is performed between your data sources and your data warehouse. Each job is always linked to a specific table or endpoint, depending on the type of connector used. ## Overview A **job** includes various configurations that define the EL process, such as: * [**Sync type**](/platform/connections/sync-types): Specifies how the data will be extracted from the source and written to the target. * [**Sync schedule**](/platform/connections/sync-schedule): Determines how often the job will run (e.g., hourly, daily). * **Column Selection**: Allows you to choose which columns will be included in the data extraction. Within a connection, each **job** can be configured independently, allowing for significant customization and adaptation to your specific use case. This flexibility ensures that data workflows can be precisely tailored to meet different requirements. However, in API-based connectors, certain jobs may have dependencies on others due to the nature of the API's structure or limitations. ### Dependent Jobs Dependent jobs occur when information from one job is required for the execution of another. **Example Scenario**:\ Consider a CRM system with two endpoints: * `/deals`: Lists all deals, providing IDs for each. * `/deal-details`: Requires the deal IDs from the first endpoint to fetch detailed records for each deal. In this case, the **Deals job** must execute first to gather the necessary IDs, which are then passed to the **Deal Details job** for its execution. **Key Characteristics of Dependent Jobs**: * **Execution Order**: Dependent jobs always run after their parent job has completed successfully. * **Sync Type Flexibility**: While the jobs are dependent, the parent and child can have different synchronization types. For example, the parent job might use incremental sync, while the child job performs a full refresh. This approach ensures accurate data flow between jobs while maintaining flexibility in how each job operates within its dependency hierarchy. ## How to create a job {% embed url="" %} ### Specify the Columns to Synchronize To select the columns to be synchronized within a Job, follow these steps: 1. **Navigate to "Manage Jobs"**: Go to the job management section in the platform's interface. 2. **Open the Column Selection Modal**: * Locate the desired job in the list. * Click the **"Open"** button associated with that job to access the column configuration modal. 3. **Customize Column Selection**: * **Select All**: Choose to include all available columns from the data source. * **Choose Specific Columns**: Select only the columns relevant to your use case. * **(Optional)** [**Anonymize Columns**](/platform/connections/column-anonymization): Configure columns to be anonymized if sensitive data needs to be protected during synchronization. {% embed url="" %} # Sync types Define the extract and load strategy A **Sync type** determine how we perform data capture and loading processes. Each strategy has its pros and cons, as well as specific use cases where it brings the most value. On the Erathos platform, we support the following update types: ## Full refresh The **Full Refresh** strategy involves a complete read and load of the source table, overwriting all values in the destination table. ## Partials In contrast, **Partial** updates capture only a subset of the table, defined by records with values greater than a specific cursor (such as creation date, update date, or even an ID). ### Understanding cursors Before moving on, it’s essential to understand what a **cursor** is and how it works. During the first execution, all the records are loaded into the destination. In subsequent pipeline executions, the cursor helps identify only the records that have been added or updated. To perform a partial update, at least one column must be selected to help identify which records should be transferred to the destination. From the columns available, we have the following options: * **Id**: Suitable if it is an integer and auto-incremental. * **Created\_at**: Suitable, but not recommended as updates in existing records would be missed. * **Updated\_at**: Suitable as it reflects the latest changes. * **Name / Gender**: Not meaningful for filtering updates. For this example, we use **Updated\_at**. From the destination table, we select the highest **Updated\_at** value and use it as a filter, selecting only records where **Updated\_at** is greater than the last loaded value. You can choose multiple cursors if needed. For instance, if the **updated\_at** column is null when a record is created you could select both **updated\_at** and **created\_at** as cursors. In this way the condition would be **`created_at > 'date' OR updated_at > 'date'`** ### Prerequisites In general, all jobs have the **Full Refresh** option available. However, for **Partial Refresh** to be enabled, the following prerequisites must be met: * A **primary key** must exist. * A column of type `date` or `datetime` must be available to serve as **cursor**. {% hint style="info" %} For APIs, Erathos maps and defines which endpoints meet the prerequisites automatically. For databases, we perform an introspection step. Learn more [here](/connectors/databases#introspection). {% endhint %} If you're using BigQuery as a destination, ensure it is not operating in *sandbox* mode, as this prevents the use of Partial Refresh. Learn more [here](/destinations/what-is-a-destination/bigquery#sandbox-mode). ### Types of partials The three variations of partial updates are as follows: #### Partial Overwrite In this strategy, new records are inserted as usual, while updated records **overwrite** outdated records in the destination database. {% hint style="info" %} This is the suggested **sync type** to be used across Erathos plataform. {% endhint %} #### Partial Append All records are inserted in this approach, resulting in updated records being duplicated (with both original and new values present in the database). #### Partial Versioned This strategy is similar to **Partial Append**, but each record is marked with an indicator identifying whether it’s the most recent version to be used. ### Advanced configuration When performing partial updates, it may occasionally be necessary to execute **Full Refresh** updates to resolve discrepancies between the source and destination datasets. To address this, you can use the **Enable Full On** parameter, which schedules routine and automatic full executions. ## Using sync types To choose the **sync type** for a job, navigate to the "**Pipeline Jobs**" page in your desired connection. ### APIs For APIs, we automatically map the best configurations and apply the optimal cursor for each job, ensuring efficient and accurate data capture. {% embed url="" %} ### Databases In contrast, when the data source is a database, it is necessary to manually define the cursor for each job that requires partial execution capabilities. {% hint style="info" %} If partial options are unavailable for a specific job, ensure that all [pre requisites](#pre-requisites) are met. {% endhint %} {% embed url="" %} # Sync schedule Define the schedule on which the jobs will be executed The primary function of a data pipeline is to keep two environments synchronized. To achieve this, pipelines rely on scheduled data update executions. These schedules are typically based on a specific **time** and an **update frequency**. ## Base hour The **Base Hour** refers to the specific time of day at which a scheduled pipeline execution begins, serving as the anchor point for the selected update frequency (e.g., weekly, daily, or every 12 hours). All subsequent executions follow this base hour based on the defined frequency. ## Frequency The available update frequencies on the Alexandria platform are: * **Manually:** Executes only when trigged by user. * **Weekly**: Executes once every week. * **Daily**: Executes every 24 hours. * **Every 12 Hours**: Executes every 12 hours. * **Every 6 Hours**: Executes every 6 hours. * **Every 3 Hours**: Executes every 3 hours. * **Every Hour**: Executes every 1 hour. * **Every 30 Minutes**: Executes every 30 minutes. * **Every 5 Minutes**: Executes every 5 minutes. ## Using sync frequencies and base hour {% embed url="" %} # Column Anonymization Protect sensitive data ## How it works **Column anonymization** is a data protection technique that modifies data to prevent the exposure or identification of individuals or sensitive information. This technique allows data to be utilized for analysis, reporting, or other purposes without compromising privacy. ## Activating column anonymization {% embed url="" %} # Block Window Prevent executions from occurring during critical time windows. ## How it works For various reasons, it may be necessary to ensure that no data extractions occur within a defined time window, thereby preserving resources from the source system. To address this need, we offer the **Block Window** feature, which defines specific time intervals to restrict data extraction jobs. This functionality allows for precise control over execution times, ensuring resource optimization for the source system. #### Configuration Options The Block Window allows you to set: * **Days**: Define specific days when the restriction applies. * **Start and End Times**: Specify the time range for the block window. #### Restriction Settings You can further customize how the restriction is applied: 1. **Cancel running executions**: Choose wheter to cancel previously started jobs executions. 2. **Allow Manual Executions**: Choose whether to permit or block manually triggered jobs during the block window. This feature provides flexibility and ensures optimal resource usage by aligning data extraction schedules with operational needs. ## Using block windows {% embed url="" %} # Custom retry strategy Customize the number of retries and buffer between attempts to retrieve data on connection and job level. {% hint style="info" %} This feature is only available on the PRO and Enterprise plans {% endhint %} ## How it works? Retries are the number of attempts our platform will do in order to try to extract the data once it receives an error response. If you set 5 retries, Erathos will make 5 attempts to retrieve data **before** showing you an error message and sending an alert. Besides the number of retries, you can also customize the backoff multiplier which dictates the buffer time between each attempt and how it varies over time. You can define a custom retry strategy at Connection level, applying to all jobs, or at job level. Be aware that the job retry strategy will overwrite the connection customization for that specific job. ## Using a custom retry strategy ### On Connection level * Select a connection * Go to settings tab * Click on "Control settings" {% embed url="" %} ### On Job level * Go to all jobs page * Click on `...` under "Actions" column and select "Control Settings" {% embed url="" %} # Connect to databases {% hint style="info" %} Make sure to include our IP address (**35.212.87.86**) to your firewall’s whitelist. {% endhint %} To connect to a database—whether as a [source](/platform/connections) or a [destination](/destinations/what-is-a-destination)—you need to ensure that the database is accessible from the **Erathos infrastructure**. To establish this connection: 1. **Firewall Configuration**: * Allow the Erathos IP (e.g., **35.212.87.86**) in your database's firewall settings. This step ensures that the infrastructure can reach your database. 2. **Tunneling Credentials**: * If the connection requires a tunnel (e.g., SSH or VPN), make sure the tunnel credentials are properly registered on the platform. * This involves providing the necessary details such as host, port, username, and private key (if applicable). {% embed url="" %} # Running jobs manually Jobs can be manually executed outside their scheduled routines. This is particularly useful for working with the most recent data or resolving discrepancies. #### How to Manually Execute a Job: 1. **Access the Jobs Screen**: * Navigate to the **Jobs** section of the desired connection. 2. **Select the Job**: * Locate the specific job you wish to run. 3. **Trigger Execution**: * Click the **Play** button next to the job. * The execution will start immediately, bypassing the predefined schedule. {% embed url="" %} If the job is configured for a **partial sync**, clicking the **Play** button will start a new execution of this type. For a **full refresh** execution instead, use the dropdown menu next to the Play button. This allows you to select the desired execution type before initiating the job. {% embed url="" %} # Custom Backfill Manually execute jobs with custom cursor value {% hint style="info" %} This feature is only available on PRO and Enterprise plans. {% endhint %} ## How it works Custom backfill allows you to customize the [cursor](https://docs.erathos.com/platform/connections/sync-types#understanding-cursors) value for a specific job run. This is valuable when you need to reprocess data without running a [Full Refresh](https://docs.erathos.com/platform/connections/sync-types#full-refresh). For example, you want to reprocess all the data starting from 01/01/2026 because a new column was added or some records have been deleted. ### Soft delete You may enable the soft delete option in order to detect cases when records from your data source no longer exist. That is, records that are not found during the custom backfill execution will then be marked as deleted on your data warehouse. ## Using the custom backfill feature * Go to the jobs page * Click on `...` to see more Actions and then select Run Custom Backfill {% embed url="" %} # Alert Integrations Receive Notifications. ## Overview It is possible to configure channels to receive notifications about job activity on the Erathos platform. Currently, the available options include: * [**Discord**](/platform/alert-integrations/discord) * [**Email**](/platform/alert-integrations/email) * [**Slack**](/platform/alert-integrations/slack) To configure your preferred notification channel, navigate to the **Settings** section of the platform and select the **Communications** option. From there, you can choose your desired integration. ## Take action from notifications We believe notifications should be actionable. To achieve this, we offer integrated actions directly within messages sent to **Discord** or **Slack**.
These actionable notifications allow you to interact with jobs or workflows directly from the messaging platform. For example, you can: * Retry failed jobs. * Jump to execution details. * Mute notifications for a specific period. # Discord To enable Discord integration, follow these steps: 1. **Navigate to Settings**: 1. Go to the **Settings** section of the platform. 2. **Access Communications Settings**: 1. Select the **Communications** tab. 3. **Add a Notification Channel**: 1. Click the **"Add Channel"** button. 4. **Configure Discord Notifications**: 1. In the modal that opens, choose the **Discord** option and give the channel a name. 5. **Add Recipients and Email Details**: 1. Authorize the intregration via OAuth. 2. Select the **discord channel** that the integration will send notifications. 6. **Save** 1. Click the butten **Create channel**. This will set up your email notifications, allowing you to customize the recipients and the content for the alerts sent by the system. {% embed url="" %} # Email To enable email notifications, follow these steps: 1. **Navigate to Settings**: 1. Go to the **Settings** section of the platform. 2. **Access Communications Settings**: 1. Select the **Communications** tab. 3. **Add a Notification Channel**: 1. Click the **"Add Channel"** button. 4. **Configure Email Notifications**: 1. In the modal that opens, choose the **Email** option and give the channel a name. 5. **Add Recipients and Email Details**: 1. On the next screen, enter the list of email addresses that should receive the notifications.\ Additionally, specify the **email subject** that will appear when the email is sent. 6. **Save** 1. Click the butten **Create channel**. This will set up your email notifications, allowing you to customize the recipients and the content for the alerts sent by the system. {% embed url="" %} # Slack To enable Slack integration, follow these steps: 1. **Navigate to Settings**: 1. Go to the **Settings** section of the platform. 2. **Access Communications Settings**: 1. Select the **Communications** tab. 3. **Add a Notification Channel**: 1. Click the **"Add Channel"** button. 4. **Configure Discord Notifications**: 1. In the modal that opens, choose the **Slack** option and give the channel a name. 5. **Add Recipients and Email Details**: 1. Authorize the intregration via OAuth. 2. Select the **slack channel** that the integration will send notifications. 6. **Save** 1. Click the butten **Create channel**. This will set up your email notifications, allowing you to customize the recipients and the content for the alerts sent by the system. {% embed url="" %} # Runs history You can view detailed information about completed job executions by navigating to the **"Runs"** tab of the desired connection or on the **"Runs"** page through the navbar on the left. #### Steps to Access Execution Details: 1. **Open the "Runs" page**: * Click on the **"Runs"** page to view a list of all executions. 2. **Filter Executions**: * Use filters to narrow down the list by: * **Job Name** * **Connection** * **Execution Status** (e.g., success, failure) * **Date Range.** 3. **View Execution Details**: * Click on a specific execution from the list. * A side panel will appear, showing additional information such as execution logs, timestamps, metrics, and any errors encountered. This feature allows you to efficiently track, analyze, and debug job executions, ensuring smoother data workflows. {% embed url="" %} # How we move data The data synchronization process in Erathos follows the flow illustrated below:
* **Data Source Environment**: The process begins with data extraction from your source system, such as a database (e.g., PostgreSQL) or a SaaS platform like HubSpot, configured in **Connections**. * **Temporary Storage**: During each job execution, the extracted data is temporarily stored in a cloud bucket (e.g., S3, GCS, or Azure Blob Storage) within Erathos' infrastructure. These temporary files ensure efficient and scalable handling of data. * **Loading to Data Warehouse**: Once the data is ready for transfer, Erathos uses commands like `COPY` (or equivalent methods specific to the destination) to load the data from the temporary storage into your Data Warehouse. * **Data Cleanup**: After the process is complete, all temporary files are deleted, ensuring security and optimal use of storage resources. # APIs # ActiveCampaign Find out how to connect ActiveCampaign to your data warehouse effortlessly. ## Using the Erathos platform When selecting ActiveCampaign as a new connector on the Erathos platform, you will need to name your connection and fill in the following form: ![](https://help.erathos.com/rails/active_storage/blobs/redirect/eyJfcmFpbHMiOnsibWVzc2FnZSI6IkJBaHBhZz09IiwiZXhwIjpudWxsLCJwdXIiOiJibG9iX2lkIn19--b0e4bab201120ddfa98a12925793b488199fd36f/activecampaign.png) ## How to find my Account Name? Your **Account Name** can be found directly in the URL after logging in to ActiveCampaign, as is shown on the attachment below:
Based on the example above, you should fill the **account name** information with: **123456demo** ## How to find my API Token? To find your API Token, follow these steps: 1. Log in to your account 2. Access **Account Settings** 3. Select the **Developer** tab, where the token will be displayed 4. Click on Copy API Key and paste it on the Erathos platform accordingly ![](https://help.erathos.com/rails/active_storage/blobs/redirect/eyJfcmFpbHMiOnsibWVzc2FnZSI6IkJBaHBjZz09IiwiZXhwIjpudWxsLCJwdXIiOiJibG9iX2lkIn19--fb2f8ae91ea9a0a1afd42f29c86d6cd22b46e128/Untitled%20\(45\).png) With this connection created you can seemlessly move your ActiveCampaign data to your BigQuery, Redshift or Postgres data-warehouse. ## What endpoints can I access with the Erathos platform? * accounts * accounts\_contacts * accounts\_custom\_fields * accounts\_custom\_fields\_values * addresses * automations * brandings * calendar\_feeds * campaigns * campaign\_links * messages * email\_activities * contacts\_custom\_fields\_values * contacts\_custom\_fields * contacts\_automations * contacts * contacts\_scores * deals * pipelines * stages * deals\_custom\_fields * deals\_custom\_fields\_values * forms * lists * saved\_responses * scores * segments * tags * tasks * tasks\_types * users * deal\_roles * deal\_activities # Agendor ### Using the Erathos platform When selecting Agendor as a new connector on the Erathos platform, you will need to name your connection and fill in the following form: * **Token** — your personal API token from your Agendor account With this connection created you can seamlessly move your Agendor data to your BigQuery, Redshift or Postgres data warehouse. ### How to find my token? You can find your API Token by logging into Agendor and navigating to **Menu > Integrações** (Integrations). Your token will be displayed on that page. Now, paste the value in the Erathos platform Token field. Don't forget to click on **Save and close** to advance to the next steps of the integration. ### What endpoints can I access with the Erathos platform? * organizations * people * deals * tasks * users * categories * sectors * lead\_origins * loss\_reasons * funnels * deal\_stages * deal\_statuses * metrics * products * product\_categories # Amplitude Find out how to connect Amplitude to your data warehouse effortlessly. ## Using the Erathos platform When selecting Amplitude as a new connector on the Erathos platform, you will need to name your connection and fill in the following form: ![](https://help.erathos.com/rails/active_storage/blobs/redirect/eyJfcmFpbHMiOnsibWVzc2FnZSI6IkJBaHBhQT09IiwiZXhwIjpudWxsLCJwdXIiOiJibG9iX2lkIn19--9890f44badc1b4472f27501e9613ca48542e598c/amplitude.png) ## How to find the API Key and API Secret credentials? 1. In the Amplitude Analytics web app, access your settings on the upper right corner of the page. 2. Click on projects and select the desired project 3. In the General tab, copy the credencials as in the attachment bellow and paste them on the Erathos platform accordingly ![](https://help.erathos.com/rails/active_storage/blobs/redirect/eyJfcmFpbHMiOnsibWVzc2FnZSI6IkJBaHBhUT09IiwiZXhwIjpudWxsLCJwdXIiOiJibG9iX2lkIn19--8d6895e1eccd407b4736f63d7dcc4f28f4886af3/Untitled%20\(37\).png) With this connection established you can seemlessly move your Amplitude data to your BigQuery, Redshift or Postgres data-warehouse. ## What endpoints can I access with the Erathos platform? * export # Asaas Find out how to connect Asaas to your data warehouse effortlessly. ## Using the Erathos platform When selecting Asaas as a new connector on the Erathos platform, you will need to name your connection and fill in the following form: ![](https://help.erathos.com/rails/active_storage/blobs/redirect/eyJfcmFpbHMiOnsibWVzc2FnZSI6IkJBaHBjdz09IiwiZXhwIjpudWxsLCJwdXIiOiJibG9iX2lkIn19--b2919068f6fda932c09388a6dd72977f1f8c2a84/asaas.png) ## How to find your Asaas API Token? 1. Log in to your account 2. Through the menu access **My Account** 3. Click on **Integration** and then on **Generate new API Key**, as is displayed below: ![](https://help.erathos.com/rails/active_storage/blobs/redirect/eyJfcmFpbHMiOnsibWVzc2FnZSI6IkJBaHBkQT09IiwiZXhwIjpudWxsLCJwdXIiOiJibG9iX2lkIn19--07757e3cc03f7b619918f24c204416ea539de6d5/Untitled%20\(47\).png) Now, paste the generated token on the Erathos platform accordingly. Don't forget to click on **Save and close.** With this connection created you can seemlessly move your Asaas data to your BigQuery, Redshift or Postgres data-warehouse. ## What endpoints can I access with the Erathos platform? * customers * payments * installments * subscriptions * payment\_links * transfers * anticipations * payment\_dunnings * payment\_dunnings\_history * payment\_dunnings\_partial\_payments * bill * mobile\_phone\_recharge * credit\_bureau\_report * financial\_transactions * payment\_available\_dunnings * invoices * pix\_adress\_keys * pix\_transactions * accounts # Asana Find out how to connect Asana to your data warehouse effortlessly. ## Using the Erathos platform When selecting Asana as a new connector on the Erathos platform, you will need to authorize the connection by simply logging into the Asana account associated with your browser. Just click on '**Authorize Asana**' as shown in the attachment below: ![](https://help.erathos.com/rails/active_storage/blobs/redirect/eyJfcmFpbHMiOnsibWVzc2FnZSI6IkJBaHBkUT09IiwiZXhwIjpudWxsLCJwdXIiOiJibG9iX2lkIn19--48b478580dcd4cc06f9c4c230202c6b9780a815c/asana.png) Don't forget to click on **Save and close** to advance to the next steps of the integration. With this connection created you can seemlessly move your Asana data to your BigQuery, Redshift or Postgres data-warehouse. ## What endpoints can I access with the Erathos platform? * workspaces * users * projects * tasks * time\_tracking * goals * teams # Bling Find out how to connect Bling to your data warehouse effortlessly. ## Using the Erathos platform When selecting Bling as a new connector on the Erathos platform, you will need to name your connection and authorize access to your Bling account. With this connection created you can seamlessly move your Bling data to your BigQuery, Redshift or Postgres data warehouse. ### How to authorize? Bling uses OAuth 2.0 for authentication. When setting up the connection on Erathos, you will be redirected to Bling's authorization page. Log in to your Bling account and grant access to allow Erathos to read your data. After authorizing, you will be redirected back to the Erathos platform automatically. Click **Save and close** to complete the setup. Erathos handles all token management and refreshes on your behalf. {% hint style="warning" %} If you see a message like the one shown below, please contact Bling Support and request access to the specific modules that are interfering with the connection. Your Bling plan must be 'Mercúrio' or higher. {% endhint %}
*** ## Endpoints and fields ### categorias\_lojas Sync type availability: Full-refresh | Field | Type | | ------------------- | ------- | | loja.id | integer | | descricao | text | | codigo | text | | categoriaProduto.id | integer | | id | integer | ### categorias\_produtos Sync type availability: Full-refresh | Field | Type | | --------------- | ------- | | id | integer | | descricao | text | | categoriaPai.id | integer | ### categorias\_financeiras Sync type availability: Full-refresh | Field | Type | | -------------- | ------- | | descricao | text | | tipo | integer | | id | integer | | idCategoriaPai | integer | ### contas\_contabeis Sync type availability: Full-refresh | Field | Type | | --------------- | ------- | | id | integer | | descricao | text | | tipo | text | | aliasIntegracao | text | ### contas\_receber Sync type availability: Full and incremental refresh [Cursor](/platform/connections/sync-types#understanding-cursors): `dataEmissao` Parent of [`contas_receber_detalhes`](#contas_receber_detalhes) | Field | Type | Cursor | | --------------------------- | ------- | ------ | | situacao | integer | | | vencimento | date | | | valor | float | | | contato.id | integer | | | contato.nome | text | | | contato.numeroDocumento | text | | | contato.tipo | text | | | id | integer | | | idTransacao | text | | | linkQRCodePix | text | | | linkBoleto | text | | | dataEmissao | date | ✓ | | formaPagamento.id | integer | | | formaPagamento.codigoFiscal | integer | | | contaContabil.id | integer | | | contaContabil.descricao | text | | | origem.id | integer | | | origem.tipoOrigem | text | | | origem.numero | text | | | origem.dataEmissao | date | | | origem.valor | float | | | origem.situacao | integer | | | origem.url | text | | ### contas\_receber\_detalhes Sync type availability: Full-refresh Child of [`contas_receber`](#contas_receber) Parent of [`receber_borderos`](#receber_borderos) | Field | Type | | --------------------------- | ------- | | id | integer | | situacao | integer | | vencimento | date | | valor | float | | idTransacao | text | | linkQRCodePix | text | | linkBoleto | text | | dataEmissao | date | | contato.id | integer | | contato.nome | text | | contato.numeroDocumento | text | | contato.tipo | text | | formaPagamento.id | integer | | formaPagamento.codigoFiscal | integer | | contaContabil.id | integer | | contaContabil.descricao | text | | origem.id | integer | | origem.tipoOrigem | text | | origem.numero | text | | origem.dataEmissao | text | | origem.valor | float | | origem.situacao | integer | | origem.url | text | | saldo | float | | vencimentoOriginal | date | | numeroDocumento | text | | competencia | date | | historico | text | | numeroBanco | text | | portador.id | integer | | categoria.id | integer | | vendedor.id | integer | | ocorrencia.tipo | integer | | borderos | json | ### receber\_borderos Sync type availability: Full-refresh Child of [`contas_receber_detalhes`](#contas_receber_detalhes) | Field | Type | | ------------ | ------- | | id | integer | | data | date | | historico | text | | portador.id | integer | | categoria.id | integer | | pagamentos | json | ### contas\_pagar Sync type availability: Full and incremental refresh [Cursor](/platform/connections/sync-types#understanding-cursors): `vencimento` Parent of [`contas_pagar_detalhes`](#contas_pagar_detalhes) | Field | Type | Cursor | | --------------------------- | ------- | ------ | | situacao | integer | | | vencimento | date | ✓ | | valor | float | | | contato.id | integer | | | contato.nome | text | | | contato.numeroDocumento | text | | | contato.tipo | text | | | id | integer | | | idTransacao | text | | | linkQRCodePix | text | | | linkBoleto | text | | | dataEmissao | date | | | formaPagamento.id | integer | | | formaPagamento.codigoFiscal | integer | | | contaContabil.id | integer | | | contaContabil.descricao | text | | | origem.id | integer | | | origem.tipoOrigem | text | | | origem.numero | text | | | origem.dataEmissao | date | | | origem.valor | float | | | origem.situacao | integer | | | origem.url | text | | ### contas\_pagar\_detalhes Sync type availability: Full-refresh Child of [`contas_pagar`](#contas_pagar) Parent of [`borderos`](#borderos) | Field | Type | | ------------------ | ------- | | id | integer | | situacao | integer | | vencimento | date | | valor | float | | contato.id | integer | | formaPagamento.id | integer | | saldo | float | | dataEmissao | date | | vencimentoOriginal | date | | numeroDocumento | text | | competencia | date | | historico | text | | numeroBanco | text | | portador.id | integer | | categoria.id | integer | | ocorrencia.tipo | integer | | borderos | json | ### borderos Sync type availability: Full-refresh Child of [`contas_pagar_detalhes`](#contas_pagar_detalhes) | Field | Type | | ------------ | ------- | | id | integer | | data | date | | historico | text | | portador.id | integer | | categoria.id | integer | | pagamentos | json | ### contatos Sync type availability: Full and incremental refresh [Cursor](/platform/connections/sync-types#understanding-cursors): `id` Parent of [`contato_detalhes`](#contato_detalhes) | Field | Type | Cursor | | --------------- | ------- | ------ | | id | integer | ✓ | | nome | text | | | codigo | text | | | situacao | text | | | numeroDocumento | text | | | telefone | text | | | celular | text | | ### contato\_detalhes Sync type availability: Full-refresh Child of [`contatos`](#contatos) | Field | Type | | ------------------------------ | ------- | | id | integer | | nome | text | | codigo | text | | situacao | text | | numeroDocumento | text | | telefone | text | | celular | text | | fantasia | text | | tipo | text | | indicadorIe | integer | | ie | text | | rg | text | | orgaoEmissor | text | | email | text | | endereco.geral.endereco | text | | endereco.geral.cep | text | | endereco.geral.bairro | text | | endereco.geral.municipio | text | | endereco.geral.uf | text | | endereco.geral.numero | text | | endereco.geral.complemento | text | | endereco.cobranca.endereco | text | | endereco.cobranca.cep | text | | endereco.cobranca.bairro | text | | endereco.cobranca.municipio | text | | endereco.cobranca.uf | text | | endereco.cobranca.numero | text | | endereco.cobranca.complemento | text | | vendedor.id | integer | | dadosAdicionais.dataNascimento | text | | dadosAdicionais.sexo | text | | dadosAdicionais.naturalidade | text | | financeiro.limiteCredito | float | | financeiro.condicaoPagamento | text | | financeiro.categoria.id | integer | | pais.nome | text | | tiposContato | json | | pessoasContato | json | ### tipos\_contatos Sync type availability: Full-refresh | Field | Type | | --------- | ------- | | id | integer | | descricao | text | ### contratos Sync type availability: Full and incremental refresh [Cursor](/platform/connections/sync-types#understanding-cursors): `data` Parent of [`contrato_detalhes`](#contrato_detalhes) | Field | Type | Cursor | | ---------- | ------- | ------ | | descricao | text | | | data | date | ✓ | | numero | text | | | valor | float | | | situacao | integer | | | contato.id | integer | | | id | integer | | ### contrato\_detalhes Sync type availability: Full-refresh Child of [`contratos`](#contratos) | Field | Type | | --------------------------------- | ------- | | id | integer | | categoria.id | integer | | cobranca.dataBase | date | | cobranca.contato.id | integer | | cobranca.vencimento.tipo | integer | | cobranca.vencimento.dia | integer | | cobranca.vencimento.periodicidade | integer | | contaContabil.id | integer | | contato.id | integer | | data | date | | dataFim | date | | desconto.valor | float | | desconto.dataFim | date | | descricao | text | | emitirOrdemServico | boolean | | formaPagamento.id | integer | | numero | text | | observacoes | text | | situacao | integer | | tipoManutencao | integer | | valor | float | | vendedor.id | integer | | vendedor.comissao.aliquota | float | | vendedor.comissao.numeroParcelas | integer | | notaFiscal.mes | integer | | notaFiscal.gerar | integer | | notaFiscal.descontarImpostoRenda | integer | | notaFiscal.texto | text | | notaFiscal.cfop | text | | notaFiscal.iss.descontar | boolean | | notaFiscal.iss.aliquota | integer | | notaFiscal.item.codigoServico | text | | notaFiscal.item.produto.id | integer | ### depositos Sync type availability: Full-refresh | Field | Type | | ------------------ | ------- | | id | integer | | descricao | text | | situacao | integer | | padrao | boolean | | desconsiderarSaldo | boolean | ### formas\_pagamentos Sync type availability: Full-refresh Parent of [`formas_pagamentos_detalhes`](#formas_pagamentos_detalhes) | Field | Type | | ------------- | ------- | | id | integer | | descricao | text | | tipoPagamento | integer | | finalidade | integer | | situacao | integer | | fixa | boolean | | padrao | integer | | juros | float | | multa | float | ### formas\_pagamentos\_detalhes Sync type availability: Full-refresh Child of [`formas_pagamentos`](#formas_pagamentos) | Field | Type | | ----------------------------- | ------- | | id | integer | | descricao | text | | destino | integer | | finalidade | integer | | tipoPagamento | integer | | situacao | integer | | fixa | boolean | | padrao | integer | | condicao | text | | taxas.aliquota | float | | taxas.valor | float | | taxas.prazo | integer | | dadosCartao.bandeira | integer | | dadosCartao.tipo | integer | | dadosCartao.cnpjCredenciadora | text | | juros | float | | multa | float | | utilizaDiasUteis | boolean | ### logisticas Sync type availability: Full-refresh Parent of [`remessas_logisticas`](#remessas_logisticas) | Field | Type | | ---------------- | ------- | | id | integer | | descricao | text | | tipoIntegracao | text | | integracaoNativa | boolean | | situacao | text | | integracao.id | integer | | servicos | json | ### servicos\_logisticas Sync type availability: Full-refresh | Field | Type | | ----------------- | ------- | | id | integer | | descricao | text | | freteItem | float | | estimativaEntrega | integer | | codigo | text | | logistica.id | integer | | transportador.id | integer | | aliases | json | | ativo | boolean | | idCodigoServico | text | ### remessas\_logisticas Sync type availability: Full-refresh Child of [`logisticas`](#logisticas) | Field | Type | | ----------- | ------- | | id | integer | | dataCriacao | date | | descricao | text | | numeroPlp | text | | objetos | json | | situacao | integer | ### naturezas\_operacoes Sync type availability: Full-refresh | Field | Type | | --------- | ------- | | id | integer | | situacao | integer | | padrao | integer | | descricao | text | ### nfce Sync type availability: Full and incremental refresh [Cursor](/platform/connections/sync-types#understanding-cursors): `dataEmissao` Parent of [`nfce_detalhes`](#nfce_detalhes) | Field | Type | Cursor | | ---------------------------- | --------- | ------ | | id | integer | | | tipo | integer | | | situacao | integer | | | numero | text | | | dataEmissao | timestamp | ✓ | | dataOperacao | timestamp | | | naturezaOperacao.id | integer | | | loja.id | integer | | | loja.numero | text | | | contato.id | integer | | | contato.nome | text | | | contato.tipoPessoa | text | | | contato.numeroDocumento | text | | | contato.contribuinte | text | | | contato.ie | text | | | contato.rg | text | | | contato.telefone | text | | | contato.email | text | | | contato.endereco.endereco | text | | | contato.endereco.bairro | text | | | contato.endereco.municipio | text | | | contato.endereco.numero | text | | | contato.endereco.complemento | text | | | contato.endereco.cep | text | | | contato.endereco.uf | text | | | contato.endereco.pais | text | | ### nfce\_detalhes Sync type availability: Full-refresh Child of [`nfce`](#nfce) | Field | Type | | ---------------------------------------- | --------- | | id | integer | | tipo | integer | | situacao | integer | | numero | text | | dataEmissao | timestamp | | dataOperacao | timestamp | | serie | integer | | valorNota | float | | finalidade | text | | chaveAcesso | text | | xml | text | | linkDanfe | text | | linkPDF | text | | numeroPedidoLoja | text | | naturezaOperacao.id | integer | | loja.id | integer | | loja.numero | text | | contato.id | integer | | contato.nome | text | | contato.tipoPessoa | text | | contato.numeroDocumento | text | | contato.contribuinte | text | | contato.ie | text | | contato.rg | text | | contato.telefone | text | | contato.email | text | | contato.endereco.endereco | text | | contato.endereco.bairro | text | | contato.endereco.municipio | text | | contato.endereco.numero | text | | contato.endereco.complemento | text | | contato.endereco.cep | text | | contato.endereco.uf | text | | contato.endereco.pais | text | | transporte.fretePorConta | integer | | transporte.transportador.nome | text | | transporte.transportador.numeroDocumento | text | | transporte.volumes | json | | transporte.etiqueta.nome | text | | transporte.etiqueta.endereco | text | | transporte.etiqueta.numero | text | | transporte.etiqueta.complemento | text | | transporte.etiqueta.municipio | text | | transporte.etiqueta.uf | text | | transporte.etiqueta.cep | text | | transporte.etiqueta.bairro | text | | vendedor.id | integer | | valorFrete | float | | optanteSimplesNacional | boolean | | itens | json | ### nfe Sync type availability: Full and incremental refresh [Cursor](/platform/connections/sync-types#understanding-cursors): `dataEmissao` Parent of [`nfe_detalhes`](#nfe_detalhes) | Field | Type | Cursor | | ---------------------------- | --------- | ------ | | id | integer | | | tipo | integer | | | situacao | integer | | | numero | text | | | dataEmissao | timestamp | ✓ | | dataOperacao | timestamp | | | naturezaOperacao.id | integer | | | loja.id | integer | | | loja.numero | text | | | contato.id | integer | | | contato.nome | text | | | contato.tipoPessoa | text | | | contato.numeroDocumento | text | | | contato.contribuinte | text | | | contato.ie | text | | | contato.rg | text | | | contato.telefone | text | | | contato.email | text | | | contato.endereco.endereco | text | | | contato.endereco.bairro | text | | | contato.endereco.municipio | text | | | contato.endereco.numero | text | | | contato.endereco.complemento | text | | | contato.endereco.cep | text | | | contato.endereco.uf | text | | | contato.endereco.pais | text | | ### nfe\_detalhes Sync type availability: Full-refresh Child of [`nfe`](#nfe) | Field | Type | | ---------------------------------------- | --------- | | id | integer | | tipo | integer | | situacao | integer | | numero | text | | dataEmissao | timestamp | | dataOperacao | timestamp | | serie | integer | | valorNota | float | | finalidade | text | | chaveAcesso | text | | xml | text | | linkDanfe | text | | linkPDF | text | | numeroPedidoLoja | text | | naturezaOperacao.id | integer | | loja.id | integer | | loja.numero | text | | contato.id | integer | | contato.nome | text | | contato.tipoPessoa | text | | contato.numeroDocumento | text | | contato.contribuinte | text | | contato.ie | text | | contato.rg | text | | contato.telefone | text | | contato.email | text | | contato.endereco.endereco | text | | contato.endereco.bairro | text | | contato.endereco.municipio | text | | contato.endereco.numero | text | | contato.endereco.complemento | text | | contato.endereco.cep | text | | contato.endereco.uf | text | | contato.endereco.pais | text | | transporte.fretePorConta | float | | transporte.transportador.nome | text | | transporte.transportador.numeroDocumento | text | | transporte.volumes | json | | transporte.etiqueta.nome | text | | transporte.etiqueta.endereco | text | | transporte.etiqueta.numero | text | | transporte.etiqueta.complemento | text | | transporte.etiqueta.municipio | text | | transporte.etiqueta.uf | text | | transporte.etiqueta.cep | text | | transporte.etiqueta.bairro | text | | vendedor.id | integer | | valorFrete | float | | optanteSimplesNacional | boolean | | itens | json | | parcelas | json | ### nfse Sync type availability: Full and incremental refresh [Cursor](/platform/connections/sync-types#understanding-cursors): `dataEmissao` Parent of [`nfse_detalhes`](#nfse_detalhes) | Field | Type | Cursor | | ----------------------- | ------- | ------ | | id | integer | | | numeroRPS | text | | | serie | text | | | numero | text | | | situacao | integer | | | dataEmissao | date | ✓ | | valor | float | | | contato.id | integer | | | contato.nome | text | | | contato.numeroDocumento | text | | | contato.email | text | | ### nfse\_detalhes Sync type availability: Full-refresh Child of [`nfse`](#nfse) | Field | Type | | ----------------------- | ------- | | id | integer | | numeroRPS | text | | serie | text | | numero | text | | situacao | integer | | dataEmissao | date | | valor | float | | link | text | | codigoVerificacao | text | | contato.id | integer | | contato.nome | text | | contato.numeroDocumento | text | | contato.email | text | ### propostas\_comerciais Sync type availability: Full and incremental refresh [Cursor](/platform/connections/sync-types#understanding-cursors): `data` Parent of [`propostas_comerciais_detalhes`](#propostas_comerciais_detalhes) | Field | Type | Cursor | | ------------- | ------- | ------ | | id | integer | | | data | date | ✓ | | situacao | text | | | total | float | | | totalProdutos | float | | | numero | integer | | | contato.id | integer | | | loja.id | integer | | ### propostas\_comerciais\_detalhes Sync type availability: Full-refresh Child of [`propostas_comerciais`](#propostas_comerciais) | Field | Type | | ------------------------------------- | ------- | | id | integer | | data | date | | situacao | text | | total | float | | totalProdutos | float | | numero | integer | | contato.id | integer | | loja.id | integer | | desconto | float | | outrasDespesas | float | | garantia | integer | | dataProximoContato | date | | observacoes | text | | observacaoInterna | text | | totalOutrosItens | integer | | aosCuidadosDe | text | | introducao | text | | prazoEntrega | text | | vendedor.id | integer | | transporte.freteModalidade | integer | | transporte.frete | float | | transporte.quantidadeVolumes | float | | transporte.prazoEntrega | integer | | transporte.pesoBruto | float | | transporte.contato.id | integer | | transporte.contato.nome | text | | transporte.volumes.id | integer | | transporte.volumes.servico | text | | transporte.volumes.codigoRastreamento | text | | itens | json | | parcelas | json | ### pedidos\_compras Sync type availability: Full and incremental refresh [Cursor](/platform/connections/sync-types#understanding-cursors): `data` Parent of [`pedidos_compras_detalhes`](#pedidos_compras_detalhes) | Field | Type | Cursor | | -------------- | ------- | ------ | | id | integer | | | numero | integer | | | data | date | ✓ | | dataPrevista | date | | | totalProdutos | float | | | total | float | | | situacao.valor | integer | | | fornecedor.id | integer | | ### pedidos\_compras\_detalhes Sync type availability: Full-refresh Child of [`pedidos_compras`](#pedidos_compras) | Field | Type | | ------------------------ | ------- | | id | integer | | numero | integer | | data | date | | dataPrevista | date | | totalProdutos | float | | total | float | | situacao.valor | integer | | fornecedor.id | integer | | ordemCompra | text | | observacoes | text | | observacoesInternas | text | | desconto.valor | float | | desconto.unidade | text | | categoria.id | integer | | tributacao.totalICMS | float | | tributacao.totalIPI | float | | transporte.frete | float | | transporte.transportador | text | | transporte.fretePorConta | integer | | transporte.pesoBruto | float | | transporte.volumes | integer | | itens | json | | parcelas | json | ### pedidos\_vendas Sync type availability: Full and incremental refresh [Cursor](/platform/connections/sync-types#understanding-cursors): `data` Parent of [`pedidos_vendas_detalhes`](#pedidos_vendas_detalhes) | Field | Type | Cursor | | ----------------------- | ------- | ------ | | id | integer | | | numero | integer | | | numeroLoja | text | | | data | date | ✓ | | dataPrevista | date | | | dataSaida | date | | | totalProdutos | float | | | total | float | | | situacao.id | integer | | | situacao.valor | integer | | | loja.id | integer | | | contato.id | integer | | | contato.nome | text | | | contato.tipoPessoa | text | | | contato.numeroDocumento | text | | ### pedidos\_vendas\_detalhes Sync type availability: Full-refresh Child of [`pedidos_vendas`](#pedidos_vendas) | Field | Type | | ------------------------------- | ------- | | id | integer | | numero | integer | | numeroLoja | text | | data | date | | dataPrevista | date | | dataSaida | date | | totalProdutos | float | | total | float | | situacao.id | integer | | situacao.valor | integer | | loja.id | integer | | contato.id | integer | | contato.nome | text | | contato.tipoPessoa | text | | contato.numeroDocumento | text | | numeroPedidoCompra | text | | outrasDespesas | float | | observacoes | text | | observacoesInternas | text | | desconto.valor | float | | desconto.unidade | text | | categoria.id | integer | | notaFiscal.id | integer | | tributacao.totalICMS | float | | tributacao.totalIPI | float | | transporte.fretePorConta | integer | | transporte.frete | float | | transporte.quantidadeVolumes | integer | | transporte.pesoBruto | float | | transporte.prazoEntrega | integer | | transporte.contato.nome | text | | transporte.contato.id | integer | | transporte.etiqueta.nome | text | | transporte.etiqueta.endereco | text | | transporte.etiqueta.numero | text | | transporte.etiqueta.complemento | text | | transporte.etiqueta.municipio | text | | transporte.etiqueta.uf | text | | transporte.etiqueta.cep | text | | transporte.etiqueta.bairro | text | | transporte.etiqueta.nomePais | text | | transporte.volumes | json | | vendedor.id | integer | | intermediador.cnpj | text | | intermediador.nomeUsuario | text | | taxas.taxaComissao | float | | taxas.custoFrete | float | | taxas.valorBase | float | | itens | json | | parcelas | json | ### produtos Sync type availability: Full-refresh Parent of [`produtos_detalhes`](#produtos_detalhes) | Field | Type | | ------------------------- | ------- | | id | integer | | nome | text | | tipo | text | | situacao | text | | formato | text | | idProdutoPai | integer | | codigo | text | | preco | float | | precoCusto | float | | estoque.saldoVirtualTotal | float | | descricaoCurta | text | | imagemURL | text | ### produtos\_detalhes Sync type availability: Full-refresh Child of [`produtos`](#produtos) | Field | Type | | ------------------------------------- | ------- | | id | integer | | nome | text | | tipo | text | | situacao | text | | formato | text | | codigo | text | | preco | float | | descricaoCurta | text | | imagemURL | text | | dataValidade | date | | unidade | text | | pesoLiquido | float | | pesoBruto | float | | volumes | integer | | itensPorCaixa | float | | gtin | text | | gtinEmbalagem | text | | tipoProducao | text | | condicao | integer | | freteGratis | boolean | | marca | text | | descricaoComplementar | text | | linkExterno | text | | observacoes | text | | descricaoEmbalagemDiscreta | text | | categoria.id | integer | | estoque.minimo | float | | estoque.maximo | float | | estoque.crossdocking | integer | | estoque.localizacao | text | | estoque.saldoVirtualTotal | float | | fornecedor.id | integer | | fornecedor.contato.id | integer | | fornecedor.contato.nome | text | | fornecedor.codigo | text | | fornecedor.precoCusto | float | | fornecedor.precoCompra | float | | actionEstoque | text | | dimensoes.largura | float | | dimensoes.altura | float | | dimensoes.profundidade | float | | dimensoes.unidadeMedida | integer | | tributacao.origem | integer | | tributacao.nFCI | text | | tributacao.ncm | text | | tributacao.cest | text | | tributacao.codigoListaServicos | text | | tributacao.spedTipoItem | text | | tributacao.codigoItem | text | | tributacao.percentualTributos | float | | tributacao.valorBaseStRetencao | float | | tributacao.valorStRetencao | float | | tributacao.valorICMSSubstituto | float | | tributacao.codigoExcecaoTipi | text | | tributacao.classeEnquadramentoIpi | text | | tributacao.valorIpiFixo | float | | tributacao.codigoSeloIpi | text | | tributacao.valorPisFixo | float | | tributacao.valorCofinsFixo | float | | tributacao.codigoANP | text | | tributacao.descricaoANP | text | | tributacao.percentualGLP | float | | tributacao.percentualGasNacional | float | | tributacao.percentualGasImportado | float | | tributacao.valorPartida | float | | tributacao.tipoArmamento | float | | tributacao.descricaoCompletaArmamento | text | | tributacao.dadosAdicionais | text | | tributacao.grupoProduto.id | integer | | midia.video.url | text | | midia.imagens.externas | json | | midia.imagens.internas | json | | linhaProduto.id | integer | | estrutura.tipoEstoque | text | | estrutura.lancamentoEstoque | text | | estrutura.componentes | json | | camposCustomizados | json | | variacoes | json | ### vendedores Sync type availability: Full-refresh | Field | Type | | ---------------- | ------- | | id | integer | | contato.id | integer | | contato.nome | text | | contato.situacao | text | | descontoLimite | float | | loja.id | integer | ### canais\_venda Sync type availability: Full-refresh | Field | Type | | --------- | ------- | | id | integer | | descricao | text | | tipo | text | | situacao | integer | ### grupos\_produtos Sync type availability: Full-refresh | Field | Type | | -------------------- | ------- | | id | integer | | nome | text | | grupoProdutoPai.id | integer | | grupoProdutoPai.nome | text | ### produtos\_lojas Sync type availability: Full-refresh | Field | Type | | ------------------ | ------- | | id | integer | | codigo | text | | preco | float | | precoPromocional | float | | produto.id | integer | | loja.id | integer | | fornecedorLoja.id | integer | | marcaLoja.id | integer | | categoriasProdutos | json | ### modulos Sync type availability: Full-refresh Parent of [`modulos_situacoes`](#modulos_situacoes) | Field | Type | | -------------- | ---- | | id | text | | nome | text | | descricao | text | | criarSituacoes | text | ### modulos\_situacoes Sync type availability: Full-refresh Child of [`modulos`](#modulos) | Field | Type | | --------- | ---- | | id | text | | nome | text | | idHerdado | text | | cor | text | ### Entity Relationships ```mermaid erDiagram contas_receber ||--o{ contas_receber_detalhes : "id = id_conta_receber" contas_receber_detalhes ||--o{ receber_borderos : "id = id_bordero" contas_pagar ||--o{ contas_pagar_detalhes : "id = id_conta_pagar" contas_pagar_detalhes ||--o{ borderos : "id = id_bordero" contatos ||--o{ contato_detalhes : "id = id_contato" contratos ||--o{ contrato_detalhes : "id = id_contrato" formas_pagamentos ||--o{ formas_pagamentos_detalhes : "id = id_forma_pagamento" logisticas ||--o{ remessas_logisticas : "id = id_logisticas" nfce ||--o{ nfce_detalhes : "id = id_nfce" nfe ||--o{ nfe_detalhes : "id = id_nfe" nfse ||--o{ nfse_detalhes : "id = id_nfse" propostas_comerciais ||--o{ propostas_comerciais_detalhes : "id = id_propostas_comerciais" pedidos_compras ||--o{ pedidos_compras_detalhes : "id = id_pedido_compra" pedidos_vendas ||--o{ pedidos_vendas_detalhes : "id = id_pedido_venda" produtos ||--o{ produtos_detalhes : "id = id_produto" modulos ||--o{ modulos_situacoes : "id = id_modulo" categorias_lojas { integer id PK } categorias_produtos { integer id PK } categorias_financeiras { integer id PK } contas_contabeis { integer id PK } contas_receber { integer id PK } contas_receber_detalhes { integer id PK } receber_borderos { integer id PK } contas_pagar { integer id PK } contas_pagar_detalhes { integer id PK } borderos { integer id PK } contatos { integer id PK } contato_detalhes { integer id PK } tipos_contatos { integer id PK } contratos { integer id PK } contrato_detalhes { integer id PK } depositos { integer id PK } formas_pagamentos { integer id PK } formas_pagamentos_detalhes { integer id PK } logisticas { integer id PK } servicos_logisticas { integer id PK } remessas_logisticas { integer id PK } naturezas_operacoes { integer id PK } nfce { integer id PK } nfce_detalhes { integer id PK } nfe { integer id PK } nfe_detalhes { integer id PK } nfse { integer id PK } nfse_detalhes { integer id PK } propostas_comerciais { integer id PK } propostas_comerciais_detalhes { integer id PK } pedidos_compras { integer id PK } pedidos_compras_detalhes { integer id PK } pedidos_vendas { integer id PK } pedidos_vendas_detalhes { integer id PK } produtos { integer id PK } produtos_detalhes { integer id PK } vendedores { integer id PK } canais_venda { integer id PK } grupos_produtos { integer id PK } produtos_lojas { integer id PK } modulos { text id PK } modulos_situacoes { text id PK } ``` # Blip Find out how to connect Blip to your data warehouse effortlessly. ## How to find my credentials? To connect Blip with Erathos, you need to register your Blip domain and token. To find these details, go to **Settings > Connection Information** (as shown in the image below). * **Domain**: Copy the value from "URL to send commands" — everything **before** `/commands`. * **Token**: Copy the value from "Header Authentication" — everything **after** `Key:`.
## What endpoints can I access with the Erathos platform? * active\_messages * active\_users * contacts * documment * documment\_collections * engaged\_users * last\_messages * list\_members * lists * received\_messages * reports * sent\_messages * threads # Beehiiv Find out how to connect Beehiiv to your data warehouse effortlessly. ## Using the Erathos platform When selecting Beehiiv as a new connector on the Erathos platform, you will need to name your connection and fill in the following form: ![](https://help.erathos.com/rails/active_storage/blobs/redirect/eyJfcmFpbHMiOnsibWVzc2FnZSI6IkJBaHBBaUlCIiwiZXhwIjpudWxsLCJwdXIiOiJibG9iX2lkIn19--270cb49b64f3c5c920954baff8d414412ad192b1/beehiiv%20conector.png) ## How to find my Access token? 1. On the left panel in your account, scroll down and select **Settings**. ![Settings.png](https://beehiivhelp.zendesk.com/hc/article_attachments/23927915594647) 2. Then, click on **Integrations**, which will open up the [API](https://app.beehiiv.com/settings/integrations/api) tab. ![](https://beehiivhelp.zendesk.com/hc/article_attachments/21229398024343) 3. To create a new API key that can be used to integrate your beehiiv account, click on the **New API Key** button. 4. A form will appear on the right. You must name your new API key and click on the **Create New Key** button.\ ![](https://beehiivhelp.zendesk.com/hc/article_attachments/21229389598743) 5. You’ll receive a success message at the top of your screen and then you can proceed to copy your new API key. ![be86132a-723c-4339-9a6e-f3b328e17b6f](https://beehiivhelp.zendesk.com/hc/article_attachments/23927955817751) **Warning:** Remember to save your new API key somewhere safe, it will not be displayed again. Don't forget to copy and paste the token on the Erathos platform Acces token field and click on **Save and close**. With this connection created you can seemlessly move your Beehiiv data to your BigQuery, Redshift or Postgres data-warehouse. ## What information can I bring to my data-warehouse with the Erathos platform? * publications * posts * email\_blasts * referral\_program * segments * subscriptions # BomControle Find out how to connect BomControle to your data warehouse effortlessly. ## Using the Erathos platform When selecting BomControle as a new connector on the Erathos platform, you will need to name your connection and fill in the following form:
## How to find my API Key? 1. Log into BomControle platform. Click on the cog icon to open the configuration menu and then select the option **Configuração de API Key** will be available.
2. On the configuration screen, click the button in the bottom right corner **Cadastrar Novo** 3. To create the credential you will need to inform a name to easily identify the purpose of the API key (suggestion: Erathos), which company may use the key, and which access permissions you wish to concede. 4. To finish the process find the created key and click the button **Copiar API Key para o Clipboard** to open a new window where you will be able to copy the key value. Don't forget to copy and paste the token on the Erathos platform Api Key field and click on **Save and close**. With this connection created you can seemlessly move your BomControle data to your BigQuery, Redshift or Postgres data-warehouse. ## What information can I bring to my data-warehouse with the Erathos platform? * categoria\_financeira * cliente\_detalhes * conta\_financeira * departamento * financeiro * venda # Braintrust ### Using the Erathos platform When selecting Braintrust as a new connector on the Erathos platform, you will need to name your connection and fill in the following form: * **API Key** — Your Braintrust API key, used to authenticate all requests to the Braintrust API. With this connection created you can seamlessly move your Braintrust data to your BigQuery, Redshift or Postgres data warehouse. ### How to find my token? You can find your API Key by navigating to **Settings > API keys** inside the Braintrust dashboard. Click **Create key**, give it a descriptive name, and copy the generated value. Now, paste the value in the Erathos platform API Key field. Don't forget to click on **Save and close** to advance to the next steps of the integration. ### What endpoints can I access with the Erathos platform? * organizations * users * projects * roles * groups * experiments * datasets * prompts * functions * experiment\_events * dataset\_events # Campaign Monitor Find out how to connect Campaign Monitor to your data warehouse effortlessly. ## Using the Erathos platform: When selecting Campaign Monitor as a new connector on the Erathos platform, you will need to authorize the connection by simply logging into the Campaign Monitor account associated with your browser. Just click on '**Authorize Campaign Monitor**' as shown in the attachment below: ![](https://help.erathos.com/rails/active_storage/blobs/redirect/eyJfcmFpbHMiOnsibWVzc2FnZSI6IkJBaHBlQT09IiwiZXhwIjpudWxsLCJwdXIiOiJibG9iX2lkIn19--df233ae4f9745600da59c688e44c4c131b483634/campaign%20monitor.png) Don't forget to click on **Save and close** to advance to the next steps of the integration. With this connection created you can seemlessly move your Campaign Monitor data to your BigQuery, Redshift or Postgres data-warehouse. ## What endpoints can I access with the Erathos platform? * clients * lists * listsdetails * liststats * listcustomfields * activesubscribers * unconfirmedsubscribers * segments * suppressionlist * tags * sentcampaigns * campaign\_opens * campaign\_clicks * scheduledcampaigns * journeys * journeysummary * emailrecipients * emailopens * emailclicks * emailbounces * emailunsubscribes * unsubscribedsubscribers * bouncedsubscribers * deletedsubscribers * campaign\_bounces * campaign\_recipients * campaign\_unsubscribes * campaign\_summary # ClickUp Find out how to connect Clickup to your data warehouse effortlessly. ## Using the Erathos platform: When selecting ClickUp as a new connector on the Erathos platform, you will need to authorize the connection by simply logging into the ClickUp account associated with your browser. Just click on '**Authorize ClickUp**' as shown in the attachment below: ![](https://help.erathos.com/rails/active_storage/blobs/redirect/eyJfcmFpbHMiOnsibWVzc2FnZSI6IkJBaHBlUT09IiwiZXhwIjpudWxsLCJwdXIiOiJibG9iX2lkIn19--f9f10b84239f62a850ddefc804cf41146c2ef41c/clickup.png) Don't forget to click on **Save and close** to advance to the next steps of the integration. With this connection created you can seemlessly move your ClickUp data to your BigQuery, Redshift or Postgres data-warehouse. ## What endpoints can I access with the Erathos platform? * teams * spaces * folders * lists * list\_members * goals * goal\_folders * time\_tracking * tasks * task\_members * task\_time\_status # Cloud Chat (CloudHumans) Connect your Cloud Chat Data Extract API to your data warehouse. Sync tickets, delivery events, and metrics to BigQuery, Redshift, Postgres, Databricks, and more. ## Using the Erathos platform When selecting Cloud Chat Data Extract API as a new connector on the Erathos platform, you will need to name your connection and fill in the following form: * **API Access Token** — your Cloud Chat API access token, used to authenticate all requests to the Cloud Chat Data Extract API With this connection created you can seamlessly move your Cloud Chat data to your BigQuery, Redshift or Postgres data warehouse. ### How to find my token? To generate an API access token, log into your Cloud Chat platform and navigate to the **Settings → Account → API** (or **Integrations**) section. Locate the **API access tokens** area and click **Generate new token** to create a credential for the data extract API. Copy the generated token and paste it into the **API Access Token** field on the Erathos platform. Once pasted, click **Save and close** to complete the setup and start syncing your Cloud Chat data. ## Endpoints and fields ### base\_ticket\_metrics Sync type availability: Full and incremental refresh [Cursor](https://docs.erathos.com/platform/connections/sync-types#understanding-cursors): `createdAt` | Field | Type | Cursor | | ---------------------- | --------- | ------ | | ticketId | integer | | | displayTicketId | integer | | | inboxId | integer | | | accountId | integer | | | accountName | text | | | ticketStatus | text | | | teamName | text | | | ticketPriorityName | text | | | ticketType | text | | | inboxName | text | | | ticketTitle | text | | | channel | text | | | tags | text | | | createdAt | timestamp | ✓ | | firstReplyAt | timestamp | | | firstReplyTime | float | | | resolvedAt | timestamp | | | totalResolutionTimeMin | float | | | agentId | integer | | | ticketOwner | text | | | ticketOwnerEmail | text | | | contactId | integer | | | contactName | text | | | contactEmail | text | | | contactPhone | text | | | campaignId | integer | | | proactivelyInitiated | boolean | | ### ticket\_metrics\_with\_agent\_information Sync type availability: Full and incremental refresh [Cursor](https://docs.erathos.com/platform/connections/sync-types#understanding-cursors): `createdAt` | Field | Type | Cursor | | ---------------------------- | --------- | ------ | | ticketId | integer | | | displayTicketId | integer | | | inboxId | integer | | | accountId | integer | | | accountName | text | | | ticketStatus | text | | | teamName | text | | | ticketPriorityName | text | | | ticketType | text | | | inboxName | text | | | ticketTitle | text | | | channel | text | | | tags | text | | | createdAt | timestamp | ✓ | | firstReplyAt | timestamp | | | firstReplyTime | float | | | resolvedAt | timestamp | | | totalResolutionTimeMin | float | | | agentId | integer | | | ticketOwner | text | | | ticketOwnerEmail | text | | | contactId | integer | | | contactName | text | | | contactEmail | text | | | contactPhone | text | | | campaignId | integer | | | proactivelyInitiated | boolean | | | ticketLink | text | | | agentOnResolutionId | integer | | | agentOnResolutionName | text | | | agentOnResolutionEmail | text | | | firstAgentReplyId | integer | | | firstAgentReplyName | text | | | firstAgentReplyEmail | text | | | firstAgentAssignmentTime | timestamp | | | firstAgentFirstReplyTime | timestamp | | | firstAgentReplyTimeMin | float | | | firstAgentResolutionTimeMin | float | | | csatScore | float | | | csatFeedback | text | | | contactCustomFields | json | | | conversationCustomFields | json | | | conversationAdditionalFields | json | | ### ticket\_summary Sync type availability: Full-refresh | Field | Type | | --------------- | ------- | | ticketId | integer | | displayTicketId | integer | | ticketLink | text | | summary | text | ### campaign\_delivery\_events Sync type availability: Full and incremental refresh [Cursor](https://docs.erathos.com/platform/connections/sync-types#understanding-cursors): `updatedAt` | Field | Type | Cursor | | ------------------ | --------- | ------ | | id | integer | | | campaignId | integer | | | campaignTitle | text | | | audience | text | | | contactId | integer | | | contactName | text | | | contactEmail | text | | | contactPhoneNumber | text | | | ticketId | integer | | | displayTicketId | text | | | messageSent | boolean | | | sentAt | timestamp | | | messageReceived | boolean | | | receivedAt | timestamp | | | messageRead | boolean | | | readAt | timestamp | | | messageReplied | boolean | | | repliedAt | timestamp | | | error | text | | | createdAt | timestamp | | | updatedAt | timestamp | ✓ | ### single\_contact\_delivery\_events Sync type availability: Full and incremental refresh [Cursor](https://docs.erathos.com/platform/connections/sync-types#understanding-cursors): `updatedAt` | Field | Type | Cursor | | ------------------ | --------- | ------ | | id | integer | | | contactId | integer | | | contactName | text | | | contactEmail | text | | | contactPhoneNumber | text | | | ticketId | integer | | | displayTicketId | text | | | messageSent | boolean | | | sentAt | timestamp | | | messageReceived | boolean | | | receivedAt | timestamp | | | messageRead | boolean | | | readAt | timestamp | | | messageReplied | boolean | | | repliedAt | timestamp | | | error | text | | | createdAt | timestamp | | | updatedAt | timestamp | ✓ | ## Entity Relationships ```mermaid erDiagram ticket_summary ||--o{ base_ticket_metrics : "ticketId = ticketId" ticket_summary ||--o{ ticket_metrics_with_agent_information : "ticketId = ticketId" ticket_summary ||--o{ campaign_delivery_events : "ticketId = ticketId" ticket_summary ||--o{ single_contact_delivery_events : "ticketId = ticketId" ticket_summary { int ticketId PK } base_ticket_metrics { int ticketId PK } ticket_metrics_with_agent_information { int ticketId PK } campaign_delivery_events { int id PK } single_contact_delivery_events { int id PK } ``` # Conta Azul Find out how to connect Conta Azul to your data warehouse effortlessly. ## Using the Erathos platform: When selecting Conta Azul as a new connector on the Erathos platform, you will need to authorize the connection by simply logging into the Conta Azul account associated with your browser. Just click on '**Authorize Conta Azul**' as shown in the attachment below: ![](https://help.erathos.com/rails/active_storage/blobs/redirect/eyJfcmFpbHMiOnsibWVzc2FnZSI6IkJBaHBlZz09IiwiZXhwIjpudWxsLCJwdXIiOiJibG9iX2lkIn19--0e493bcd146f8d71cc97f9eb4cc69c9fc939a9bc/conta%20azul.png) Don't forget to click on **Save and close** to advance to the next steps of the integration. With this connection created you can seemlessly move your Conta Azul data to your BigQuery, Redshift or Postgres data-warehouse. ## What information can I bring to my data-warehouse with the Erathos platform? * products * services * sales * sale\_items * customers * suppliers * plans * Finance # Convenia Find out how to connect Convenia to your data warehouse effortlessly. ## Using the Erathos platform When selecting Convenia as a new connector on the Erathos platform, you will need to name your connection and fill in the following form: ![](https://help.erathos.com/rails/active_storage/blobs/redirect/eyJfcmFpbHMiOnsibWVzc2FnZSI6IkJBaHBBWkU9IiwiZXhwIjpudWxsLCJwdXIiOiJibG9iX2lkIn19--cecf316729ef7c4df3dc35a6bfaf28974dd1d78f/Untitled%20\(63\).png) ## **How to find your token?** 1. Click on your profile picture (or inicials) and select **Settings**. 2. Click on **API**. 3. Select the **Add new token** option. ![](https://help.erathos.com/rails/active_storage/blobs/redirect/eyJfcmFpbHMiOnsibWVzc2FnZSI6IkJBaHBBWk09IiwiZXhwIjpudWxsLCJwdXIiOiJibG9iX2lkIn19--419fe9f08d0873fe2780fb29a7b4f27ad72373b6/image%20\(5\).png) 1. Name the token ![](https://help.erathos.com/rails/active_storage/blobs/redirect/eyJfcmFpbHMiOnsibWVzc2FnZSI6IkJBaHBBWlE9IiwiZXhwIjpudWxsLCJwdXIiOiJibG9iX2lkIn19--c3506a6780f453c4c231fbfd1651965781f3c7fe/image%20\(6\).png) 2. Select the permissions and level os access to information of the token you wish to create.(they must be selected in the endpoint category that is beign used) ![](https://help.erathos.com/rails/active_storage/blobs/redirect/eyJfcmFpbHMiOnsibWVzc2FnZSI6IkJBaHBBWlU9IiwiZXhwIjpudWxsLCJwdXIiOiJibG9iX2lkIn19--0db1f079dfa8ebda8f2758122c0ef9989ba7a412/image%20\(7\).png) 3. Click on add to save the token and it will be available to use! Now paste the token value in the Token field in the Erathos platform. Don't forget to click on **Save and close** to advance to the next steps of the integration. With this connection created you can seemlessly move your Convenia data to your BigQuery, Redshift or Postgres data-warehouse. ## What endpoints can I access with the Erathos platform? * colaboradores * historico\_salarial * ferias\_solicitadas * ferias\_periodos * colaboradores\_alteracoes * colaboradores\_faltas * colaboradores\_dependentes * colaboradores\_desligados * ferias\_coletivas * departamentos * centro\_custo * cargos * folhas\_de\_pagamentos * etnias * nacionalidades * vinculos\_empregaticios * estado\_civil * escolaridade * conta\_bancaria * bancos * estados * cidades * tipos\_de\_desligamento * tipos\_aviso\_previos * identidade\_genero * relacionamento\_contato\_emergencia # CustomerX Find out how to connect CustomerX to your data warehouse effortlessly. ## Using Erathos platform When selecting CustomerX as a new connector on the Erathos platform, you will need to name your connection and fill in the following form:
## How to find my API Token? Each user has a unique `api_token`, which can be found in the system registration at: * **Top right menu** → **User** * **View Profile** * **API Token field**
For further information check out [CustomerX documentation](https://doc.api.customerx.com.br/#intro). ## What endpoints can I access with Erathos platform? | Endpoints | | --------- | | clients | | csat | | tasks | # Delighted Find out how to connect Delighted to your data warehouse effortlessly. ## Using the Erathos platform When selecting Delighted as a new connector on the Erathos platform, you will need to name your connection and fill in the following form: ![](https://help.erathos.com/rails/active_storage/blobs/redirect/eyJfcmFpbHMiOnsibWVzc2FnZSI6IkJBaHBldz09IiwiZXhwIjpudWxsLCJwdXIiOiJibG9iX2lkIn19--f3b91fa6880960538055af6b358be13203a008e5/delighted.png) ## Como encontrar o User API Token no Delighted? To find your project's API token, head to **Integrations >API** Don't forget that limited users can't view the API token and each project has it own key. # Facebook Ads Find out how to connect Facebook Ads to your data warehouse effortlessly. ## Using the Erathos platform: When selecting Facebook Ads as a new connector on the Erathos platform, you will need to authorize the connection by simply logging into the Facebook Ads account associated with your browser. Just click on '**Authorize Facebook Ads**' as shown in the attachment below: ![](https://help.erathos.com/rails/active_storage/blobs/redirect/eyJfcmFpbHMiOnsibWVzc2FnZSI6IkJBaHBmQT09IiwiZXhwIjpudWxsLCJwdXIiOiJibG9iX2lkIn19--27b4de2a7b23b1a3f1ef43d92507e904a0113362/facebook%20ads.png) Don't forget to click on **Save and close** to advance to the next steps of the integration. With this connection created you can seemlessly move your Facebook Ads data to your BigQuery, Redshift or Postgres data-warehouse. ## What endpoints can I access with the Erathos platform? * adcampaigns * adstudies * adsets * ads * adcreatives * adimages * advideos * custom\_audiences * users * insights\_canvas\_action * insights\_reaction\_action * insights\_device\_action * insights\_product\_action * insights\_delivery\_purchase\_roas * insights\_carousel\_card\_action * insights\_video\_view\_type\_action * insights\_campaigns * insights\_delivery\_platform\_device * insights\_ad * insights\_adset * insights\_all\_levels * insights\_delivery\_platform * insights\_video\_sound\_action * insights\_age\_gender\_demographics * insights\_gender\_demographics * insights\_region\_demographics * insights\_dma\_region\_demographics * insights\_country\_demographics * insights\_age\_demographics * insights\_delivery\_device # Feedz ### Using the Erathos platform When selecting Feedz as a new connector on the Erathos platform, you will need to name your connection and fill in the following form: * **Token** — your Feedz API v2 integration key, used to authenticate all requests to the Feedz API With this connection created you can seamlessly move your Feedz data to your BigQuery, Redshift or Postgres data warehouse. ### How to find my token? To generate your Feedz API token, you must be a **System Administrator** on your Feedz account. Navigate to **Settings → Integrations → API Integration Key v2** and generate a new key. Once the token is generated, copy it and paste it into the **Token** field on the Erathos platform. Then click **Save and close** to complete the setup. Note: if you need to test the integration before connecting to production data, Feedz provides a Sandbox environment at `sandbox.feedz.dev` — request access through your Feedz account manager. ## Endpoints and fields ### employees Sync type availability: Full-refresh | Field | Type | | ---------------- | --------- | | employeeId | text | | name | text | | full\_name | text | | email | text | | cpf | text | | admission\_at | timestamp | | birth\_at | timestamp | | status | text | | department | text | | job\_description | text | | direct\_manager | text | | company | text | | branch | text | | role | text | | origin | text | | team | text | | groups | text | ### departments Sync type availability: Full-refresh | Field | Type | | ----- | ---- | | id | text | | name | text | ### branches Sync type availability: Full-refresh | Field | Type | | ----- | ---- | | id | text | | name | text | ### profile\_job\_descriptions Sync type availability: Full-refresh | Field | Type | | -------------- | ---- | | id | text | | title | text | | description | text | | id\_job\_group | text | ### profile\_job\_groups Sync type availability: Full-refresh | Field | Type | | ----------- | --------- | | id | text | | title | text | | description | text | | idCompany | text | | createdAt | timestamp | | updatedAt | timestamp | ### turnovers Sync type availability: Full-refresh | Field | Type | | --------------------- | --------- | | id | text | | reason | text | | type | text | | department | text | | last\_day\_working | timestamp | | profile.id | text | | profile.name | text | | profile.email | text | | profile.dt\_admission | timestamp | | profile.status | text | ### digital\_admission Sync type availability: Full-refresh | Field | Type | | ------------------- | --------- | | id | text | | name | text | | email | text | | deadline\_at | timestamp | | created\_at | timestamp | | updated\_at | timestamp | | profile\_department | text | | profile\_job | text | | status | text | ### celebrations Sync type availability: Full and incremental refresh [Cursor](/platform/connections/sync-types#understanding-cursors): `dt_create` | Field | Type | Cursor | | ----------------- | --------- | ------ | | id | text | | | id\_profile\_from | text | | | id\_profile\_to | text | | | comment | text | | | dt\_create | timestamp | ✓ | ### mood Sync type availability: Full and incremental refresh [Cursor](/platform/connections/sync-types#understanding-cursors): `date` | Field | Type | Cursor | | ----------- | ----- | ------ | | mood | text | | | description | text | | | department | text | | | branch | text | | | name | text | | | average | float | | | date | date | ✓ | ### objectives Sync type availability: Full-refresh | Field | Type | | ------------------ | ----- | | id | text | | id\_parent | text | | id\_owner | text | | id\_company | text | | id\_department | text | | objective | text | | percentage\_status | float | ### complete\_survey Sync type availability: Full-refresh Parent of [`complete_survey_answers`](#complete_survey_answers) | Field | Type | | -------------------- | ---- | | id | text | | id\_company | text | | id\_profile\_created | text | | title | text | ### complete\_survey\_answers Sync type availability: Full-refresh Child of [`complete_survey`](#complete_survey) | Field | Type | | ----------------------- | ---- | | id | text | | id\_company | text | | id\_survey | text | | id\_question | text | | id\_profile | text | | id\_profile\_department | text | ### fast\_survey Sync type availability: Full-refresh Parent of [`fast_survey_answers`](#fast_survey_answers) | Field | Type | | -------------------- | ---- | | id | text | | id\_company | text | | id\_profile\_created | text | | question | text | ### fast\_survey\_answers Sync type availability: Full-refresh Child of [`fast_survey`](#fast_survey) | Field | Type | | ---------------- | ----- | | id | text | | id\_fast\_survey | text | | id\_profile | text | | score | float | | answer | text | | answer\_option | text | ### pulse Sync type availability: Full-refresh | Field | Type | | --------------- | ---- | | id | text | | id\_company | text | | id\_profile | text | | id\_departments | text | | name | text | | description | text | ### enps Sync type availability: Full-refresh | Field | Type | | ----------- | --------- | | dt\_create | timestamp | | dt\_final | timestamp | | departments | text | | detractors | integer | | passives | integer | | promoters | integer | ### notifications Sync type availability: Full and incremental refresh [Cursor:](/platform/connections/sync-types#understanding-cursors) `dt_created` | Field | Type | Cursor | | --------------- | --------- | ------ | | id | text | | | link | text | | | custom\_message | text | | | dt\_created | timestamp | ✓ | | message | text | | ## Entity Relationships ```mermaid erDiagram complete_survey ||--o{ complete_survey_answers : "id = id_survey" fast_survey ||--o{ fast_survey_answers : "id = id_fast_survey" profile_job_groups ||--o{ profile_job_descriptions : "id = id_job_group" departments ||--o{ objectives : "id = id_department" departments ||--o{ complete_survey_answers : "id = id_profile_department" departments ||--o{ pulse : "id = id_departments" employees { string employeeId PK } departments { string id PK } branches { string id PK } profile_job_descriptions { string id PK } profile_job_groups { string id PK } turnovers { string id PK } digital_admission { string id PK } celebrations { string id PK } mood { string mood } objectives { string id PK } complete_survey { string id PK } complete_survey_answers { string id PK } fast_survey { string id PK } fast_survey_answers { string id PK } pulse { string id PK } enps { timestamp dt_create } notifications { string id PK } ``` # FreshChat Find out how to connect FreshChat to your data warehouse effortlessly. ## Using the Erathos platform When selecting FreshChat as a new connector on the Erathos platform, you will need to name your connection and fill in the following form: ![](https://help.erathos.com/rails/active_storage/blobs/redirect/eyJfcmFpbHMiOnsibWVzc2FnZSI6IkJBaHBmUT09IiwiZXhwIjpudWxsLCJwdXIiOiJibG9iX2lkIn19--b0380f1258d395899e6874753c8384235b5554ad/freshchat.png) ## How to find my FreshChat Domain URL? For independent Freshchat accounts the URL to access product resources through API requests usually follows the format below: **https\://\.freshchat.com/v2/\** Example: ## How to find my FreshChat API Token? 1. Access the **Administrador** tab 2. Click on **configurate** 3. Enter the **API Tokens** page 4. Click on **Generate Token** 5. The authentication server exhibits the access token (API Token) For integrated FreshChat accounts, available as part of a Freshsales Suite account, the URL will follow this format: **** ## To obtain the API Token: 1. Go to **Settings** 2. Select **Administrator Settings** 3. Then access **Website and API Tracking** 4. Enter the **API Configurations** page 5. Go to the **API Details for chat** section 6. In the **Your API Key** field, the API Token will be exhibited. With this connection created you can seemlessly move your FreshChat data to your BigQuery, Redshift or Postgres data-warehouse. ## What end´points can I access with the Erathos platform? * users * groups * channels * roles * agents * user\_conversations * conversations * messages # Freshdesk Find out how to connect Freshdesk to your data warehouse effortlessly. ## Using the Erathos platform When selecting Freshdesk as a new connector on the Erathos platform, you will need to name your connection and fill in the following form: ![](https://help.erathos.com/rails/active_storage/blobs/redirect/eyJfcmFpbHMiOnsibWVzc2FnZSI6IkJBaHBBWlk9IiwiZXhwIjpudWxsLCJwdXIiOiJibG9iX2lkIn19--c4ec1e88ea320f747fe866d9392c04686d543f01/Untitled%20\(64\).png) ## How to find my Freshdesk API Token? 1. Log in to your account 2. Click on your profile picture in the upper right corner and select Profile settings as in the attachment below: ![](https://help.erathos.com/rails/active_storage/blobs/redirect/eyJfcmFpbHMiOnsibWVzc2FnZSI6IkJBaHBBWmM9IiwiZXhwIjpudWxsLCJwdXIiOiJibG9iX2lkIn19--05cb1b54f8843a524ddd542ccef372345bc038a6/Untitled%20\(65\).png) 3. On the right, click on **View API Key** and complete the captcha verification. ![](https://help.erathos.com/rails/active_storage/blobs/redirect/eyJfcmFpbHMiOnsibWVzc2FnZSI6IkJBaHBBWmc9IiwiZXhwIjpudWxsLCJwdXIiOiJibG9iX2lkIn19--6ebd1ea1a4d01ee72ff630aa67cc918e6765beef/Untitled%20\(66\).png) 4. Copy and paste the value exhibited in the Erathos platform API Token field. ## How to find my Freshdesk Domain URL? 1. Log in to your account 2. Access the apps icon in the bottom left ![](https://help.erathos.com/rails/active_storage/blobs/redirect/eyJfcmFpbHMiOnsibWVzc2FnZSI6IkJBaHBBWms9IiwiZXhwIjpudWxsLCJwdXIiOiJibG9iX2lkIn19--3599c89bd88a710d5b83141fdf720b9b4e61dc16/Untitled%20\(67\).png) 3. In the left side bar, your Domain URL will be displayed ![](https://help.erathos.com/rails/active_storage/blobs/redirect/eyJfcmFpbHMiOnsibWVzc2FnZSI6IkJBaHBBWm89IiwiZXhwIjpudWxsLCJwdXIiOiJibG9iX2lkIn19--f3f6e7257b40e975e275146aad9664bcdd60f224/Untitled%20\(68\).png) Now copy and paste the Domain URL found in the Domain URL field in the Erathos platfom. Don't forget to click on **Save and close** to advance to the next steps of the integration. With this connection created you can seemlessly move your Freshdesk data to your BigQuery, Redshift or Postgres data-warehouse. ## What endpoints can I access with the Erathos platform? * tickets * ticket\_forms * contacts * agents * roles * groups * group\_agents * companies * time\_entries * mailboxes * products # Gainsight Find out how to connect Gainsight to your data warehouse effortlessly. ## Using the Erathos platform When selecting Gainsight as a new connector on the Erathos platform, you will need to name your connection and fill in the following form: ![](https://help.erathos.com/rails/active_storage/blobs/redirect/eyJfcmFpbHMiOnsibWVzc2FnZSI6IkJBaHBBaHdCIiwiZXhwIjpudWxsLCJwdXIiOiJibG9iX2lkIn19--e6dea7c0330b5839c7163615b631b475e9cdf1be/gainsight%20form.png) ## How to find my API key? 1. Enable the app and navigate to the **Apps** page from the navigation bar. 2. Click on **Configure Next** to API Access. 3. Select the API key in the API details section. For additional documentation on the API, [*click here*](https://developers.northpass.com/)*.* Don't forget to copy and paste the key on the Erathos platform API key field and click on **Save and close**. With this connection created you can seemlessly move your Gainsight data to your BigQuery, Redshift or Postgres data-warehouse. ## What endpoints can I access with the Erathos platform? * accounts * engagement\_events * custom\_events * engagement\_view\_events * feature\_match\_events * form\_submit\_events * identify\_events * lead\_events * page\_view\_events * segment\_match\_events * session\_events * features * segments * survey\_responses * users # Github ### Using the Erathos platform When selecting GitHub as a new connector on the Erathos platform, you will need to name your connection and fill in the following form: * **Token** — your GitHub Personal Access Token used to authenticate API requests * **Org** — the GitHub organization name whose repositories and members you want to sync With this connection created you can seamlessly move your GitHub data to your BigQuery, Redshift or Postgres data warehouse. ### How to find my token? You can generate a Personal Access Token by navigating to **Settings > Developer settings > Personal access tokens > Tokens (classic)** inside your GitHub account. Click **Generate new token**, give it a descriptive name, set the desired expiration, and select the scopes your integration requires — at minimum `repo` (to read repository data) and `read:org` (to read organization members). Once generated, copy the token value immediately — GitHub will not show it again. Paste the value into the Erathos platform **Token** field. For the **Org** field, enter your organization's name exactly as it appears in your GitHub organization URL (e.g. `my-company` from `github.com/my-company`). Don't forget to click on **Save and close** to advance to the next steps of the integration. ### What endpoints can I access with the Erathos platform? * repositories * members * issues * pull\_requests * commits # Google Ads Find out how to connect Google Ads to your data warehouse effortlessly. ## Using the Erathos platform: When selecting Google Ads as a new connector on the Erathos platform, you will need to authorize the connection by simply logging into the Google Ads account associated with your browser. Just click on '**Authorize Google Ads**'. Don't forget to click on **Save and close** to advance to the next steps of the integration. With this connection created you can seemlessly move your Google Ads data to your BigQuery, Redshift or Postgres data-warehouse. ## What endpoints have metrics information? In the Google Ads connection, all jobs with the `_stats` suffix contain performance metrics such as **CTA, CTR, spend, CPA**, and others. These jobs are organized according to the Google Ads hierarchy, including levels such as **ad**, **ad group**, and **campaign**. **Examples:** * `campaign` * `campaign_stats` * `adgroup` * `adgroup_stats` * `ad_group_ad` * `ad_group_ad_stats` # Hotmart Find out how to connect Hotmart to your data warehouse effortlessly. ## Using the Erathos platform When selecting Hotmart as a new connector on the Erathos platform, you will need to name your connection and fill in the following form:
## How to generate Hotmart credentials? * On Hotmart platform, go to **Tools >** [**Developer Credentials**](https://app-vlc.hotmart.com/tools/credentials) * Click the **Create Credential** button and give your credential a name. This name is just to better organize your credentials. * If you are going to use this Credential for our test environment **sandbox**, check the sandbox option in the *Type* field. If the Credential is for the production environment, just leave the box blank and click the Confirm button. Once created, you won't be able to change the type of a credential, but you must create a new one with the desired type. * If everything goes well, three pieces of information will be generated: `client_id`, `client_secret` and `token` of the Basic type. \ For further support, go to the [hotmart documentation](https://developers.hotmart.com/docs/en/start/app-auth). ## What endpoints can I access with Erathos platform? | Endpoints | | ------------------- | | coupons | | modules | | pages | | price\_details | | products | | sales\_comission | | sales\_history | | sales\_participants | | subscriptions | | user\_progress | | users | # HubSpot Find out how to connect HubSpot to your data warehouse effortlessly. ## Using the Erathos platform: ### Creating a data pipeline with HubSpot data #### Connect to HubSpot * Using Erathos click in **explore** **data sources** or in connectors on the left side menu (the second icon).
* Select HubSpot connector and name your connection
When selecting HubSpot as a new connector on the Erathos platform, you will need to authorize the connection by simply logging into the HubSpot account associated with your browser. Just click on '**Authorize integration**' as shown in the attachment below:
* Select the proper HubSpot account
* Connect app
Don't forget to click on **Save and test** to advance to the next steps of the integration.
#### Manage Jobs With this connection created you can seemlessly move your HubSpot data to your BigQuery, Redshift or Postgres data-warehouse. * Click in manage jobs to select endpoints and schedule pipeline runs. * Name your schema * Your schema name is where all the tables will be created (you won't be able to change this later)
* Activate jobs * Select a [sync frequency](https://docs.erathos.com/platform/connections/sync-schedule#frequency) * Select a [sync type](https://docs.erathos.com/platform/connections/sync-types) * Select a [sync time](https://docs.erathos.com/platform/connections/sync-schedule#frequency) * Select fields (optional) * Click "Open" beside the endpoint name to see all the fields available * If you don't to this, all the fields will be selected automatically.
* All the tables in your data warehouse will be the same as the endpoint name #### Create a destination * Click in settings on the left side menu * Go to destination in the workspace menu * Select the chosen destination and fill the necessary information to connect * [BigQuery self hosted](https://docs.erathos.com/destinations/bigquery) * [BigQuery hosted by Erathos](/destinations/what-is-a-destination/bigquery/hosted-by-erathos) (in case that you don't have a data warehouse yet) * [Databricks](https://docs.erathos.com/destinations/databricks) * [PostgreSQL](https://docs.erathos.com/destinations/postgresql) * [Redshift](https://docs.erathos.com/destinations/redshift) * [S3 Iceberg](https://docs.erathos.com/destinations/s3-iceberg) {% hint style="warning" %} If you use 'bulk actions' to change properties in HubSpot, we recommend manually executing a Full Refresh afterward. The HubSpot API does not properly update the 'updated\_at' field when bulk actions are performed, which can lead to inconsistencies in the API response." {% endhint %} ### Disconnect the app * Login and click on the HubSpot connection
* Go to the settings tab * Delete connection
**Note:** If you delete the connection you will still have access to the data in your destination, but it will not be up-to-date anymore. * You can also uninstall the app in HubSpot, please check the "Uninstall an app" topic on the following documentation: [Uninstall an app](https://knowledge.hubspot.com/integrations/connect-apps-to-hubspot?_ga=2.94035293.1315053923.1752660941-1718272043.1752660941#uninstall-an-app) ## What endpoints can I access with the Erathos platform? * communications * deal\_history * contacts\_tickets\_associations * contacts\_deals\_associations * feedback\_submissions * line\_items * products * quotes * goal\_targets * calls * emails * meetings * notes * postal\_mail * tasks * owners * deals\_pipelines * tickets\_pipelines * companies * deals\_tickets\_associations * deals * contacts * tickets * companies\_tasks\_associations * companies\_calls\_associations * deals\_tasks\_associations * deals\_calls\_associations * companies\_contacts\_associations * companies\_deals\_associations * companies\_tickets\_associations * contacts\_meetings\_associations * contacts\_calls\_associations * contacts\_emails\_associations * contacts\_communications\_associations * tickets\_meetings\_associations * tickets\_calls\_associations * tickets\_emails\_associations * tickets\_communications\_associations * analytics\_reports\_sources * analytics\_reports\_sources\_breakdowns * marketing\_emails * form\_submission # Intelipost ### Using the Erathos platform When selecting Intelipost as a new connector on the Erathos platform, you will need to name your connection and fill in the following form: * **API Key** — Your Intelipost API key, used to authenticate all requests to the API With this connection created you can seamlessly move your Intelipost data to your BigQuery, Redshift or Postgres data warehouse. ### How to find my token? You can find your API Key inside the Intelipost platform by navigating to **Settings → Integrations → API Keys** in your account. Now, paste the value in the Erathos platform API Key field. Don't forget to click on **Save and close** to advance to the next steps of the integration. ### What endpoints can I access with the Erathos platform? * delivery\_methods * shipment\_order # Intercom Find out how to connect Intercom to your data warehouse effortlessly. ## Using the Erathos platform When selecting Intercom as a new connector on the Erathos platform, you will need to name your connection and fill in the following form: ![](https://help.erathos.com/rails/active_storage/blobs/redirect/eyJfcmFpbHMiOnsibWVzc2FnZSI6IkJBaHBBWnM9IiwiZXhwIjpudWxsLCJwdXIiOiJibG9iX2lkIn19--bfe41c9b852f16ec78e0168d84476a096eda137a/intercom.png) ## How to find my token? You can find your Access Token following this path **Configure > Authentication** inside Intercom's Developer Hub. ![](https://help.erathos.com/rails/active_storage/blobs/redirect/eyJfcmFpbHMiOnsibWVzc2FnZSI6IkJBaHBBWnc9IiwiZXhwIjpudWxsLCJwdXIiOiJibG9iX2lkIn19--d49970fbf8a79a165b7eadcfe9ae4fd096c314c0/intercom%202.png) Now, paste the value in the Erathos platform Token field. Don't forget to click on **Save and close** to advance to the next steps of the integration. With this connection created you can seemlessly move your Intercom data to your BigQuery, Redshift or Postgres data-warehouse. ## What endpoints can I access with the Erathos platform? * company\_attached\_contacts * help\_centers * segments * companies * admins * articles * contacts * notes * conversations * collections * subscription\_types * tags * teams * tickets * activity\_logs # Jira Find out how to connect Jira to your data warehouse effortlessly. ## Using the Erathos platform When selecting Jira as a new connector on the Erathos platform, you will need to name your connection and fill in the following form: ![](https://help.erathos.com/rails/active_storage/blobs/redirect/eyJfcmFpbHMiOnsibWVzc2FnZSI6IkJBaHBBaWdCIiwiZXhwIjpudWxsLCJwdXIiOiJibG9iX2lkIn19--203c03e850892fd701d40839627fb2d5ebe706d6/jira%20form.png) ### How to find my Domain URL? 1. Access Jira Software on your browser 2. Copy the URL displayed on your search bar. You may have to click on the bar to see the complete URL. 3. If you're on the dashboard page, the URL will be everything up until **/secure/Dashboard.jspa** 4. If you're observing an isse, the URL will be everything up until **/browse** 5. If you're accessing a project or board, the URL will be everything up until **project** or **/secure/RapidBoard.jspa** ⚠️ In case your URL looks something like [mycompany.atlassian.net](http://mycompany.atlassian.net), that means you'reusing Jira Cloud, therefore you must download the Jira Cloud app. ### How to generate an API Token? 1. Access . 2. Click on Create API Token. 3. A text box will appear, in which you must insert a short and memorable name for the token you wish to create. 4. Copy the new token and paste it on the User API Token field in the Erathos platform. ![](https://help.erathos.com/rails/active_storage/blobs/redirect/eyJfcmFpbHMiOnsibWVzc2FnZSI6IkJBaHBBaWtCIiwiZXhwIjpudWxsLCJwdXIiOiJibG9iX2lkIn19--eb23fe1bd1b02dde1ff42916a659ad3062f07b66/Untitled.png) Don't forget to click on **Save and close** to proceed to the next steps of the integration! With this connection created you can seemlessly move your Jira data to your BigQuery, Redshift or Postgres data-warehouse. ## What endpoints can I access with the Erathos platform? * projects * project\_details * project\_status * project\_categories * users * user\_groups * groups * issue\_worklogs * dashboards * issues * issue\_subtasks * issue\_comments * issue\_components * issue\_links * issue\_changelogs * events # LangSmith ### Using the Erathos platform When selecting LangSmith as a new connector on the Erathos platform, you will need to name your connection and fill in the following form: * **Token** — Your LangSmith personal API key, used to authenticate all requests to the LangSmith API. ### How to find my token? You can find your API key by navigating to **Settings → API Keys** inside the LangSmith platform at [smith.langchain.com](https://smith.langchain.com). Click **Create API Key**, give it a name, and copy the generated value. Now, paste the value in the Erathos platform Token field. Don't forget to click on **Save and close** to advance to the next steps of the integration. With this connection created you can seamlessly move your LangSmith data to your BigQuery, Redshift or Postgres data warehouse. ### What endpoints can I access with the Erathos platform? * sessions * datasets * examples * feedback * repos * runs # Linear Find out how to connect Linear to your data warehouse effortlessly. ### Using the Erathos platform When selecting Linear as a new connector on the Erathos platform, you will need to name your connection and fill in the following form: * **Token** — your Linear Personal API Key With this connection created you can seamlessly move your Linear data to your BigQuery, Redshift or Postgres data warehouse. ### How to find my token? You can generate a Personal API Key by navigating to **Settings > API > Personal API keys** inside your Linear workspace. Click **Create key**, give it a name, and copy the generated key. Paste the value into the Erathos platform **Token** field. Don't forget to click on **Save and close** to advance to the next steps of the integration. ### What endpoints can I access with the Erathos platform? * issues * teams * users * projects * workflow\_states * cycles * issue\_labels * comments # Linkedin Ads Find out how to connect Linkedin Ads to your data warehouse effortlessly. ## Using the Erathos platform: When selecting Linkedin Ads as a new connector on the Erathos platform, you will need to authorize the connection by simply logging into the Linkedin Ads account associated with your browser. Just click on '**Authorize Linkedin Ads**' as shown in the attachment below: ![](https://help.erathos.com/rails/active_storage/blobs/redirect/eyJfcmFpbHMiOnsibWVzc2FnZSI6IkJBaHBBWHM9IiwiZXhwIjpudWxsLCJwdXIiOiJibG9iX2lkIn19--03b61f147d2457e9fef30895e903a6e38a52f0ad/linkedIn%20ads.png) Don't forget to click on **Save and close** to advance to the next steps of the integration. With this connection created you can seemlessly move your Linkedin Ads data to your BigQuery, Redshift or Postgres data-warehouse. ## What endpoints can I access with the Erathos platform? * ad\_accounts * account\_users * campaign\_groups * campaigns * creatives * organizations * industries * metrics\_campaign\_creative\_projection * metrics\_creative\_content\_projection * metrics\_member\_industry\_projection * metrics\_campaign\_conversion * metrics\_member\_company\_projection # MailChimp Find out how to connect MailChimp to your data warehouse effortlessly. ## Using the Erathos platform When selecting MailChimp as a new connector on the Erathos platform, you will need to name your connection and fill in the following form: ![](https://help.erathos.com/rails/active_storage/blobs/redirect/eyJfcmFpbHMiOnsibWVzc2FnZSI6IkJBaHBBWjA9IiwiZXhwIjpudWxsLCJwdXIiOiJibG9iX2lkIn19--4bc60617a84b66a50770da2a273c92eba3570aa8/mailchimp.png) ## How to find my MailChimp API Token? 1. Log in to your account 2. Click on your profile to expand the account pannel and select **Account settings**. 3. Click on the **Extras** menu and select **API Keys**. Copy an existent API key or click on Create a Key. Now paste the found value on the Erathos platform Token field. Don't forget to click on **Save and close** to advance to the next steps of the integration. With this connection created you can seemlessly move your MailChimpdata to your BigQuery, Redshift or Postgres data-warehouse. ## What endpoints can I access with the Erathos platform? * allowlists * exports * ip\_addresses * ip\_pools * inbound\_domains * mailbox\_routes * scheduled\_emails * denylisted\_emails * account\_senders * sender\_domains * subaccounts * tags * templates * tracking\_domains * senders * allowlisted\_emails # MailGun Find out how to connect MailGun to your data warehouse effortlessly. ## Using the Erathos platform When selecting MailGun as a new connector on the Erathos platform, you will need to name your connection and fill in the following form: ![](https://help.erathos.com/rails/active_storage/blobs/redirect/eyJfcmFpbHMiOnsibWVzc2FnZSI6IkJBaHBBaEFCIiwiZXhwIjpudWxsLCJwdXIiOiJibG9iX2lkIn19--3aba41ef72d78acc7ebb3a76a1794b465e3b8903/mailgun%20form.png) ## How to find my MailGun API Token? 1. Access the Mail Gun control panel 2. Click on Account Settings, located on the upper right corner of the page 3. Click on API Security ## How to find my MailGun Domain Name? 1. Access the Mail Gun controle panel 2. Then, on the **navigation panel to the left**, click on the option **Sending** to expand your suboption list 3. Click on the **Domains** suboption to view them Now paste the API Token and Domain Name values found on the Erathos platform form. Don't forget to click on **Save and close** to advance to the next steps of the integration. With this connection created you can seemlessly move your MailGun data to your BigQuery, Redshift or Postgres data-warehouse. ## What endpoints can I access with the Erathos platform? * ips * events * routes # MeetRox Find out how to connect MeetRox to your data warehouse effortlessly. ## How to find my API Key? 1. Log in to the [MeetRox platform](https://app.meetrox.ai/) and navigate to **Manage > Settings > API Keys** to generate your key. 2. Only users with **manager** permissions can generate an API key. ## What endpoints can I access with the Erathos platform? * calls * call\_details # MercadoLibre Find out how to connect MercadoLibre to your data warehouse effortlessly. ## Using the Erathos platform When selecting MercadoLibre as a new connector on the Erathos platform, you will need to authorize the connection by simply logging into the MercadoLibre account associated with your browser. Just click on '**Authorize MercadoLibre**' as shown in the attachment below:
Follow the steps in the pop-up window to confirm authorization. Don't forget to click on **Save and close** to advance to the next steps of the integration. With this connection created you can seemlessly move your MercadoLibre data to your [data warehouse](/destinations/what-is-a-destination). {% hint style="danger" %} You must be logged in as the **owner** of the MercadoLibre account. {% endhint %} ### What endpoints can I access with the Erathos platform? | MercadoLibre endpoints | | ---------------------- | | inventory\_stock | | items | | orders | {% hint style="info" %} You can suggest new endpoints and connectors [here](https://erathos.notion.site/1370250b751080bcbdc7de95225f6008?pvs=105). {% endhint %} # Mixpanel Find out how to connect Mixpanel to your data warehouse effortlessly. ## Using the Erathos platform When selecting Mixpanel as a new connector on the Erathos platform, you will need to name your connection and fill in the following form: ![](https://help.erathos.com/rails/active_storage/blobs/redirect/eyJfcmFpbHMiOnsibWVzc2FnZSI6IkJBaHBBYk09IiwiZXhwIjpudWxsLCJwdXIiOiJibG9iX2lkIn19--61f8d863be2fe3a2fa31321b917b9f15aed3837c/mixpanel.png) ## How to find my Password and Username credentials? To create a service account you must: 1. Access the Project Settings or Organization Settings page 2. Select the Service Account option 3. Copy the exhibited values (in this case **Password** can appear as **Secret**) ![](https://help.erathos.com/rails/active_storage/blobs/redirect/eyJfcmFpbHMiOnsibWVzc2FnZSI6IkJBaHBBYlU9IiwiZXhwIjpudWxsLCJwdXIiOiJibG9iX2lkIn19--1a19acaf351a4c0c9683e15146de73b936d7a12b/service%20account.png) ## How to find my Project ID credenctial? To find the project informations you must: 1. Enter the Organtization Settings page 2. Select the Projects option 3. Click on the project which you need the informations from ![](https://help.erathos.com/rails/active_storage/blobs/redirect/eyJfcmFpbHMiOnsibWVzc2FnZSI6IkJBaHBBYmM9IiwiZXhwIjpudWxsLCJwdXIiOiJibG9iX2lkIn19--e944a1e57a00ee88731f075d9a98d4e1330a500f/project%20ID.webp)Now paste the three credential values found on the Erathos platform form. Don't forget to click on **Save and close** to advance to the next steps of the integration. With this connection created you can seemlessly move your Mixpanel data to your BigQuery, Redshift or Postgres data-warehouse. ## What endpoints can I access with the Erathos platform? * export # Monday Find out how to connect Monday to your data warehouse effortlessly. ## Using the Erathos platform When selecting Monday as a new connector on the Erathos platform, you will need to name your connection and fill in the following form: ![](https://help.erathos.com/rails/active_storage/blobs/redirect/eyJfcmFpbHMiOnsibWVzc2FnZSI6IkJBaHBBaDRCIiwiZXhwIjpudWxsLCJwdXIiOiJibG9iX2lkIn19--4b51125ca63c7afed590a9b7fa8bf71c0836c34e/monday%20form.png) ## How to find my API Token? ### Through the Admin Tab: 1. Log in to your account 2. Click on your profile picture in the top right corner. 3. Select **Administration** > **Connections** > **API**. 4. Copy your personal token. **Warning**: you can always regenerate a new token, but doing so will cause any previous tokens to expire. ### Through the Developer tab: 1. Log in to your account 2. Click on your profile picture in the top right corner. 3. Select **Developers**. This will open the *Developer Center* in another tab. 4. Click **My Access Tokens** > **Show**. **Warning**: you can always regenerate a new token, but doing so will cause any previous tokens to expire. Don't forget to copy and paste the token on the Erathos platform Token field and click on **Save and close**. With this connection created you can seemlessly move your Monday data to your BigQuery, Redshift or Postgres data-warehouse. ## What endpoints can I access with the Erathos platform? * boards * activity\_logs * groups * items * folders * teams * users * workspaces * docs # Movidesk Find out how to connect Movidesk to your data warehouse effortlessly. ## Using the Erathos platform When selecting Movidesk as a new connector on the Erathos platform, you will need to name your connection and fill in the following form: ![](https://help.erathos.com/rails/active_storage/blobs/redirect/eyJfcmFpbHMiOnsibWVzc2FnZSI6IkJBaHBBaUFCIiwiZXhwIjpudWxsLCJwdXIiOiJibG9iX2lkIn19--b3e8de57b57309db451c4c4911bb94e92c7b6a6e/movidesk%20form.png) ## How to find my API Token? 1. Log in to your account; 2. Go to **Settings > Account > Parameters** 3. In the environment guide, click on **Generate new key** You can follow these steps as many times as you need, but keep in mind that by generating a new key all integrations that use the past key will stop. Don't forget to copy and paste the token on the Erathos platform Token field and click on **Save and close**. With this connection created you can seemlessly move your Movidesk data to your BigQuery, Redshift or Postgres data-warehouse. ## What information can I bring to my data-warehouse with the Erathos platform? * persons * tickets * timeAgreement * surveys\_questions * surveys\_responses * activities * timeAgreementConsumption * tickets\_past # Nomus ERP ### Using the Erathos platform When selecting Nomus ERP as a new connector on the Erathos platform, you will need to name your connection and fill in the following form: * **Empresa** — the company subdomain used in your Nomus ERP URL (e.g. `mycompany` from `mycompany.nomus.com.br`) * **API Key** — the REST integration key from your Nomus ERP general configuration screen With this connection created you can seamlessly move your Nomus ERP data to your BigQuery, Redshift or Postgres data warehouse. ### How to find my token? You can find your API Key inside Nomus ERP by navigating to **Configurações Gerais** (General Configuration). Look for the field labelled **chave-integração-rest** — this is the static REST integration key used to authenticate all API requests. Copy the value of **chave-integração-rest** and paste it into the **API Key** field on the Erathos platform. Don't forget to click on **Save and close** to advance to the next steps of the integration. ### What endpoints can I access with the Erathos platform? * pessoas * representantes * vendedores * clientes * produtos * familias\_produto * grupos\_produto * tipos\_produto * unidades\_medida * atributos\_produto * tabelas\_preco * pedidos * propostas * notas\_credito\_cliente * pedidos\_compra * solicitacoes * notas\_credito\_fornecedor * contas\_receber * contas\_pagar * boletos * recebimentos * pagamentos * condicoes\_pagamentos * formas\_pagamento * contas\_bancarias * tipos\_movimentacao * nfes * nfses * setor\_estoque * movimentacoes\_estoque * documentos\_estoque * ordens * apontamentos * empenhos * operacoes\_roteiro\_ordem * inventarios * atividades * centros\_trabalho * centros\_custo * recursos * causas\_problemas * componentes\_lista\_materiais * roteiros\_produto * processos * contratos\_servico * empresas * usuarios # Notion Connect your Notion workspace to your data warehouse. Sync pages, blocks, users, and comments to BigQuery, Redshift, Postgres, Databricks, and more. ## Using the Erathos platform When selecting Notion as a new connector on the Erathos platform, you will need to name your connection and fill in the following form: * **Token** — your Notion internal integration token, used to authenticate all requests to the Notion API With this connection created you can seamlessly move your Notion data to your BigQuery, Redshift or Postgres data warehouse. ### How to find my token? To generate a Notion integration token, go to and click **New integration**. Give it a name, select the workspace you want to connect, and click **Submit**. After creating the integration, copy the **Internal Integration Token** shown on the integration settings page. Then go to each Notion page or database you want to sync and add the integration under **Share → Invite**, granting it the appropriate access level. Paste the token into the **Token** field on the Erathos platform and click **Save and close** to complete the setup. ## Endpoints and fields ### users Sync type availability: Full-refresh | Field | Type | | ----------- | ---- | | id | text | | name | text | | type | text | | avatar\_url | text | ### pages Sync type availability: Full and incremental refresh [Cursor](https://docs.erathos.com/platform/connections/sync-types#understanding-cursors): `last_edited_time` Parent of [blocks](#blocks), [comments](#comments) | Field | Type | Cursor | | ------------------ | --------- | ------ | | id | text | | | created\_time | timestamp | | | last\_edited\_time | timestamp | ✓ | | archived | boolean | | | url | text | | | parent.type | text | | ### blocks Sync type availability: Full-refresh Child of [pages](#pages) | Field | Type | | ------------------ | --------- | | id | text | | type | text | | created\_time | timestamp | | last\_edited\_time | timestamp | | has\_children | boolean | | archived | boolean | ### comments Sync type availability: Full-refresh Child of [pages](#pages) | Field | Type | | ------------------ | --------- | | id | text | | discussion\_id | text | | created\_time | timestamp | | last\_edited\_time | timestamp | | created\_by.id | text | | parent.type | text | ## Entity Relationships ```mermaid erDiagram pages ||--o{ blocks : "id = page_id" pages ||--o{ comments : "id = page_id" users ||--o{ comments : "id = created_by.id" users { text id PK } pages { text id PK } blocks { text id PK } comments { text id PK } ``` # Nuvia API Connect your Nuvia API to your data warehouse. Sync conversations, contacts, campaigns, and knowledge data to BigQuery, Redshift, Postgres, Databricks, and more. ## Using the Erathos platform When selecting Nuvia API as a new connector on the Erathos platform, you will need to name your connection and fill in the following form: * **Token** — your Nuvia API bearer token used to authenticate API requests With this connection created you can seamlessly move your Nuvia API data to your BigQuery, Redshift or Postgres data warehouse. ### How to find my token? To obtain your Nuvia API token, log in to your Nuvia account and navigate to **Settings → Integrations → API Keys**. If you don't already have an API key, create a new one by clicking the appropriate button and copying the generated value. Paste the token into the **Token** field on the Erathos platform connection form. Click **Save and close** to complete setup. Your Nuvia API connection is now ready to sync data to your data warehouse. ## Endpoints and fields ### agents Sync type availability: Full-refresh | Field | Type | | ----------- | --------- | | id | integer | | name | text | | description | text | | model | text | | status | text | | createdAt | timestamp | | updatedAt | timestamp | ### campaigns Sync type availability: Full-refresh Parent of [campaign\_enrollments](#campaign_enrollments) | Field | Type | | --------- | --------- | | id | integer | | name | text | | status | text | | type | text | | createdAt | timestamp | | updatedAt | timestamp | ### campaign\_enrollments Sync type availability: Full-refresh Child of [campaigns](#campaigns) | Field | Type | | ---------- | --------- | | id | integer | | campaignId | integer | | contactId | integer | | status | text | | createdAt | timestamp | | updatedAt | timestamp | ### contacts Sync type availability: Full-refresh | Field | Type | | --------- | --------- | | id | integer | | name | text | | email | text | | phone | text | | status | text | | createdAt | timestamp | | updatedAt | timestamp | ### conversations Sync type availability: Full and incremental refresh [Cursor](https://docs.erathos.com/platform/connections/sync-types#understanding-cursors): `createdAt` Parent of [messages](#messages) | Field | Type | Cursor | | --------- | --------- | ------ | | id | integer | | | subject | text | | | status | text | | | agentId | integer | | | contactId | integer | | | createdAt | timestamp | ✓ | | updatedAt | timestamp | | ### inboxes Sync type availability: Full-refresh | Field | Type | | --------- | --------- | | id | integer | | name | text | | email | text | | type | text | | createdAt | timestamp | | updatedAt | timestamp | ### knowledge Sync type availability: Full-refresh | Field | Type | | --------- | --------- | | id | integer | | title | text | | type | text | | status | text | | createdAt | timestamp | | updatedAt | timestamp | ### messages Sync type availability: Full-refresh Child of [conversations](#conversations) | Field | Type | | -------------- | --------- | | id | integer | | conversationId | integer | | content | text | | type | text | | sender | text | | createdAt | timestamp | | updatedAt | timestamp | ### tables Sync type availability: Full and incremental refresh [Cursor](https://docs.erathos.com/platform/connections/sync-types#understanding-cursors): `updatedAt` Parent of [table\_rows](#table_rows) | Field | Type | Cursor | | ----------- | --------- | ------ | | id | integer | | | name | text | | | description | text | | | createdAt | timestamp | | | updatedAt | timestamp | ✓ | ### table\_rows Sync type availability: Full-refresh Child of [tables](#tables) | Field | Type | | --------- | --------- | | id | integer | | tableId | integer | | data | json | | createdAt | timestamp | | updatedAt | timestamp | ## Entity Relationships ```mermaid erDiagram campaigns ||--o{ campaign_enrollments : "id = campaignId" contacts ||--o{ campaign_enrollments : "id = contactId" conversations ||--o{ messages : "id = conversationId" agents ||--o{ conversations : "id = agentId" contacts ||--o{ conversations : "id = contactId" tables ||--o{ table_rows : "id = tableId" agents { integer id PK text name text description text model text status timestamp createdAt timestamp updatedAt } campaigns { integer id PK text name text status text type timestamp createdAt timestamp updatedAt } campaign_enrollments { integer id PK integer campaignId integer contactId text status timestamp createdAt timestamp updatedAt } contacts { integer id PK text name text email text phone text status timestamp createdAt timestamp updatedAt } conversations { integer id PK text subject text status integer agentId integer contactId timestamp createdAt timestamp updatedAt } inboxes { integer id PK text name text email text type timestamp createdAt timestamp updatedAt } knowledge { integer id PK text title text type text status timestamp createdAt timestamp updatedAt } messages { integer id PK integer conversationId text content text type text sender timestamp createdAt timestamp updatedAt } tables { integer id PK text name text description timestamp createdAt timestamp updatedAt } table_rows { integer id PK integer tableId json data timestamp createdAt timestamp updatedAt } ``` # Octadesk ### Using the Erathos platform When selecting Octadesk as a new connector on the Erathos platform, you will need to name your connection and fill in the following form: * **URL** — The base URL of your Octadesk account (e.g. `https://yourcompany.octadesk.services`) * **Token** — Your Octadesk API key, used to authenticate all requests * **Agent Email** — The email address of the Octadesk agent associated with the API key With this connection created you can seamlessly move your Octadesk data to your BigQuery, Redshift or Postgres data warehouse. ### How to find my token? You can find your API Key inside your Octadesk account by navigating to **Settings > WhatsApp API > Generate API Key** (Gerar apiKey). Copy the key that is displayed. Paste the value into the Erathos platform **Token** field. In the **Agent Email** field, enter the email address of the Octadesk agent under whose credentials the API key was generated. In the **URL** field, enter your account's base URL, which can also be found under **Settings > WhatsApp API > Base URL**. Don't forget to click on **Save and close** to advance to the next steps of the integration. ### What endpoints can I access with the Erathos platform? * chats * messages * events * contacts * tickets * ticket\_interactions * ticket\_tags * ticket\_groups * ticket\_forms * ticket\_priorities * ticket\_types * ticket\_channels * ticket\_status * organizations * survey\_submissions # Omie Find out how to connect Omie to your data warehouse effortlessly. ## Using the Erathos platform When selecting **Omie** as a new connector on the Erathos platform, you will need to name your connection and fill in the following form: ![](https://help.erathos.com/rails/active_storage/blobs/redirect/eyJfcmFpbHMiOnsibWVzc2FnZSI6IkJBaHBBWHc9IiwiZXhwIjpudWxsLCJwdXIiOiJibG9iX2lkIn19--48704996ee7714ad3ab6dae94deafa96118d1b2d/Omie.png) ## Obtaining these informations through **My Apps** 1. Log in to your account ![](https://help.erathos.com/rails/active_storage/blobs/redirect/eyJfcmFpbHMiOnsibWVzc2FnZSI6IkJBaHBBWDA9IiwiZXhwIjpudWxsLCJwdXIiOiJibG9iX2lkIn19--fffed2f53c13db1a05cb2a619eb168ead1c91253/Untitled%20\(49\).png) 2. Click on the Settings button and select App Summary ![](https://help.erathos.com/rails/active_storage/blobs/redirect/eyJfcmFpbHMiOnsibWVzc2FnZSI6IkJBaHBBWDQ9IiwiZXhwIjpudWxsLCJwdXIiOiJibG9iX2lkIn19--d0f8e77eb61a0e175a1cfd23608587b99af167fb/Untitled%20\(50\).png) 3. Navigate to the end of the page to find your **Integration Key** ![](https://help.erathos.com/rails/active_storage/blobs/redirect/eyJfcmFpbHMiOnsibWVzc2FnZSI6IkJBaHBBWDg9IiwiZXhwIjpudWxsLCJwdXIiOiJibG9iX2lkIn19--2e737eb02667c0565daf4db708de20c2db9ad00f/Untitled%20\(51\).png) ## Obtaining these informations through **Developer** 1. Log in to your account 2. In your browser, open another tab and access this link: to the Developer Area 3. Click on **Apps** to find the credentials ![](https://help.erathos.com/rails/active_storage/blobs/redirect/eyJfcmFpbHMiOnsibWVzc2FnZSI6IkJBaHBBWUE9IiwiZXhwIjpudWxsLCJwdXIiOiJibG9iX2lkIn19--b78db50d66633608020a575bb95bf2f782d57e42/Untitled%20\(52\).png) 4. Copy the App Key and App Secret ![](https://help.erathos.com/rails/active_storage/blobs/redirect/eyJfcmFpbHMiOnsibWVzc2FnZSI6IkJBaHBBWUU9IiwiZXhwIjpudWxsLCJwdXIiOiJibG9iX2lkIn19--81effccc0af8b1ae12c4148c32282987347a0cd8/Untitled%20\(53\).png) Now paste the copied values in the Erathos platform accordingly. Don't forget to click on **Save and close** to advance to the next steps of the integration. With this connection created you can seemlessly move your Omie data to your BigQuery, Redshift or Postgres data-warehouse. ## What endpoints can I access with the Erathos platform? * tabela\_precos\_itens * formas\_pagamento\_vendas * caracteristicas\_produtos * etapas\_faturamento * meios\_pagamento * origem\_pedidos * notas\_fiscais * pedidos * etapas\_pedidos * remessas * servicos * ordens\_servicos * contratos\_servicos * servicos\_municipio * formas\_pagamento\_servicos * tipo\_contrato * classificao\_servico * notas\_fiscais\_servicos * posicao\_estoque * clientes * projetos * empresas * departamentos * categorias * parcelas * tipo\_atividade * cnaes * cidades * paises * tipos\_anexos * tipos\_entrega * tipo\_assinante * crm\_contas * crm\_contatos * crm\_oportunidades * crm\_tarefas * crm\_solucoes * crm\_fases * crm\_usuarios * crm\_status * crm\_motivos * crm\_tipos * crm\_parceiros * crm\_finders * crm\_origens * crm\_concorrentes * crm\_verticais * crm\_tipostarefa * conta\_corrente * conta\_corrente\_lancamentos * conta\_pagar * conta\_receber * movimento\_financeiro * bancos * tipos\_documentos * tipos\_contas\_correntes * dre * finalidade\_transferencia * origem\_lancamento * produtos * produtos\_caracteristicas * produtos\_estruturas * ordem\_de\_producao * notas\_de\_entrada * recebimentos * familias\_produtos * unidades\_produtos * compradores * fornecedores * formas\_pagamentos\_compras * ncms * cfop * cst * ajuste\_estoque * movimento\_estoque * locais\_estoque * cupons\_fiscais * cupons\_fiscais\_itens * tabela\_precos * pedidos\_lista\_parcelas\_parcelas * pedidos\_det * notas\_fiscais\_det # Pipefy Find out how to connect Pipefy to your data warehouse effortlessly. ## Using the Erathos platform When selecting Pipefy as a new connector on the Erathos platform, you will need to name your connection and fill in the following form with a Service Account:
## How to create a Pipefy Service Account? {% hint style="info" %} Make sure you are a Super Admin in the organization before following those steps. {% endhint %} 1. Click on the **name of your company** or your **profile image** at the top of the page. Then, click on **Members and Permissions**\ ![](/files/3JccrvyiyxLyg8Q37U9a) 2. Click on the **Service Accounts tab**\ ![](/files/PP4tKQfRI8GObF791UgS) 3. Click on **Create Service Account**\ ![](/files/snsk5moriN5zJDDLNpOm) 4. Enter the Account Name. This will be used to create the email address and needs to be up to 20 characters.\ If you’d like, add a description. Up to 140 characters. 5. Define the role that this account will have on the organization. 6. Define how long tokens generated for this service account will work before they expire. The minimum time is 5 minutes and the maximum is 30 days. 7. Click on the Service Account on the list and get the Client ID, the Client Secret, and the token endpoint. **This is sensitive information,** so beware when sharing or storing it. Don't forget to click on **Save and close** to advance to the next steps of the integration. With this connection created you can seemlessly move your Pipefy data to your BigQuery, Redshift, Databricks or Postgres data-warehouse. ## What endpoints can I access with the Erathos platform? * organizations * pipes * cards * phases * cards\_phases\_history * tables * tables\_records # Piperun ### Using the Erathos platform When selecting Piperun as a new connector on the Erathos platform, you will need to name your connection and fill in the following form: * **Token:** Your Piperun personal API token used to authenticate requests to the Piperun API With this connection created you can seamlessly move your Piperun data to your BigQuery, Redshift or Postgres data warehouse. ### How to find my token? Your Piperun API token can be found in your account settings. Log in to Piperun, click on your profile icon in the top-right corner, and navigate to **Settings → Integrations → API**. Your personal API token will be listed there. Once you have copied your token, paste it into the **Token** field on the Erathos platform and click **Save and close**. ### What endpoints can I access with the Erathos platform? * companies * persons * deals * activities * pipelines * stages * notes * files * custom\_fields # Ploomes Find out how to connect Ploomes to your data warehouse effortlessly. ## How to find my User Key? 1. In your Ploomes account, navigate to Administration
2. In the integrations section, select Integrations Users.
2. Create a new user and copy the API Key.
## What endpoints can I access with the Erathos platform? * accounts * cities * countries * states * contacts * contact\_number\_of\_employees * contact\_origins * contact\_lines\_of\_business * contact\_relationships * contact\_status * contact\_types * currencies * deals * deal\_stages * deals\_status * deals\_loss\_reasons * deal\_pipelines * documents * document\_templates * documentdepartments\_templates * interaction\_records * phone\_types * roles * tags * teams * users * tasks * task\_types * task\_interval\_units * task\_email\_reminders * quotes * quotes\_approval\_status * products * product\_families * product\_groups * product\_parts * orders * order\_stages * fields * field\_entity # PostHog Connect your PostHog analytics to your data warehouse. Sync events, persons, feature flags, and experiments to BigQuery, Redshift, Postgres, Databricks, and more. ## Using the Erathos platform When selecting PostHog as a new connector on the Erathos platform, you will need to name your connection and fill in the following form: * **Token** — Your PostHog personal API key used for authentication With this connection created you can seamlessly move your PostHog data to your BigQuery, Redshift or Postgres data warehouse. ### How to find my token? To authenticate with PostHog, you need a personal API key. Log in to your PostHog instance, click on your profile in the top-right corner, and navigate to **Settings → Personal API keys**. Click **+ Create personal API key**, give it a name (e.g. "Erathos"), and copy the generated key. Paste the personal API key into the **Token** field on the Erathos platform connection form. Click **Save and close** to complete setup. ## Endpoints and fields ### actions Sync type availability: Full-refresh | Field | Type | | --------------- | --------- | | id | integer | | name | text | | description | text | | created\_at | timestamp | | updated\_at | timestamp | | created\_by\_id | integer | | deleted | boolean | ### annotations Sync type availability: Full-refresh | Field | Type | | --------------- | --------- | | id | integer | | content | text | | created\_at | timestamp | | date\_marker | timestamp | | created\_by\_id | integer | ### cohorts Sync type availability: Full-refresh | Field | Type | | --------------- | --------- | | id | integer | | name | text | | description | text | | created\_at | timestamp | | updated\_at | timestamp | | is\_static | boolean | | created\_by\_id | integer | ### dashboards Sync type availability: Full-refresh | Field | Type | | --------------- | --------- | | id | integer | | name | text | | description | text | | created\_at | timestamp | | updated\_at | timestamp | | created\_by\_id | integer | | deleted | boolean | ### events Sync type availability: Full and incremental refresh [Cursor](https://docs.erathos.com/platform/connections/sync-types#understanding-cursors): `created_at` | Field | Type | Cursor | | ------------ | --------- | ------ | | id | text | | | event | text | | | distinct\_id | text | | | timestamp | timestamp | | | properties | text | | | elements | text | | | created\_at | timestamp | ✓ | ### experiments Sync type availability: Full-refresh | Field | Type | | --------------- | --------- | | id | integer | | name | text | | description | text | | created\_at | timestamp | | updated\_at | timestamp | | created\_by\_id | integer | ### feature\_flags Sync type availability: Full-refresh | Field | Type | | --------------- | --------- | | id | integer | | key | text | | name | text | | active | boolean | | created\_at | timestamp | | created\_by\_id | integer | | deleted | boolean | ### persons Sync type availability: Full-refresh | Field | Type | | -------------- | --------- | | id | text | | distinct\_id | text | | properties | text | | created\_at | timestamp | | is\_identified | boolean | | name | text | | email | text | ### session\_recordings Sync type availability: Full-refresh | Field | Type | | ------------ | --------- | | id | text | | session\_id | text | | distinct\_id | text | | viewed | boolean | | start\_time | timestamp | | end\_time | timestamp | | duration | float | | created\_at | timestamp | ### surveys Sync type availability: Full-refresh | Field | Type | | --------------- | --------- | | id | integer | | name | text | | description | text | | created\_at | timestamp | | updated\_at | timestamp | | created\_by\_id | integer | ## Entity Relationships ```mermaid erDiagram actions { integer id PK text name text description timestamp created_at timestamp updated_at integer created_by_id boolean deleted } annotations { integer id PK text content timestamp created_at timestamp date_marker integer created_by_id } cohorts { integer id PK text name text description timestamp created_at timestamp updated_at boolean is_static integer created_by_id } dashboards { integer id PK text name text description timestamp created_at timestamp updated_at integer created_by_id boolean deleted } events { text id PK text event text distinct_id timestamp timestamp text properties text elements timestamp created_at } experiments { integer id PK text name text description timestamp created_at timestamp updated_at integer created_by_id } feature_flags { integer id PK text key text name boolean active timestamp created_at integer created_by_id boolean deleted } persons { text id PK text distinct_id text properties timestamp created_at boolean is_identified text name text email } session_recordings { text id PK text session_id text distinct_id boolean viewed timestamp start_time timestamp end_time float duration timestamp created_at } surveys { integer id PK text name text description timestamp created_at timestamp updated_at integer created_by_id } ``` # Qulture.Rocks Find out how to connect Qulture.Rocks to your data warehouse effortlessly. ## Using the Erathos platform When selecting Qulture.Rocks as a new connector on the Erathos platform, you will need to name your connection and fill in the following form: ![](https://help.erathos.com/rails/active_storage/blobs/redirect/eyJfcmFpbHMiOnsibWVzc2FnZSI6IkJBaHBBZG89IiwiZXhwIjpudWxsLCJwdXIiOiJibG9iX2lkIn19--4621b668403813d3ec3a6bb8b21068e17eaa52b1/qulture%20rocks%20form.png) ## How to find my Qulture.Rocks Company ID? ## How to find my Qulture.Rocks API Token? 1. Log in to your account as **administrator** 2. Enter the **Organization** page 3. Click on **Integrations** 4. Select **Platform API** 5. Click on **generate token again** 6. Copy and paste the token value on the Erathos platform connection form With this connection created you can seemlessly move your Qulture.Rocks data to your BigQuery, Redshift or Postgres data-warehouse. ## What endpoints can I access with the Erathos platform? * surveys * topics\_with\_questions * survey\_participations * list\_answers\_survey\_participation * participants * team\_results * list\_answers\_survey * boxes * box\_calibrations * box\_participations * box\_participation\_calibrations * feedbacks * idp\_cycles * idp * idp\_goals * idp\_actions * teams * contracts * contract\_records * one\_on\_one\_employee * contract\_feelings * contract\_priorities * team\_members * cycles * okr * key\_results * key\_result\_tasks * one\_on\_one\_reports * one\_on\_one\_tasks * feelings * praises * job\_title * job\_positions # RD Station CRM Find out how to connect RD Station CRM to your data warehouse effortlessly. ## Using the Erathos platform When selecting RD Sttaion CRM as a new connector on the Erathos platform, you will need to name your connection and fill in the following form: ![](https://help.erathos.com/rails/active_storage/blobs/redirect/eyJfcmFpbHMiOnsibWVzc2FnZSI6IkJBaHBBaGtCIiwiZXhwIjpudWxsLCJwdXIiOiJibG9iX2lkIn19--51a01b8af669f6b1b5c51476680bdcf639f8ced8/rd%20station%20crm.png) ## How to find my RD Station Token? 1. Log in to your RD Station CRM **account** 2. Click on **username**, in the top right corner 3. In the dropdown menu, click on **Profile** 4. If you have already generated a token, you can use the same one, which will be shown in the texto **Instance Token** field 5. In case there is no token inthe field mentioned, click on **Generate Token** Warning: The Disable Token button will irreversibly undo all API or webhook integrations for the user. Even if the user clicks the Generate Token button again afterward, a different code will be generated, and the integrations will need to be set up again. Therefore, only use this button if you really want to undo the integrations! With this connection created you can seemlessly move your RD Station CRM data to your BigQuery, Redshift or Postgres data-warehouse. ## What endpoints can I access with the Erathos platform? * tasks * activities * deals * deal\_contacts * deal\_products * users * teams * organizations * contacts * products * pipelines * pipeline\_stages * sources * campaigns * deal\_details # RD Station Marketing Find out how to connect RD Station Marketing to your data warehouse effortlessly. ## Using the Erathos platform: When selecting RD Station Marketing as a new connector on the Erathos platform, you will need to authorize the connection by simply logging into the RD Station Marketing account associated with your browser. Just click on '**Authorize RD Station Marketing**' as shown in the attachment below: ![](https://help.erathos.com/rails/active_storage/blobs/redirect/eyJfcmFpbHMiOnsibWVzc2FnZSI6IkJBaHBBWU09IiwiZXhwIjpudWxsLCJwdXIiOiJibG9iX2lkIn19--c650e0b2bd314d794ed69bda1c2a27f7331a5822/rd%20station%20markeitng.png) Don't forget to click on **Save and close** to advance to the next steps of the integration. With this connection created you can seemlessly move your RD Station Marketing data to your BigQuery, Redshift or Postgres data-warehouse. ## What endpoints can I access with the Erathos platform? * custom\_fields * segmentations * segmentation\_contacts * contact\_details * contact\_conversion\_events * contact\_opportunity\_events * contact\_funnels * workflows * emails * landing\_pages * popups * forms * webhook\_subscriptions # Runrun.it Connect your Runrun.it platform to your data warehouse. Sync tasks, projects, clients, users, and boards to BigQuery, Redshift, Postgres, Databricks, and more. ## Using the Erathos platform When selecting Runrun.it as a new connector on the Erathos platform, you will need to name your connection and fill in the following form: * **App-Key** — your Runrun.it application key, used to identify your account * **User-Token** — your personal API token, used to authenticate API requests on your behalf With this connection created you can seamlessly move your Runrun.it data to your BigQuery, Redshift or Postgres data warehouse. ### How to find my token? To authenticate with the Runrun.it API, you need two credentials: an **App-Key** and a **User-Token**. To find your **App-Key**, log in to Runrun.it and navigate to **Manage → Integrations → API Integration**. The App-Key identifies your Runrun.it account and will be displayed on the integrations page. To generate your **User-Token**, click on your profile avatar in the top-right corner, then select **My Account → API**. Generate a new personal token if you haven't already and copy it. Paste both credentials into the **App-Key** and **User-Token** fields on the Erathos platform and click **Save and close** to complete the setup. ## Endpoints and fields ### boards Sync type availability: Full-refresh Parent of [board\_stages](#board_stages) | Field | Type | | ----------- | --------- | | id | integer | | name | text | | created\_at | timestamp | | updated\_at | timestamp | ### board\_stages Sync type availability: Full-refresh Child of [boards](#boards) | Field | Type | | ----------- | --------- | | id | integer | | name | text | | board\_id | integer | | created\_at | timestamp | | updated\_at | timestamp | ### clients Sync type availability: Full-refresh | Field | Type | | ---------------- | --------- | | id | integer | | name | text | | is\_active | boolean | | organization\_id | integer | | created\_at | timestamp | | updated\_at | timestamp | ### manual\_work\_periods Sync type availability: Full and incremental refresh [Cursor](https://docs.erathos.com/platform/connections/sync-types#understanding-cursors): `created_at` | Field | Type | Cursor | | ----------------- | --------- | ------ | | id | integer | | | user\_id | integer | | | task\_id | integer | | | started\_at | timestamp | | | ended\_at | timestamp | | | duration\_seconds | integer | | | created\_at | timestamp | ✓ | | updated\_at | timestamp | | ### projects Sync type availability: Full-refresh | Field | Type | | ----------- | --------- | | id | integer | | name | text | | client\_id | integer | | is\_active | boolean | | is\_public | boolean | | created\_at | timestamp | | updated\_at | timestamp | ### tags Sync type availability: Full-refresh | Field | Type | | ----------- | --------- | | id | integer | | name | text | | created\_at | timestamp | | updated\_at | timestamp | ### task\_types Sync type availability: Full-refresh | Field | Type | | ----------- | --------- | | id | integer | | name | text | | is\_active | boolean | | created\_at | timestamp | | updated\_at | timestamp | ### tasks Sync type availability: Full and incremental refresh [Cursor](https://docs.erathos.com/platform/connections/sync-types#understanding-cursors): `updated_at` | Field | Type | Cursor | | -------------------------- | --------- | ------ | | id | integer | | | title | text | | | desired\_date | timestamp | | | desired\_start\_date | timestamp | | | desired\_delivery\_date | timestamp | | | delivered\_at | timestamp | | | current\_estimate\_seconds | integer | | | time\_worked | integer | | | is\_working\_on | boolean | | | is\_overdue | boolean | | | project\_id | integer | | | user\_id | integer | | | type\_id | integer | | | board\_id | integer | | | board\_stage\_id | integer | | | created\_at | timestamp | | | updated\_at | timestamp | ✓ | ### teams Sync type availability: Full-refresh | Field | Type | | ----------- | --------- | | id | integer | | name | text | | created\_at | timestamp | | updated\_at | timestamp | ### users Sync type availability: Full-refresh | Field | Type | | ----------- | --------- | | id | integer | | name | text | | email | text | | avatar\_url | text | | is\_active | boolean | | is\_admin | boolean | | is\_master | boolean | | type | text | | language | text | | timezone | text | | created\_at | timestamp | | updated\_at | timestamp | ## Entity Relationships ```mermaid erDiagram boards ||--o{ board_stages : "id = board_id" clients ||--o{ projects : "id = client_id" projects ||--o{ tasks : "id = project_id" users ||--o{ tasks : "id = user_id" boards ||--o{ tasks : "id = board_id" board_stages ||--o{ tasks : "id = board_stage_id" users ||--o{ manual_work_periods : "id = user_id" tasks ||--o{ manual_work_periods : "id = task_id" boards { integer id PK } board_stages { integer id PK } clients { integer id PK } projects { integer id PK } tasks { integer id PK } users { integer id PK } manual_work_periods { integer id PK } tags { integer id PK } teams { integer id PK } task_types { integer id PK } ``` # Sankhya Find out how to connect Sankhya to your data warehouse effortlessly. ## Using the Erathos platform When selecting Sankhya as a new connector on the Erathos platform, you will need to name your connection and fill in the following form:
## How to find the API Token? 1. Access the "Gateway Settings" page. 2. In the "Endereço Sankhya" field, inform the external access adress to Sankhya OM. 3. In the "Name" field, it is recommended to specify the environment type (Production, Test, Training). 4. In "Application," specify the application that will be integrated. 5. Enter a user linked to the Sankhya ID in the "User Code" field. Once saved, the TOKEN will be generated. Don't forget to click on **Save and close** to advance to the next steps! With this connection created you can seemlessly move your Sankhya data to your BigQuery, Redshift or Postgres data-warehouse. ## What endpoints can I access with the Erathos platform? * Usuario * TipoNegociacao * TipoTitulo * Parceiro * Natureza * Empresa * EmpresaProdutoImpostos * ContaBancaria * Banco * Financeiro * BaixaBancaria # Sentry Find out how to connect Sentry to your data warehouse effortlessly. ## Using the Erathos platform When selecting Sentry as a new connector on the Erathos platform, you will need to name your connection and fill in the following form: ![](https://help.erathos.com/rails/active_storage/blobs/redirect/eyJfcmFpbHMiOnsibWVzc2FnZSI6IkJBaHBBZUU9IiwiZXhwIjpudWxsLCJwdXIiOiJibG9iX2lkIn19--1f512adfefaaa7d81ddc3be8e9989758de598808/sentry%20form.png) 1. Lon in to your Sentry account 2. Click **Settings** in the left-side menu; 3. Open the **Organization Settings** page; 4. Click **Custom Integrations** in the left panel to create a new internal integration and generate the auth token; 5. Select **Create New Integration**; 6. Ensure that **Internal Integration** is selected before proceeding to **Next**; 7. Name your integration;![](https://help.erathos.com/rails/active_storage/blobs/redirect/eyJfcmFpbHMiOnsibWVzc2FnZSI6IkJBaHBBZUk9IiwiZXhwIjpudWxsLCJwdXIiOiJibG9iX2lkIn19--882101b3dcced245f732f75535666d0d80528e62/sentry%20image%20video.gif) 8. In **Permissions**, set the desired permissions for API requests; 9. Click **Save Changes**; 10. At the bottom of the page, copy the generated token found under **Tokens**; 11. Paste the Token value on the Erathos platform connection form. Don't forget to click on **Save and close** to advance to the next steps! With this connection created you can seemlessly move your Sentry data to your BigQuery, Redshift or Postgres data-warehouse. ## What endpoints can I access with the Erathos platform? * organizations * organization\_users * organization\_trusted\_relays * organization\_repositories * organization\_projects * organization\_metric\_alert\_rules * spike\_protection\_notifications * organization\_releases * organization\_replays * organization\_selectors * organization\_teams * projects * project\_issue\_alert\_rules * project\_users * project\_user\_feedback * project\_service\_hooks * project\_issues * project\_events # Sienge ### Using the Erathos platform When selecting Sienge as a new connector on the Erathos platform, you will need to name your connection and fill in the following form: * **Subdomain** — your company's Sienge subdomain (the identifier that appears in your Sienge API URLs, e.g. `mycompany`) * **User** — your Sienge user email (e.g. `your@email.com`) * **Password** — your Sienge user password With this connection created you can seamlessly move your Sienge data to your BigQuery, Redshift or Postgres data warehouse. ### What endpoints can I access with the Erathos platform? * accountancy\_accounts * accountancy\_entries * accountancy\_entry\_generator\_entry\_batches * accountancy\_entry\_generator\_entries * accountancy\_entry\_generator\_entry\_batch\_entries * accounts\_balances * accounts\_receivable\_receivable\_bills * accounts\_receivable\_receivable\_bill\_installments * accounts\_receivable\_receivable\_bill\_budget\_categories * accounts\_statements * accountancy\_batch * bearers\_receivable * bills * bills\_by\_change\_date * bills\_installments * bills\_taxes * bills\_budget\_categories * bills\_departments\_cost * bills\_buildings\_cost * bills\_attachments * bills\_units * building\_cost\_estimations\_cost\_estimate\_resources * building\_cost\_estimations\_resources * building\_cost\_estimations\_resource\_units\_of\_movement * building\_cost\_estimations\_sheets * building\_projects\_calendar\_days\_off * building\_projects\_progress\_logs * checking\_accounts * cities * civil\_status * closing\_accountancy * commissions * commissions\_configurations\_brokers * sales\_commissions * companies * construction\_daily\_report * construction\_daily\_report\_event\_types * construction\_daily\_report\_types * cost\_centers * cost\_databases * cost\_databases\_resources * cost\_databases\_work\_items * cost\_databases\_work\_items\_assemblies * creditors * creditors\_bank\_informations * creditors\_pix\_informations * customer\_types * customers * customers\_attachments * departments * enterprises * indexers * inventory\_movements * stock\_reservations * stock\_inventories\_items * nfes * nfes\_payments * nfes\_linked\_nfes * payment\_condition\_types * patrimony\_fixed * patrimony\_movable * price\_tables * professions * property\_rental * property\_types * purchase\_quotations\_negotiations * purchase\_requests\_items * real\_estate\_map * resource\_groups * sales\_contracts * sales\_contracts\_attachments * sales\_contracts\_guarantors * sites * supply\_contracts\_measurements * supply\_contracts\_measurements\_items * supply\_contracts\_measurements\_attachments * trademarks * units * units\_characteristics * units\_situations * units\_of\_measure * work\_item\_groups * bulk\_accountancy\_account\_balance * bulk\_accountancy\_account\_cost\_center\_balance * bulk\_bank\_movement * bulk\_building\_cost\_estimation\_items * bulk\_building\_resources * bulk\_business\_budget * bulk\_customer\_debt\_balance * bulk\_customer\_extract\_history * bulk\_defaulters\_receivable\_bills * bulk\_defaulters\_receivable\_bills\_by\_aging * bulk\_income * bulk\_invoice\_items * bulk\_outcome * bulk\_purchase\_quotations * bulk\_sales # Shopify Find out how to connect Shopify to your data warehouse effortlessly. ## Using the Erathos platform: The rate limit for Shopify API is based on the complexity of the requested data. The more fields are queried the higher the consumption and potential wait required to complete the extraction. In order to create a Shopify connection with its own isolated rate limit usage, our platform requires the credentials of your own OAuth App. Follow the steps bellow to create a new app. ## Credentials 1. After selecting the Shopify connector, navigate to its credentials page on Erathos platform. 1. Copy the Redirect URL. 2. Go to [Shopify dev dashboard](https://dev.shopify.com/dashboard/). 1. On Apps tab, click on the **Create App** button. Two options will be shown: Get started with Shopify CLI or Start with Dev Dashboard. 2. Choose Dev Dashboard by typing a name and clicking Create. 3. Upon creation you will be redirected to the App **Versions** tab. 1. Use `https://app.erathos.com` as **App URL**. 2. Disable the option **Incorporate app in Shopify admin**. 3. Choose the permission **Scopes** to concede to the App: `read_all_orders,read_orders,read_products,read_shipping,read_inventory,read_customers,read_assigned_fulfillment_orders`. 4. Enable the option **Use Legacy Install Flow**. 5. Paste Erathos Redirect URL copied during step 1.a in the field **Redirect URLs**. 6. Click **Launch** to finish the version creation. 4. Use the sidebar to go to the **Settings** tab. There you will find the **Client ID** and **Secret Key** that needs to be filled in Erathos credential page acessed during step 1. 3. Back on Erathos, continue from the connection credentials page in step 1: 1. Paste the **Client ID**. 2. Paste the Secret Key in the field **Client Secret**. 3. Type your **shop name** omiting shopify.com (e.g. yourstore for **yourstore**.shopify.com). 4. Click on **Save and test.** 4. After being redirected to the Connection settings page, go back the credentials page. 1. There click on **Authorize integration** in order to be redirected to Shopify. 2. Read the permissions being conceded and confirm the authorization. 3. After being redirected back to Erathos, click on **Save and test** to finish. 5. Your connection is now ready be used. Proceed to the manage jobs option to choose which endpoints and fields you wish to extract. ## What endpoints can I access with the Erathos platform? * customers * inventory\_items * orders * products * shipping * shop # Stripe Find out how to connect Stripe to your data warehouse effortlessly. ## Using the Erathos platform When selecting Stripe as a new connector on the Erathos platform, you will need to name your connection and fill in the following form: ![](https://help.erathos.com/rails/active_storage/blobs/redirect/eyJfcmFpbHMiOnsibWVzc2FnZSI6IkJBaHBBWVE9IiwiZXhwIjpudWxsLCJwdXIiOiJibG9iX2lkIn19--f9416a5b1a8a5470d06b3e18cc6cafcbff11aca1/stripe.png) ## How to find Stripe's API Token? A restricted API Key allows only the access level that has been specified. To create a restricted API Key: 1. Access the **API Keys** page 2. You can either create a restricted key form scratch or clone an already existent key. * To create a key form scratch, click on **Create restricted key.** In this case, the standard value for all permissions is **None.** * To clone an already existent key: on the line of the key that you want to clone, click on the navigation menu and select **Duplicate key.** In this case, the standard value for each permisison is equivalent to its value in the now cloned key. 3. In the **Key name** field, insert a name. If you cloned an existent key, the standand name is the cloned key's name. 4. For each resouce that the new key should be able to access, select the correspondent permission. If you use Connect, you can also select the key permission when accessing connected accounts. The availabe permissions are **None**, **Reader** or **Recorder**. 5. Click on **Create key**. 6. Stripe will send a verification code to your email inbox ou through a text message. It may not be sent immediatly, be patient! When received, insert the code in the text box. If the text box doesn't advance to the next step automatically, click on **Continue**. 7. The text box will exhibit **the new key value**. Click to copy and **save** it, you won't be able to retrieve it. 8. In the Add an observation field, indicate where you saved the key value and click on **Concluded**. Now paste the informations in the correct fields in the Erathos platform. Don't forget to click on **Save and close** to advance to the next steps of the integration. With this connection created you can seemlessly move your Stripe data to your BigQuery, Redshift or Postgres data-warehouse. ## What endpoints can I access with the Erathos platform? * files * payouts * refunds * payment\_method\_domains * products * prices * tax\_rates * shipping\_rates * checkout\_sessions * payment\_links * credit\_notes * invoices * invoice\_items * plans * quotes * subscriptions * subscription\_items * schedules * connected\_accounts * external\_bank\_accounts * persons * application\_fees * transfers * early\_fraud\_warnings * open\_reviews * authorizations * cardholders * issuing\_disputes * issuing\_transactions * locations * readers * report\_runs * financial\_connections\_accounts # Superlógica Find out how to connect Superlogica to your data warehouse effortlessly. ## Using the Erathos platform When selecting Superlógica as a new connector on the Erathos platform, you will need to name your connection and fill in the following form: ![](https://help.erathos.com/rails/active_storage/blobs/redirect/eyJfcmFpbHMiOnsibWVzc2FnZSI6IkJBaHBBWVU9IiwiZXhwIjpudWxsLCJwdXIiOiJibG9iX2lkIn19--663d189a5b042c16f6d1fbb032c57c72bea95b5e/superl%C3%B3gica.png) ## How to find my Superlógica Access Token? The access token is a code that informs each integration user's permissions. These permissions can be altered. 1. To create the access tokens, enter the users page in or pass your mouse along your user and click on **All users** as the attechment below: ![](https://help.erathos.com/rails/active_storage/blobs/redirect/eyJfcmFpbHMiOnsibWVzc2FnZSI6IkJBaHBBWVk9IiwiZXhwIjpudWxsLCJwdXIiOiJibG9iX2lkIn19--bb031cdf64d9e9ddc0a07dd9be24ef1c2dc8cf9f/Untitled%20\(54\).png) 2. Scroll down and select the **Apps (your e-mail)** option. ![](https://help.erathos.com/rails/active_storage/blobs/redirect/eyJfcmFpbHMiOnsibWVzc2FnZSI6IkJBaHBBWWM9IiwiZXhwIjpudWxsLCJwdXIiOiJibG9iX2lkIn19--5f9cb25c57714054eaa3f952302a0ead7e9fc73c/Untitled%20\(55\).png) 3. Then, click in **New App Token** ![](https://help.erathos.com/rails/active_storage/blobs/redirect/eyJfcmFpbHMiOnsibWVzc2FnZSI6IkJBaHBBWWc9IiwiZXhwIjpudWxsLCJwdXIiOiJibG9iX2lkIn19--1f0d5f7499523083323b6f8514b66dfadd3e3152/Untitled%20\(56\).png) 4. Now, fill in the name and description fields regarding your app and click on **Save**. ![](https://help.erathos.com/rails/active_storage/blobs/redirect/eyJfcmFpbHMiOnsibWVzc2FnZSI6IkJBaHBBWWs9IiwiZXhwIjpudWxsLCJwdXIiOiJibG9iX2lkIn19--c90059d6f422fd14f3fbf27fe0210095939c23f5/Untitled%20\(57\).png) 5. In the next page, the system wil, display the App token, Secret and Access token values. Only the App Token and Access token values are necessary for the connection. ![](https://help.erathos.com/rails/active_storage/blobs/redirect/eyJfcmFpbHMiOnsibWVzc2FnZSI6IkJBaHBBWW89IiwiZXhwIjpudWxsLCJwdXIiOiJibG9iX2lkIn19--07a558109358d7029bccee91d5eba24f0409d59c/Untitled%20\(58\).png) 6. In the **Released Apps** field No campo **Aplicativos liberados** above the creation interface you will see all the available for integration apps. ![](https://help.erathos.com/rails/active_storage/blobs/redirect/eyJfcmFpbHMiOnsibWVzc2FnZSI6IkJBaHBBWXM9IiwiZXhwIjpudWxsLCJwdXIiOiJibG9iX2lkIn19--8c5ab9c2fd3024a0eeef0b03affa2bf0bc98c737/Untitled%20\(59\).png) **P.S.: The App Token and the Access Token expire within 1 year. After that, to continue using the API, you will need to generate a new token.** Now paste the **App Token** and **Access Token** values in the correct fields of the Erathos platform. Don't forget to click on **Save and close** to advance to the next steps of the integration. With this connection created you can seemlessly move your Superlógica data to your BigQuery, Redshift or Postgres data-warehouse. ## What endpoints can I access with the Erathos platform? * clientes * clientes\_vinculados * contratos\_ativos * contratos\_trial * contratos\_pendentes * cobrancas * contas\_bancarias * centro\_custos * fornecedores * adimplentes * inadimplentes * metricas * movimentacoes\_bancarias * produtos\_servicos * cupons * departamentos * receitas\_eventuais * assinaturas * planos * notafiscal # TikTok Ads Find out how to connect Tiktok Ads to your data warehouse effortlessly. ### Using the Erathos platform Extracting data from TikTok Ads requires allowing Erathos App to access your TikTok account by simply logging into the Tiktok account associated with your browser and agreeing with the requested permission. First, in the **Credentials** page click on the 🔄 button and you will be redirected a TikTok authorization page where you can confirm which account and which permissions are being granted to Erathos:
{% hint style="info" %} The user account used must have the appropriate permissions to be able to see the advertiser accounts. You can assign one of the following roles (admin, operator, analyst) using [this guide](https://ads.tiktok.com/help/article/change-the-permissions-for-your-tiktok-business-center-partner?lang=en) {% endhint %} Click on **Confirm** and you will be redirected back to Erathos platform where you need to then click **Save and test** to proceed to the next step of the connection creation. After selecting the desired endpoints and their job settings you will be able to seemlessly move your TikTok Ads data to your BigQuery, Databricks, PostgreSQL, or Redshift data-warehouse. ### What endpoints can I access with the Erathos platform? * adgroups * ads * campaigns * report\_ad\_audience\_attribute\_daily * report\_ad\_audience\_attribution\_daily * report\_ad\_audience\_basicdata\_daily * report\_ad\_audience\_engagement\_daily * report\_ad\_audience\_pageevent\_daily * report\_ad\_audience\_videoplay\_daily * report\_ad\_basic\_attribute\_daily * report\_ad\_basic\_clicks\_daily * report\_ad\_basic\_conversion\_app\_daily * report\_ad\_basic\_conversion\_attribution\_daily * report\_ad\_basic\_conversion\_messaging\_daily * report\_ad\_basic\_conversion\_offline\_daily * report\_ad\_basic\_conversion\_shop\_daily * report\_ad\_basic\_conversion\_tiktok\_daily * report\_ad\_basic\_conversion\_website\_daily * report\_ad\_basic\_core\_daily * report\_ad\_basic\_image\_daily * report\_ad\_basic\_instantexperience\_daily * report\_ad\_basic\_interactive\_daily * report\_ad\_basic\_live\_daily * report\_ad\_basic\_san\_daily * report\_ad\_basic\_skan\_app\_daily * report\_ad\_basic\_skan\_attribution\_daily * report\_ad\_basic\_skan\_core\_daily * report\_ad\_basic\_socials\_daily * report\_ad\_basic\_video\_daily * report\_ad\_daily\_by\_age\_gender * report\_ad\_daily\_by\_country * report\_ad\_daily\_by\_language * report\_ad\_daily\_by\_platform * report\_adgroup\_audience\_basicdata\_daily * report\_adgroup\_audience\_engagement\_daily * report\_adgroup\_basic\_core\_daily * report\_adgroup\_daily\_by\_age\_gender * report\_adgroup\_daily\_by\_country * report\_adgroup\_daily\_by\_language * report\_adgroup\_daily\_by\_platform * report\_campaign\_audience\_basicdata\_daily * report\_campaign\_audience\_engagement\_daily * report\_campaign\_basic\_core\_daily * report\_campaign\_daily\_by\_age\_gender * report\_campaign\_daily\_by\_country * report\_campaign\_daily\_by\_language * report\_campaign\_daily\_by\_platform # Tiny Find out how to connect Tiny to your data warehouse effortlessly. ## Using the Erathos platform: When selecting Tiny as a new connector on the Erathos platform, you will need to authorize the connection by simply logging into the Tiny account associated with your browser. Just click on '**Authorize Tiny**' as shown in the attachment below: ![](https://help.erathos.com/rails/active_storage/blobs/redirect/eyJfcmFpbHMiOnsibWVzc2FnZSI6IkJBaHBBZDg9IiwiZXhwIjpudWxsLCJwdXIiOiJibG9iX2lkIn19--8fe4e7c55d34f171d3f404431871462d3df0e2f2/tiny%20form.png) Don't forget to click on **Save and close** to advance to the next steps of the integration. With this connection created you can seemlessly move your Tiny data to your BigQuery, Redshift or Postgres data-warehouse. ## What endpoints can I access with the Erathos platform? * dados\_da\_empresa * categorias * contatos * contatos\_detalhes * pessoas * contatos\_tipos * expedicao * formas\_envio * formas\_envio\_detalhes * formas\_pagamento * intermediadores * listas\_precos * marcas * notas * notas\_detalhes * pedidos * pedidos\_detalhes * separacao * separacao\_detalhes * vendedores * produtos * produtos\_detalhes * produto\_estoques # Tiny V3 Find out how to connect Tiny V3 to your data warehouse effortlessly. ## Using the Erathos platform: When selecting Tiny as a new connector on the Erathos platform, you will need to create an tiny app and authorize the connection. {% hint style="info" %} It is necessary to have the extension "**Gestão de Aplicativos**" enabled on your Tiny Account. {% endhint %}
1. In your Tiny account: 1. Navigate to `Menu` > `Configurações` > `Aba geral` > `Aplicativos`. 2. Create a new app. 3. Give it a name. 4. In the **URLs de Redirecionamento** field paste the Redirect URL provided in the Erathos plataform (image above). 5. Save and copy the **`Client ID`** and **`Client Secret`** 2. On the Erathos plataform 1. Paste both **`Client ID`** and **`Client Secret`**. 2. Click Save and test. 3. Click the Authorize Integration and follow the Authorization process 4. Click Save and test ## What endpoints can I access with the Erathos platform? * categorias * categorias\_receita\_despesa * contas\_pagar * contas\_pagar\_detalhes * contas\_receber * contas\_receber\_detalhes * contatos * contatos\_detalhes * contatos\_tipos * dados\_da\_empresa * expedicao * expedicao\_detalhes * formas\_envio * formas\_envio\_detalhes * formas\_pagamento * intermediadores * listas\_precos * marcas * notas * notas\_detalhes * ordem\_compras * ordem\_compras\_detalhes * ordem\_servicos * ordem\_servicos\_detalhes * pedidos * pedidos\_detalhes * pessoas * produto\_estoques * produtos # Teamwork Desk Find out how to connect Teamwork Desk to your data warehouse effortlessly. ## Using the Erathos platform When selecting Teamwork Desk as a new connector on the Erathos platform, you will need to name your connection and fill in the following form: ![](https://help.erathos.com/rails/active_storage/blobs/redirect/eyJfcmFpbHMiOnsibWVzc2FnZSI6IkJBaHBBZUE9IiwiZXhwIjpudWxsLCJwdXIiOiJibG9iX2lkIn19--9bddfc4989cf67f8b6001ffcaac9f35aa001263a/teamwork%20desk.png) ## How to find the Domain URL? 1. Log in to your account 2. Copy the URL address shown in your navigation bar (until `desk...)`. ## How to find the API Token? 1. In your account, click on your profile, located in the bottom left corner; 2. Click on **View Profile**; 3. Access **API keys;** 4. In the upper right corner, select Create an API key\*\*;\*\* 5. Copy the value found and paste it on the Erathos platform connection form Don't forget to click on **Save and close** to advance to the next steps of the integration! With this connection created you can seemlessly move your Teamwork Desk data to your BigQuery, Redshift or Postgres data-warehouse. ## What endpoints can I access with the Erathos platform? * companies * customers * conversationmessages * inboxes * tickets * messages * permissions * spamlists * timelogs * triggers * notifications * permissionusers * users * ticket\_priorities * ticket\_reminders * ticket\_activities * ticket\_sources * ticket\_read * ticket\_statuses * ticket\_templates * ticket\_types * ticket\_user\_decks # Track.co Find out how to connect Track.co to your data warehouse effortlessly. ## Using the Erathos platform When selecting [Track.co](http://track.co) as a new connector on the Erathos platform, you will need to name your connection and fill in the following form: ![](https://help.erathos.com/rails/active_storage/blobs/redirect/eyJfcmFpbHMiOnsibWVzc2FnZSI6IkJBaHBBZDQ9IiwiZXhwIjpudWxsLCJwdXIiOiJibG9iX2lkIn19--2baee2834973fec2115726ef4a7def3b68a183d0/track.co%20fomr.png) ## How to find my Organization UUID and API Token? 1. Log in to your account 2. In the main menu, locate the Settings section; 3. Click on Integrations and select the API option. 4. To enable API usage, click on the Activate API button. (This will allow you to generate the authentication token and UUID). 5. Place these informations somewhere safe, they are necessary for API requests. 6. Paste the found values on the Erathos platform connection form. Don't forget to click on **Save and close** to advance to the next steps! With this connection created you can seemlessly move your [Track.co](http://track.co) data to your BigQuery, Redshift or Postgres data-warehouse. ## What endpoints can I access with the Erathos platform? * surveys * distributions * distributions\_status * attributes * templates * interactions\_exports * interactions # Trello Find out how to connect Trello to your data warehouse effortlessly. ## Using the Erathos platform When selecting [Trello.com](https://trello.com/) as a new connector on the Erathos platform, you will need to name your connection and fill in the following form:
## How to find my API Key and API Token? 1. Navigate to . 2. Create a new **Power-up**. 3. Fill the form with your information (you can leave the URL field blank). 4. Generate a new **API Key**. 5. Copy your **API Key** (1) and create a **token** (2) manually.
## What endpoints can I access with the Erathos platform? * organizations * members * boards * cards * lists * actions # Twitch.tv Find out how to connect Twitch.tv to your data warehouse effortlessly. ## Using the Erathos platform: When selecting [Twitch.tv](http://twitch.tv) as a new connector on the Erathos platform, you will need to authorize the connection by simply logging into the [Twitch.tv](http://twitch.tv) account associated with your browser. Just click on '**Authorize** [**Twitch.tv**](http://twitch.tv)' as shown in the attachment below: ![](https://help.erathos.com/rails/active_storage/blobs/redirect/eyJfcmFpbHMiOnsibWVzc2FnZSI6IkJBaHBBYnc9IiwiZXhwIjpudWxsLCJwdXIiOiJibG9iX2lkIn19--1819c4e1df97e04fd803c6b7e85e73add5cee51b/twitch%20tv.png) Don't forget to click on **Save and close** to advance to the next steps of the integration. With this connection created you can seemlessly move your [Twitch.tv](http://twitch.tv) data to your BigQuery, Redshift or Postgres data-warehouse. ## What endpoints can I access with the Erathos platform? * user * banned\_users * moderators * vips * polls * videos * clips * goals * subscriptions * channels * followers # Twygo Find out how to connect Twygo to your data warehouse effortlessly. ## Using the Erathos platform When selecting Twygo as a new connector on the Erathos platform, you will need to name your connection and fill in the following form:
## How to generate Twygo's credentials? Fill out the form with your own credentials. Erathos will use this information to generate an access token as explained on [Twygo's documentation](https://documenter.getpostman.com/view/10208526/SWTA9dne#4e2e0cfd-5ad5-496b-a52d-b65fbea3d784). ## What endpoints can I access with Erathos platform? | Endpoints | | ---------------- | | courses | | portfolio | | students | | students\_events | # Typeform Find out how to connect Typeform to your data warehouse effortlessly. ## Using the Erathos platform When selecting Typeform as a new connector on the Erathos platform, you will need to name your connection and fill in the following form: ![](https://help.erathos.com/rails/active_storage/blobs/redirect/eyJfcmFpbHMiOnsibWVzc2FnZSI6IkJBaHBBWXc9IiwiZXhwIjpudWxsLCJwdXIiOiJibG9iX2lkIn19--51254cb36c4180d41d84a485dd806791aa864e76/typeform.png) ## How to find my Typeform Token? 1. Log in to your account 2. In the upper left corner of the page, in the drop-down menu beside your username, click on **Account**. 3. In the left menu, enter the Personal Tokens page. 4. Select Generate new token. 5. In the token's fielnd name, type in a name that can help you identify it later. 6. Define the necessary permissions and level of access for this API Token. 7. Click on Generate Token. Now, copy the token value and paste it on the Erathos platform's Token field. Don't forget to click on **Save and close** to advance to the next steps of the integration. With this connection created you can seemlessly move your Typeform data to your BigQuery, Redshift or Postgres data-warehouse. ## What endpoints can I access with the Erathos platform? * workspaces * forms * forms\_insights * forms\_fields\_insights * forms\_responses # Vindi Find out how to connect Vindi to your data warehouse effortlessly. ## Using the Erathos platform When selecting Vindi as a new connector on the Erathos platform, you will need to name your connection and fill in the following form: ![](https://help.erathos.com/rails/active_storage/blobs/redirect/eyJfcmFpbHMiOnsibWVzc2FnZSI6IkJBaHBBZDA9IiwiZXhwIjpudWxsLCJwdXIiOiJibG9iX2lkIn19--d2230dc405dc1dd1eb2520603038f9c0deccd7c6/vindi%20form.png) ## How to find the API Key? 1. Log in to your account 2. In the menu, select **Settings > Organization Data > Access keys** 3. Generate your private API key Now simply copy and paste the value on the Erathos platform connection form to advance to the next steps. Don't forget to click on **Save and close**! With this connection created you can seemlessly move your Vindi data to your BigQuery, Redshift or Postgres data-warehouse. ## What endpoints can I access with the Erathos platform? * customers * plans * plan\_items * products * payment\_methods * subscriptions * product\_items * periods * period\_usages * bills * charges * transactions * payment\_profiles * invoices * messages * export\_batches * import\_batches * issues * notifications * notification\_items * merchants * roles * affiliates * merchant\_users # Zendesk Find out how to connect Zendesk to your data warehouse effortlessly. ## Using the Erathos platform When selecting Zendesk as a new connector on the Erathos platform, you will need to name your connection and fill in the following form: ![](https://help.erathos.com/rails/active_storage/blobs/redirect/eyJfcmFpbHMiOnsibWVzc2FnZSI6IkJBaHBBZHM9IiwiZXhwIjpudWxsLCJwdXIiOiJibG9iX2lkIn19--d9e3b3e2f142ac7b5c0b29c4e754787a3fe1fd96/zendesk%20form.png) ## How to find the API Token? It may be necessary to enable API token access. To do this: 1. In the Admin Center, click **Apps and Integrations** on the sidebar. 2. Select **APIs > Zendesk API**. 3. In the **Settings** tab, enable API token access. ## To generate the API token: 1. You must be an administrator, and API token access must be enabled in your account. 2. In the Admin Center, click **Apps and Integrations** on the sidebar. 3. Select **APIs > Zendesk API**. 4. Click the **Add API token** button to the right of **Active API Tokens**. 5. The token will be generated and displayed. ## How to find the Domain URL? 1. Go to the **Support Admin** home page. 2. The **Domain URL** will appear in the upper right corner of the screen, as shown below: In this case, the Domain URL would be **yoursubdomain**. ![](https://help.erathos.com/rails/active_storage/blobs/redirect/eyJfcmFpbHMiOnsibWVzc2FnZSI6IkJBaHBBZHc9IiwiZXhwIjpudWxsLCJwdXIiOiJibG9iX2lkIn19--368cc16c38bd2057adf68b79ca894771a6ed1593/zendesk%20url%20domain.png) #### How to find the Username? The username is usually the email you use to log into your Zendesk account. From here, simply copy and paste the information into the Erathos platform and click **Save and close** to advance to the next steps. Once the connector is created, you can create your data pipeline from Zendesk to your data warehouse in BigQuery, Redshift, or Postgres. ## What endpoints can I access with the Erathos platform? * ticket\_fields * organization\_subscriptions * groups * group\_memberships * satisfaction\_ratings * comments * audits * metrics * activities * skips * tickets * suspended\_tickets * users * profiles * events * organizations * organization\_memberships * tickets\_export # Databases # Firebird Find out how to connect Firebird to your data warehouse effortlessly. In this page you will learn how to connect **Firebird** to **Erathos** to move your data seamlessly. The available connections between databases and the Erathos platform are through **Open Connection**, **Static IP** and **SSH tunnel**. {% hint style="info" %} Erathos supports Firebird version 2.0 and higher. {% endhint %} ## Connecting Firebird: 1. Log in to your Erathos account 2. Select Firebird as connector 3. Name your connection 4. Fill in the following form with the required information ![](https://help.erathos.com/rails/active_storage/blobs/redirect/eyJfcmFpbHMiOnsibWVzc2FnZSI6IkJBaHBBZE09IiwiZXhwIjpudWxsLCJwdXIiOiJibG9iX2lkIn19--1ec89188048303271abf7a9666276f2df1348817/firebird%20form.png) On the Advanced config toggle button, you can select which connection you'd like to perform. ![](https://help.erathos.com/rails/active_storage/blobs/redirect/eyJfcmFpbHMiOnsibWVzc2FnZSI6IkJBaHBBZFU9IiwiZXhwIjpudWxsLCJwdXIiOiJibG9iX2lkIn19--13dc0765bce851858f1ef8f97acf8608b3ca9a68/advanced%20config%20firebird.png) In this case, you can only choose between **Open Connection** and **Static IP.** If you choose to connect through Static IP, you will need to follow the instuction below: ![](https://help.erathos.com/rails/active_storage/blobs/redirect/eyJfcmFpbHMiOnsibWVzc2FnZSI6IkJBaHBBZFk9IiwiZXhwIjpudWxsLCJwdXIiOiJibG9iX2lkIn19--df86f4129465181563c0c9ec75f60dacddeb2c5a/IP%20Fixo%20Firebire.png) Don't forget to click on **Save and close** to advance to the next steps of the integration. With this connection created you can seemlessly move your Firebird data to your BigQuery, Redshift or Postgres data-warehouse. # MongoDB Find out how to connect MongoDB to your data warehouse effortlessly. ### Before you begin Make sure you have access to your **MongoDB connection string**. It can be in one of the following formats: **Standard format:** ```python mongodb://username:password@localhost:27017/myDatabase ``` **SRV format (used with MongoDB Atlas):** ```python mongodb+srv://username:password@cluster0.mongodb.net/myDatabase ``` ### How to Fill Out the Connection Form in Erathos Use the details from your connection string to complete the form as follows: | Field | Value | | ------------ | ------------------------------------- | | **DB** | `myDatabase` | | **Host** | `cluster0.mongodb.net` or `localhost` | | **Port** | `27017` | | **User** | `username` | | **Password** | `password` | # MySQL Find out how to connect MySQL to your data warehouse effortlessly. In this page you will learn how to connect **MySQL** to **Erathos** to move your data seamlessly. The available connections between databases and the Erathos platform are through **Open Connection**, **Static IP** and **SSH tunnel**. ## Connecting MySQL: 1. Log in to your Erathos account 2. Select MySQL as connector 3. Name your connection 4. Fill in the following form with the required information ![](https://help.erathos.com/rails/active_storage/blobs/redirect/eyJfcmFpbHMiOnsibWVzc2FnZSI6IkJBaHBBYjg9IiwiZXhwIjpudWxsLCJwdXIiOiJibG9iX2lkIn19--0141d7bbc892fd163d35c018ab8828ac0288b921/mysql%20form.png) On the Advanced config toggle button, you can select which connection you'd like to perform. ![](https://help.erathos.com/rails/active_storage/blobs/redirect/eyJfcmFpbHMiOnsibWVzc2FnZSI6IkJBaHBBY0E9IiwiZXhwIjpudWxsLCJwdXIiOiJibG9iX2lkIn19--e4aa49f32c9efb5103c03f86e5e613bc8ec655e9/SSH%20MySQL.png) If you choose to connect through Static IP, you will need to follow the instuction below: ![](https://help.erathos.com/rails/active_storage/blobs/redirect/eyJfcmFpbHMiOnsibWVzc2FnZSI6IkJBaHBBZFk9IiwiZXhwIjpudWxsLCJwdXIiOiJibG9iX2lkIn19--df86f4129465181563c0c9ec75f60dacddeb2c5a/IP%20Fixo%20Firebire.png) If you choose to connect through SSH Tunnel, you will need to fill in the additional form below: ![](https://help.erathos.com/rails/active_storage/blobs/redirect/eyJfcmFpbHMiOnsibWVzc2FnZSI6IkJBaHBBaEVCIiwiZXhwIjpudWxsLCJwdXIiOiJibG9iX2lkIn19--95ff8235b083b1c88751d5ca3111e682b9c5d141/SSH%20MySQL.png) Don't forget to click on **Save and close** to advance to the next steps of the integration. With this connection created you can seemlessly move your MySQL data to your BigQuery, Redshift or Postgres data-warehouse. # Neo4j Find out how to connect Neo4j to your data warehouse effortlessly. In this page you will learn how to connect **Neo4j** to **Erathos** to move your data seamlessly. The available connections between databases and the Erathos platform are through **Open Connection**, **Static IP** and **SSH tunnel**. ## Connecting Neo4j: 1. Log in to your Erathos account 2. Select Neo4j as connector 3. Name your connection 4. Fill in the following form with the required information
On the Advanced config toggle button, you can select which connection you'd like to perform. If you choose to connect through SSH Tunnel, you will need to fill in the additional form below: With this connection created you can seemlessly move your Neo4j data to your BigQuery, Databricks, Redshift or Postgres data-warehouse. # Oracle Find out how to connect Oracle to your data warehouse effortlessly. # PostgreSQL Find out how to connect PostgreSQL to your data warehouse effortlessly. In this page you will learn how to connect **PostgreSQL** to **Erathos** to move your data seamlessly. The available connections between databases and the Erathos platform are through **Open Connection**, **Static IP** and **SSH tunnel**. ## Connecting PostgreSQL: 1. Log in to your Erathos account 2. Select PostgreSQL as connector 3. Name your connection 4. Fill in the following form with the required information
On the **Advanced Connection Settings**, you can optionally activate connecting through a SSH tunnel by filling in the fields ssh\_host, ssh\_keepalive\_interval, ssh\_password, ssh\_port, and ssh\_user.
When using CDC, the following values may be used in cdc\_snapshot\_mode: * *initial*: performs an initial snapshot, after it completes, streaming following changes from WAL. * *no\_data*: does not perform any snapshots, only streams changes that are currently available on WAL Don't forget to click on **Save and close** to advance to the next steps of the integration. With this connection created you can seemlessly move your PostgreSQL data to your BigQuery, Redshift or Postgres data-warehouse. ### CDC setup In order to enable CDC in your PostgreSQL connection you need to confirm the following settings in your database. The following query should return the values wal\_level = logical, max\_replication\_slots = 10 (or higher) and max\_wal\_senders = 10 (or higher), max\_slot\_wal\_keep\_size ≠ -1 (to safely prevent replication failures from completely filling the database disk, a hard limit should be set based in your database disk size). ```sql SELECT name, setting, short_desc, context FROM pg_settings WHERE name IN ('wal_level', 'max_replication_slots', 'max_wal_senders', 'max_slot_wal_keep_size'); -- If necessary, configuration parameters may be altered with: ALTER SYSTEM SET wal_level = logical; ALTER SYSTEM SET max_replication_slots = 10; ALTER SYSTEM SET max_wal_senders = 10; ALTER SYSTEM SET max_slot_wal_keep_size = '5GB'; ``` {% hint style="warning" %} Important: You must restart the database to apply changes to the settings above. The only exception is max\_slot\_wal\_keep\_size, which supports hot-reloading. {% endhint %} By default each UPDATE/DELETE statement on a given table will not collect the complete before/after state of the affected records, only when set as FULL identity will cdc be able to capture such changes. The queries below can be used the ascertain the replica identity configuration and update it to FULL when necessary. ```sql -- Result Legend -- f = FULL -- d = DEFAULT (Logs only the primary key). -- i = INDEX (Logs the columns covered by a specific unique index). -- n = NOTHING (Logs no information for updates/deletes). SELECT relreplident FROM pg_class WHERE oid = 'your_table_name'::regclass; -- Update table replica identity level ALTER TABLE your_table_name REPLICA IDENTITY FULL; ``` At the database side, the last configuration that needs to be confirmed is whether the credentials being used have the privilege for replication access. ```sql SELECT rolname, rolreplication FROM pg_roles WHERE rolname = 'your_existing_user'; -- If rolreplication is FALSE, then grant privilege with: ALTER ROLE your_existing_user WITH REPLICATION; ``` {% hint style="danger" %} Important: By default, a replication slot will retain an infinite amount of WAL data. You need to set a hard ceiling to prevent a CDC failure from completely consuming your disk space through the max\_slot\_wal\_keep\_size setting. {% endhint %} #### Replication slot removal In order to delete the replication slot when deleting the connection or to free up space in your database disk, use the following queries: ```sql -- Find the exact name of your connection slot by looking up slots starting with 'erathos-cdc' SELECT slot_name FROM pg_replication_slots; -- Check memory retained SELECT slot_name, active, pg_size_pretty(pg_wal_lsn_diff(pg_current_wal_lsn(), restart_lsn)) AS retained_wal FROM pg_replication_slots; -- Drop it to free up space in the database SELECT pg_drop_replication_slot('your_slot_name'); ``` # What is a destination? Explore Erathos destinations Destinations are the target database for your source connectors. They are at workspace level setup, and the 4th step of your onboarding flow. You can edit or add your destination on worspace settings -> Destination
### Can I have multiple destinations? No, our goal is that you centralize your data, not to create a mess with multiple source of truth. 1 workspace is entitled to 1 destination. ### What are the available destinations?
/pages/GPtHyGxdaOlXBosu7OU6
/pages/k4aIpFZdbRqFhrQE7IFp
/pages/1TH0hcfkqucySNmnVwxk
/pages/zYQnUkdgHWWZtIU51Xeu
/pages/GrdqeRLjlbXAVaxPtJc3
/pages/dEuIBSU1qlUW3J1eA8rd
# Azure SQL Server Connect Erathos to Azure SQL Server. To connect to your SQL Server instance (hosted on Azure Cloud), there are some simple preliminary steps to allow your database to be accessible by our platform. ## Setup ### Firewall {% hint style="success" %} Our **IP address** is **35.212.87.86.** {% endhint %} You will need to add Erathos IP address to your firewall whitelist. Navigate to the main page of the chosen SQL Server database and select the **Networking** under the **Security** sidemenu. Ascertain your database is not completely private by selecting **Selected networks** to allow public access for IPs that comply to the firewall rules. Then, add Erathos platform IP as the **Start IPv4 address** and **End IP address** and give a name easy to identify the rule's purpose at a later time. Persist the new firewall rule by clicking **Save** at the bottom of the page.
### Credentials In order to identify the **host address** of your database and the **username** of the server admin you can navigate to the **Overview** sidemenu option of the main page of the selected database, where you can find the credentials under the **Essentials** section.
It is also possible to locate your **host address**, **database port**, **database name** and **admin** **username** by navigating to **Azure SQL Database > SQL databases** and selecting the database you wish to use as your target data warehouse. Inside the database, select **Settings > Connection strings** in the sidemenu to view your credentials.
## Connect to Erathos To connect Erathos to your Azure SQL Server: 1. **Create a New Destination** * Go to **Settings** > **Data Warehouse**. * Select **Azure SQL Server**. 2. **Fill Out the Form** * Input your credentials, such as **Host address**, **Database name**, **Server admin** **password Database port** and **Server admin username**.
3. **Advanced Connection Settings (Optional)** * If you wish to establish your connection through your own server in order to restrict the direct access to the database you may also fill out the ssh credentials form. For more information, please referer to [Databases connection types](/connectors/databases#connection-types). {% hint style="info" %} If you need help connecting to your SQL Server, reach out to our team at . {% endhint %} # BigQuery Connect Erathos to BigQuery. To connect to your Google BigQuery, we recommend creating a new service account exclusively for use by the Erathos platform. This approach follows best practices, as it allows you to assign only the minimal roles needed for this service account and makes it easier to manage and revoke access when necessary. {% hint style="info" %} If you dont have a Google BigQuery, we can host for you. Referer to [Hosted by Erathos](/destinations/what-is-a-destination/bigquery/hosted-by-erathos) {% endhint %} ### Creating a service account To create a service account, follow these steps: 1. **Navigate to the IAM & Admin Section** * From the main menu, go to **IAM & Admin** > **Service Accounts**. 2. **Create a New Service Account** * Click on the **+ CREATE SERVICE ACCOUNT** button. * Provide a **Name** and **Description** for the service account to help identify its purpose, e.g., "Erathos Access Account." 3. **Set Permissions** * On the same screen, assign **roles** to the service account. For minimal access, assign only the following roles needed for Erathos to connect to your BigQuery: * **BigQuery Data Editor.** * **BigQuery Job User.** * **BigQuery Metadata Viewer.** * **BigQuery User.** * Click **Continue**. 4. **Generate a Key for the Service Account** * After creating the service account, locate it in the **Service Accounts** list and click on it. * Go to the **Keys** tab, click **ADD KEY** > **Create new key**. * Select **JSON** as the key type and click **Create** to download the key file. This file is essential for authenticating Erathos with Google BigQuery. {% embed url="" %} ### Connect to Erathos To connect Erathos to your BigQuery: 1. **Create a New Destination** * Go to **Settings** > **Data Warehouse**. * Select **Google BigQuery**. 2. **Fill Out the Form** * Check the box for **Self-hosted.** * Upload the JSON file obtained from the previous step * Select the region where your data will be hosted (if unsure, we recommend using `US`). 3. **Complete the Setup.** {% embed url="" %} {% hint style="info" %} If you need help connecting to your BigQuery, reach out to our team at . {% endhint %} ### Sandbox mode BigQuery Sandbox is a free usage tier that allows you to explore BigQuery without providing billing information. However, it comes with limitations — such as restricted storage, query usage, and no access to features like DML (Data Manipulation Language) operations. **How to Disable Sandbox Mode**\ To disable Sandbox mode, you need to enable billing for your Google Cloud project. 1. Go to the Google Cloud Console. 2. Open your project. 3. Navigate to **Billing** and link a billing account.\ Once billing is enabled, your project will automatically exit Sandbox mode, unlocking full BigQuery functionality. {% hint style="info" %} Enabling billing does **not** mean you will be charged immediately. Google Cloud offers a generous [free tier](https://cloud.google.com/bigquery/pricing#free-tier) for BigQuery, which includes free monthly quotas for storage and queries. As long as your usage stays within these limits, you won’t incur any charges. {% endhint %} # Hosted by Erathos Connect Erathos to a BigQuery. ## Create a hosted BigQuery To connect Erathos to a BigQuery hosted by us, follow these steps: 1. **Create a New Destination** * Go to **Settings** > **Data Warehouse**. * Select **Google BigQuery**. 2. **Fill Out the Form** * Check the box for **Hosted by Erathos.** * Select the region where your data will be hosted (if unsure, we recommend using `US`). 3. **Complete the Setup.** {% embed url="" %} {% hint style="info" %} If you need help connecting to your BigQuery, reach out to our team at . {% endhint %} ## Access BigQuery data When using **BigQuery Studio (BQ Studio)** to access the BigQuery warehouse hosted by Erathos, the email you use within Erathos must be a **Google account email**. If you already have another Google account, you can add that email as a user — see the section on inviting users below for details. Alternatively, you can connect programmatically using a **service account JSON key**: 1. **Via BQ Studio (Web UI):** * Make sure the Erathos email is a valid Google account. * If you use a different Google account, you can **invite that email** as a user—this allows access via BQ Studio using the invited account. 2. **Via Service Account (JSON Key):** * Navigate to the **“Destinations”** section under **Settings**. * In the general configuration of your workspace, go to **destination** and **download the service account JSON key file**.
*** ## Invite additional users To connect invite additional to a BigQuery hosted by Erathos, follow these steps: 1. **Go to Datawarehouse Settings** * Go to **Settings** > **Data Warehouse.** 2. **Invite users by email** * Expand "**Members"** section * Type the desired emails * Click on **Send invite** {% embed url="" %} # ClickHouse Connect Erathos to Clickhouse. You can connect the Erathos platform to any ClickHouse instance, including **ClickHouse Cloud** and **self-hosted deployments**, to leverage its high-performance, column-oriented database capabilities. To connect to your ClickHouse instance, the following information is necessary: Host, Port, Username, and Password. The tutorial below shows you how to obtain these credentials. ### ClickHouse Cloud The easiest way to find your credentials is via your database configuration or the ClickHouse Cloud console. If you are using ClickHouse Cloud: 1. Log into your ClickHouse Cloud console and select your service. 2. Click the Connect button on your service overview page. This will open a panel containing your integration details.
3. Locate your Host (your service URL, which usually ends in `.clickhouse.cloud`).
4. Locate your Port (typically 8443 for HTTPS). 5. Identify your Username (the default is usually `default`). 6. Retrieve your Password, which was generated when you initially created the service. {% hint style="info" %} For security reasons, ClickHouse Cloud only displays the password once upon service creation. If you do not have it saved, you must go to your service settings to reset the password. Confirm you have copied and pasted the new password somewhere safe before proceeding. {% endhint %} ### Self-Hosted ClickHouse If you are using a self-hosted ClickHouse deployment (VM, Kubernetes, Docker or any other environment), obtain the following information from your server configuration or your database administrator: * **Host**: The hostname or IP address of your ClickHouse server. * **Port**: The port exposed by your ClickHouse server (commonly `8123` for HTTP or `8443` for HTTPS, depending on your configuration). * **Username**: A ClickHouse user with the required permissions. * **Password**: The password associated with that user. Make sure your ClickHouse instance is reachable from the Erathos platform and that any required firewall or network rules allow the connection. {% hint style="info" %} Include our IP address (**35.212.87.86**) to your firewall’s whitelist. {% endhint %} ### Connect to Erathos To connect Erathos to your ClickHouse database: 1. Create a New Destination: Go to Settings > Destination and select ClickHouse. 2. Input db\_host: Paste the Host URL copied from your connection panel. 3. Input db\_port: Enter your designated port (e.g., 8443). 4. Input db\_username: Enter your database username. 5. Input db\_password: Enter your database password. 6. Complete the Setup: Save the configuration to finalize the connection. {% hint style="info" %} If you need help connecting to your ClickHouse database, reach out to our team at [support@erathos.com](https://www.google.com/search?q=mailto%3Asupport%40erathos.com). {% endhint %} --- [Next Page](/llms-full.txt/1)