The Lyftron Provider for Copper offers the most natural way to access Copper data from Lyftron with ease and also enables to connect with BI, MDM & ML tools, Data warehouses, Databases and other SAAS based applications with zero code and zero infrastructure requirements. The provider wraps the complexity of accessing Copper data into easy-to-integrate relational fully managed ANSI Sql format. Make faster and better business decisions with Lyftron’s Copper data provider and automatically build your data migration pipelines in minutes, not months
The provider hides the complexity of accessing data and provides additional powerful security features, smart caching, batching, socket management, and more.
- Comprehensive Delta load mechanism.
- Real-time access to Copper.
- Comprehensive full support of ANSI Sql to query data with ease.
- Collaborative query processing.
The user must have credentials for Copper, Lyftron and your destination data warehouse, lake or database to perform the data pipeline operation with Lyftron
Step1: Setup Copper account
1.1 Create account in Copper and login
1.2. After Login go to -> Integration and click on -> Api key and generate new API key
Establishing a Connection with Lyftron's Quickstart Steps
Create your Copper connection with Lyftron by following the easy steps show below:
Step2 : Login to Lyftron
Start creating your connection
2.1 Click on Connect section on the left panel → Click on Add Connection button Choose your provider -> Type Copper in search bar
Step2.2. Enter your connection details
In the Connection String section enter the values of the below parameters. The following connection string is required to establish Copper connection with Lyftron.Profile=Copper;ProfileSettings='UserEmail=[your_emailID];APIKey=[your_apikey];'
Give connection name as Copper -> Replace “your_api_key” with CopperAPI-key , and replace "firstname.lastname@example.org" with your email address associate with Copper account, click on test connection -> click save. If connection is not successful so, check the error
|Connection Name||Enter your connection details||Required|
|UserEmail||your Copper email@example.com;||Required|
|APIKey||your Copper api_key||Required|
|Logfile**||Use the logfile option to debug your job and provide your connection name to generate the log file. [ConnectionConfigurationPath]\Connection_name_log.tx||Optional|
|Verbosity**||Choose verbosity 1-5 based on the severity of debugging||Optional|
** For more information, check the Lyftron logging and debugging section.
If you want more detailed information about how to establish a connection with Lyftron, click on Lyftron Connection Quick Start guide.
Once you are done entering your connection details, simply click on the Test Connection button to test the connectivity. In case your connection fails, add Logfile and Verbosity parameters and check the Lyftron logging and debugging section, to debug the error.
Save your connection
Step3 : Normalize
Create data source
After establishing connection, datasource metadata import is needed and for that Lyftron automatically normalize your API & different SQL dialects data into ANSI SQL format and also gives you API sources into simple, code less out of the box data model.
3.1 Click on Normalize section from the left panel -> Click on Add Data Source button, Enter data source name -> Choose Copper from the existing connection list -> Click next
3.2 Choose the table you want to import and -> Click Create
The provider models the data in APIs into a list of tables that can be queried using standard SQL statements.
Generally, querying APIs tables is the same as querying a table in a relational database. Sometimes there are special cases, for example, including a certain column in the WHERE clause might be required to get data for certain columns in the table. This is typically needed for situations where a separate request must be made for each row to get certain columns.
|Account||Tables||Fetch Account Details|
|Activities||Tables||Fetch an Activity by ID|
|ActivityTypes||Tables||List Activity Types|
|Companies||Tables||Fetch a Company by ID|
|CompanyActivities||Tables||See a Company's Activities|
|ConnectFields||Tables||List the connections on specified entity|
|ContactTypes||Tables||List Contact Types|
|CustomActivityTypes||Tables||List All Custom Activity Types|
|CustomerSources||Tables||List Customer Sources|
|CustomFields||Tables||List Custom Field Definitions|
|LeadActivities||Tables||See a Lead's Activities|
|Leads||Tables||Fetch a Lead by ID|
|LeadStatuses||Tables||List Lead Statuses|
|LossReasons||Tables||List Loss Reasons|
|Opportunities||Tables||Fetch an Opportunity by ID|
|People||Tables||Fetch a Person by ID|
|PeopleActivities||Tables||See a Person's Activities|
|PipelineStages||Tables||List Pipeline Stages|
|Projects||Tables||Fetch a Project by ID|
|RelatedItems||Tables||View all records related to an Entity|
|Tasks||Tables||Fetch a Task by ID|
|Users||Tables||Fetch User by ID|
|Webhooks||Tables||List all subscriptions|
Step 4: Analyze
Querying the data source data
Lyftron allows you to query the source data by simply writing the ANSI Sql query. Please keep in mind as the data is coming directly from API so, there’s a limit to API calls and performance delay from the Stripe API side which Lyftron can’t control so, don’t expect to pull millions of records in just fraction of seconds. If you have heavy data loads, create the pipeline to unload that data into the Lyftron warehouse and query from it.
4.1. Click on the analyze section on the left panel -> Choose data source from the list, Drag and drop the table -> Choose your querying options
4.2. Click on -> EXECUTE and selected query will return data successfully