Every Zap starts with a single trigger that watches for new or updated data, starting the user’s workflow. Action steps then make use of that data.
success
message.
Unsucessful actions should return 4xx
errors. If your API returns a 2xx
error, add custom code to your API call to replace it with a correct error.
Update actions should be separate from create actions.
Actions may create multiple items if needed, using the same data, though you will likely need to customize the API call code to create multiple items at once. Only do this for linked items, such as if an app stores customers and customer addresses separately. If the multiple items that need to be created are top-level, complex items in your app, they should be separate actions within Zapier. You can then link the two with a drop-down menu in the action to select the paired item, add a search action for users to find the specific item they need, and then let them match the items with the Use a Custom Value option in Zapier.
200
with an empty array must be returned. If your API returns a 404
error for searches without results, add custom code to your API call to replace it with an empty array.
Copy
field to clarify to users that the action is irreversible once the API request is made.