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.

The Root Cause: In-Process Driver Risks

When you configure a Linked Server using the OLE DB Provider for ODBC (MSDASQL), the third-party driver runs inside the SQL Server process (sqlservr.exe). This is the “In-Process” model, and it has significant architectural flaws:

SQL Server Linked Server ODBC Crash Zone

• Memory Contention: The driver shares SQL Server’s memory heap, meaning driver memory leaks directly starve the SQL Buffer Pool.
• Unmanaged Code: You are executing third-party native code directly inside the database engine.
• The Fatal Crash: If the driver hits an access violation (error 0xc0000005), it kills the entire sqlservr.exe process, taking all databases offline.

The “Zero-Touch” Remote Isolation Model

ZappySys Data Gateway introduces Process Isolation. Instead of installing risky drivers on your production database host, you can run the Gateway on a Remote PC or dedicated App Server.

Architectural diagram of ZappySys Data Gateway using TDS protocol to provide safe, out-of-process data integration for SQL Server.

• No Drivers on SQL Server: You never have to touch your SQL Server machine or install third-party .dll files on it.
• Native TDS Communication: SQL Server communicates with the Gateway using the standard, Microsoft-hardened TDS protocol.
• Engine Stability: If a cloud API failure or driver bug occurs, it happens in the isolated ZappySysGateway.exe process—SQL Server stays online.

Supported Connectors via ZappySys Integration Hub

ZappySys provides a secure, out-of-process bridge for hundreds of modern data sources.

Native API & Cloud Connectors

• CRM/ERP: Salesforce, Dynamics 365, HubSpot, ServiceNow, Zoho CRM.
• Marketing: Amazon Ads, Google Ads, Google Search Console, Mailchimp.
• Collaboration: SharePoint Online, Google Sheets, Jira, Azure DevOps, OneDrive.

Big Data & NoSQL (Safe JDBC Bridge)

Systems using Java-based drivers run safely within the Gateway process, preventing JDBC memory overhead from affecting SQL Server:

• Sources: Google BigQuery, Amazon Athena, MongoDB, Infor Data Lake, Cosmos DB.

Side-by-Side Comparison

Summary: Protect Your Production Uptime

A driver bug should fail a query—it should never crash your production database engine. ZappySys Data Gateway provides the architectural “firewall” your infrastructure deserves.

The post Stop SQL Server Crashes: Why ZappySys Data Gateway Beats ODBC Linked Servers appeared first on ZappySys Blog.

If you’re using ZappySys SSIS Power Pack to manage files in Azure Data Lake Storage Gen2 (ADLS v2)—including hierarchical folders required by many modern data lake workloads (for example, Parquet-based pipelines)—this guide walks you through the complete setup process step by step.

Steps

Validating your Azure Storage Account Is Gen2 (ADLS v2)

Before connecting from SSIS, confirm that your Azure Storage Account is ADLS Gen2–enabled, which means it supports a hierarchical namespace.

1. Check the Storage Account Type. Go to Azure Portal → Storage Accounts and verify that your account is ADLS v2 (Gen2).
   

   Validate Your Account Type

2. Open the storage account
3. Locate Hierarchical namespace
4. Ensure it is set to Enabled
5. If hierarchical namespace is not enabled, click Enable
6. During the wizard, Azure may require Soft Delete to be turned off
7. Disable both soft delete options if prompted
   

   How to enable hierarchical namespace option in Azure Blob Storage – ADSL Gen2

Important
Enabling hierarchical namespace is a one-way operation. Once enabled, the storage account cannot be reverted to a flat namespace.

Connect Azure ADLS Gen2 in SSIS

ZappySys supports multiple authentication methods. The two most common options are Access Key and SAS Token.

Option A: Connect Using Storage Account Access Key. This is the simplest method and works well for internal or controlled environments.

1. Obtain the Access Key.
2. Go to your Storage Account.
3. Navigate to Access keys.
4. Copy Key1 or Key2.
   

   Azure Storage Account – Obtain Access Key for Connection API calls

5. Create or open an SSIS project in Visual Studio and add the ZappySys Azure Storage Task.
6. Create a new connection and choose Access Key authentication.
7. Enter the Storage Account Name and Access Key and test the connection.
   

   Connect Azure Storage Account in SSIS – Using Access Key Method

Option B: Connect Using SAS Token (Recommended for Least-Privilege Access). SAS tokens are ideal when you want restricted, time-bound, or container-level access.

1. Navigate to the Target Container
2. Open Storage Account → Containers.
3. Select the container you want to grant access to.
   

   Containers in Azure Portal

4. Click Generate SAS to generate a Container-Level SAS Token.
5. Select required permissions (Read / Write / List / Delete).
6. Set expiration date.
7. Generate and copy the SAS URL.
   

   Azure Storage Account – Generate SAS Token (Container Level)

Recommended: Use SAS URL for quicker and more reliable configuration. While SAS Token authentication is still supported, Copy SAS URL is easier and more user-friendly because it already includes the container path. When you paste the SAS URL into the Connection UI, the container name is automatically detected, eliminating the need to enter it as a separate step manually.

8. Go to our Microsoft Azure Blob connection and use the SAS Token in SSIS
9. Choose SAS Token authentication in the Azure Storage Task and provide the SAS Token or URL.
10. Test the connection and click OK to save the configuration.
    

    Connect Azure Storage Account in SSIS – Using SAS Token Method

Download Files from Azure ADLS Gen2 in SSIS

1. Inside the ZappySys Azure Storage Task, select the connection created in the previous step.
2. Use the option DownloadAzure File(s) to local directory.
3. Select the Parquet or CSV files you want to download. You can pull files from date-partitioned folders and use dynamically built paths with SSIS variables.
   

   Download Azure Storage Files in SSIS (ADSL v2 or Legacy Blob Storage)

Upload Files to Azure ADLS Gen2 in SSIS

1. Change the Storage Action to Upload local file(s) to Azure.
2. Upload single files or entire folders.
3. Choose between Overwrite or skip existing files.
4. Use the ZappySys placeholder engine to dynamically build source and destination paths.
   

   Upload Local Files to Azure Blob Storage in SSIS (ADSL v2 or Legacy Blob Storage)

Other Azure Storage File Operations

The Azure Storage Task supports many additional operations:

• Sync folders
• Create containers or directories
• Delete files or folders
• List files recursively
  

  Azure Storage File Operations in SSIS (Sync, Create, Delete, List)

Advanced Filtering and Sorting

Most operations support advanced filtering and sorting options. These options are available under the Advanced Filter and Sorting tab:

• Filter by file name
• Filter by size
• Filter by modified date
• Sort ascending or descending
• Limit the number of files processed
  

  More filter options

Similar filtering capabilities are also available in:

• Amazon S3 Storage Task
• Secure FTP Task
• Other ZappySys file-based connectors

Summary

With ZappySys SSIS Power Pack, you can fully manage Azure Data Lake Storage Gen2 directly inside SSIS—including hierarchical folders, secure authentication, and advanced file operations—without writing custom code.

This makes it easy to:

• Build modern data lake pipelines
• Work with Parquet and partitioned data
• Secure access using SAS tokens
• Automate file movement at scale

Still need help?

If the issue persists, please get in touch with our support team:

• Live Chat: Open the chat widget (bottom right of this page)
• Email: support@zappysys.com
• Support Center: Support | ZappySys

The post SSIS: How to download & upload files from Azure Data Lake Storage Gen2 (ADLS v2) appeared first on ZappySys Blog.

In this article, you will learn how to download Outlook (Office 365) emails as .EML or .MSG files using ZappySys SSIS PowerPack without writing any code. We’ll leverage the power of Microsoft Graph API, which provides unified access to Microsoft 365 services like Outlook Mail, and integrate it seamlessly using the API Connector for SSIS Outlook Mail (Office 365), Web API Destination and other components. By the end, you’ll be able to automate the process of extracting emails and saving them to disk in standard email formats directly from your SSIS package.

Step 1: Register an Application in Azure Portal

To access Outlook emails via Microsoft Graph API, the first step is to register an application in the Azure Portal. This allows your SSIS package to authenticate securely and retrieve mail data from Office 365.
Step by step info is available here Outlook Mail (Office 365) Connector Authentication section.

User Credentials

Use delegated access (User Credentials) whenever you want to let a signed-in user work with their own resources or resources they can access. Whether it’s an admin setting up policies for their entire organization or a user deleting an email in their inbox, all scenarios involving user actions should use delegated access.
Refer to this links for the detailed steps: User Credentials [OAuth]

Application Credentials

Application-only access is broader and more powerful than delegated access (User Credentials), so you should only use app-only access where needed. Use it when:

1. The application needs to run in an automated way, without user input (for example, a daily script that checks emails from certain contacts and sends automated responses).
2. The application needs to access resources belonging to multiple different users (for example, a backup or data loss prevention app might need to retrieve messages from many different chat channels, each with different participants).
3. You find yourself tempted to store credentials locally and allow the app to sign in ‘as’ the user or admin.

Refer to this links for the detailed steps: Application Credentials [OAuth]

Step 2: Download Outlook (Office 365) Emails as .EML Files using SSIS

Now let’s look at some examples of how to access your Outlook emails using our easy-to-use Outlook Mail Connector in ZappySys SSIS PowerPack. This connector simplifies calling the Microsoft Graph API, so you can retrieve emails with just a few clicks.
In this section we will learn how to configure and use Outlook Mail (Office 365) Connector in API Source to extract data from Outlook Mail (Office 365).

1. Begin with opening Visual Studio and Create a New Project.
2. Select Integration Service Project and in new project window set the appropriate name and location for project.
   And click OK.
3. In the new SSIS project screen you will find the following:
   1. SSIS ToolBox on left side bar
   2. Solution Explorer and Property Window on right bar
   3. Control flow, data flow, event Handlers, Package Explorer in tab windows
   4. Connection Manager Window in the bottom

   

   Note: If you don’t see ZappySys SSIS PowerPack Task or Components in SSIS Toolbox, please refer to this help link.
4. Now, Drag and Drop SSIS Data Flow Task from SSIS Toolbox. Double click on the Data Flow Task to see Data Flow designer.
5. From the SSIS toolbox drag and API Source (Predefined Templates) on the data flow designer surface, and double click on it to edit it:
   
6. Select New Connection to create a new connection:
   
7. Use a preinstalled Outlook Mail (Office 365) Connector from Popular Connector List or press Search Online radio button to download Outlook Mail (Office 365) Connector. Once downloaded simply use it in the configuration:
   

   Outlook Mail (Office 365) Connector Selection

8. Proceed with selecting the desired Authentication Type. Then select API Base URL (in most cases default one is the right one). Finally, fill in all the required parameters and set optional parameters if needed. You may press a link Steps to Configure which will help set certain parameters. More info is available in Authentication section.
   1. User Credentials [OAuth]
      

      User Credentials [OAuth]

      OR
   2. Application Credentials [OAuth]
      

      Application Credentials [OAuth]

9. Select the Get Messsages endpoint, change/pass the properties values, and click on Preview Data button to make the API call.
   

   API Source – Get Messages Endpoint

10. That’s it — click OK and you’re done! In just a few clicks, you’ve successfully configured a connection to Outlook Mail (Office 365) using the Outlook Mail Connector.
11. Now let’s move to the next step — retrieving the full email content.
    You’ll use the Web API Destination component to make the Get MIME content API call. Within this task, you can dynamically pass the Message ID to fetch each email’s raw .EML content from Outlook (Office 365).
    For more details, refer to the official Microsoft documentation: Get Outlook Mail MIME content
12. Drag and drop the Web API Destination component from the SSIS Toolbox onto your Data Flow.
    Double-click to open it, then configure as follows and create a new OAuth Connection if needed:URL:

    https://graph.microsoft.com/v1.0/me/messages/<%Id%>/$value

    The <%Id%> placeholder is dynamically replaced by SSIS at runtime with the actual Message ID, allowing the Web API Destination to download each email’s .EML content individually.

    

    Get MIME content’ API call using the Web API Destination

13. You’ll also need to create the OAuth connection using the same credentials.
    On the Advanced tab, make sure to set the Redirect URL correctly.For detailed steps, refer to this guide:
    How to set up OAuth 2.0 in SSIS
    

    Outlook Mail OAuth 2.0 Connection

14. Next, add a Derived Column transformation to create a new column that defines the file path for saving the .EML file.
    In this example, we’ll use the Message ID to generate a unique file name for each email:Expression:

    (DT_WSTR,1000)”E:\\zsTemp\\” + [Id] + “.eml”

    

    Derived Column – Dynamic File Path

15. Now, add an Export Column transformation to save the email content to a file.
    • Extract Column: set to ResponseText (this holds the email content from Web API Destination)
    • File Path Column: set to the column you created in the Derived Column step (e.g., FilePath)
    • Enable Force Truncate and Write Byte-Order Mark options
    

    Export Column – write the email content to a file on disk.

16. Set File Encoding to UTF-8 (Optional)
    Next, go to the Control Flow and use the Advanced File System Task to convert the downloaded .eml file’s encoding to UTF-8.
    This step is optional — I had to apply it on my system because the files weren’t opening correctly due to a non-UTF-8 encoding.
    If you encounter a similar issue, follow this step to ensure proper compatibility with email clients.
    

    Advanced File System Task – Change Encoding

17. That’s it! The process will now automatically download your Outlook messages to your local system as .EML files.
    

    Outlook .eml file’s

Conclusion

Using ZappySys SSIS PowerPack and Microsoft Graph API, you can easily automate the download of Outlook (Office 365) emails in .EML format — all within SSIS and without writing any code.
This approach is ideal for archiving, compliance, or integrating email content into downstream systems.
With a few simple components and steps, your email extraction workflow can be up and running in minutes.

The post How to download Outlook (Office 365) Emails as .EML or .MSG Files appeared first on ZappySys Blog.

In this article, we will explore some MongoDB query tricks that can help you retrieve the information you require. Be sure to check out our articles on MongoDB source and MongoDB execute SQL task here.

Examples

Filtering by Date: First, let’s look at filtering data by date. Ensure that your database has the date column in the same format. You can filter by date using either of these formats:

Select date from dataTable where date > '2019-08-17 10:42:20'

“Or”

select date from dataTable where date > '2019/08/17 10:42:20'

Getting the Highest Date: If you need to retrieve the highest date in a column, you can use the ‘Order by’ command along with ‘top 1’. Use DESC for the highst result and ASC for the lowest result.

Select top 1 date from dataArray order by date DESC

Highest Date Example

Sorting Orders: The following SQL statement selects all orders from the ‘OrdersList’ table. It sorts the results in ascending order by the ‘AddressInfo.City’ and in descending order by the ‘stars’ column

SELECT * FROM OrdersList ORDER BY AddressInfo.City ASC, stars DESC

Sorting Orders Example

Matching Elements in an Array: In the next example, we are attempting to match elements inside an array

Select * from OrdersList where Tags in ('ca', 'aa')

Matching Elements Example

Excluding Elements from an Array: You can also exclude elements that are not in the array

Select * from OrdersList where Tags NOT in ('ca', 'aa')

Excluding Elements Example

Conclusion

These are some examples that you can utilize with our SQL tool. If you want to explore more complex examples, you can refer to this article.

The post MongoDB Query Tricks for Getting the Information You Need appeared first on ZappySys Blog.

OpenAI, the creators of ChatGPT, provide both a web interface and an API for seamless integration of their tools into applications. This article provides a comprehensive guide on how to establish a connection with the OpenAI API in SSIS using ZappySys JSON Source, enabling seamless data integration and retrieval.

Prerequisites

Before we perform steps listed in this article, you will need to make sure following prerequisites are met:

1. SSIS designer installed. Sometimes it is referred as BIDS or SSDT (download it from Microsoft site).
2. Basic knowledge of SSIS package development using Microsoft SQL Server Integration Services.
3. Make sure ZappySys SSIS PowerPack is installed (download it).
4. Optional (If you want to Deploy and Schedule ) – Deploy and Schedule SSIS Packages

Step-by-step guide to making a ChatGPT Rest API call

How to get an OpenAI API Key for ChatGPT

First, obtain your API key from OpenAI. This key is required for authenticating your requests.

To access the services, you will be required to set up an account with OpenAI. Click here to create your account. Once your account has been successfully created, proceed to log in to your OpenAI account.

You can find the API key by following these steps:

1. Navigate to the top right corner of the screen.
2. Click on your account name.
3. From the drop-down menu, select “API Keys.”
4. Alternatively, you can directly access the API Keys section by clicking here.

To generate a new secret key, please follow these steps:

1. Go to the API Keys page.
2. Look for the “Create new secret key” button.
3. Click the button to generate a new secret key.

Generate a new key

Upon generation, your API key will be visible on the screen. It’s crucial to copy the key and store it in a secure location immediately, as it will not be displayed again for security purposes.

The new key

Now that you have your API key, you can begin utilizing it to make calls with your components. A preliminary example involves retrieving a list of all available models in OpenAI. For detailed instructions, please refer to the API documentation available here.

ChatGPT Rest API call using JSON Source

1. Drag and Drop the SSIS Data Flow Task from the SSIS Toolbox.

Drag and drop Data flow task

2. Double-click on the DataFlow task to see the DataFlow designer surface.

3. From the SSIS toolbox drag and drop ZS JSON Source on the dataflow designer surface.

Drag and drop a JSON source

4. We will use this on the URL path:

https://api.openai.com/v1/models

5. In the HTTP headers grid add the following values by clicking Raw Edit button :

Authorization: Bearer YOUR_OPENAI_API_KEY
OpenAI-Organization: org-YQ9qpxxxxxxxxxxxxgoPi

6. Select your preferred Array Filter, simply click the “Select Filter” button. for this API call we need to select the

$.data[*]

7. Final step: Click ‘Preview’ to initiate the ChatGTP Rest API call. You will also find a demonstration within our component, along with the resulting output from the call, below.

ChatGPT call

That’s it the configuration for the ChatGPT Rest API call has been completed successfully.

Load ChatGPT data in SQL Server using Upsert Destination (Insert or Update)

ZappySys SSIS PowerPack makes it easy to load data from various sources such as REST, SOAP, JSON, XML, CSV or from other source into SQL Server, or PostgreSQL, or Amazon Redshift, or other targets. The Upsert Destination component allows you to automatically insert new records and update existing ones based on key columns. Below are the detailed steps to configure it.

Step 1: Add Upsert Destination to Data Flow

1. Drag and drop the Upsert Destination component from the SSIS Toolbox.
2. Connect your source component (e.g., JSON / REST / Other Source) to the Upsert Destination.

SSIS - Data Flow - Drang and Drop Upsert Destination Component

Step 2: Configure Target Connection

1. Double-click the Upsert Destination component to open the configuration window.
2. Under Connection, select an existing target connection or click NEW to create a new connection.
   • Example: SQL Server, or PostgreSQL, or Amazon Redshift.

Step 3: Select or Create Target Table

1. In the Target Table dropdown, select the table where you want to load data.
2. Optionally, click NEW to create a new table based on the source columns.

Configure SSIS Upsert Destination Connection - Loading data (REST / SOAP / JSON / XML /CSV) into SQL Server or other target using SSIS

Step 4: Map Columns

1. Go to the Mappings tab.
2. Click Auto Map to map source columns to target columns by name.
3. Ensure you check the Primary key column(s) that will determine whether a record is inserted or updated.
4. You can manually adjust the mappings if necessary.

SSIS Upsert Destination - Columns Mappings

Step 5: Save Settings

• Click OK to save the Upsert Destination configuration.

Step 6: Optional: Add Logging or Analysis

• You may add extra destination components to log the number of inserted vs. updated records for monitoring or auditing purposes.

Step 7: Execute the Package

• Run your SSIS package and verify that the data is correctly inserted and updated in the target table.

SSIS Upsert Destination Execution

Conclusion

In this article, we explored the seamless process of establishing a connection with ChatGPT in SSIS and integrating data effortlessly, all without the need for coding. Interested in trying it out yourself? Feel free to Download ZappySys SSIS PowerPack by clicking here and experience the simplicity firsthand. Should you have any lingering queries, please don’t hesitate to ask by clicking here or initiating a conversation with our experts via the live chat icon at the bottom-right corner of this page.

The post Call ChatGPT REST API in SSIS appeared first on ZappySys Blog.

In SQL Server Integration Services (SSIS), validating expressions, paths, and URLs is a crucial part of ensuring the integrity and success of your data integration processes. In this article, we’ll explore how the Validator Task can help you achieve this.

Before we dive into practical examples, be sure to check our comprehensive Validator Task article to discover the full range of options it offers. You can access it here.

Validating an Example

Let’s start by validating an example stored in a variable. You can source your example data from a variety of components, such as the Set Variable Transformation (see our article here) or the REST API Task (read more here). Once you have the example data in a variable, the Validator Task comes into play. You can configure the necessary expressions, as demonstrated in this example.

Configurate the validator task to compare two string.

Validating a File or a Folder

In some cases, you may need to validate a path, which might involve checking file or folder properties, such as their existence or size. Our advanced File System Task or SFTP Task can help you accomplish this. In our example, we’ll show you how to count the number of files in a folder and trigger a pass condition when there are more than five files.:

We employ a wildcard to retrieve all TXT files from the folder and store the result in a variable called “count.”

Validate the result: Next, we’ll drag and drop the Validator Task and select “Check SSIS expression (true or false).” We’ll use the expression @[User::count]==3 to validate whether we have 3 files in that folder. We’ll set the expected result as true, and we’ll also check the option to save the validator status to a variable and throw an error if the validator fails to terminate the package.

You can validate the expressions with the result you want (true/false)

You will receive a valid example, and the package will run successfully, or it will fail, as shown in this example:

Example from success and a failure example

You can use more examples, such as checking if a file exists or verifying the existence of a folder using the Advanced File System, Validator Task or other components.

Some examples for advanced file system task and Secure FTP task

Validating a URL

There are scenarios where the success of a URL is critical. If a URL fails, you may want your SSIS process to stop. Here’s an example of how to set up a REST API Task to handle errors, save the result in a variable, and use the Validator Task to mark a URL as invalid in case of failure.

Use this option to continue on any error and save the result in a Boolean variable

Now for validator task we set up the next configuration:

Validate if the URL is valid

The last step is running the package. Here you will see the two cases.

Comparing both results if the URL is valid or not

Conclusion

In conclusion, the Validator Task in SSIS empowers you to dynamically choose the path you need based on the results of previous tasks. This flexibility can significantly enhance the efficiency of your data integration processes, ultimately saving you time and ensuring data integrity.

For additional information, you can check articles for Advanced file system task, Secure FTP task and Validator task.

You can apply this approach to other components where you need to capture a result in a variable and then use the Validator Task.

The post Examples with Validator task appeared first on ZappySys Blog.