Start with the scenario, how it works and step-by-step example

Overview  

A scenario runs automatically whenever a new file is detected in a monitored folder. Scenarios are processed top-to-bottom: each item in the scenario is either an action or a condition (conditions can contain nested actions for match/fail branches). Actions run in the order they appear, so ordering controls the processing flow and final outputs.

Create a scenario (step‑by‑step example)

1. Edit the monitored folder and go in step 2, click "Add something" to insert a new item in the scenario. You must choose whether to add an Action or a Condition. For this example, choose Action. 

2. Select the desired action from the action list. Example: choose "Convert to PDF", click Next, set the action properties, then click OK. The "Convert to PDF" action is now added to the top of the scenario.

3. Add the next action: click "Add something" → Action → select "Add stamp" (watermark), configure the stamp properties, and click OK. The stamp action will run after the conversion because it appears below the conversion in the scenario list.  

4. Add a save action: click "Add something" → Action → choose "Save to" (or "Save file"), select the destination folder where you want the resulting PDF saved, and click OK. This saves the processed file to your chosen folder after conversion and stamping.  

5. Add a notification action: click "Add something" → Action → choose "Notification to Slack", configure the Slack channel/message and any attachment options, then click OK. This sends a team notification once the prior actions complete. 

6. Click on 'Continue', set a name for this hot folder. From now on, each new file detected in the monitored folder will be converted to PDF, stamped, saved to the target folder, and then a Slack notification will be sent (in that exact order).

Notes and best practices

• Order matters: actions execute sequentially from top to bottom; move items up/down to change execution order.  
• Use conditions when you need branching logic (e.g., apply different stamps or destinations depending on file content or metadata). Conditions can contain their own actions for match/fail paths.  
• Test with sample files and a short monitoring interval to confirm the scenario behaves as expected before putting it into production. 

To learn more

About adding and configuring conditions, see the dedicated conditions tutorial referenced here.