Action Types FAQ

The Click action allows you to programmatically click on any element on the webpage using XPath selectors. **How to use:** 1. Select "Click" from the action type dropdown 2. Enter the XPath selector for the element you want to click 3. **Use the visual selector to automatically get XPath selectors** - this will highlight clickable elements and generate XPaths for you 4. Refresh the page to test if your XPath works as expected 5. The action will automatically click the specified element when the job runs **XPath Examples:** - `//button[@id='submit']` - Click a button with ID 'submit' - `//a[contains(text(), 'Login')]` - Click a link containing 'Login' - `//input[@type='submit']` - Click a submit button **Troubleshooting:** If your XPath doesn't work, please refer to the "XPath Selectors Guide" section above for detailed instructions on getting and testing XPath selectors. **Best Practices:** - Use stable XPath selectors that won't change with page updates - Test your XPath selectors before creating the job - Avoid overly complex XPath expressions that might break

The Type action allows you to automatically fill in text fields, forms, and other input elements on the webpage. **How to use:** 1. Select "Type" from the action type dropdown 2. Enter the text you want to type into the input field 3. The action will automatically type the specified text when the job runs **Common Use Cases:** - Filling out login forms - Entering search terms - Filling contact forms - Setting form values **Best Practices:** - Use clear, descriptive text that won't change - Consider using placeholder text or labels for identification - Test with different input field types (text, email, password, etc.)

The Delete Element action allows you to programmatically remove elements from the webpage using XPath selectors. **How to use:** 1. Select "Delete" from the action type dropdown 2. Enter the XPath selector for the element you want to delete 3. Use the mouse icon to visually select elements on the page 4. The action will automatically remove the specified element when the job runs **XPath Examples:** - `//div[@class='popup']` - Remove a popup div - `//span[@class='notification']` - Remove notification elements - `//*[contains(@class, 'banner')]` - Remove banner elements **Use Cases:** - Removing popups or overlays - Cleaning up unwanted elements - Hiding notifications - Removing ads or promotional content

The Wait action allows you to add delays between other actions to ensure proper timing and page loading. **How to use:** 1. Select "Wait" from the action type dropdown 2. Choose the delay duration (0, 3, or 6 seconds) 3. The action will pause execution for the specified time **Available Delays:** - **0 seconds**: No delay (immediate execution) - **3 seconds**: Short delay for quick page interactions - **6 seconds**: Longer delay for slower loading pages **When to use:** - After clicking elements that trigger page changes - Before typing in fields that might not be ready - Between multiple actions that need proper sequencing - When pages have slow loading animations **Best Practices:** - Use shorter delays when possible to keep jobs fast - Use longer delays for pages with heavy JavaScript - Test different delay times to find the optimal setting

The Cookie action allows you to set cookies on the webpage, which can be useful for authentication, preferences, or tracking. **How to use:** 1. Select "Cookie" from the action type dropdown 2. Fill in the cookie details: - **Name**: The cookie name (e.g., 'session_id', 'user_pref') - **Value**: The cookie value (e.g., 'abc123', 'dark_mode') - **Domain**: The domain where the cookie should be set (e.g., '.example.com') 3. The action will set the cookie when the job runs **Common Use Cases:** - Setting authentication tokens - Storing user preferences - Bypassing login forms - Maintaining session state **Best Practices:** - Use descriptive cookie names - Set appropriate domain values - Consider cookie expiration times - Test cookie functionality before creating jobs

The Local Storage action allows you to set values in the browser's local storage, which persists across browser sessions. **How to use:** 1. Select "Local Store" from the action type dropdown 2. Fill in the storage details: - **Key**: The storage key name (e.g., 'user_settings', 'theme') - **Value**: The storage value (e.g., '{"theme":"dark"}', 'enabled') 3. The action will set the local storage value when the job runs **Common Use Cases:** - Setting application preferences - Storing user settings - Maintaining application state - Bypassing configuration steps **Best Practices:** - Use clear, descriptive key names - Store JSON data as strings - Consider data size limits - Test storage functionality before creating jobs

The Reload action allows you to refresh the webpage, which can be useful for getting fresh content or resetting page state. **How to use:** 1. Select "Reload" from the action type dropdown 2. No additional configuration needed 3. The action will reload the page when the job runs **Common Use Cases:** - Getting fresh content from dynamic pages - Resetting page state - Clearing temporary data - Refreshing after other actions **Best Practices:** - Use sparingly as it can slow down job execution - Consider if other actions might be more efficient - Test reload timing with other actions - Monitor job performance with reload actions