Hi ​@Troy Tessalone,

Thank you for bringing this topic to the community's attention. Understanding the limitations and best practices when building Zaps is important to ensure they function as intended.

These apps and actions can't be the last step in a Zap because they are designed to facilitate or modify data flow rather than perform a final action. Here's a brief explanation of each:

1. Delay: This app pauses the Zap for a specified time before continuing to the following action. It doesn't produce a result but helps manage timing within the Zap.
2. Filter: Filters determine whether a Zap should continue based on specific conditions. Since they don't perform an action themselves, they need to be followed by another step that acts on the filtered data.
3. Formatter: Formatter is used to change data into the desired format. Like filters, formatters modify the data but don't perform a final action, so another step is needed to act on the formatted data.
4. Looping: Looping allows for repetitive actions within a Zap. It processes each item in a list but requires another action to complete the process for each item.
5. Paths: Paths allow for conditional logic within Zaps, directing the flow based on different conditions. They need subsequent actions to execute the outcomes of those conditions.
6. "Find" or "Search" Actions: These actions locate specific data within an app. After finding the data, another action typically needs to be taken to use it, such as updating a record or sending a notification.

To ensure your Zaps run smoothly, always follow these steps with an action that completes the intended workflow, such as sending an email, updating a database, or creating a new record.