Used for sourcing data from Microsoft Access
This connection type supports the following task types:
This connection can be used in a Data Migration.
Usable as Source | Usable as Target | Usable as Incremental Source | Usable as Incremental Target |
---|---|---|---|
✔ | ❌ | ✔ | ❌ |
Template Name | Description |
---|---|
Access | The standard connection string for Access, uses DataSource |
Aconex is a project management tool, predominately used for mail organisation. It is used to import mail data and metadata through our data migration task type.
This connection type supports the following task types:
This connection can be used in a Data Migration.
Usable as Source | Usable as Target | Usable as Incremental Source | Usable as Incremental Target |
---|---|---|---|
✔ | ❌ | ✔ | ❌ |
The Aconex API is extremely throttled especially with concurrent requests. If you are experiencing connection dropouts during Data Migrations of multiple tables it’s recommended that you either turn off parallel data migrations or lower the degree of parallelism.
Template Name | Description |
---|---|
Aconex | Requires an Aconex Username and Password, as well as an application key and host. |
Used for migrating Data in and out of AWS’ NoSQL & Big Data DynamoDB
This connection type supports the following task types:
This connection can be used in a Data Migration.
Usable as Source | Usable as Target | Usable as Incremental Source | Usable as Incremental Target |
---|---|---|---|
✔ | ✔ | ✔ | ❌ |
Template Name | Description |
---|---|
Amazon DynamoDB | The standard connection string for DynamoDB, uses Access Key, Secret Key, Domain and Region. |
Used for migrating data in and out of AWS’ Simple Storage Service (S3) Buckets.
This connection type supports the following task types:
This connection can be used in a Data Migration.
Usable as Source | Usable as Target | Usable as Incremental Source | Usable as Incremental Target |
---|---|---|---|
✔ | ✔ | ❌ | ❌ |
Used for executing scripts on the Azure Batch service.
This connection type supports the following task types:
Learn how to create an Azure Batch Account in the Azure Portal in the Azure Documentation Quickstart.
The fields for the Azure Batch Account connection can be found easily in the “Keys” section of the Azure Resource.
Used for connecting to Azure Blob Containers.
This connection type supports the following task types:
This connection can be used in a Data Migration.
Usable as Source | Usable as Target | Usable as Incremental Source | Usable as Incremental Target |
---|---|---|---|
✔ | ✔ | ❌ | ❌ |
Used as a flexible, secure means of integrating Loome Integrate with Azure Products and Services.
This connection type supports the following task types:
To create an Azure Enterprise Application Registration for usage in Loome Integrate:
Search for App Registrations in Azure Portal
Create a new Application Registration
Fill out the form, giving the app a meaningful name, setting the type to “Web App / API” and putting the Loome Integrate URL as the sign-on URL.
Copy the “Application Id” as this is the same “Application Id” required in your Loome Integrate connection, then click settings.
Open the “Keys” blade, create a new Password and save. The value that you are prompted to copy is the “Password” used in your connection.
Click the directory icon on the top right of the Portal, copy the ID of your current directory (cirecled in red). This is your “Tenant ID” for your new connection.
Type “Subscriptions” in the search bar, open the subscriptions page and copy the subscription ID for the resources you wish to access. This is the “Subscription ID” for your new connection. To ensure your application is able to easily list resources it can use in Loome Integrate, open up Access Control and give the newly created application “Reader” permissions.
Once you have filled out all the fields you now have a direct connection to your Azure Subscription through that app registration.
You will need to assign that application “Contributor” permissions to the resources it needs to use. Learn more about Azure Active Directory permissions here.
A connector used for importing data to and from Azure Data Lake Storage Gen2.
This connection type supports the following task types:
This connection can be used in a Data Migration.
Usable as Source | Usable as Target | Usable as Incremental Source | Usable as Incremental Target |
---|---|---|---|
✔ | ✔ | ❌ | ✔ |
Template Name | Description |
---|---|
Azure Data Lake Storage Gen2 | The standard connection string for Azure Data Lake Storage Gen2, that also requires an Account Access Key. |
Used as a flexible, secure means of integrating Loome Integrate with Azure Table Storage.
This connection type supports the following task types:
This connection can be used in a Data Migration.
Usable as Source | Usable as Target | Usable as Incremental Source | Usable as Incremental Target |
---|---|---|---|
✔ | ✔ | ❌ | ❌ |
Template Name | Description |
---|---|
Azure Storage | The standard connection string for Azure Tables. Uses AccessKey and Account. |
Used for importing Data from Bing Ads.
This connection type supports the following task types:
This connection can be used in a Data Migration.
Usable as Source | Usable as Target | Usable as Incremental Source | Usable as Incremental Target |
---|---|---|---|
✔ | ❌ | ❌ | ❌ |
Used for Importing Data from the Bing Search Cognitive Services.
Refer to Connection Notes for how to import data from Bing Search using Query as a Source.
This connection type supports the following task types:
This connection can be used in a Data Migration.
Usable as Source | Usable as Target | Usable as Incremental Source | Usable as Incremental Target |
---|---|---|---|
✔ | ❌ | ❌ | ❌ |
Bing Search requires a Microsoft Cognitive Services application which can be created in the Azure Portal.
The Api Key is used in the Connection String
You must use Query as a source and provide a search using the SearchTerm column eg:
When using the Target filter feature with Bing Search, you must first apply the target filter ‘SearchTerms’. You can then add other filters to refine your data. Learn more about Target Filters here.
Used for importing Data from Apache Cassandra.
This connection type supports the following task types:
This connection can be used in a Data Migration.
Usable as Source | Usable as Target | Usable as Incremental Source | Usable as Incremental Target |
---|---|---|---|
✔ | ❌ | ✔ | ❌ |
Template Name | Description |
---|---|
Apache Cassandra | The standard connection string for Cassandra, uses Database, Port and Server. |
Used for importing data from Couchbase.
This connection type supports the following task types:
This connection can be used in a Data Migration.
Usable as Source | Usable as Target | Usable as Incremental Source | Usable as Incremental Target |
---|---|---|---|
✔ | ❌ | ✔ | ❌ |
Template Name | Description |
---|---|
Couchbase Server | The standard connection string for Couchbase, uses User, Password and Server |
Used for interacting with an Azure or AWS hosted Databricks instance.
This connection type supports the following task types:
This connection can be used in a Data Migration.
Usable as Source | Usable as Target | Usable as Incremental Source | Usable as Incremental Target |
---|---|---|---|
❌ | ✔ | ❌ | ❌ |
Databricks connection do not require a typical connection string, instead it requires just the hostname of the URL you use to access the Databricks UI.
The Access token for Databricks can be generated using the following tutorial.
Used for importing Data from Microsoft Dynamics CRM.
This connection type supports the following task types:
This connection can be used in a Data Migration.
Usable as Source | Usable as Target | Usable as Incremental Source | Usable as Incremental Target |
---|---|---|---|
✔ | ❌ | ❌ | ❌ |
Template Name | Description |
---|---|
Microsoft Dynamics CRM | The standard connection string for Dynamics CRM, uses basic authentication with a username and password. |
It is highly recommended that for the Dynamics CRM connector you create a designated service account for Loome Integrate as this will avoid the potential of having any actual user information passed through Loome Integrate.
Currently Loome Integrate does not support including the user information through the secure user-password inputs, this feature is coming soon.
Used for importing data from Excel (.xls/.xsls
) files.
This connection type supports the following task types:
This connection can be used in a Data Migration.
Usable as Source | Usable as Target | Usable as Incremental Source | Usable as Incremental Target |
---|---|---|---|
✔ | ❌ | ❌ | ❌ |
Template Name | Description |
---|---|
Excel Files | The standard Excel connection string which imports data from a file located at the provided path. |
.csv
and other flat file formats, see how to use File Definitions.Used for importing Data from the Facebook Application using OAuth.
This connection type supports the following task types:
This connection can be used in a Data Migration.
Usable as Source | Usable as Target | Usable as Incremental Source | Usable as Incremental Target |
---|---|---|---|
✔ | ❌ | ❌ | ❌ |
A Developer Application can be created here: https://developers.facebook.com
For the OAuth Connection, the Client ID for Facebook is your App ID. While your Client Secret is your App Secret.
Add the Generated Redirect URI to Facebook.
Add the following to the Connection String InitiateOauth=OFF;Target=YOUR_TARGET_ID
Currently there is no way to refresh the Facebook Token automatically so you will need to reauthorize your Facebook Connection every 90 Days.
Used for importing file structure and from an FTP server.
This connection type supports the following task types:
This connection can be used in a Data Migration.
Usable as Source | Usable as Target | Usable as Incremental Source | Usable as Incremental Target |
---|---|---|---|
✔ | ❌ | ❌ | ❌ |
Connector for Google AdWords. Provides easy access to Google AdWords data, including Campaigns, AdGroups, Performance and more.
This connection type supports the following task types:
This connection can be used in a Data Migration.
Usable as Source | Usable as Target | Usable as Incremental Source | Usable as Incremental Target |
---|---|---|---|
✔ | ❌ | ❌ | ❌ |
Template Name | Description |
---|---|
Google AdWords | OAuth Access Token, Developer Token, Client Customer |
Used for importing data from Google Analytics. Requires the additional configuration of an OAuth application.
This connection type supports the following task types:
This connection can be used in a Data Migration.
Usable as Source | Usable as Target | Usable as Incremental Source | Usable as Incremental Target |
---|---|---|---|
✔ | ❌ | ❌ | ❌ |
All Google based connection types utilise additional connection security, learn more here.
Strict security rules around the usage of Google Applications means that you may need to verify your application with Google before you use it.
A connector used for importing data to and from Google BigQuery.
This connection type supports the following task types:
This connection can be used in a Data Migration.
Usable as Source | Usable as Target | Usable as Incremental Source | Usable as Incremental Target |
---|---|---|---|
✔ | ✔ | ❌ | ❌ |
Template Name | Description |
---|---|
Google BigQuery | The standard connection string for Google BigQuery, that also requires an authentication file. |
A connector used to import data to and from Google Cloud Storage Bucket.
This connection type supports the following task types:
This connection can be used in a Data Migration.
Usable as Source | Usable as Target | Usable as Incremental Source | Usable as Incremental Target |
---|---|---|---|
✔ | ✔ | ❌ | ❌ |
Template Name | Description |
---|---|
Google Cloud Storage Bucket | The standard connection string for Google Cloud Storage Bucket, requires bucket url and credentialfile. |
To connect to Google Cloud Storage Bucket, you will need to create a GCP Service Account and retrieve a Credential File. Learn more about creating a credential file here.
To retrieve the url
, you can get it from the Link for gsutil section of the bucket overview.
Some table names including special characters such as ‘$’ and ‘.’ may not work with Google Cloud Storage Buckets as they cannot be safely expressed as a URI on Google Cloud Platform.
Used for importing data from HBase.
This connection type supports the following task types:
This connection can be used in a Data Migration.
Usable as Source | Usable as Target | Usable as Incremental Source | Usable as Incremental Target |
---|---|---|---|
✔ | ❌ | ✔ | ❌ |
Template Name | Description |
---|---|
Apache HBase | The standard connection string for HBase, uses Server and Port. |
Used for migrating data from various sources into the Hadoop File System over WebHDFS.
This connection type supports the following task types:
This connection can be used in a Data Migration.
Usable as Source | Usable as Target | Usable as Incremental Source | Usable as Incremental Target |
---|---|---|---|
❌ | ✔ | ❌ | ❌ |
Template Name | Description |
---|---|
Hadoop | The standard connection string for HDFS using WebHDFS. |
WebHDFSPort=50070;
.Used for running Hive SQL statements on a Hadoop instance.
This connection type supports the following task types:
Template Name | Description |
---|---|
Hive (Default Security) | The default connection string for Hive using Host and DefaultSecurityUser |
Hive (Kerberos) | The Kerberos Credentials connection for Hive using Host. |
Used for importing Data from HPCC.
This connection type supports the following task types:
This connection can be used in a Data Migration.
Usable as Source | Usable as Target | Usable as Incremental Source | Usable as Incremental Target |
---|---|---|---|
✔ | ❌ | ❌ | ❌ |
Template Name | Description |
---|---|
HPCC Systems | The Standard Connection for HPCC uses URL, User, Password, Version and Cluster. |
Used for pulling in Marketing & CRM data from a HubSpot instance.
HubSpot uses the OAuth Authentication standard. Additional Security required when using HubSpot. A Modal will display when generating a HupSpot connection asking for Client ID & Client Secret.
Unlike other OAuth based connections, Hubspot does not require a redirect URI so there is no need to generate one in Loome Integrate Online.
This connection type supports the following task types:
This connection can be used in a Data Migration.
Usable as Source | Usable as Target | Usable as Incremental Source | Usable as Incremental Target |
---|---|---|---|
✔ | ❌ | ❌ | ❌ |
Template Name | Description |
---|---|
HubSpot Standard | Standard OAuth refresh connection String |
The username and password fields are the same fields you’d use to log into HPCC.
The only required scope for a Loome Integrate HubSpot account is “Basic OAuth Functionality” as Loome Integrate Online will automatically ask for all possible scopes associated with an account.
Json Standard for pulling in Data from the JSON format.
This connection type supports the following task types:
This connection can be used in a Data Migration.
Usable as Source | Usable as Target | Usable as Incremental Source | Usable as Incremental Target |
---|---|---|---|
✔ | ❌ | ❌ | ❌ |
Template Name | Description |
---|---|
JSON | The Standard JSON Connection Type |
The Connector importing data from JIRA.
This connection type supports the following task types:
This connection can be used in a Data Migration.
Usable as Source | Usable as Target | Usable as Incremental Source | Usable as Incremental Target |
---|---|---|---|
✔ | ✔ | ❌ | ❌ |
Template Name | Description |
---|---|
JIRA | The standard JIRA Connection String |
Used for connecting to a Hadoop cluster’s Spark instance so that Loome Integrate can execute Spark jobs remotely.
This connection type supports the following task types:
Like with Databricks and Azure Blob, the Livy connection type does not require a typical connection string and instead only needs the host URL of your Hadoop cluster.
If you require Kerberos/SPNEGO authentication you will need to provide the username and domain of the Kerberos user to impersonate.
Marketing Automation platform that helps you share email.
This connection type supports the following task types:
This connection can be used in a Data Migration.
Usable as Source | Usable as Target | Usable as Incremental Source | Usable as Incremental Target |
---|---|---|---|
✔ | ❌ | ❌ | ❌ |
Template Name | Description |
---|---|
MailChimp | The Standard connection uses an APIKey that Mail Chimp Provides. |
Used to import marketing data from Marketo.
This connection type supports the following task types:
This connection can be used in a Data Migration.
Usable as Source | Usable as Target | Usable as Incremental Source | Usable as Incremental Target |
---|---|---|---|
✔ | ❌ | ✔ | ❌ |
Template Name | Description |
---|
Marketo | The connection string will require OAuth Client ID and Client Secret, as well as your Web Services REST API Endpoint.
Used for connection to Microsoft Graph API that enables you to access Microsoft Cloud service resources.
This connection type supports the following task types:
This connection can be used in a Data Migration.
Usable as Source | Usable as Target | Usable as Incremental Source | Usable as Incremental Target |
---|---|---|---|
✔ | ❌ | ❌ | ❌ |
Microsoft Graph | The Standard connection used an Client ID, Client Secret & Tenant Name.
You will need an App Registration with Default Client Type to Public. You will need a redirect URI of type Public client/native.
You will need to generate a Client Secret. You will need to add API Permissions for Microsoft.Graph of type Application for the following:
Used for working with Microsoft SQL Server, works with both On-Premise and Azure Hosted SQL Server instances.
This connection type supports the following task types:
This connection can be used in a Data Migration.
Usable as Source | Usable as Target | Usable as Incremental Source | Usable as Incremental Target |
---|---|---|---|
✔ | ✔ | ✔ | ✔ |
Template Name | Description |
---|---|
SQL Server Standard | The standard connection string for connecting to a SQL Server instance on the same server as the Agent, uses integrated SSPI security. |
SQL Server SSAS | Uses SSAS to connect to a SQL Server instance. |
SQL Server Trusted | Uses trusted security to connect to a SQL Server instance. This requires the agent to be running as a trusted account. |
SQL Azure Standard | Uses the Azure standard URL naming convention to connect to SQL Server. |
The connection strings used by this connection are standard ADO.NET connection strings.
You can use Visual Studio to easily generate or find a connection string for a connected SQL Server.
Used for MSGen tasks
This connection type supports the following task types:
Connection used for importing into and out of MongoDB.
This connection type supports the following task types:
This connection can be used in a Data Migration.
Usable as Source | Usable as Target | Usable as Incremental Source | Usable as Incremental Target |
---|---|---|---|
✔ | ✔ | ❌ | ❌ |
Template Name | Description |
---|---|
MongoDB | The Standard Connection for MongoDB that uses Server, Port, Database, User and Password. |
Used for sourcing data from MYOB AccountRight.
Loome Integrate Online only supports MYOB AccountRight desktop at this current time.
This connection type supports the following task types:
This connection can be used in a Data Migration.
Usable as Source | Usable as Target | Usable as Incremental Source | Usable as Incremental Target |
---|---|---|---|
✔ | ❌ | ❌ | ❌ |
Due to the schema of MYOB AccountRight’s tables, it’s highly recommended that target connections for MYOB AccountRight include some form of JSON parsing capabilities. For SQL Server, versions later than 2016 support JSON parsing using the built in JSON functions.
Template Name | Description |
---|---|
MYOB AccountRight Local | The standard connection string for connecting to MYOB AccountRight desktop instances. |
The username and password fields are the same fields you’d use to log in to MYOB AccountRight.
You may need to manually install the MYOB AccountRight API connector, learn more here..
If you don’t know what your host is and MYOB AccountRight is installed on the same computer as the agent, your connection string will be host=http://localhost:8080/accountright/;
.
Used for sourcing data from a MySQL server.
This connection type supports the following task types:
This connection can be used in a Data Migration.
Usable as Source | Usable as Target | Usable as Incremental Source | Usable as Incremental Target |
---|---|---|---|
✔ | ❌ | ✔ | ❌ |
Template Name | Description |
---|---|
MySQL | The standard MySQL connection string. |
3306
.Used for sourcing data from NationBuilder.
This connection type supports the following task types:
This connection can be used in a Data Migration.
Usable as Source | Usable as Target | Usable as Incremental Source | Usable as Incremental Target |
---|---|---|---|
✔ | ❌ | ❌ | ❌ |
Template Name | Description |
---|---|
NationBuilder | The standard NationBuilder connection string. |
Used for importing data from an OData service.
This connection type supports the following task types:
This connection can be used in a Data Migration.
Usable as Source | Usable as Target | Usable as Incremental Source | Usable as Incremental Target |
---|---|---|---|
✔ | ❌ | ❌ | ❌ |
Template Name | Description |
---|---|
OData (No Authentication) | The standard OData connection string for working with unauthenticated endpoints. |
OData (Basic Authentication) | The OData connection string for working with Basic/Digest authentication. |
OData (Authorization Header) | The OData connection string for working with endpoints secured by tokens passed in the Authorization header. |
CustomHeaders
property can be done by separating each header: value
with a new line.Used for connecting to a wide range of data sources over an ODBC DSN.
This connection type supports the following task types:
This connection can be used in a Data Migration.
Usable as Source | Usable as Target | Usable as Incremental Source | Usable as Incremental Target |
---|---|---|---|
✔ | ❌ | ✔ | ❌ |
Template Name | Description |
---|---|
ODBC | Uses the provided DSN name to connect over ODBC to the data source. |
The ODBC connection requires some additional configuration on the Agent host as a DSN must be configured before attempting to use the connection.
DSN’s should be configured at a System Level for best results.
Recommend DSN Configuration Guides
Used for sourcing data from a PostgreSQL
This connection type supports the following task types:
This connection can be used in a Data Migration.
Usable as Source | Usable as Target | Usable as Incremental Source | Usable as Incremental Target |
---|---|---|---|
✔ | ❌ | ✔ | ❌ |
Template Name | Description |
---|---|
PostgreSQL | The Standard Connection for PostgreSQL that uses Server, Port, Database, User and Password. |
Used for sourcing data from Sage 50
This connection type supports the following task types:
This connection can be used in a Data Migration.
Usable as Source | Usable as Target | Usable as Incremental Source | Usable as Incremental Target |
---|---|---|---|
✔ | ❌ | ❌ | ❌ |
Template Name | Description |
---|---|
Sage 50 UK | The standard connection string for working with a Sage 50 UK application. |
Used for importing data from a Salesforce service.
This connection type supports the following task types:
This connection can be used in a Data Migration.
Usable as Source | Usable as Target | Usable as Incremental Source | Usable as Incremental Target |
---|---|---|---|
✔ | ❌ | ❌ | ❌ |
Template Name | Description |
---|---|
Salesforce | Standard User, Password and the Security Token |
Used for sourcing data from Salesforce Chatter
This connection type supports the following task types:
This connection can be used in a Data Migration.
Usable as Source | Usable as Target | Usable as Incremental Source | Usable as Incremental Target |
---|---|---|---|
✔ | ❌ | ❌ | ❌ |
Used for importing data from Salesforce Marketing Cloud.
This connection type supports the following task types:
This connection can be used in a Data Migration.
Usable as Source | Usable as Target | Usable as Incremental Source | Usable as Incremental Target |
---|---|---|---|
✔ | ❌ | ❌ | ❌ |
Template Name | Description |
---|---|
Salesforce Marketing Cloud | Used for setting the instance of Marketing Cloud that is being targeted, that is S10 by default. |
Username and Password are that of the Salesforce Marketing Account API user you wish to login as.
The account used for the connection must have the API User setting enabled:
Loome Integrate Online only performs read operations on Salesforce Marketing Cloud and will never modify or add any data to the instance.
Used for importing Data from SAP.
This connection type supports the following task types:
This connection can be used in a Data Migration.
Usable as Source | Usable as Target | Usable as Incremental Source | Usable as Incremental Target |
---|---|---|---|
✔ | ❌ | ❌ | ❌ |
Template Name | Description |
---|---|
SAP NetWeaver | The Standard connection string requires Host, User, Password, Client, System Number, ConnectionType and Location. |
Used for importing Data from the SharePoint.
This connection type supports the following task types:
This connection can be used in a Data Migration.
Usable as Source | Usable as Target | Usable as Incremental Source | Usable as Incremental Target |
---|---|---|---|
✔ | ❌ | ❌ | ❌ |
Template Name | Description |
---|---|
MicrosoftSharePoint (On-premise & Online) | The Standard connection string requires User, Password, Auth Scheme, URL |
Used for working with Snowflake data warehouse.
This connection type supports the following task types:
This connection can be used in a Data Migration.
Usable as Source | Usable as Target | Usable as Incremental Source | Usable as Incremental Target |
---|---|---|---|
✔ | ✔ | ✔ | ✔ |
Template Name | Description |
---|---|
Snowflake | The standard Snowflake connection string-requires details such as the host, account, role, database and warehouse to connect to. |
The username and password fields for this connection type should be your Snowflake Data Warehouse credentials.
The role of your account should be provide when creating the connection, if it’s not known the default will be set to public.
When using the connection string the YOUR_FULL_HOST can contain your YOUR_ACCOUNT values as shown below:
Conection String Template:
"account=YOUR_ACCOUNT;host=YOUR_FULL_HOST.snowflakecomputing.com;role=PUBLIC;db=YOUR_DATABASE;"
"account=Perspective;host=perspective.ap-southeast-2.snowflakecomputing.com;role=PUBLIC;db=DEMO_WH;WAREHOUSE=DEMO_WH"
"account=readeraccount01;host=perspective.ap-southeast-2.snowflakecomputing.com;role=PUBLIC;db=DGDatabase;WAREHOUSE=DEMO_WH"
Snowflake Data Migrations require a staging connection and staging file definition that is a blob based connection such as Azure Blob and a blob file definition respectively.
When performing a Data Migration from a Snowflake Source to a different Snowflake Target it will require a staging connection or internal staging. SnowSQL is required to be installed on the same host as the Agent if you wish to perform internal staging.
Learn more about Snowflake Data Warehouse here.
When using an internal stage for Snowflake connections users will have to install SnowSQL. Users will also have to restart their Agent if they install SnowSQL in an existing running Agent.
Used for importing data from a Sugar CRM instance.
This connection type supports the following task types:
This connection can be used in a Data Migration.
Usable as Source | Usable as Target | Usable as Incremental Source | Usable as Incremental Target |
---|---|---|---|
✔ | ❌ | ❌ | ❌ |
Template Name | Description |
---|---|
Sugar CRM | The default connection string for Sugar CRM. |
It is highly recommended that for the Sugar CRM Connection you create a designated service account for Loome Integrate as this will avoid the potential of having any actual user information passed through Loome Integrate.
Currently Loome Integrate does not support including the user information through the secure user-password inputs, this feature is coming soon.
Used for importing Data from the Square.
This connection type supports the following task types:
This connection can be used in a Data Migration.
Usable as Source | Usable as Target | Usable as Incremental Source | Usable as Incremental Target |
---|---|---|---|
✔ | ❌ | ❌ | ❌ |
Used for importing Data from an RSS.
This connection type supports the following task types:
This connection can be used in a Data Migration.
Usable as Source | Usable as Target | Usable as Incremental Source | Usable as Incremental Target |
---|---|---|---|
✔ | ❌ | ❌ | ❌ |
Template Name | Description |
---|---|
RSS | The standard connection string for working with a xBase, uses a URL |
Used for importing Data from xBase.
This connection type supports the following task types:
This connection can be used in a Data Migration.
Usable as Source | Usable as Target | Usable as Incremental Source | Usable as Incremental Target |
---|---|---|---|
✔ | ❌ | ❌ | ❌ |
Template Name | Description |
---|---|
XBase | The standard connection string for working with a xBase, uses a Data Source, Include Files. |
Used for importing data from a Xero instance, includes support for Xero Payroll.
This connection type supports the following task types:
This connection can be used in a Data Migration.
Usable as Source | Usable as Target | Usable as Incremental Source | Usable as Incremental Target |
---|---|---|---|
✔ | ❌ | ❌ | ❌ |
Template Name | Description |
---|---|
XERO Standard | The standard connection string for working with a XERO private application. |
Xero Payroll Australia | The connection string for querying payroll data in an Australian based XERO Private application. |
Xero Payroll USA | The connection string for querying payroll data in a United States based XERO Private application. |
Due to limitations in the XERO connector utilised by Loome Integrate Online, you must create separate Xero connections if you wish to import data from both the standard and payroll Xero connections.
To setup Loome Integrate with Xero, you will need to create an OAuth 2 Application in Xero Developers.
First step to creating a Xero App is to signup for a developer account at https://developer.xero.com/myapps/, once you’ve signed up you will be able to create a New App from the “My Apps” page.
In the provided form, fill out details that are applicable to your institution. For the OAuth 2 redirect URI you can provide a fake value as we’ll be modifying this later.
Once the new Xero app is created, you will be redirected to the app’s management page. Scroll down and you will see the Client Id and the option to generate a Client Secret. Copy both the Client Id and newly created Client Secret, save them somewhere secure as you will need them in Loome Integrate.
Open up Loome Integrate and navigate to the connections page. If you are updating an existing Xero connnection edit it and click the “Manage Additional Security” button. If you are creating a new connection, simply create a new connection and select “Xero 2019” as the type. You will be prompted with a screen which asks for you Client Id and Secret, insert them into the form and then click the “Generate Redirect URI” button.
Copy the value of the Redirect URI and open up the Xero Developers tab again, you will need to replace the previous redirect URI with the one generated by Loome Integrate. Save your Xero app and return to Loome Integrate.
In Loome Integrate click “Authorize” at the bottom of the popup, a tab will open that redirects you to Xero for a login.
You will need to give Loome Integrate access to the organization you want to import data from, once you approve the Organisation you will be asked to close the window as Authorisation is successful.
Once you return to Loome Integrate, you will be notified that authorisation was successful.
Once you proceed to the next page of the Connection wizard, you can specify the schema to import using the Connection string.
Xero Data Type/Product | Connection String |
---|---|
Accounting Data | Schema=Accounting; |
Assets Data | Schema=Assets; |
Payroll (Australia) Data | Schema=PayrollAUS; |
Files Data | Schema=Files; |
Project Data | Schema=Projects; |
If the connection string is left blank, Xero will default to using the Accounting schema.
Once you have added the required connection string, click submit. You now have a Xero OAuth 2 connection.
Used for Importing Data from XML
This connection type supports the following task types:
This connection can be used in a Data Migration.
Usable as Source | Usable as Target | Usable as Incremental Source | Usable as Incremental Target |
---|---|---|---|
✔ | ❌ | ❌ | ❌ |
Template Name | Description |
---|---|
XML | The standard connection string for working with a XML, uses a GenerateSchemaFiles, XPath, URI and Location |
YouTube Analytics uses the OAuth authentication standard. You can use the OAuth credentials embedded in the provider or you can register an application with Google to obtain you own.
This connection type supports the following task types:
This connection can be used in a Data Migration.
Usable as Source | Usable as Target | Usable as Incremental Source | Usable as Incremental Target |
---|---|---|---|
✔ | ❌ | ❌ | ❌ |
YouTube uses the OAuth Authentication. Additionally, set the Callback URL property. Set the OAuth Properties (OAuth Client ID and OAuth Client Secret), Developer Token and ClientCustomerID.
This connection type supports the following task types:
This connection can be used in a Data Migration.
Usable as Source | Usable as Target | Usable as Incremental Source | Usable as Incremental Target |
---|---|---|---|
✔ | ❌ | ❌ | ❌ |
This Zoho connection allows developers to migrate data from Zoho CRM.
This connection type supports the following task types:
This connection can be used in a Data Migration.
Usable as Source | Usable as Target | Usable as Incremental Source | Usable as Incremental Target |
---|---|---|---|
✔ | ❌ | ❌ | ❌ |
Template Name | Description |
---|---|
Zoho CRM | Standard AuthToken used for Zoho CRM 2018 Configuration |
Used for migrating data from Zuora.
This connection type supports the following task types:
This connection can be used in a Data Migration.
Usable as Source | Usable as Target | Usable as Incremental Source | Usable as Incremental Target |
---|---|---|---|
✔ | ❌ | ✔ | ❌ |
Zuora does not need a Connection String Template.
Users will need a Client ID and Client Secret.
Here is a guide on how to create a Client ID and Client Secret.