Insomnia and AWS Lambda Integration for Low‑Traffic Cost Reduction

Goal

Reduce the cost of running AWS Lambda functions when using Insomnia to validate a low‑traffic API.

Constraints include the pay‑per‑request pricing model, the need to avoid unnecessary invocations during development, and the desire to keep test runs reproducible without manual intervention.

Specific questions:

• Which Insomnia features (e.g., environment variables, pre‑request scripts, or collection runners) can be configured to conditionally execute requests only when needed?
• How can Insomnia be set up to reuse existing connections or cache responses to limit Lambda invocations?
• Is there a way to trigger Insomnia test runs from an external scheduler so that executions occur only during defined low‑traffic windows?