{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":21257,"path":"integrate-applications/integration-hub/import-rest-message-step.md","title":"Import a REST message into a REST step","bundle":null,"doc_type":null,"release":"australia","body":"\n# Import a REST message into a REST step\n\nTransfer data from an existing Platform REST message into a REST step.\n\n## Before you begin\n\n-   This import is done from within a REST step in Workflow Studio. To create a REST step, [Create an action](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/build-workflows/create-action.md) and add a [REST step](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/integrate-applications/integration-hub/rest-request-action-designer.md) to it.\n-   The REST step uses Connection and Credential aliases for authentication details. If your REST message stores authentication details, create a Connection and Credential alias for them. For more information, see [Create a Connection and Credential alias](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-security/connection-alias.md).\n-   Role required: admin\n\n## Procedure\n\n1.  Navigate to **All** &gt; **Process Automation** &gt; **Flow Designer**.\n\n2.  On the Workflow Studio landing page, select **Actions** and open the action that has the REST step you want to use for the import.\n\n3.  In the REST step, locate the **Build Request** field and select **From REST Message**.\n\n4.  In the **REST Message** field, select the REST message to import.\n\n5.  In the **REST Message Function** field, select the function.\n\n    The available options are determined by the HTTP methods associated with the selected REST message.\n\n6.  Select the **Import REST Message** button.\n\n    The Import ServiceNow REST Message window displays the data from the selected REST message.\n\n7.  Select the **Configure step** button.\n\n\n## Result\n\nThe data from the REST message is loaded into the REST step. No future changes to the REST message are copied to the derivative REST steps. Rather than maintain two versions of your REST logic, you should only maintain and update the REST step.\n\nIf the imported REST message has a MID Server configured in any of its functions, the **Use MID** check box in the Connection Details section is checked and a data pill provided for the MID Server.\n\n## What to do next\n\nFill in any other required fields and test the step with the **Test REST step** button.\n\n**Parent Topic:**[REST step](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/integrate-applications/integration-hub/rest-request-action-designer.md)\n\n"}}