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
+10Lines changed: 10 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -74,6 +74,16 @@ To set up a new Actions-framework destination for the first time:
74
74
You can choose **Quick Setup** to use the default mappings, or choose **Customized Setup** (if available) to create new mappings and conditions from a blank state. You can always edit these mappings later.
75
75
7. Once you’re satisfied with your mappings, click **Create Destination**.
76
76
77
+
## Migrate a classic destination to an actions-based destination
78
+
79
+
Moving from a classic destination to an actions-based destination is a manual process. Segment recommends that you follow the procedure below:
80
+
81
+
1. Create the actions-based destination with your development or test source.
82
+
2. Copy API keys, connection details, and other settings from the classic destination to the actions-based destination.
83
+
3. Refer to the actions-based destination's documentation for information about migrating specific settings.
84
+
4. Disable the classic version of the destination, and enable the actions-based version.
85
+
5. Verify that data is flowing from the development or test source to the partner tool.
86
+
6. Repeat the steps above with your production source.
77
87
78
88
## Edit a destination action
79
89
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