NoteThis information was accurate at the time of publication. Please check out the latest product update notes for any updates or changes.
As mentioned in our previous update, today any custom actions created with the Start Simple Builder (legacy custom actions) have been converted to an API Request action.
During this process your Zap workflows will continue to run as normal. However, after we migrate to API Requests actions, legacy custom actions will be deprecated. This means:
- They will be removed from the Custom Actions Library.
- They won’t be available for use in new Zap workflows.
- They won’t appear among other actions within the Zap editor.
How will these converted actions appear in my existing Zap workflows?
Before: legacy custom action
Here’s an example of the request settings for a custom action built in the Start Simple Builder:
This custom action also has 3 input fields:
This is how the action appears in the Zap editor:
After: API Request action
The noticeable difference is all of the settings for this action can be accessed directly in the Zap editor.
Based on how your legacy custom action is set up, all values in previous input fields will appear as either static or mapped fields.
If you encounter an “invalid JSON” error with your API Request action, review our troubleshooting guide.
I want to use my converted actions in new Zap workflows
As API Request actions cannot be re-selected in the Zap editor across multiple Zap workflows. You will either need to:
- Re-create the action using the new Custom Actions builder experience. This means you only need to create it once.
- Copy your action settings into a new API Request action in your new Zap. Repeat this for every Zap you want this action in.
If you want your actions to be shareable with your teammates, Zapier recommends re-creating the action as a custom action.