Copy a step
Is there a step on your canvas you'd like to use in another flow? Or, maybe there's an existing step on the palette you'd like to customize or extend? You can create copies of steps – either on the canvas or in the palette – to use as a template or a starting point for your own new steps.
When you drag a step from the palette, you create an instance of that step on the canvas and you configure its settings and fields to meet the needs of your flow. When you copy that step on the canvas, you're duplicating the instance of that step with its current canvas configuration.
When you copy a step in the palette, you're copying the underlying structure of how that step is defined as a new step in the palette, which you own and can edit.
You can copy an existing step on your canvas to duplicate the step and its current canvas configuration. This saves time and reduces error when you're building multiple flows on the same canvas that follow the same set of steps. For example, maybe you've configured a custom step and now you want to reuse it in different branches of your flow, with minor modifications to its messages or response options.
To copy a step on the canvas:
- Locate the step you want to create a copy of on the canvas.
- Hover over the step and click the three vertical dots from the menu that appears.
- Select Copy Step.
- The copied step appears highlighted on your canvas near the original step.
- Edit the name of your copied step, if desired.
- Connect the step to a flow and edit any of its configuration settings, if necessary.
- Save your flow canvas.
You can copy a step in the palette to duplicate the step's definition. For example, if 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, custom step or HTTP trigger in the palette to use as a template or starting point for your own step. When you copy a step or HTTP trigger, Flow Designer creates a new step or trigger with the original step's definition and logic, including its icon, description, allowable endpoints, inputs, outputs, and script. As the owner of the new step, you can edit its definition, deploy it, and share it with others.
To copy a step in the palette:
- Locate the 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 a dialog box for defining the new step or trigger, 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 on the Triggers tab of the palette, 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.
- For HTTP triggers on the Triggers tab of the palette, select Copy.
- On the Settings tab, Flow Designer automatically assigns a name to the new 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 or HTTP trigger, 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 and HTTP 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 in the palette, 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.