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.

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

Integrating Tripletex with SQL Server Integration Services (SSIS) lets you synchronize accounting data with databases, reporting systems, and other business applications. ZappySys SSIS PowerPack simplifies this process by providing components that handle HTTP requests, authentication, and data extraction without requiring custom code.

This tutorial walks you through the complete process of creating Tripletex API credentials, generating a session token, and building an SSIS package that extracts data from Tripletex.

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. Install ZappySys SSIS PowerPack.

Steps

Generate 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 a Tripletex session token

Tripletex requires a session token for API authentication. The session token is generated from the Consumer Token and Employee Token obtained in the previous step.

1. In your SSIS package, navigate to the Variables section and create the following variables:
   1. ConsumerToken (String) — Enter the Consumer Token from the previous step.
   2. EmployeeToken (String) — Enter the Employee Token from the previous step.
   3. SessionToken (String) — Stores the generated session token.
   4. CompanyID (String) — Enter your Tripletex company ID, or use 0 if it is 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-12-31

7. For production environments, use:
   

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

8. Use a future expiration date when you generate the token. If you copy these examples later, replace the sample date before testing.
9. Set the HTTP Request Method to PUT.
10. Test the connection. If successful, you will see the generated session token in the response.
    

    Tripletex – Generate Session Token

Use an HTTP dynamic token connection (recommended)

You can also generate and reuse the session token through an HTTP connection with a dynamic token configuration.

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-12-31

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

   Tripletex – SSIS HTTP connection

7. Go to the Dynamic Token tab.
8. Enter the previous URL.
9. Set 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 it is 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 Authorization 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), select Use credentials and choose 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 dialog.
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 data extraction is working correctly.
   

   Tripletex – Final Result

Conclusion

You have now 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 the Tripletex API, and loading it into SQL Server or another destination.

This pattern can help automate business processes such as invoice tracking, customer synchronization, project reporting, and financial analysis. By using ZappySys SSIS PowerPack, you can build the workflow with less custom code while keeping the package easier to maintain.

Explore the full capabilities of ZappySys SSIS PowerPack to extend this solution with additional transformations, data validation, error handling, and scheduling through SQL Server Agent.

Frequently Asked Questions

Why does Tripletex require a session token?

Tripletex uses a session token for API authentication. In this workflow, the session token is generated from the Consumer Token and Employee Token before SSIS sends requests to the API.

Should I use the REST API Task or a dynamic token connection?

Both approaches can work. A dynamic token connection is often easier to reuse across multiple components because the token generation logic is stored in the connection instead of being repeated in each task.

What should I check if authentication fails?

Confirm that the Consumer Token and Employee Token are correct, the expiration date is still in the future, and the Authorization header contains the expected Company ID and session token values.

Next step

If you want to build similar API integrations in SSIS, download SSIS PowerPack and use the same pattern for other REST API workflows.

Need Help?

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

1. Live Chat — Use the chat widget in the 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.

This tutorial walks you through the process of extracting blog posts and comments data from Blogger using the REST API and Zappysys SSIS connectors. In this guide, you will learn how to authenticate with the Blogger REST API, configure a Zappysys REST data source, and load extracted data into SQL Server. This approach eliminates the need for custom code and provides a graphical interface for managing complex API integrations.

Zappysys provides a powerful REST connector that simplifies integrating cloud-based APIs into your SQL Server Integration Services packages. We will demonstrate a practical ETL pattern using ZappySys REST connectivity to extract data from Blogger and load it into SQL Server within SSIS.

Prerequisites

Before you begin, make sure you have the following:

• First, you will need to have SSIS installed
• Secondly, make sure to have SSDT
• Thirdly, access to a Blogger blog with appropriate permissions to read public posts and comments.
• Finally, do not forget to install ZappySys SSIS PowerPack.

Steps

Create/Select a Project in the Google API Console

1. Navigate to the Google API Console.
2. Click on the Project Dropdown at the top bar and either select an existing project or create a new one by clicking CREATE PROJECT.
   

   Google Console – Create or select a project

3. Once the project is set, click ENABLE APIS AND SERVICES.
4. Search for the Blogger API v3 and click ENABLE.
   

   Google Console – Enable Blogger API

5. Return to the main screen and click on the OAuth Consent Screen tab.
6. Select the External user type and click CREATE.
7. Provide the application name, user support email, and developer contact information, then click SAVE AND CONTINUE.
8. Click through the remaining scopes and summary pages (no additional scopes are required for this tutorial), and click SAVE AND CONTINUE on each.
9. Move to the Credentials tab.
10. Click CREATE CREDENTIALS in the top bar, choose OAuth Client ID, select Desktop App as the Application Type, and click Create to obtain your Client ID and Secret.
    

    Google Console – Create credentials

11. Download the credentials JSON file and save it in a secure location on your development machine.

Create the OAuth connection for Blogger

1. Create or select your SSIS project, and open the package.dtsx file.
2. Drag and drop the ZS REST API task from the Toolbox.
3. Inside Connection Manager, right-click and select New connection…
4. Inside the SSIS connectors, select the ZS-OAuth
   
   

   Create a new SSIS OAuth API Connection Manager

5. Select the Google API provider
6. Enter the Client ID and Client Secret you generated in the past step
7. Use Blogger URL scope: https://www.googleapis.com/auth/blogger
8. Generate the token
9. Test the connection to ensure it is working correctly.
10. Click OK to save the connection.
    

    OAuth connection – Blogger API

Get information from a Blog

1. Create a string variable {{User::BlogID}} and enter the ID from the blog you want to get information from.
2. From the SSIS Toolbox, drag the ZS REST API Task onto the Control Flow designer.
3. Double-click the task to open the editor.
4. Select the connection manager you created in the previous step.
5. In the URL Path field, enter: https://www.googleapis.com/blogger/v3/blogs/{{User::BlogID}}/posts
6. Set the HTTP method to GET.
7. Click the Preview tab to test the API connection and view sample data.
8. If the preview is successful, click OK to configure the task.
   

   REST API task – Blogger example

Save the information in a SQL table

1. Drag and drop a Data Flow into the Control Flow and double-click it.
   

   Drag and drop Data flow.

2. In the Data Flow, drag and drop the JSON source, then double-click it to configure it.
   

   SSIS JSON Source – Drag and Drop

3. Use the same configuration as in the REST API task, but first enable the Use credentials option.
4. Enter the URL, select the OAuth connection, and use the Method GET.
5. You can use the filter option to get the object you want to get data from: $.Items[*]
6. Preview the data and click OK to save the configuration.
   

   JSON Source – Blogger Example Request
7. Now drag and drop a destination component. In our case, we will use the Upsert destination component.
   

   SSIS – Data Flow – Drag and Drop Upsert Destination Component

8. Double-click in the Upsert destination component to configure it.
9. Select the Action you want to use.
10. Create or select a database connector.
11. Create or select a table.
12. Use the options Insert or/and Update.
13. Map the column; if the columns have the same name, it will be automatic.
14. Select at least one column for a primary key.
15. Click OK to save the configuration.
    

    Upsert destination – Blogger example

16. Run the package, and you will see the data from Blogger in your database
    

    Blogger – result

Code Examples

Sample REST API Request

Here’s an example of retrieving blog posts using the Blogger REST API:

GET https://www.googleapis.com/blogger/v3/blogs/{blogId}/posts
Authorization: Bearer {access_token}
Content-Type: application/json

Example response:

{
  "kind": "blogger#posts",
  "items": [
    {
      "kind": "blogger#post",
      "id": "7109703471293209437",
      "title": "Getting started with Blogger API",
      "content": "Learn how to integrate Blogger with your applications...",
      "published": "2026-03-15T10:30:00Z",
      "updated": "2026-03-20T14:15:00Z",
      "url": "http://example.blogspot.com/2026/03/getting-started.html",
      "author": {
        "displayName": "John Doe"
      }
    }
  ]
}

SQL Table Structure

Recommended table structure for storing Blogger posts data:

CREATE TABLE BloggerPosts (
    PostID BIGINT PRIMARY KEY,
    BlogID BIGINT NOT NULL,
    Title NVARCHAR(MAX),
    Content NVARCHAR(MAX),
    AuthorName NVARCHAR(255),
    PublishedDate DATETIME,
    UpdatedDate DATETIME,
    PostURL NVARCHAR(MAX),
    CreatedDate DATETIME DEFAULT GETDATE(),
    ModifiedDate DATETIME DEFAULT GETDATE()
);

Conclusion

You have successfully learned how to use Zappysys SSIS connectors to extract data from the Blogger
platform using the REST API. With ZappySys SSIS PowerPack, connecting Blogger to your SQL Server becomes
straightforward and reliable. By configuring the REST connector for Blogger and using the native SSIS destination,
you can build a robust ETL pipeline for extracting blog data.

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 Blogger with SSIS appeared first on ZappySys Blog.

In our previous post, we explored how to read and write MongoDB data using the ZappySys MongoDB Source and Destination SSIS connectors. In this article, you will learn how to connect MariaDB to MongoDB using ZappySys SSIS PowerPack and transfer data between both systems.

We will demonstrate a practical ETL pattern using ZappySys ODBC/JDBC connectivity to extract data from MariaDB and load it into MongoDB within SSIS.

Prerequisites

Before you begin, make sure you have the following:

• First, you will need to have SSIS installed
• Secondly, make sure to have SSDT
• Thirdly, access credentials for both MariaDB and MongoDB
• Finally, do not forget to install ZappySys SSIS PowerPack and ZappySys ODBC PowerPack

Steps

Configure MariaDB Connection Using ODBC (JDBC Bridge)

Since MariaDB connectivity is handled via JDBC, we will use the ZappySys JDBC Bridge Driver to expose it as an ODBC data source.

1. Visit the official MariaDB website.
2. Download the latest MariaDB JDBC driver.
3. Save the .jar file locally, for example: D:\Zappysys\drivers\mariadb-java-client-3.5.7.jar
4. Download and install ZappySys ODBC PowerPack if not already installed.
5. Open ODBC Data Sources (64-bit).
   

   Open ODBC Data Sources

6. Create a User data source (User DSN) based on ZappySys JDBC Bridge Driver:
   

   Create a User data source

7. Configure the JDBC Connection. Fill in the connection details
   • Connection String  jdbc:mariadb://{host-name}:{port}/{database-name}

   • JDBC Driver File D:\Zappysys\drivers\mariadb-java-client-3.5.7.jar

   • Username root

   • Password ********

   • Connection Parameters[]
8. Click Test Connection. If configured correctly, you should see a success message.
   

   Zappysys JDBC – MariaDB

9. You can also use the Preview tab to select the table and execute SQL queries. For advanced SQL examples, refer to the JDBC Bridge documentation.
   

   Zappysys JDBC – MariaDB preview result

Connect MariaDB to SSIS

1. Open Visual Studio.
2. Create a New Project.
3. Select Integration Services Project.
4. Provide a project name and location, then click OK.
5. Drag and drop a Data Flow Task from the SSIS Toolbox onto the Control Flow surface.
   

   Drag and drop Data flow.

6. Double-click the task to open the Data Flow Designer.
7. Drag and drop an ODBC Source component into the Data Flow.
   

   Drag and drop the ODBC source.

8. Double-click the component to configure it.
9. Click New… to create a new ODBC Connection Manager.
   

   Creating an ODBC Connection Manager in SSIS

10. Select the MariaDB ODBC DSN you created earlier.
11. Click Test Connection and click OK to save the configuration.
    

    Creating an ODBC Connection Manager in SSIS from JDBC

12. Choose Data Access Mode: Table name or SQL command.
13. Select the desired table or enter a custom query.
14. Click Preview to validate the data, and click OK to save the configuration.
    
    

    Preview an ODBC Connection Manager in SSIS from JDBC

Configure MongoDB Destination

1. In the Connection Manager pane, click New Connection.
2. Select ZS-MONGODB.
3. Configure the connection:
   • Host
   • Username
   • Password
   • Database
4. Use the other tabs for more configuration if needed
5. Click Test Connection and Click OK.
   

   MongoDB connection configuration

6. Drag and drop the MongoDB Destination component.
   

   Drag and drop the MongoDB destination

7. Connect it to the ODBC Source and double-click to configure it.
8. Select the MongoDB connection.
   

   MongoDB Destination – Select connection

9. Go to the Properties tab and choose the operation and the target table.
   

   MongoDB Destination – Properties configuration

10. Go to the Column Mappings tab and map source columns to destination columns.
    

    MongoDB Destination – Map the columns.

11. Click OK to save the configuration.
12. Run the SSIS package. If everything is configured correctly, the data will be transferred from MariaDB to MongoDB.
    

    MongoDB Destination – Final Result

Conclusion

With ZappySys SSIS PowerPack and ODBC PowerPack, connecting MariaDB to MongoDB becomes straightforward and reliable.

By configuring the ODBC/JDBC bridge for MariaDB and using the native MongoDB destination in SSIS, you can build a robust ETL pipeline between the two databases.

Explore the full capabilities of the ZappySys SSIS PowerPack and ZappySys ODBC PowerPack to optimize your data integration tasks.

Need Help?

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

• Live Chat — Use the chat widget (bottom-right corner of this page)
• Email — support@zappysys.com
• Support Center — Support | ZappySys

The post SSIS tutorial: How to load MariaDB data into MongoDB appeared first on ZappySys Blog.

In our previous post, we explored how to read and write PostgreSQL data using the ZappySys PostgreSQL Source and Destination connectors for SSIS. In this article, you will learn how to connect MariaDB to PostgreSQL using ZappySys SSIS PowerPack and transfer data between both systems.

We will demonstrate a practical ETL pattern using ZappySys ODBC/JDBC connectivity to extract data from MariaDB and load it into PostgreSQL within SSIS.

Prerequisites

Before you begin, make sure you have the following:

• First, you will need to have SSIS installed
• Secondly, make sure to have SSDT
• Thirdly, access credentials for both MariaDB and PostgreSQL
• Finally, do not forget to install ZappySys SSIS PowerPack and ZappySys ODBC PowerPack

Steps

Configure MariaDB Connection Using ODBC (JDBC Bridge)

Since MariaDB connectivity is handled via JDBC, we will use the ZappySys JDBC Bridge Driver to expose it as an ODBC data source.

1. Visit the official MariaDB website.
2. Download the latest MariaDB JDBC driver.
3. Save the .jar file locally, for example: D:\Zappysys\drivers\mariadb-java-client-3.5.7.jar
4. Download and install ZappySys ODBC PowerPack if not already installed.
5. Open ODBC Data Sources (64-bit).
   

   Open ODBC Data Sources

6. Create a User data source (User DSN) based on ZappySys JDBC Bridge Driver:
   

   Create a User data source

7. Configure the JDBC Connection. Fill in the connection details
   • Connection String  jdbc:mariadb://{host-name}:{port}/{database-name}

   • JDBC Driver File D:\Zappysys\drivers\mariadb-java-client-3.5.7.jar

   • Username root

   • Password ********

   • Connection Parameters[]
8. Click Test Connection. If configured correctly, you should see a success message.
   

   Zappysys JDBC – MariaDB

9. You can also use the Preview tab to select the table and execute SQL queries. For advanced SQL examples, refer to the JDBC Bridge documentation.
   

   Zappysys JDBC – MariaDB preview result

Connect MariaDB to SSIS

1. Open Visual Studio.
2. Create a New Project.
3. Select Integration Services Project.
4. Provide a project name and location, then click OK.
5. Drag and drop a Data Flow Task from the SSIS Toolbox onto the Control Flow surface.
   

   Drag and drop Data flow.

6. Double-click the task to open the Data Flow Designer.
7. Drag and drop an ODBC Source component into the Data Flow.
   

   Drag and drop the ODBC source.

8. Double-click the component to configure it.
9. Click New… to create a new ODBC Connection Manager.
   

   Creating an ODBC Connection Manager in SSIS

10. Select the MariaDB ODBC DSN you created earlier.
11. Click Test Connection and click OK to save the configuration.
    

    Creating an ODBC Connection Manager in SSIS from JDBC

12. Choose Data Access Mode: Table name or SQL command.
13. Select the desired table or enter a custom query.
14. Click Preview to validate the data, and click OK to save the configuration.
    
    

    Preview an ODBC Connection Manager in SSIS from JDBC

Configure PostgreSQL Destination

1. In the Connection Manager pane, click New Connection.
2. Select ZS-POSTGRESQL.
3. Configure the connection:
   • Host
   • Username
   • Password
   • Port
   • Database name
4. Use the other tabs for more configuration if needed
5. Click Test Connection and Click OK.
   

   PostgreSQL connection configuration

6. Drag and drop the PostgreSQL Destination component.
   

   Drag and drop the PostgreSQL destination.

7. Connect it to the ODBC Source and double-click to configure it.
8. Select the PostgreSQL connection.
   

   PostgreSQL Destination – Choose the connection

9. Go to the Properties tab and choose the target table.
   

   PostgreSQL Destination – Choose the target table

10. Go to the Column Mappings tab and map source columns to destination columns.
    

    PostgreSQL Destination – Map the columns

11. Click OK to save the configuration.
12. Run the SSIS package. If everything is configured correctly, the data will be transferred from MariaDB to PostgreSQL.
    

    PostgreSQL Destination – Final result

Alternative Option — Using Upsert Destination

An alternative destination component is the Upsert Destination; you can replace it with the PostgreSQL destination. You can preview data from the element, select the options to insert or/and update, and more.

1. Replace the PostgreSQL Destination with the Upsert Destination.
2. Select your PostgreSQL connection.
3. Choose the target table.
4. Choose Insert or/and Update action.n
5. Map the columns.
6. Select the primary key column(s).
7. Configure additional options under the Advanced tab if needed.
   

   Upsert Destination – PostgreSQL destination table

8. Run the package to perform the upsert operation.
   

   Upsert Destination – Final result

Conclusion

With ZappySys SSIS PowerPack and ODBC PowerPack, connecting MariaDB to PostgreSQL becomes straightforward and reliable.

By configuring the ODBC/JDBC bridge for MariaDB and using the native PostgreSQL destination in SSIS, you can build a robust ETL pipeline between the two databases.

Explore the full capabilities of the ZappySys SSIS PowerPack and ZappySys ODBC PowerPack to optimize your data integration tasks.

Need Help?

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

• Live Chat — Use the chat widget (bottom-right corner of this page)
• Email — support@zappysys.com
• Support Center — Support | ZappySys

The post SSIS tutorial: Migrating MariaDB data to PostgreSQL appeared first on ZappySys Blog.

In this article, you’ll learn how to connect SSIS PowerPack (ZappySys) to AliPay OpenAPI to call REST endpoints from SSIS. We’ll focus on the practical integration pattern AliPay requires: sending requests to the OpenAPI gateway with the correct parameters and a valid RSA2 signature, then parsing JSON responses in SSIS.

AliPay OpenAPI basics (what SSIS must send)

AliPay OpenAPI calls typically go through a single gateway endpoint:

• Sandbox gateway:
  

  https://openapi-sandbox.dl.alipaydev.com/gateway.do

A request is built from:

• Standard parameters (for example: app_id, method, charset, sign_type, timestamp, version)
• biz_content (usually JSON)
• sign (a signature generated from the parameters using RSA/RSA2—AliPay recommends RSA2)

AliPay requires you to construct a “string to sign” from parameters and attach sign and sign_type to the request, then validate/verify responses using the AliPay public key.

High-level integration pattern in SSIS

Because AliPay signing is mandatory, the most reliable SSIS approach is a two-step pattern:

1. Generate the signature (RSA2) for the request parameters.
2. Call the AliPay gateway from ZappySys (REST API Task or REST API Source), passing the signed parameters.

ZappySys components support custom HTTP methods, headers, request bodies, and advanced options—so they work well once you have the signed payload ready.

Steps

Start in the AliPay Sandbox

AliPay strongly recommends using the sandbox for development and debugging. In the sandbox, you must:

• An AliPay Developer Account
• An AliPay App ID
• Use the sandbox gateway URL
• RSA2 Private Key (generated in AliPay developer console)
• AliPay Public Key (for verification)
• Access to the AliPay Sandbox environment (recommended for testing)

Decide where you will generate the RSA2 signature

You have three common options:

• Option A (Recommended): SSIS Script Task (C#) to generate signature
  Use a Script Task before the ZappySys call to build parameters and compute sign.
• Option B: Use an AliPay SDK in a small helper app
  Run it via Execute Process Task to output signed parameters (JSON/text), then pass them to ZappySys.
• Option C: Use a signing microservice
  SSIS calls your internal service to get sign, then calls AliPay.

AliPay’s documentation emphasizes the signature process and verification using the AliPay public key.

Example: What a signed AliPay request looks like

AliPay’s gateway model is “parameters + signature.” Conceptually, your final request includes:

• app_id
• method (the API name you’re calling)
• charset (often utf-8)
• sign_type (recommended RSA2)
• timestamp
• version
• biz_content (JSON)
• sign (computed over the canonicalized parameter string)

AliPay documents that sign and sign_type are appended after creating the string to be signed, and verification uses the AliPay public key.

Configure the ZappySys REST API Task (Control Flow)

Use this when operating (e.g., creating a payment, refunding, or querying).

1. Drag ZappySys REST API Web Service Task into Control Flow.
2. Set the task:
   • Method: POST (commonly used with AliPay gateway)
   • URL:
     

     https://openapi-sandbox.dl.alipaydev.com/gateway.do

   • Headers: use
     

     Content-Type: application/x-www-form-urlencoded

   • Body: form-encoded parameters; use this format: key1=value1&key2=value2…

     app_id=YOUR_APP_ID&method=alipay.trade.query&charset=utf-8&sign_type=RSA2&timestamp=2026-02-20 10:00:00&version=1.0&biz_content={"out_trade_no":"202602200001"}&sign=GENERATED_SIGNATURE

3. Click Test Request/Response to confirm you get a valid JSON response.
   

   Alipay REST API

Troubleshooting common AliPay + SSIS issues

• invalid-signature / missing-signature: most often caused by parameter ordering, incorrect URL-encoding, wrong key pair, or using sandbox keys against production (or vice versa).
• Wrong gateway: sandbox and production are fully isolated—ensure your app_id,keys, and gateway host match the environment.
• Encoding issues: confirm UTF-8 everywhere and ensure parameters are encoded exactly once before submission.
• Parsing JSON: use ZappySys JSON Source preview and JSONPath filters to flatten nested objects.

Security best practices

• Store private keys securely (SSIS variables protected, encrypted config, or secret vaults).
• Do not hardcode secrets in packages.
• Use a sandbox for development, then switch to production only after full validation.

Conclusion

Download SSIS PowerPack today and see for yourself how easy it is to connect SSIS PowerPack (ZappySys) to AliPay is absolutely achievable once you treat AliPay’s OpenAPI as a signed gateway integration. The key is generating a correct RSA2 signature for every request, then using ZappySys REST components to send the parameters and parse responses.

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 tutorial: How to connect to AliPay appeared first on ZappySys Blog.

In this article, we’ll learn how to integrate a documented API in Swagger with SQL Server Integration Services (SSIS) using ZappySys PowerPack.

Swagger enables us to visualize and test REST endpoints, while ZappySys SSIS provides advanced components for consuming APIs and transforming data in ETL processes.

Steps

Get the Swagger endpoints

1. Review the server’s endpoint list. In this example, we will explore the Pet category.
   

   Swagger – Pet category

2. From the list, we can see multiple endpoints and HTTP methods, including GET, POST, PUT, and DELETE.
3. Click on an endpoint to expand it. For this example, we will use Add a new pet to the store.
   
   

   Swagger – Create a new pet

4. Click Try it out. Swagger will allow you to edit the request body and choose the content type (JSON or XML).
5. Click Execute. Swagger will display
   • The generated request in cURL format
   • The Request URL
   • The Response body
   • The HTTP status code
6. In the Response JSON, we can see the new pet with status code 200, indicating success.
7. Now, with the CURL syntax, we can use that inside our tool.
   

   Swagger – Create a new pet CURL

POST request: Create Pet Request

1. Open Visual Studio and create a new Integration Services Project.
2. After the project is created, locate the SSIS Toolbox on the left panel.
3. Drag and drop the REST API Task onto the Control Flow surface and double-click it to configure
   

   Drag and Drop REST API Task

4. Use the cURL generated from Swagger. For reference, you can review our article about converting cURL to an SSIS API Task.
   

   curl -X 'POST' \
     'https://petstore.swagger.io/v2/pet' \
     -H 'accept: application/json' \
     -H 'Content-Type: application/json' \
     -d '{
     "id": 123,
     "category": {
       "id": 456,
       "name": "Friendly"
     },
     "name": "Zappy",
     "photoUrls": [
       "string"
     ],
     "tags": [
       {
         "id": 0,
         "name": "tech"
       }
     ],
     "status": "available"
   }'

5. -X POST represents the HTTP method. Set the Request Method to POST.
6. Enter the URL from the cURL command.
7. Each -H represents a Header. Add the corresponding headers inside the REST API Task.
8. The -d parameter represents the Body. Paste the JSON payload into the Body section.
9. Click Test Request/Response to validate the configuration.
   

   SSIS – Create a new pet

10. You can use additional components such as JSON Source or XML Source, depending on how you plan to process the response.

POST request: Upload a file

1. Next, we will upload an image for the pet we created earlier
   

   Swagger – upload image

2. Generate the CURL code.
   

   curl -X 'POST' \
     'https://petstore.swagger.io/v2/pet/123/uploadImage' \
     -H 'accept: application/json' \
     -H 'Content-Type: multipart/form-data' \
     -F 'file=@new.jpg;type=image/jpeg'

3. Configure the REST API Task with:
   • Request Method: POST
   • URL
   • Headers
   • File parameter
4. Check the option File upload.
5. Specify the full file path (e.g., file=@D:\Zappysys\new.jpg).
6. Click Test Request to validate the upload.
7. You can find an article about uploading files here.
   

   SSIS – upload an image

GET request: Get the Pet information

1.  Now we will get the pet we created earlier. This is the example
   

   Swagger – get pet by id

2. We generate the CURL
   

   curl -X 'GET' \
     'https://petstore.swagger.io/v2/pet/123' \
     -H 'accept: application/json'

3. Inside the Visual Studio project, drag and drop the SSIS Data Flow Task from the SSIS Toolbox. Double-click on the Data Flow Task to see the Data Flow designer.
   

   Drag and Drop SSIS Data Flow Task from SSIS Toolbox

4. From the SSIS toolbox, drag and drop a JSON Source onto the data flow designer surface, and double-click on it to edit it
   

   SSIS JSON Source – Drag and Drop

5. We use the method GET
6. We enter the URL with the ID from the earlier response.
7. We can use the filter to get the object we need, and now we can check the data.
8. Preview the data, and you will see the Pet’s information
   

   SSIS – get a pet by ID

PUT request: Update an existing pet

1. We go to the updated pet example and run the example
   

   Swagger – update a pet

2. Generate the CURL
   

   curl -X 'PUT' \
     'https://petstore.swagger.io/v2/pet' \
     -H 'accept: application/json' \
     -H 'Content-Type: application/json' \
     -d '{
     "id": 0,
     "category": {
       "id": 0,
       "name": "string"
     },
     "name": "doggie2",
     "photoUrls": [
       "string"
     ],
     "tags": [
       {
         "id": 0,
         "name": "string"
       }
     ],
     "status": "available"
   }'

3. Inside the JSON source, we configure the HTTP method to PUT.
4. Change the url and the header.
5. Inside the Body we can change the values from the existing pet.
6. Test the connection and check the result.
   

   SSIS – update a pet

DELETE request: Remove an existing pet

1. Now we will delete the pet using this example.
   

   Swagger – delete a pet

2. Generate the CURL to delete the pet
   

   curl -X 'DELETE' \
     'https://petstore.swagger.io/v2/pet/1234' \
     -H 'accept: application/json' \
     -H 'api_key: special-key'

3. Inside the JSON source, configure the HTTP method to DELETE.
4. Change the URL to include the pet’s ID.
5. Inside the header, we need to insert an API key.
6. Test the connection, and we will delete the pet.
   

   aSSIS – delete a pet

Authentication method

1. Some APIs require authentication. You can configure authentication using an HTTP Connection Manager.
2. Enter the login URL if required.
3. Select the credential type (e.g., Basic – Username/Password).
4. Enter the credentials.
5. Click OK to save the configuration.
6. This connection can be reused across multiple REST API Tasks or JSON Sources.
7. For more details on basic authentication, click here. For more details on the OAuth connection, click here.
   

   Swagger – SSIS basic authentication

Conclusion

Integrating Swagger-documented APIs with ZappySys SSIS becomes significantly easier when using the generated cURL command as a reference. Swagger provides a clear and interactive way to understand API endpoints, request structures, headers, and payload formats, while cURL offers a direct, executable representation of the HTTP request.

By translating the cURL command into the REST API Task or JSON Source configuration, developers can confidently replicate API calls inside SSIS without guesswork. This approach ensures accuracy, reduces troubleshooting time, and provides a consistent workflow for handling GET, POST, PUT, DELETE operations, file uploads, and authentication scenarios.

Download SSIS PowerPack today and see for yourself how easy it is to combine Swagger and ZappySys SSIS, enabling organizations to seamlessly integrate modern REST APIs into enterprise ETL processes and bridge the gap between cloud-based services and traditional SQL Server data platforms.

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 tutorial: How to connect to Swagger 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.

If you need to upload files from SSIS to SharePoint Online, the ZappySys SharePoint Online Connector for SSIS gives you a direct way to configure the connection, authenticate, and send files without building the API calls from scratch.

This guide shows how to upload one file or multiple files to SharePoint Online using SSIS, API Source, and supporting SSIS components.

Upload files to SharePoint Online with SSIS

In this section, you will configure the SharePoint Online Connector in API Source and use it to upload files to SharePoint Online.

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

   SSIS Toolbox – ZappySys Tasks

   NOTE: If you don’t see ZappySys SSIS PowerPack Task or Components in the SSIS Toolbox, please refer to this help link.
4. Drag and drop the SSIS Data Flow Task from the SSIS Toolbox. Double-click on the Data Flow Task to see the Data Flow Designer.
   
5. From the SSIS Toolbox, drag and drop API Source (Predefined Templates) onto the Data Flow Designer surface, then double-click it to edit it:
   
6. Select New Connection to create a new connection:
   

Configuring the SharePoint Online Connector

1. Use a preinstalled SharePoint Online Connector from the Popular Connector List or press the Search Online radio button to download SharePoint Online Connector. Once downloaded simply use it in the configuration:
   

   SSIS ZS API Connection Manager – Select SharePoint Online Connector

2. Select the desired authentication type. Then choose the API Base URL. In most cases, the default value is correct. Fill in the required parameters and add optional parameters only when needed.
3. After configuring the required properties in API Connection Manager, click Test Connection to confirm that the connection works.
   

   Method 1: Connect to SharePoint Online using user credentials [OAuth]

   Use the Steps to Configure link to help set the required parameters.

   

   SSIS ZS API Connection Manager – Generate Token – SharePoint Online with User Credentials

   Method 2: Connect to SharePoint Online using application credentials [OAuth]

   Use the Steps to Configure link to help set the required parameters.

   

   SSIS API Source – Generate Token – SharePoint Online with Application Credentials

How to upload a local file to SharePoint Online

In the API Source Component, we’ve chosen the API Connection Manager. Next, we need to configure the remaining properties of the component to upload a local file to SharePoint Online.

1. Choose the Upload file endpoint from the “Select Table/Endpoint” dropdown menu.
2. Select the desired Drive ID from the DriveId drop-down.
3. Specify the desired source file path for the file being uploaded by setting the DiskFilePath parameter.
4. Specify the desired Target Path by setting the SharePointFilePath parameter.

Please refer to the sample screenshot below.

SSIS API Source – SharePoint Online – Upload Single File

After configuring the properties above, click Preview Data to test the API call. At this point, the SharePoint Online Connector is ready to upload a local file from SSIS.

How to upload multiple files to SharePoint Online

In the API Source Component, we’ve selected the API Connection Manager. Next, we need to configure the remaining properties of the component to upload multiple files to SharePoint Online. Additionally, we should utilize a Foreach Loop Container to iterate through each file one by one in a loop.

1. Create 3 SSIS variables as described below.
   

   Variable Name	Datatype	Value
   varFileLists	Object	System.Object
   varFileName	String	fake.extension
   varFullFilePath	String	C:/fake/fake.extension

2. Go to Control Flow, From the SSIS toolbox drag and drop ZS Advanced File System Task on the control flow designer surface, and double click on it to edit it:
   
3. Select the “Get file list as ADO.NET Data Table” action from the Action drop-down menu. Set the file path in the Path textbox. Choose the variable (Object type) where you want to store the file list, and then click the OK button to save the settings.
   

   SSIS Advanced File System Task – Get file list as ADO.net Data Table

4. Now, drag and drop the “Foreach Loop Container” from the SSIS Toolbox and connect it with the “ZS Advanced File System Task.” Double-click on the “Foreach Loop Container” to edit its properties.
   

   SSIS Foreach Loop Container – Drag & Drop

5. In the Foreach Loop Editor’s “Collection” tab, choose the Enumerator as “Foreach ADO Enumerator.” In the “ADO object source variable” field, select your SSIS object-typed variable. Select the “Rows in the first table” radio option.
   

   SSIS Foreach Loop Editor – Collection – Select Variable & Enumeration mode

6. In the Foreach Loop Editor’s “Variable Mappings” tab, select the variables that you want to map to the values from the collection, and then click the “OK” button to save your selections.
   

   SSIS Foreach Loop Editor – Variable Mappings

7. Inside the Foreach Loop Container, drag and drop the Data Flow Task, and then rename it according to your preference.
   

   SSIS Data Flow Task – Drag & Drop inside Foreach Loop Container

8. Double-click on the Data Flow Task to see the Data Flow Designer, From the SSIS Toolbox, drag and drop API Source (Predefined Templates) onto the Data Flow Designer surface, then double-click it to edit it:
   
9. Double-click on the API Source component to configure it for uploading multiple files to SharePoint Online.
   1. Choose the Upload file endpoint from the “Select Table/Endpoint” dropdown menu.
   2. Set the SharePointFilePath parameter to the SSIS variable that contains the file name, such as varFileName.
   3. Set the DiskFilePath parameter to the SSIS variable that contains the local file path, such as varFullFilePath.
      When configuring the SSIS variable directly in the Raw Edit, JSON may become invalid due to the requirement of slashes within the local file path. To address this, we use a JSONENC Placeholder Function for proper escaping.
      

      <<{{User::varUserFullFilePath}},FUN_JSONENC>>

   4. If you wish to upload the local file to a specific folder in SharePoint Online, please set the folderName in the SharePointFilePath parameter.

   Please refer to the sample screenshot below.

   

   SSIS API Source – SharePoint Online – Upload Multiple files configuration

   To configure dynamic filenames and file paths, you can set variables. Click on “Raw Edit,” and in the “Edit Parameters” popup, you can use SSIS variables, as shown in the above image.

   Once you have configured all the mentioned properties above, please click on the “Preview Data” button to initiate the API call.
   After that, execute the SSIS package and confirm that the files are uploaded to SharePoint Online. The screenshot below shows a sample result.

   

   Multiple files uploaded on SharePoint Online using SSIS

   You have now configured the SharePoint Online Connector to upload multiple files from SSIS.

Conclusion

In this guide, you learned how to connect to SharePoint Online using SSIS API Connection Manager and upload one or many files using the SSIS API Source component, SSIS ZS Advanced File System Task, Foreach Loop Container, and SSIS variables.

Frequently Asked Questions

Can I upload more than one file to SharePoint Online from SSIS

Yes. You can use a Foreach Loop Container with SSIS variables and ZS Advanced File System Task to iterate through a file list and upload files one by one.

What is the easiest way to upload files to SharePoint Online from SSIS

The simplest approach is to use the SharePoint Online Connector for SSIS, because it provides ready-made authentication and upload endpoints inside the ZappySys connector interface.

Which component uploads the files

The upload action is configured in API Source by selecting the Upload file endpoint and setting values such as DriveId, DiskFilePath, and SharePointFilePath.

Next step

If you want to build this workflow in your own SSIS package, download SSIS PowerPack and review the SharePoint Online Connector guide.

The post How to upload files on SharePoint Online using SSIS appeared first on ZappySys Blog.