You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/connections/destinations/actions.md
+13-9Lines changed: 13 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -82,15 +82,19 @@ Moving from a classic destination to an actions-based destination is a manual pr
82
82
5. Verify that data is flowing from the development or test source to the partner tool.
83
83
6. Repeat the steps above with your production source.
84
84
85
-
Copying over your Destination Filters from the Classic Destination to the Actions Destination
86
-
87
-
This functionality is not available within the UI, but is available via the Public API for all customers on Segment's Business Tier Plan.
88
-
1. Send a request to the Public API endpoint : [List Filters from Destination]([url](https://docs.segmentapis.com/tag/Destination-Filters#operation/listFiltersFromDestination)). The `destinationId` can be found in the URL while viewing the destination in your Segment workspace.
89
-
- List Filters from Destination : `GET` - `https://api.segmentapis.com/destination/{destinationId}/filters?pagination%5Bcount%5D=100`
90
-
2. Grab the response and parse through the `data.filters` object. Each object returned inside the `data.filters` object is an individual filter associated with that Intercom Prod destination.
91
-
4. Next, send individual `POST` requests to the Public API endpoint : [Create Filter for Destination]([url](https://docs.segmentapis.com/tag/Destination-Filters/#operation/createFilterForDestination)), for each of the filters from step 2. Specify the Actions `destinationId`, found in the URL when viewing that destination, and then the body of the request is the individual filters from step 2.
92
-
- POST - https://api.segmentapis.com/destination/{destinationId}/filters
93
-
6. If the bodies of those requests didn't already include the field `"enabled": true`, make sure to enable each of those filters after creating them.
85
+
### Migrate your destination filters from the classic destination to the actions destination
86
+
87
+
> warning ""
88
+
> You can only migrate your destination filters using the Public API if you're on the business tier plan. This functionality isn't available in the Segment app.
89
+
90
+
To migrate your destination filters to your actions destination from the classic destination:
91
+
1. Send a request to the Public API endpoint.
92
+
- Use [List Filters from Destination](https://docs.segmentapis.com/tag/Destination-Filters#operation/listFiltersFromDestination){:target="_blank"} . The `destinationId` can be found in the URL while viewing the destination in your Segment workspace.
93
+
2. Grab the response and parse through the `data.filters` object. Each object returned inside the `data.filters` object is an individual filter associated with the specified destination.
94
+
4. Send individual `POST` requests to the Public API endpoint.
95
+
- Use [Create Filter for Destination](https://docs.segmentapis.com/tag/Destination-Filters/#operation/createFilterForDestination){:target="_blank"} , for each of the filters from step 2.
96
+
- Specify the Actions `destinationId`, found in the URL when viewing that destination. The body of the request is the individual filters from step 2.
97
+
6. If the bodies of those requests don't already include the field `"enabled": true`, make sure to enable each of those filters after you create them.
94
98
95
99
## Edit a destination action
96
100
You can add or remove, disable and re-enable, and rename individual actions from the Actions tab on the destination's information page in the Segment app. Click an individual action to edit it.
0 commit comments