Frequently Asked Questions
Learn how to use features and action types in your monitoring jobs.
What is the Import Feature?
The import feature allows you to create multiple monitoring jobs at once by uploading a JSON file or pasting JSON data. This is especially useful when you need to set up many jobs quickly.
How to Use the Import Feature:
1. Go to your Dashboard and click the "Import Jobs" button
2. Choose one of two options:
• Upload File: Click "Choose File" and select a JSON file from your computer
• Paste JSON: Switch to the "Paste JSON" tab and paste your JSON data directly
3. The system will automatically check your file for errors
4. Review the preview showing how many jobs will be imported
5. Click "Import" to create all your jobs at once
What Your JSON File Should Look Like:
Your JSON file must have a specific structure. At the top level, you need a "jobs" array containing all your monitoring jobs. Each job in the array should include:
• jobURL: The website URL you want to monitor (must start with http:// or https://)
• monitoringMode: Either "visual" (for visual changes) or "text" (for text content changes)
• actions: An object containing your monitoring settings:
- interval: How often to check (in minutes). Allowed values: 5, 10, 15, 30, 60, 180, 360, 720, 1440, or 10080
- threshold: The change threshold (0, 0.05, 0.1, or 0.2)
- waitFor: Wait time before checking (0, 3, or 6 seconds)
- disableJS: (Optional) Set to true or false to disable JavaScript
- actions: (Optional) An array of actions to perform (maximum 12 actions)
• entirePage: (Optional) Only allowed with "text" monitoring mode. Set to true or false
Example JSON Structure:{
"jobs": [
{
"jobURL": "https://example.com",
"monitoringMode": "visual",
"actions": {
"interval": 30,
"threshold": 0.1,
"waitFor": 3
}
}
]
}
Important Limits:
• Maximum file size: 1MB
• Maximum jobs per import: 100 jobs
• Your account has daily import limits based on your subscription plan
After Importing:
Some jobs may require additional configuration (like selecting a region). These will appear in the "Pending Imports" tab. Simply click "Finalize" on each pending import to complete the setup. Once finalized, your jobs will appear in your main jobs list and start monitoring automatically.
Setting Nicknames:
Nicknames cannot be included in import files. After importing, you can add custom nicknames to your jobs directly from the dashboard to make them easier to identify.
Need Help?
If you encounter errors during import, the system will show you exactly what needs to be fixed. Common issues include invalid URLs, incorrect field values, or missing required fields. Make sure your JSON is properly formatted and all values match the allowed options listed above.
Ready to start monitoring? Create a free account or view our website monitoring pricing plans.
Available Actions
XPath Selectors Guide
XPath selectors help you target specific elements on web pages. Here's how to get and use them:
Method 1: Browser Developer Tools (Recommended)
2. Select "Inspect Element" or "Inspect"
3. In the developer tools, right-click on the highlighted HTML element
4. Choose "Copy" → "Copy XPath"
5. Paste the XPath into your action
Method 2: Using Our Visual Selector
2. This will highlight clickable elements on the page
3. Click on the element you want to target
4. The XPath will be automatically generated for you
Testing Your XPath
1. Open Chrome DevTools (F12)
2. Go to the Console tab
3. Type:
$x("//paste-your-xpath-here")4. Press Enter - if it returns the element, your XPath works!
Common XPath Patterns
//button[@id='submit'] - Button with specific ID•
//a[contains(text(), 'Login')] - Link containing specific text•
//input[@type='email'] - Email input field•
//div[@class='form-group']//input - Input inside a form group•
//*[contains(@class, 'btn-primary')] - Element with specific classPro Tips
id or data-* attributes• Avoid overly complex XPaths that might break with page updates
• Test your XPath in the browser console before using it
• Consider using relative XPaths when possible
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 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