# Transform data to support data-out integrations

 Try using one of our SDKs or the Pipelines API instead

Changing actionsA block in a campaign workflow—like a message, delay, or attribute change. for data coming into Customer.io can be complex. If you’re just getting started, we suggest that you format your data based on our default actions and don’t change them.

These integrations are based on the [Pipelines API](/integrations/api/cdp/) already, and our libraries make it easier to understand and manage action mappings for destinations.

## How it works[](#how-it-works)

By default, we automatically map traffic from integrations based on our [Track API](/integrations/api/track/) to our newer [Pipelines APIs](/integrations/api/cdp/) to support downstream integrations—services outside of Customer.io. But, if you want more control over how we map incoming data to your workspace, you can edit your workspace’s actionsA block in a campaign workflow—like a message, delay, or attribute change..

**Be careful: changing the default workspace mappings means you’re no longer processing data as explained in our documentation.**

## Edit your workspace’s actions[](#edit-your-workspaces-actions)

Updating your workspace’s *actions* determines how we handle incoming data, including whether we process it at all. While you can change the default mappings, keep in mind that changing mappings affects the data that goes to your workspace!

1.  Go to [*Data & Integrations* > *Integrations*](https://fly.customer.io/workspaces/last/journeys/integrations/all/overview).
2.  Hover over the icon in an integration that sends data to Customer.io and then select your workspace’s name.
3.  Go to the **Actions** tab.
    
    [![Enable the Transform Data feature](https://docs.customer.io/images/cdp-track-transform-setting.png)](#a6b6bbf9a871e2ad981021baaab481fe-lightbox)
    
4.  Click and click **Edit** to change an action.
5.  From here, you can edit or add actions—including filtering the calls that go to your workspace. For example, you may want to handle an event with a specific name differently from other events. When you edit an action, you can change:
    *   **Trigger**: the conditions that trigger the action. Common conditions include the `type` (like `track` or `identify`), the `event` name, or an *Event Property*.
    *   **Data Structure**: the transformations for data matching the trigger. In general, most changes are typically limited to the **Optional Data** section—additional properties or attributes you want to set when we receive an event or a call matching your trigger conditions.
        
        [![Update the data structure, focusing on the trigger and optional properties](https://docs.customer.io/images/cdp-track-data-structure.png)](#f683f77c5cb0997dc05d69bd059cd821-lightbox)
        

 Review the default mappings

Before you change actions for your workspace, review our [default mappings](/integrations/data-in/connections/classic-api/cio-journeys-api/) to understand how we translate incoming data to the newer format. Changing these mappings affects the way we process data in your workspace!