Copy a step
Is there an existing step that you'd like to customize or extend? Maybe you're using one of our built-in ServiceNow steps and you'd like to add additional inputs to better match your company's ServiceNow configuration. Or, perhaps someone in your organization has written a custom step that you could use for your team's processes, with some minor tweaks.
You can create a copy of a built-in step or a custom step to use as a template or starting point for your own step. When you copy either a built-in or custom step, Flow Designer creates a new custom step with the original step's definition and logic, including its icon, description, allowable endpoints, inputs, outputs, and script. As the owner of this new custom step, you can edit its definition, deploy it, and share it with others.
- Locate the built-in or custom step you want to create a copy of in the palette.
- Beside the step's name, click the gear icon and select the option to copy the step. This opens the New Custom Step dialog box, with values for settings, inputs, outputs, and script copied from the original step.
- For built-in steps on the Apps tab of the palette, select Copy as custom step.
- For built-in App triggers, select Copy as HTTP trigger.
- For custom steps on the Custom tab of the palette, select Copy Step. If the custom step you're copying has versions, you'll have the option to select which version to copy.
- On the Settings tab, Flow Designer automatically assigns a name to the new custom step. You can rename your step something unique to make it easier to identify in the palette.
- If you copied a built-in step or app trigger, the default name for your step is <Application> - <Step Name> (e.g., "ServiceNow - Add Comment").
- If you copied a custom step, your step is named Copy of <Step Name> (e.g., "Copy of Email Parser").
- Edit the description, icon, and version details, if needed.
- Click Save to create the copied version of the step. Your new step is available either on the Custom tab of the palette (for apps and custom steps) or in the HTTP Triggers section of the Triggers tab (for app triggers), in the list of steps that are Owned by you.
- By default, the state of your copied step is set to "In Development". You can keep your step in this state until you are ready to use it in flows and share it with other users.
- Edit any settings that need to change from the step you copied (for example, in the endpoint, inputs, outputs, and script).
- Test your step in a flow.
- Once your step is ready to go, set its Current State to "Deployed" and click Save.
- To share your step with others, configure its Usage Permissions.
Copied steps are independent of the step they originated from and do not receive updates if the original step is modified. For example, if you copy one of Flow Designer's built-in steps, like the 'Create Incident' step for ServiceNow, your custom step is not updated if changes are made to the original built-in step available on the Apps tab of the palette.