Skip to main content
Screenshotly’s API handles on-demand captures. To schedule recurring screenshots, combine it with an external scheduling mechanism.

Cron jobs

Run a capture script on a schedule using cron (Linux/macOS):
Add a crontab entry to run daily at 2:00 AM:

GitHub Actions

Create a scheduled workflow to capture screenshots automatically:

AWS Lambda

Deploy your capture logic as a Lambda function triggered by EventBridge on a schedule:
Configure an EventBridge rule with a cron expression to trigger the Lambda function on your desired schedule.

Workflow automation tools

You can also use no-code platforms to schedule captures:
  • Zapier — create a Zap with a Schedule trigger and a Webhooks action calling the Screenshotly API
  • Make (Integromat) — use the HTTP module with a scheduling trigger
See no-code integrations for setup details.

Best practices

  • Store API keys securely — use environment variables or secrets managers, never hardcode keys in scripts
  • Log results — capture timestamps, URLs, and outcomes for troubleshooting
  • Set up failure alerts — send notifications via email or Slack if scheduled captures fail
  • Stagger schedules — if running many scheduled captures, spread them out to avoid rate limit issues
  • Manage storage — implement a retention policy for stored screenshots to control costs