Trello is a popular project management platform used by teams worldwide to organize tasks, track progress, and collaborate on projects. Many applications and tools need to integrate with Trello data for reporting, analytics, and business intelligence. Using Zappysys ODBC Driver for Trello, you can easily query card data, lists, and board information from Trello using standard SQL queries without writing custom code.

This tutorial demonstrates how to connect to Trello via ODBC and extract card and board data for use in your applications, databases, and reporting tools.

Prerequisites

1. A Windows or Linux system with an ODBC driver manager installed.
2. An ODBC-compatible application (Excel, Power BI, Tableau, database tool, etc.).
3. A Trello account with at least one board and list created.
4. Finally, install the ZappySys ODBC Driver.

Steps

Generate Trello API Key and Token

1. Go to the Trello Power-up page and log in to your account.
2. Create a new App and fill in the form.
   

   Trello – Create a new App

3. Inside your new App, click the API key, then generate a new API Key.
   

   Trello – API key page

4. In the API Key section, click the Token link to generate an access token.
   

   Trello – API key and Token link

5. Choose the token’s expiration time (Recommended: 30 days for security).
6. Review the permissions and click Create Token.
7. Copy the generated token and store it securely.
8. You now have both your API Key and Token. Keep these credentials confidential.

Creating a new ODBC DSN using ZappySys JSON Driver

1. Search for ODBC in the Windows Start menu and open the ODBC Data Source Administrator.
   
2. In the User DSN or System DSN tab, click Add to create a new data source.
3. In the ODBC Data Source Setup window, select the ZappySys JSON Driver and click Continue.
   

 Configure the Connection and API Settings

1. In the Base URL field, enter the URL:
   

   https://api.trello.com/1/members/me/boards?key={{TrelloApiKey}}&token={{TrelloToken}}

   For more examples:
   GET /boards/{boardId}/cards — Retrieve all cards from a specific board
GET /boards/{boardId}/lists — Retrieve all lists from a specific board
GET /cards/{cardId} — Retrieve details of a specific card

2. In the Request Method, use GET
3. You can use the Array filter to get the object you need.
4. Test the connection to check everything is working fine
   

   Trello – ODBC configuration

Preview the data

1. Once your ODBC DSN is configured, go to the preview tab.
2. Select the table you want to use.
3. Press the Preview data button to see the result.
   

   Trello – ODBC final result

Conclusion

Connecting to Trello via ODBC with the Zappysys ODBC Driver simplifies integrating project management data into your applications, databases, and reporting tools without custom development. By following the steps outlined in this tutorial, you can build reliable data connections that allow you to query Trello data using standard SQL and access it from Excel, Power BI, Python, SQL Server, and many other tools. Whether you need to track project progress, analyze team productivity, consolidate data from multiple teams, or create executive dashboards, Trello integration via ODBC provides a flexible and powerful solution.

Explore the full capabilities of the ZappySys ODBC Drivers to optimize your data access and integration strategy. You can extend this solution to include periodic data synchronization, real-time dashboards, and advanced transformations using your preferred analytics platform.

Need Help?

If you encounter any issues, our support team is here to help:

1. Live Chat — Use the chat widget (bottom-right corner of this page)
2. Email — support@zappysys.com
3. Support Center — Visit the ZappySys Support Portal

The post How to extract data from Trello appeared first on ZappySys Blog.

Trello is a popular project management platform used by teams worldwide to organize tasks, track progress, and collaborate on projects. Many organizations need to integrate Trello data with SQL Server for reporting, analytics, and business intelligence purposes. Using Zappysys SSIS PowerPack, you can easily extract card data, lists, and board information from Trello using REST APIs without writing custom code.

This tutorial demonstrates how to connect SSIS to Trello and load card and board data into SQL Server tables using the Zappysys REST API Source component.

Prerequisites

1. SQL Server Integration Services (SSIS) is installed.
2. Visual Studio with SSIS extension or SQL Server Data Tools (SSDT).
3. A Trello account with at least one board and list created.
4. Zappysys SSIS PowerPack installed on your system.

Steps
Generate Trello API Key and Token

1. Go to the Trello Power-up page and log in to your account.
2. Create a new App and fill in the form.
   

   Trello – Create a new App

3. Inside your new App, click the API key, then generate a new API Key.
   

   Trello – API key page

4. In the API Key section, click the Token link to generate an access token.
   

   Trello – API key and Token link

5. Choose the token’s expiration time (Recommended: 30 days for security).
6. Review the permissions and click Create Token.
7. Copy the generated token and store it securely.
8. You now have both your API Key and Token. Keep these credentials confidential.

Configure SSIS Package Variables

1. Open your SSIS project in Visual Studio or SQL Server Data Tools (SSDT).
2. Create a new package or open an existing one.
3. Navigate to the Variables section and create the following variables:
   1. TrelloApiKey (String) — Enter the API Key you generated in the previous step.
   2. TrelloToken (String) — Enter the access token you created.
   3. BoardId (String) — Enter your Trello Board ID.
4. Ensure all variables are marked as sensitive if they contain authentication credentials to secure the package.

Create and Configure the  JSON Source

1. 1. Add a new Data Flow Task to your SSIS package.
   2. Double-click the Data Flow Task to enter the Data Flow design surface.
      

      Drag and drop Data flow

   3. Drag a ZappySys JSON Source component from the toolbox onto the canvas.
      

      SSIS JSON Source – Drag and Drop

   4. Double-click the ZappySys JSON Source to open its configuration editor.
   5. In the Connection section, enter the Trello API endpoint to retrieve cards from your board:
      

      https://api.trello.com/1/members/me/boards?key={{User::TrelloApiKey}}&token={{User::TrelloToken}}

   6. Set the HTTP Request Method to GET.
   7. Click Test Connection to verify that your API credentials are correct and you can access your Trello board data.
   8. Click Preview Data to view the card data that will be extracted from Trello.
   9. Click OK to save the configuration.
      

      Trello – JSON source example

   10. Alternatively, you can use the boardId parameter in the request to retrieve specific board data. Here are some common API endpoints:
       GET /boards/{boardId}/cards — Retrieve all cards from a specific board
GET /boards/{boardId}/lists — Retrieve all lists from a specific board
GET /cards/{cardId} — Retrieve details of a specific card
       

       Trello – JSON source example board ID

Configure the Data Destination

1. Drag and drop a destination component (such as OLE DB Destination, SQL Server Destination, or Flat File Destination) into the Data Flow.
2. Connect the output arrow from the JSON Source component to the destination component.
3. Double-click the destination component to open its configuration dialog.
4. Configure the connection manager to point to your target SQL Server database.
5. In the destination editor, specify the target table where Trello data will be stored.
6. In the Mappings section, map the columns from the JSON response to the corresponding SQL Server table columns.
7. Configure error-handling options based on your requirements (fail on errors, ignore errors, or redirect error rows to an error table).
8. Click OK to save the destination configuration.
9. Execute the package and verify that the data extraction is working correctly.
   

   Trello – Final Result

Conclusion

Connecting SSIS to Trello using Zappysys REST API Source simplifies the integration of project management data into your SQL Server environment without custom development. By following the steps outlined in this tutorial, you can build reliable SSIS packages that automatically synchronize Trello board data with SQL Server for analytics, reporting, and business intelligence. Whether you need to track project progress, analyze team productivity, consolidate data from multiple teams, or create executive dashboards, Trello integration with SSIS provides a flexible and powerful solution that saves time and reduces manual data entry errors.

Explore the full capabilities of the ZappySys SSIS PowerPack to optimize your data integration tasks. By applying this pattern, you can extend your solution to include additional transformations, data validation, error handling, and scheduling through SQL Server Agent.

Need Help?

If you encounter any issues, our support team is here to help:

1. Live Chat — Use the chat widget (bottom-right corner of this page)
2. Email — support@zappysys.com
3. Support Center — Visit the ZappySys Support Portal

The post SSIS tutorial: How to retrieve data from Trello appeared first on ZappySys Blog.

Firebase is a popular cloud platform that provides real-time databases, cloud storage, and various backend services. Many organizations use Firebase to store application data and need to integrate it with their SQL Server databases for reporting, analytics, and business intelligence. Using Zappysys SSIS PowerPack, you can easily insert or extract data from Firebase Realtime Database or Firestore using REST APIs without writing custom code.

This tutorial demonstrates how to connect SSIS to Firebase and load data into SQL Server tables using the Zappysys REST API Source component.

Prerequisites

1. SQL Server Integration Services (SSIS) is installed.
2. Visual Studio with SSIS extension or SQL Server Data Tools (SSDT).
3. A Firebase project with Realtime Database or Firestore enabled.
4. Zappysys SSIS PowerPack is installed on your system.

Set Up Your Firebase Project

1. Go to the Firebase Console.
2. Select a project; if you do not have one, click on “Create a new project”.
3. Enter your project name and click “Continue.”
4. Enable Google Analytics if desired, and complete project creation.
5. Navigate to Security > Authentication.
6. In the Sign-in method tab, enable Email/Password authentication.
   

   Firebase – Enable email-password provider

7. Go to the Users tab and create a new user, enter an email and a password.
   

   Firebase – Enter a new email

8. Go to Settings > General.
9. Under the Your apps section, create a new app and select the Web option.
   

   Firebase – Create a new App

10. Enter the name for your app, and you will receive a configuration object with your app’s credentials:
11. Use this as the body:

    const firebaseConfig = {
      apiKey: "AIzaSyC2EYUliXXXXXXXXXXXXX",
      authDomain: "my-project.firebaseapp.com",
      databaseURL: "https://my-project.firebaseio.com",
      projectId: "my-project",
      storageBucket: "my-project.firebasestorage.app",
      messagingSenderId: "5750XXXXXXXXX",
      appId: "1:5750171XXXXXXXX:web:4404eca49b20XXXXXXXX"
    };

12. In the Firebase Console, navigate to Realtime Database or Firestore Database.
13. Click Create Database and select your region.
14. Set security rules. For development and testing, use

    "auth!=null"

    for read and write access.
    

    Firebase – change rules

15. From the Database tab, copy your database URL (e.g., https://my-project.firebaseio.com)

Configure the token for Firebase

1. In your SSIS package, navigate to the Variables section and create the following variables:
   1. Api_Key (String) — Enter the API key from Step 1.
   2. Token (String) — Stores the authentication token generated by Firebase.
2. Drag and drop the REST API Task component onto your SSIS package canvas and double-click to open it.
   

   Add a REST API Task in SSIS

3. Navigate to the Response Settings tab and set Response Content Type to JSON.
4. In the JSONPath field, enter: $.idToken to extract the session token from the API response.
5. Enable Save Response Content, select the Variable option, and choose your Token variable.
   

   Firebase – save token in a variable

6. Go back to the Request tab and enter the following URL. For testing, use:
   

   https://identitytoolkit.googleapis.com/v1/accounts:signInWithPassword?key={{User::api_key}}

7. Set the HTTP Request Method to POST.
8. Use the following JSON in the body with your credentials:

   {
     "email": "test@gmail.com",
     "password": "testpassword",
     "returnSecureToken": true
   }

9. Use JSON (application/json) as Body Content Type
10. Test the connection. If successful, you will see the generated token in the response.
    

    Firebase – generate token

Create and Configure the JSON Source

1. Add a new Data Flow Task to your SSIS package. Connect it downstream from the REST API task you created before.
2. Double-click the Data Flow Task to enter the Data Flow design surface.
3. Drag a ZappySys JSON Source component from the toolbox onto the canvas.
   

   SSIS JSON Source – Drag and Drop

4. Double-click the ZappySys JSON Source to open its editor.
5. Enter the following URL to the Firebase endpoint. Replace “users” with the database path where you want to send data:
   

   https://zappysys-bigquery.firebaseio.com/users.json?auth={{User::token}}

6. Set the HTTP Request Method to POST.
7. Configure the JSON payload to insert your data. Since Firebase is a NoSQL database, structure the JSON according to your data schema:
   

   {
   "user001": { "nombre": "Ana García", "email": "ana@test.com" },
   "user002": { "nombre": "Luis Pérez", "email": "luis@test.com" }
   }

   

   Firebase – send data

8. Click Preview Data, using a valid token in the variable, to test the connection and verify the data.
9. You can change the method to GET to check the data from the database
   

   Firebase – get data from the database

10. Click OK to save the configuration.

Configure the Data Destination

1. Drag and drop a destination component (such as OLE DB Destination, Flat File Destination, or Trash Destination) into the Data Flow.
2. Connect the output arrow from the JSON Source component to the destination component.
3. Double-click the destination component to open its configuration dialog.
4. Configure the destination to point to your target table or file where Firebase data will be stored.
5. In the Mappings section, map the columns from the JSON response to the corresponding destination columns.
6. Click OK to save the destination configuration.
7. Execute the package and verify that the data extraction is working correctly.
   

   Firebase – Final Result

Conclusion

Connecting SSIS to Firebase using Zappysys REST API Source simplifies the integration of cloud database data without custom development. By following the steps outlined in this tutorial, you can build reliable SSIS packages that automatically transfer data between Firebase and SQL Server for analytics, reporting, and business intelligence purposes. The REST API approach works seamlessly with both Firebase Realtime Database and Firestore, giving you the flexibility to work with your preferred cloud database structure.

Explore the full capabilities of the ZappySys SSIS PowerPack to optimize your data integration tasks. By applying this pattern, you can extend your solution to include additional transformations, data validation, error handling, and scheduling through SQL Server Agent.

Need Help?

If you encounter any issues, our support team is here to help:

1. Live Chat — Use the chat widget (bottom-right corner of this page)
2. Email — support@zappysys.com
3. Support Center — Visit the ZappySys Support Portal

The post SSIS Tutorial: How to Extract Data from Firebase appeared first on ZappySys Blog.

Tripletex is a cloud-based accounting and enterprise resource planning (ERP) platform designed for small to medium-sized businesses in Norway and other Scandinavian countries. It provides comprehensive financial management, invoicing, project accounting, and inventory management capabilities through a robust REST API.

Integrating Tripletex with ODBC enables seamless data access between your accounting system and any ODBC-compatible application, including Excel, Power BI, Tableau, custom applications, and databases. ZappySys Tripletex ODBC Driver simplifies this integration by providing a native ODBC interface that handles Tripletex authentication, API communication, and data querying without requiring custom code.

This tutorial walks you through the complete process of installing the ODBC driver, configuring a data source, and querying Tripletex data from any ODBC-compatible application.

Prerequisites

1. Windows or macOS operating system with admin access for driver installation.
2. Tripletex account with API access enabled.
3. An ODBC-compatible application (Excel, Power BI, Tableau, database tool, etc.).
4. Finally, install the ZappySys ODBC Driver.

Step-by-Step Guide

Generate your Tripletex API credentials

1. Create or log in to your Tripletex account using your administrator credentials.
2. Navigate to the Settings section by clicking on your user profile icon in the top-right corner of the screen.
3. Select API Access from the dropdown menu.
4. Click the Generate New Token button to generate a new API token.
   

   Tripletex – Generate Token

5. Provide a descriptive name for your token.
6. Set the appropriate permissions scope. For this tutorial, select Read and Write access to ensure the integration can both retrieve and push data.
7. Click Generate Token, then immediately copy the Consumer Token and Employee Token values. Store them securely in a password manager or Azure Key Vault, as Tripletex will not display them again.
   

   Tripletex – Getting Tokens

Creating a new ODBC DSN using ZappySys JSON Driver

1. Search for ODBC in the Windows Start menu and open the ODBC Data Source Administrator.
   
2. In the User DSN or System DSN tab, click Add to create a new data source.
3. In the ODBC Data Source Setup window, select the ZappySys JSON Driver and click Continue.
   

 Configure the Connection and API Settings

1. In the Base URL field, from the API documentation, enter the URL:
   

   https://api-test.tripletex.tech/v2/currency

2. Select HTTP as the connection type, then click it to configure it.
3. Select Dynamic Token as the Authentication Type.
4. In the Header Name, enter Authorization.
5. In the OAuth Scheme, use Basic.
6. Go to the Dynamic Token tab.
7. Enter the following URL with the consumer and employee token:
   

   https://api-test.tripletex.tech/v2/token/session/:create?consumerToken={ConsumerToken}&employeeToken={EmployeeToken}&expirationDate=2026-04-28

8. Set up the HTTP Request Method to PUT.
   
   

   Tripletex – ODBC dynamic token

9. Go to the Response Settings tab
10. Select Expression Type as JSON and use this JSONPath to get the Session Token:

    $.value.token

11. In Token Function, use the following function. The Authorization header must contain the Company ID( Enter your Tripletex company ID or use 0 if unknown) and Session Token in Base64-encoded format:

    <<0:[$token$],FUN_BASE64ENC>>

12. Click OK to save the connection configuration.
    

    Tripletex – ODBC save Session Token

13. In the Request Method, use GET
14. You can use the Array filter to get the object you need. We will use $.value[*].
15. Test the connection to check everything is working fine
    

    Tripletex – ODBC JSON Driver configuration

Preview the data

1. Once your ODBC DSN is configured, go to the preview tab.
2. Select the table you want to use.
3. Press the Preview data button to see the result.
   

   Tripletex – ODBC JSON Driver Final Result

Conclusion

You have successfully configured ODBC connectivity to Tripletex, enabling seamless data access from Excel, Power BI, Tableau, custom applications, and any other ODBC-compatible tool. This integration allows you to analyze financial data, create dashboards, and automate reporting without building custom APIs or ETL pipelines.

The ZappySys Tripletex ODBC Driver provides a simple, standardized interface for accessing your accounting data, making it easy to integrate Tripletex with your existing business intelligence and analytics tools. By following this tutorial, you have established a foundation for advanced data analysis, forecasting, and business intelligence workflows.

Explore the full capabilities of the ZappySys ODBC Drivers to optimize your data access and integration strategy. You can extend this solution to include periodic data synchronization, real-time dashboards, and advanced transformations using your preferred analytics platform.

Need Help?

If you encounter any issues, our support team is here to help:

1. Live Chat — Use the chat widget (bottom-right corner of this page)
2. Email — support@zappysys.com
3. Support Center — Visit the ZappySys Support Portal

The post ODBC tutorial: How to get data from Tripletex appeared first on ZappySys Blog.

Tripletex is a cloud-based accounting and enterprise resource planning (ERP) platform designed for small to medium-sized businesses in Norway and other Scandinavian countries. It provides comprehensive financial management, invoicing, project accounting, and inventory management capabilities through a robust REST API.

Integrating Tripletex with SQL Server Integration Services (SSIS) enables seamless data synchronization between your accounting system and other business applications. ZappySys SSIS PowerPack simplifies this integration by providing pre-built connectors and components that handle Tripletex authentication, API communication, and data transformation without requiring custom code.

This tutorial walks you through the complete process of setting up a Tripletex connection and building your first data integration package.

Prerequisites

1. SQL Server Integration Services (SSIS) is installed.
2. Visual Studio with SSIS extension or SQL Server Data Tools (SSDT).
3. Tripletex account with API access enabled.
4. Finally, do not forget to install ZappySys SSIS PowerPack.

Steps

Generate your Tripletex API credentials

1. Create or log in to your Tripletex account using your administrator credentials.
2. Navigate to the Settings section by clicking on your user profile icon in the top-right corner of the screen.
3. Select API Access from the dropdown menu.
4. Click the Generate New Token button to generate a new API token.
   

   Tripletex – Generate Token

5. Provide a descriptive name for your token.
6. Set the appropriate permissions scope. For this tutorial, select Read and Write access to ensure the integration can both retrieve and push data.
7. Click Generate Token, then immediately copy the Consumer Token and Employee Token values. Store them securely in a password manager or Azure Key Vault, as Tripletex will not display them again.
   

   Tripletex – Getting Tokens

Generate the Session Token

Tripletex requires a session token for API authentication. This session token is generated from the Consumer Token and Employee Token obtained in Step 1. Follow these steps:

1. In your SSIS package, navigate to the Variables section and create the following variables:
   1. ConsumerToken (String) — Enter the Consumer Token from Step 1.
   2. EmployeeToken (String) — Enter the Employee Token from Step 1.
   3. SessionToken (String) — Stores the generated session token.
   4. CompanyID (String) — Enter your Tripletex company ID (or use 0 if unknown).
2. Drag and drop the REST API Task component onto your SSIS package canvas and double-click to open it.
   

   Add a REST API Task in SSIS

3. Navigate to the Response Settings tab and set Response Content Type to JSON.
4. In the JSONPath field, enter: $.value.Token to extract the session token from the API response.
5. Enable Save Response Content, select the Variable option, and choose your SessionToken variable.
   

   Tripletex – Save Session Token in Variable

6. Go back to the Request tab and enter the following URL. For testing, use:
   

   https://api-test.tripletex.tech/v2/token/session/:create?consumerToken={{User::ConsumerToken}}&employeeToken={{User::EmployeeToken}}&expirationDate=2026-04-24

7. For production environments, use:
   

   https://tripletex.no/v2/token/session/:create?consumerToken={{User::ConsumerToken}}&employeeToken={{User::EmployeeToken}}&expirationDate=2026-04-24

8. Set the HTTP Request Method to PUT.
9. Test the connection. If successful, you will see the generated session token in the response.
   

   Tripletex – Generate Session Token

Use the HTTP dynamic token connection(Recommended)

An alternative option is using the Dynamic token inside the HTTP connection

1. Right-click in the Connection Managers pane and select New Connection…
2. Select ZS-HTTP from the SSIS connectors list
   

   Create a new HTTP connection

3. Enter the following URL with the consumer and employee token:
   

   https://api-test.tripletex.tech/v2/token/session/:create?consumerToken={ConsumerToken}&employeeToken={EmployeeToken}&expirationDate=2026-04-28

4. In Credentials Type, select Dynamic Token.
5. In the Auth header name, use Authorization.
6. For the Auth Scheme, select the option Basic.           
   

   Tripletex – SSIS HTTP connection

7. Go to the Dynamic Token tab.
8. Enter the past URL.
9. Set up the HTTP Request Method to PUT.
   
   

   Tripletex – ODBC dynamic token

10. Go to the Response Settings tab
11. Select Expression Type as JSON and use this JSONPath to get the Session Token:

    $.value.token

12. In Token Function, use the following function. The Authorization header must contain the Company ID( Enter your Tripletex company ID or use 0 if unknown) and Session Token in Base64-encoded format:

    <<0:[$token$],FUN_BASE64ENC>>

13. Click OK to save the connection configuration.
    

    Tripletex – SSIS save Session Token

Create and Configure the JSON Source

1. Add a new Data Flow Task to your SSIS package. Connect it downstream from the REST API task you created before.
2. Double-click the Data Flow Task to enter the Data Flow design surface.
3. Drag a ZappySys JSON Source component from the toolbox onto the canvas.
   

   SSIS JSON Source – Drag and Drop

4. Double-click the ZappySys JSON Source to open its editor.
5. For testing purposes, enter the following URL:
   

   https://api-test.tripletex.tech/v2/currency

6. Set the HTTP Request Method to GET.
7. Click the Headers tab and add the required Tripletex authentication headers. The Authorisation header must contain the Company ID and Session Token in Base64-encoded format:
   

   Accept: application/json
   Authorization: Basic <<{{User::CompanyID}}:{{User::SessionToken}},FUN_BASE64ENC}}>>
8. If you want to use the connection option (Recommended), just check Use credentials and select the connection you created earlier.
9. In the Array Filter field, specify the JSON path to extract the data array from the Tripletex response: $.value
10. Click Preview Data to test the connection and verify that data is being retrieved correctly from Tripletex.
    

    Tripletex – JSON Source result

11. Click OK to save the configuration.

Configure the Data Destination

1. Drag and drop a destination component (such as OLE DB Destination, Flat File Destination, or Trash Destination) into the Data Flow.
2. Connect the output arrow from the JSON Source component to the destination component.
3. Double-click the destination component to open its configuration dialogue.
4. Configure the destination to point to your target table or file where Tripletex data will be stored.
5. In the Mappings section, map the columns from the JSON response to the corresponding destination columns.
6. Click OK to save the destination configuration.
7. Execute the package and verify that the data extraction is working correctly.
   

   Tripletex  – Final Result

Conclusion

You have successfully set up a complete integration between Tripletex and SSIS using ZappySys components. This tutorial covered creating API credentials, configuring session token authentication, retrieving data from Tripletex APIs, and loading it into your SQL Server or other destinations.

This integration enables you to automate critical business processes such as invoice tracking, customer synchronization, project management, and financial reporting. By leveraging ZappySys SSIS PowerPack, you have avoided complex custom coding and achieved a scalable, maintainable solution for your data integration needs.

Explore the full capabilities of the ZappySys SSIS PowerPack to optimize your data integration tasks. By applying this pattern, you can extend your solution to include additional transformations, data validation, error handling, and scheduling through SQL Server Agent.

Need Help?

If you encounter any issues, our support team is here to help:

1. Live Chat — Use the chat widget (bottom-right corner of this page)
2. Email — support@zappysys.com
3. Support Center — Visit the ZappySys Support Portal

The post SSIS tutorial: How export data from Tripletex appeared first on ZappySys Blog.

Power BI native ODBC connectors do not support DirectQuery. This significant platform limitation forces users into Import mode, preventing real-time data access and causing refresh delays for critical business dashboards. If you have been searching for a “Power BI ODBC DirectQuery workaround” or a way to “enable DirectQuery for custom ODBC drivers,” this guide provides the exact steps to bridge that gap.

The Industry Challenge: Standard Power BI ODBC settings lack the DirectQuery option.

The Problem: Why “Import Mode” Fails Modern Data Teams

While the native Microsoft connector is useful for simple tasks, its lack of DirectQuery support creates several enterprise-level issues:

• Stale Data: There is no true real-time reporting, as data is only as fresh as your last refresh.
• Memory Constraints: Large datasets quickly bloat the Power BI model and increase memory usage.
• Refresh Overhead: Frequent changes in underlying data require complex and constant refresh schedules.
• API Lag: Data from cloud apps like Jira, SharePoint, or OneDrive becomes outdated between scheduled updates.

The Solution: ZappySys DirectQuery ODBC Connector

To fix this widespread industry problem, you can use the ZappySys DirectQuery ODBC Connector (a specialized custom Power BI connector). This tool allows you to treat any ODBC source as a live connection, unlocking real-time analytics for databases, APIs, and cloud apps.

Advanced Capabilities:

• Enable DirectQuery mode for virtually any 64-bit ODBC source.
• Query live data directly without importing massive datasets into Power BI.
• Seamlessly integrate with the ZappySys ODBC PowerPack for API and JSON connectivity.

Step 1: Install the ZappySys Connector

1. First, download and install the ZappySys ODBC PowerPack.
   This is essential for those using ZappySys drivers (e.g. REST API, JSON, JDBC Bridge (e.g. Trino, Infor, Athena) and more).
2. Download the Power BI Connector file: ZappySys-DirectQuery-ODBC-Connector.zip
3. Copy the extracted .mez file to <your-profile>\Documents\Power BI Desktop\Custom Connectors: (See next section to find exact path)
   

   Examples:
   
   C:\Users\<YourUsername>\Documents\Power BI Desktop\Custom Connectors
   C:\Users\<YourUsername>\OneDrive - <your-company>\Documents\Power BI Desktop\Custom Connectors

   
   Note: If the Custom Connectors folder does not exist, you must create it manually.For finding exact connector folder path see Microsoft Connector Extensibility documentation.

How to find the Custom Connector folder Path for Power BI

1. Type PowerShell on command line.
2. Run the lines below to print the base path and the full path. You can run one after another or paste both lines.
   

   [Environment]::GetFolderPath('MyDocuments')
   Join-Path ([Environment]::GetFolderPath('MyDocuments')) 'Microsoft Power BI Desktop\Custom Connectors'

Step 2: Update Power BI Security for Custom Connectors

1. Open Power BI Desktop.
2. Navigate to File > Options and settings > Options > Security.
3. Under Data Extensions, enable the option “Allow any extension to load without validation”.
4. Save your changes and restart Power BI Desktop to apply the new security policy.

Power BI options security settings to enable custom connectors

Step 3: Set Up a 64-bit ODBC DSN

1. Open the ODBC Data Sources (64-bit) administrator.
2. Click the System DSN tab and select Add.
3. Choose your driver (for example, the ZappySys ODBC Driver for API/Jira/SharePoint).
4. Save the DSN with a clear name, such as MyZappyDSN.

Important Architecture Note: Power BI Desktop and the Gateway require a 64-bit DSN; 32-bit DSNs are not supported for this workflow.

Windows 64-bit ODBC DSN Configuration.

Step 4: Connecting for Live Data / DirectQuery Support

1. In Power BI Desktop, go to Get Data > More...
2. Search for “zappysys” in the list.
3. Select ZappySys ODBC Connector (For DirectQuery Support).
4. Provide your DSN name (MyZappyDSN) or a full connection string.
5. Select DirectQuery mode and click connect.
   

   ZappySys ODBC Connector – To enable DirectQuery option for ODBC Datasource (Custom Install required)

Note for PowerPack Users: You can use a full connection string (e.g., Driver={ZappySys ODBC Driver};Host=...;) by using the “Copy Settings” feature within the ZappySys Driver UI. Read more how to copy full connection string

Power BI Get Data showing ZappySys DirectQuery ODBC Connector selected

Choosing Your Selection Mode

When the navigator opens, you must choose how to fetch your data:

• Table Mode: Best for simple datasets where you want to select a table from a list.
• Query Mode (SQL): Recommended for performance. Writing a custom SQL query allows you to filter and join data at the source, which is much faster for DirectQuery.

Step 5: Verify Your DirectQuery Connection (Final Result)

Once connected, it is crucial to verify that the report is truly “Live.” A successful connection will change the behavior of Power BI Desktop.

Power BI Test Dashboard showing Storage Mode: DirectQuery

Step 6: Configure the Gateway for Power BI Service

Once your report is ready, you must configure the gateway so Power BI Service can maintain the live DirectQuery connection to your data source. Follow the steps below to deploy and enable your custom connector for the On-premises Data Gateway.

6.1 Create a Dedicated Connector Folder

Do not place the connector in a user-specific folder. The gateway service account needs reliable access, so use a shared folder on a local drive instead.

• Recommended paths: C:\CustomConnectors or C:\ZappySysConnectors

6.2 Copy the Connector File

Copy your custom connector file (.mez) into the folder you created.

C:\CustomConnectors\YourConnector.mez

6.3 Grant Folder Permissions to the Gateway Service

If the connector does not appear in Power BI Service, first make sure the gateway service account can access the connector folder.

1. Right-click the folder (for example, C:\CustomConnectors) and select Properties > Security.
2. Click Edit > Add.
3. Enter NT SERVICE\PBIEgwService and click Check Names.
   NOTE: If you are using a different service account, then use that instead. To verify Services account name try below steps.
   Press Windows Key + R > open services.msc > locate On-premises data gateway service > look at Log On As
   > If it says NT SERVICE\PBIEgwService then use exact same user name
   > If it says Local System then use SYSTEM user for folder permission
   > If it says DOMAIN\Svc-PBI-Gateway then use exact same user name
4. If Windows cannot find the account, make sure the Location is set to the local machine, not the domain.
5. Grant at least Read and List folder contents permissions.

6.4 Enable Custom Connectors in the Gateway Config File

You must explicitly enable custom connectors and point the gateway to your connector folder.

1. Open this file in Notepad as Administrator:

C:\Program Files\On-premises data gateway\Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.dll.config

2. Find the <appSettings> section and add these entries:

<add key="EnableCustomConnectors" value="true" />
<add key="CustomConnectorsPath" value="C:\CustomConnectors" />

3. Save the file.
4. Restart the gateway service from services.msc or from the gateway application.

6.5 Verify the Connector in Power BI Service

After restarting the gateway, sign in to Power BI Service and try adding or mapping the data source. Your custom connector should now be available through the gateway.

FAQ: Frequently Asked Questions

Does the native Microsoft ODBC connector support DirectQuery?

No. The native Microsoft ODBC connector is limited to Import mode only.

How can I enable DirectQuery for ODBC sources in Power BI?

By using the ZappySys DirectQuery ODBC Connector and following the custom extension setup outlined in this guide.

Where is the ZappySys DirectQuery connector download?

You can find the latest version here: ZappySys DirectQuery Connector ZIP.

Troubleshooting Checklist

• Connector Missing: Ensure “Allow any extension” is checked in Power BI security settings.
• Gateway Errors: Verify the DSN name is identical on both the local PC and the gateway server.
• 32-bit vs 64-bit: Ensure you are using a 64-bit System DSN; 32-bit will cause connection failures.
• Driver Installation: Ensure the ZappySys ODBC driver is installed on all machines where the report or gateway runs.

The post Enable Power BI DirectQuery for ODBC: Solving the Live Data Problem appeared first on ZappySys Blog.

Introduction

Claude.IA is a powerful cloud-native intelligence and automation platform that offers REST APIs for accessing AI models, data processing pipelines, and automation workflows. In this guide, we will demonstrate how to connect to Claude using the Zappysys ODBC Driver for REST APIs with API key authentication.

Whether you are using Claude for intelligent document processing, data enrichment, or automated workflows, you will learn how to configure ODBC connectivity without writing custom code. Zappysys ODBC REST driver handles all the complexity, allowing you to query Claude APIs using standard SQL and connect from any ODBC-compatible application.

Prerequisites

1. Windows operating system (32-bit or 64-bit).
2. Claude’s account has API access enabled.
3. Finally, do not forget to install ZappySys ODBC PowerPack.

Steps

Generate an API Key in Claude

1. Log in to your Cloude.IA account settings.
2. Navigate to Settings > API Keys.
3. Click Create Key.
4. Enter the workspace name (optional).
5. Enter a descriptive name for the API key.
6. Press Add to generate the token Key.
7. Save the API key in a secure location; you won’t be able to view it again.
   

   Cloude- Generate Token

8. Set Up Billing (required): add a payment method via the Billing Settings page.

Creating a new ODBC DSN using ZappySys JSON Driver

1. Search for ODBC in the Windows Start menu and open the ODBC Data Source Administrator.
   
2. In the User DSN or System DSN tab, click Add to create a new data source.
3. In the ODBC Data Source Setup window, select the ZappySys JSON Driver and click Continue.
   

 Configure the Connection and API Settings

1. In the Base URL field, enter:
   

   https://api.anthropic.com/v1

2. Select HTTP as the connection type, then click it to configure it.
3. Select Static Token/API Key as the Authentication Type.
4. Enter your Claude API key in the API Key field.
5. In the Header Name, enter x-api-key.
6. In the OAuth Scheme, use none.
7. Click OK to save the configuration.
8. Set up the HTTP Request Method to POST.
9. Use this JSON as the body:
   

   {
     "model": "claude-sonnet-4-6",
     "max_tokens": 1024,
     "messages": [
       {
         "role": "user",
         "content": "{YOUR-Message}"
       }
     ]
   }
10. In the Body content type, select 

    JSON(application/json)

11. Inside the header, add:

    anthropic-version: 2023-06-01

12. You can use the Array filter to get the object you need, and you can use

    $.messages[*].content

      to get only the message.
13. Test the connection to check everything is working fine
    

    Claude – JSON ODBC Driver configuration

Preview the data

1. Once your ODBC DSN is configured, go to the preview tab.
2. Select the table you want to use.
3. Press the Preview data button to see the result.
   

   Claude – JSON ODBC Driver result

Conclusion

You now have a secure and reliable ODBC connection to Claude. API Key authentication provides a simple and secure way to connect using the Zappysys ODBC Driver for REST APIs. With this connection configured, you can build powerful data extraction, transformation, and integration workflows using Claude’s intelligence and automation capabilities from any ODBC-compatible application without writing custom code.

Explore the full capabilities of the ZappySys ODBC PowerPack to optimize your data integration tasks. By applying this pattern, you can extend your solution to include additional data sources and create unified reporting across multiple cloud-based APIs.

Need Help?

If you encounter any issues, our support team is here to help:

1. Live Chat — Use the chat widget (bottom-right corner of this page)
2. Email — support@zappysys.com
3. Support Center — Visit the ZappySys Support Portal

The post ODBC Tutorial: How to connect Claude to ODBC appeared first on ZappySys Blog.

Introduction

Claude is a powerful cloud-native intelligence and automation platform that offers REST APIs for accessing AI models, data processing pipelines, and automation workflows. In this guide, we will demonstrate how to connect Zappysys SSIS connectors to the Claude using API key authentication.

Whether you are using Claude for intelligent document processing, data enrichment, or automated workflows, you will learn how to configure SSIS integration without writing custom code. Zappysys handles all the complexity, allowing you to focus on building ETL workflows.

Prerequisites

1. 1. SQL Server Integration Services (SSIS) is installed.
   2. Visual Studio with SSIS extension or SQL Server Data Tools (SSDT).
   3. Claude.IA account with API access enabled.
   4. Finally, do not forget to install ZappySys SSIS PowerPack.

Steps

Generate an API Key in Claude

1. Log in to your Claude.IA account settings.
2. Navigate to Settings > API Keys.
3. Click Create Key.
4. Enter the workspace name (optional).
5. Enter a descriptive name for the API key.
6. Press Add to generate the token Key.
7. Save the API key in a secure location; you won’t be able to view it again.
   

   Claude – Generate Token

8. Set Up Billing (required): add a payment method via the Billing Settings page.

Create Zappysys Connection in SSIS

1. Create or select your SSIS project and open the package.
2. Right-click in the Connection Managers pane and select New Connection…
3. Select ZS-HTTP from the SSIS connectors list
   

   Create a new HTTP connection

4. In Credentials Type, select Static token/API key.
5. Enter the API key from the previous step.
6. The API documentation requires sending the token in the header with this format: x-api-key: API_KEY
   1. In the OAuth header Name, we will use x-api-key
   2. For the OAuth Scheme, set to none
7. Click OK to save the settings.
   

   Claude – HTTP connection

Create and Configure the JSON source

1. 1. In your SSIS package, drag and drop a Data Flow Task from the Toolbox into the Control Flow.
      

      Drag and drop Data flow

   2. Double-click the Data Flow Task to enter the Data Flow tab.
   3. In the Data Flow, drag and drop a ZS JSON Source component from the Toolbox.
   4. Double-click the JSON Source to open its editor.
   5. Enable Use credentials, then select your Claude HTTP connection from the connection list dropdown.
   6. Enter the following URL:
      

      https://api.anthropic.com/v1/messages

   7. Select POST as an HTTP Request Method
   8. Inside the header, add:

      anthropic-version: 2023-06-01

   9. In the Body content type, select 

      JSON(application/json)

1. Use this as the body:
   

   {
     "model": "claude-sonnet-4-6",
     "max_tokens": 1024,
     "messages": [
       {
         "role": "user",
         "content": "{YOUR-Message}"
       }
     ]
   }
2. Press on Preview to check the result.
3. You can use the Array filter to get the object you need, and you can use

   $.messages[*].content

     to get only the message.
4. Click OK to save the configuration.
   

   Claude – JSON source request

Configure the Destination

1. Drag and drop a destination component (e.g., Trash destination) into the Data Flow.
2. Connect the output arrow from the JSON Source to the destination component.
3. Double-click the destination component and configure it to point to your target table or file.
4. Map the columns from the response to the appropriate destination columns
5. Click OK to save the destination configuration.
6. Execute the package and verify that the data extraction is working correctly.
   

   Claude – Final Result

Conclusion

You now have a secure and reliable connection between Zappysys SSIS and Claude. API Key authentication is simpler to set up with our HTTP connection. With this connection configured, you can build powerful data extraction, transformation, and loading workflows using Claude’s intelligence and automation capabilities directly from your SSIS packages without writing any custom code.

Explore the full capabilities of the ZappySys SSIS PowerPack to optimize your data integration tasks. By applying this pattern, you can extend your solution to include additional transformations, data validation, error handling, and scheduling through SQL Server Agent.

Need Help?

If you encounter any issues, our support team is here to help:

1. Live Chat — Use the chat widget (bottom-right corner of this page)
2. Email — support@zappysys.com
3. Support Center — Visit the ZappySys Support Portal

The post SSIS Tutorial: How to connect Claude to SSIS appeared first on ZappySys Blog.

Introduction

Jamf Pro is a comprehensive Apple device management platform that provides REST APIs for managing Macs, iPads, and iPhones across your organization. This guide demonstrates how to connect Zappysys ODBC drivers to Jamf Pro using OAuth 2.0 API authentication.

Whether you are using Jamf Cloud or an on-premises Jamf Pro server, you will learn how to configure a secure ODBC data source to access Jamf Pro data directly from Excel, Power BI, Tableau, or any application that supports ODBC without writing any custom code. Zappysys handles all the technical complexity, allowing you to focus on data analysis and reporting.

Prerequisites

1. Windows operating system with the ODBC Data Source Administrator available.
2. Active Jamf Pro account with administrator privileges for API client configuration.
3. Finally, do not forget to install ZappySys ODBC PowerPack.

Steps

Generate Jamf credentials

1. Log in to your Jamf Pro instance as an administrator.
2. Navigate to Settings > System Settings > API Roles and Clients.
   

   Jamf – API roles and clients

3. First, create a new API Role with the required permissions:
   • Click API Roles, then click + New.
   • Enter a descriptive name (e.g., ODBC Integration Role).
   • Assign permissions based on your use case:
     • Check Read for data extraction (computers, devices, users)
     • Check Create, Update, or Delete only if you need to write data back to Jamf Pro
   • Click Save.
     

     Jamf – new API role

4. Now, create an API Client:
   • Go back to API Roles and Clients and select the API Clients tab.
   • Click + New in the upper right corner.
   • Enter a Display Name (e.g., ODBC Connector).
   • Select the API Role created in the previous step.
   • Toggle Enable API client to ON, then click Save.
5. Generate client credentials:
   • Select Generate client secret and click Create secret in the pop-up dialog.
   • Copy and securely save the Client ID and Client Secret for use in the next steps.
     

     Jamf – Generate Client ID and Client Secret

6. Record your Jamf Pro instance URL (e.g., https://your-company.jamfcloud.com).

Creating a new ODBC DSN using ZappySys JSON Driver

1. Search for ODBC in the Windows Start menu and open the ODBC Data Source Administrator.
   
2. In the User DSN or System DSN tab, click Add to create a new data source.
3. In the ODBC Data Source Setup window, select the ZappySys JSON Driver and click Continue.
   

Configuring the ODBC connection for Blogger

1. Enter the Jamf Pro API endpoint in the URL:
   • https://your-company.jamfcloud.com/JSSResource/computers — To retrieve computer inventory
   • https://your-company.jamfcloud.com/JSSResource/mobiledevices — To retrieve mobile device data
   • https://your-company.jamfcloud.com/JSSResource/users — To retrieve user information
   • https://your-company.jamfcloud.com/JSSResource/accounts — To retrieve account data
2. Select OAUTH as the connection type, then click it to configure it.
3. Set the OAuth Version to OAuth 2.0.
4. Set the Grant Type to Client Credentials Grant.
5. Provide the Client ID and Client Secret from the API Client created above.
6. Enter the Token URL:
   

   https://your-company.jamfcloud.com/api/oauth/token

7. Click OK to save the connection.
8. Set the HTTP method to GET.
9. Select the object you want to use in the Array Filter (e.g., $.account)
10. Click Test Connection to verify your credentials and API access.
    

    Jamf – ODBC JSON driver configuration

Preview the data

1. Once your ODBC DSN is configured, go to the preview tab.
2. Select the table you want to use.
3. Press the Preview data button to see the result.
   

   Jamf – ODBC JSON driver result

Conclusion

You now have a secure and flexible ODBC connection to Jamf Pro using OAuth 2.0 authentication. This approach allows you to access Jamf Pro data directly from any ODBC-compatible application—Excel, Power BI, Tableau, SQL Server, or custom applications—without writing any code. With your ODBC data source configured, you can create powerful dashboards, run ad-hoc queries, generate compliance reports, and integrate Jamf Pro device management data with your existing business intelligence tools.

Explore the full capabilities of the ZappySys ODBC PowerPack to optimize your data integration tasks. By applying this pattern, you can extend your solution to include additional data sources and create unified reporting across multiple cloud-based APIs.

Need Help?

If you encounter any issues, our support team is here to help:

1. Live Chat — Use the chat widget (bottom-right corner of this page)
2. Email — support@zappysys.com
3. Support Center — Visit the ZappySys Support Portal

The post ODBC tutorial: How to connect Jamf with ODBC appeared first on ZappySys Blog.

Introduction

Jamf Pro is a comprehensive Apple device management platform that provides REST APIs for managing Macs, iPads, and iPhones across your organization. This guide demonstrates how to connect Zappysys SSIS connectors to Jamf Pro using OAuth 2.0 API authentication.

Whether you are using Jamf Cloud or an on-premises Jamf Pro server, you will learn how to configure secure OAuth 2.0 authentication without writing any custom code. Zappysys handles all the technical complexity, allowing you to focus on building your ETL workflows for managing device inventory, policy configurations, and compliance reporting.

Prerequisites

1. SQL Server Integration Services (SSIS) must be installed.
2. Visual Studio with SSIS extension or SQL Server Data Tools (SSDT) is required.
3. Active Jamf Pro account with administrator privileges for API client configuration.
4. Finally, do not forget to install ZappySys SSIS PowerPack.

Steps

Generate Jamf credentials

1. Log in to your Jamf Pro instance as an administrator.
2. Navigate to Settings > System Settings > API Roles and Clients.
   

   Jamf – API roles and clients

3. First, create a new API Role with the required permissions:
   • Click API Roles, then click + New.
   • Enter a descriptive name (e.g., Admin).
   • Assign permissions based on your use case:
     • Check Read for data extraction (computers, devices, users)
     • Check Create, Update, or Delete only if you need to write data back to Jamf Pro
   • Click Save.
     

     Jamf – new API role

4. Now, create an API Client:
   • Go back to API Roles and Clients and select the API Clients tab.
   • Click + New in the upper right corner.
   • Enter a Display Name (e.g., SSIS Connector).
   • Select the API Role created in the previous step.
   • Toggle Enable API client to ON, then click Save.
5. Generate client credentials:
   • Select Generate client secret and click Create secret in the pop-up dialog.
   • Copy and securely save the Client ID and Client Secret for use in the next steps.
     

     Jamf – Generate Client ID and Client Secret

6. Record your Jamf Pro instance URL (e.g., https://your-company.jamfcloud.com).

Create the OAuth connection

1. Create or select your SSIS project and open the package.
2. Right-click in the Connection Managers pane and select New Connection…
3. Select ZS-OAUTH from the SSIS connectors list.
   

   Create a new SSIS OAuth API Connection Manager

4. Set the OAuth Version to OAuth 2.0.
5. Set the Grant Type to Client Credentials Grant.
6. Enter the Client ID and the Client Secret from the API Client created above
7. Enter the Token URL:
   

   https://your-company.jamfcloud.com/api/oauth/token

8. Click OK to save the connection.
   

   Jamf – OAuth connection

Create and Configure the JSON source

1. In your SSIS package, drag and drop a Data Flow Task from the Toolbox into the Control Flow.
   

   Drag and drop Data flow

2. Double-click the Data Flow Task to enter the Data Flow tab.
3. In the Data Flow, drag and drop a ZS JSON Source component from the Toolbox.
4. Double-click the JSON Source to open its editor.
5. Select your Jamf OAuth connection from the Connection Manager dropdown.
6. Enter the Jamf Pro API endpoint path in the URL field. For example:
   • https://your-company.jamfcloud.com/JSSResource/accounts — To retrieve account data
   • https://your-company.jamfcloud.com/JSSResource/computers — To retrieve computer inventory
   • https://your-company.jamfcloud.com/JSSResource/mobiledevices — To retrieve mobile device data
   • https://your-company.jamfcloud.com/JSSResource/users — To retrieve user information
7. Set the HTTP Method to GET for data retrieval.
8. Configure the JSON Path Filter to extract the specific object you need from the response (e.g., $.account or $.computers).
9. Click Preview to see sample data from the Jamf Pro API.
   

   Jamf – JSON source request

Step 4: Configure the Destination

1. Drag and drop a destination component (e.g., Trash destination) into the Data Flow.
2. Connect the output arrow from the JSON Source to the destination component.
3. Double-click the destination component and configure it to point to your target table or file.
4. Map the columns from the Jamf Pro API response to the appropriate destination columns
5. Click OK to save the destination configuration.
6. Execute the package and verify that the data extraction is working correctly.
   

   Jamf – Final Result

Conclusion

You now have a secure, reliable connection between Zappysys SSIS and Jamf Pro via OAuth 2.0. This modern, secure approach eliminates the need to store plaintext credentials and simplifies credential rotation and management. With your OAuth connection configured and JSON source component in place, you can build powerful ETL workflows to extract device inventory, policy data, user information, and compliance metrics from Jamf Pro—all flowing directly into your SQL Server database or data warehouse without writing a single line of custom code.

Explore the full capabilities of the ZappySys SSIS PowerPack to optimize your data integration tasks. By applying this pattern, you can extend your solution to include additional transformations, data validation, error handling, and scheduling through SQL Server Agent.

Need Help?

If you encounter any issues, our support team is here to help:

1. Live Chat — Use the chat widget (bottom-right corner of this page)
2. Email — support@zappysys.com
3. Support Center — Visit the ZappySys Support Portal

The post SSIS tutorial: How to connect Jamf with SSIS appeared first on ZappySys Blog.