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
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -79,7 +79,7 @@ To set up a new Actions-framework destination for the first time:
79
79
Moving from a classic destination to an actions-based destination is a manual process. Segment recommends that you follow the procedure below:
80
80
81
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. In general, actions-based destinations have fewer connection settings than their classic counterparts.
82
+
2. Copy API keys, connection details, and other settings from the classic destination to the actions-based destination.
83
83
3. Refer to the actions-based destination's documentation for information about migrating specific settings.
84
84
4. Disable the classic version of the destination, and enable the actions-based version.
85
85
5. Verify that data is flowing from the development or test source to the partner tool.
0 commit comments