Integrate HubDB with External Services using SnapLogic

SnapLogic is an integration platform-as-a-service (iPaaS) that allows users to create data integration flows with no code. When paired with the CData JDBC Drivers, users get access to live data from more than 250+ SaaS, Big Data and NoSQL sources, including HubDB, in their SnapLogic workflows.

With built-in optimized data processing, the CData JDBC Driver offers unmatched performance for interacting with live HubDB data. When platforms issue complex SQL queries to HubDB, the driver pushes supported SQL operations, like filters and aggregations, directly to HubDB and utilizes the embedded SQL engine to process unsupported operations client-side (often SQL functions and JOIN operations). Its built-in dynamic metadata querying lets you work with HubDB data using native data types.

Connect to HubDB in SnapLogic

To connect to HubDB data in SnapLogic, download and install the CData HubDB JDBC Driver. Follow the installation dialog. When the installation is complete, the JAR file can be found in the installation directory (C:/Program Files/CData/CData JDBC Driver for HubDB/lib by default).

Upload the HubDB JDBC Driver

After installation, upload the JDBC JAR file to a location in SnapLogic (for example, projects/Jerod Johnson) from the Manager tab.

Configure the Connection

Once the JDBC Driver is uploaded, we can create the connection to HubDB.

1. Navigate to the Designer tab
2. Expand "JDBC" from Snaps and drag a "Generic JDBC - Select" snap onto the designer
3. Click Add Account (or select an existing one) and click "Continue"
4. In the next form, configure the JDBC connection properties:
   • Under JDBC JARs, add the JAR file we previously uploaded
   • Set JDBC Driver Class to cdata.jdbc.hubdb.HubDBDriver

   • Set JDBC URL to a JDBC connection string for the HubDB JDBC Driver, for example:

     jdbc:hubdb:AuthScheme=OAuth;OAuthClientID=MyOAuthClientID;OAuthClientSecret=MyOAuthClientSecret;CallbackURL=http://localhost:33333;RTK=XXXXXX;InitiateOAuth=GETANDREFRESH

     NOTE: RTK is a trial or full key. Contact our Support team for more information.

     Built-In Connection String Designer

     For assistance in constructing the JDBC URL, use the connection string designer built into the HubDB JDBC Driver. Either double-click the JAR file or execute the jar file from the command-line.

     java -jar cdata.jdbc.hubdb.jar

     Fill in the connection properties and copy the connection string to the clipboard.

     There are two authentication methods available for connecting to HubDB data source: OAuth Authentication with a public HubSpot application and authentication with a Private application token.

     Using a Custom OAuth App

     AuthScheme must be set to "OAuth" in all OAuth flows. Be sure to review the Help documentation for the required connection properties for you specific authentication needs (desktop applications, web applications, and headless machines).

     Follow the steps below to register an application and obtain the OAuth client credentials:

     1. Log into your HubSpot app developer account.
        • Note that it must be an app developer account. Standard HubSpot accounts cannot create public apps.
     2. On the developer account home page, click the Apps tab.
     3. Click Create app.
     4. On the App info tab, enter and optionally modify values that are displayed to users when they connect. These values include the public application name, application logo, and a description of the application.
     5. On the Auth tab, supply a callback URL in the "Redirect URLs" box.
        • If you're creating a desktop application, set this to a locally accessible URL like http://localhost:33333.
        • If you are creating a Web application, set this to a trusted URL where you want users to be redirected to when they authorize your application.
     6. Click Create App. HubSpot then generates the application, along with its associated credentials.
     7. On the Auth tab, note the Client ID and Client secret. You will use these later to configure the driver.

     8. Under Scopes, select any scopes you need for your application's intended functionality.

        A minimum of the following scopes is required to access tables:

        • hubdb
        • oauth
        • crm.objects.owners.read
     9. Click Save changes.
     10. Install the application into a production portal with access to the features that are required by the integration.
         • Under "Install URL (OAuth)", click Copy full URL to copy the installation URL for your application.
         • Navigate to the copied link in your browser. Select a standard account in which to install the application.
         • Click Connect app. You can close the resulting tab.

     Using a Private App

     To connect using a HubSpot private application token, set the AuthScheme property to "PrivateApp."

     You can generate a private application token by following the steps below:

     1. In your HubDB account, click the settings icon (the gear) in the main navigation bar.
     2. In the left sidebar menu, navigate to Integrations > Private Apps.
     3. Click Create private app.
     4. On the Basic Info tab, configure the details of your application (name, logo, and description).
     5. On the Scopes tab, select Read or Write for each scope you want your private application to be able to access.
     6. A minimum of hubdb and crm.objects.owners.read is required to access tables.
     7. After you are done configuring your application, click Create app in the top right.
     8. Review the info about your application's access token, click Continue creating, and then Show token.
     9. Click Copy to copy the private application token.

     To connect, set PrivateAppToken to the private application token you retrieved.

5. After entering the connection properties, click "Validate" and "Apply"

Read HubDB Data

In the form that opens after validating and applying the connection, configure your query.

• Set Schema name to "HubDB"
• Set Table name to a table for HubDB using the schema name, for example: "HubDB"."NorthwindProducts" (use the drop-down to see the full list of available tables)
• Add Output fields for each item you wish to work with from the table

Save the Generic JDBC - Select snap.

With connection and query configured, click the end of the snap to preview the data (highlighted below).

Once you confirm the results are what you expect, you can add additional snaps to funnel your HubDB data to another endpoint.

Piping HubDB Data to External Services

For this article, we will load data in a Google Spreadsheet. You can use any of the supported snaps, or even use a Generic JDBC snap with another CData JDBC Driver, to move data into an external service.

1. Start by dropping a "Worksheet Writer" snap onto the end of the "Generic JDBC - Select" snap.
2. Add an account to connect to Google Sheets
3. Configure the Worksheet Writer snap to write your HubDB data to a Google Spreadsheet

You can now execute the fully configured pipeline to extract data from HubDB and push it into a Google Spreadsheet.

Piping External Data to HubDB

As mentioned above, you can also use the JDBC Driver for HubDB in SnapLogic to write data to HubDB. Start by adding a Generic JDBC - Insert or Generic JDBC - Update snap to the dashboard.

1. Select the existing "Account" (connection) or create a new one
2. Configure the query:
   • Set Schema name to "HubDB"
   • Set Table name to a table for HubDB using the schema name, for example: "HubDB"."NorthwindProducts" (use the drop-down to see the full list of available tables)
3. Save the Generic JDBC - Insert/Update snap

At this point, you have configured a snap to write data to HubDB, inserting new records or updating existing ones.

More Information & Free Trial

Using the CData JDBC Driver for HubDB you can create a pipeline in SnapLogic for integrating HubDB data with external services. For more information about connecting to HubDB, check at our CData JDBC Driver for HubDB page. Download a free, 30 day trial of the CData JDBC Driver for HubDB and get started today.