--- title: "Set up file action - Zip" slug: "set-up-file-action-zip" description: "Learn how to zip and unzip files in the Working folder using the Zip file action, enhancing your email file management in Azure file storage." tags: ["Task topic"] updated: 2026-09-01T11:10:22Z published: 2026-09-01T11:10:22Z canonical: "docs.staedean.com/set-up-file-action-zip" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.staedean.com/llms.txt > Use this file to discover all available pages before exploring further. # Set up file action - Zip You can use the **Zip** file action to zip or unzip a file in the Working folder. You can use this, for example, in combination with the **Email** file action to send or receive zipped files using email. If the direction is: - **Source**, before the message is run, the file is unzipped to the **Working** folder. The original ZIP file stays in the **Working** folder. - **Target**, after the message is run, the created file is zipped to the **Working** folder. The original file is deleted from the **Working** folder. Next file actions in the file action sequence are done with the ZIP file. > [!NOTE] > Note > > You can use file actions of type **ZIP** only for connectors of type **Azure file storage**. ### Steps 1. Click **Connectivity studio - Integration Design**. 2. Click the **Connectors** tab. 3. In the list, find and select the desired connector. 4. Click **Edit**. 5. You can export the connectivity setup and import it into another D365 F&SCM environment. For example, you first set up and test the connectivity setup in a development environment. When finished, you deploy the setup in your production environment. To protect your production data, use different file locations for your development or testing environment and for your production environment. To strictly distinguish between different environments, you can define unique file action properties for each of your environment types. So, each file action can have a different set of properties for each applicable environment type. Which file action properties are applicable to the current environment is defined in the **Environment type** field on the **Connectivity studio parameters**. **Example**: If set to **Development**, the file action properties, as defined for environment type **Development** are applicable. In the **Environment types** field, select an option. > [!NOTE] > **Note** > > For each file action, you can repeat the sub-tasks for each of your environment types. To set the environment-specific properties of a file action, only change the environment type, find the file action, and set the properties. So, do not create a new file action for each environment type. 6. Expand the **File action** section. 7. Sub-task: Set up a **Zip** file action with direction **Source**. 1. Click **New**. 2. In the **Name** field, type a value. 3. In the **File action** field, select **Zip**. 4. Click **Save**. 5. In the **Direction** field, select **Source**. 6. Define the name of the file to be unzipped. You can use filtering symbols. **Example:** CustGroup*.txt. In the **File name** field, type a value. 7. You can (temporarily) disable a flow action. **Example:** In a test setup, the setup to do the file action is not available. To prevent errors during test runs of the message, you disable the file action. In this way, you do not have to change or delete the file action. In the **Skip** field, select an option. 8. Sub-task: Set up a **Zip** file action with direction **Target**. 1. Click **New**. 2. In the **Name** field, type a value. 3. In the **File action** field, select **Zip**. 4. Click **Save**. 5. In the **Direction** field, select **Target**. 6. Click **Save**. 7. You can (temporarily) disable a file action. **Example:** In a test setup, the setup to do the file action is not available. To prevent errors during test runs of the message, you disable the file action. In this way, you do not have to change or delete the file action. In the **Skip** field, select an option. 9. Close the page.