What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
In Make, start a scenario with Razorpay’s Watch Payment Captured trigger, then use the HTTP Make a request module to call a screenshot API and route the returned image or URL to your chosen destination. For production, first confirm how your trigger handles webhook signature verification: Razorpay requires HMAC-SHA256 verification of the raw request body, and the reviewed Make documentation does not establish that a Make-only custom-webhook scenario can perform that check.
Choose how Razorpay will start the Make scenario
Use the trigger that matches your event and security requirements. Make documents its built-in Razorpay trigger as firing when a new payment is successfully captured. Alternatively, Razorpay can send an event to a Make Custom webhook.
| Approach | When it fits | Important consideration |
|---|---|---|
| Razorpay — Watch Payment Captured | You want Make’s built-in Razorpay trigger for successfully captured payments. | The reviewed documentation does not establish what raw-body or signature-validation controls are available through the built-in connection. |
| Razorpay webhook → Make Custom webhook | You want Razorpay to deliver an event directly to a Make webhook URL. | Do not assume the Make route can meet Razorpay’s raw-body HMAC requirement. Confirm that before sending production events directly to it. |
Use a captured-payment event when the screenshot should follow a successful capture. Razorpay notes that webhook payloads are snapshots: a payment.authorized payload can describe authorization-time details even if the payment has already been captured by the time the event fires. Select the event whose meaning matches the action you intend to take.
Build the capture workflow in Make
- Create a scenario and add the trigger. In Make, create a new scenario and select Razorpay’s Watch Payment Captured module, or add a Custom webhook trigger and configure Razorpay to deliver the chosen event to its generated URL. Connect the account or webhook as appropriate and use a test event to inspect the fields Make receives.
- Choose the target page from trusted data. Map a fixed, allowlisted page URL or a URL stored in trusted order metadata. Do not send an arbitrary URL from untrusted event data to a screenshot endpoint: that can turn the scenario into a way to request captures of unintended pages.
- Add an HTTP request for the screenshot. Add Make’s HTTP Make a request module after the trigger. For the ScreenshotOne example below, use method
GET, endpoint https://api.screenshotone.com/take, and query parametersurlandaccess_key. Map the trusted page URL tourland keep the API key in Make’s protected connection or other secret storage rather than exposing it in a public page. Use HTTPS. - Route the result. Configure the next module for the destination your workflow needs, such as cloud storage or an internal record. Whether the HTTP response is handled as image data or as a URL depends on the API response and the destination module; test the actual response mapping before enabling the scenario for live payments.
- Test failure and duplicate paths. Run a non-production payment through the scenario, confirm the correct page was captured, and verify how the destination behaves if the same event is processed again or a capture request fails.
Handle Razorpay signatures, retries and duplicate events
Razorpay signs webhook bodies with HMAC-SHA256 using the configured webhook secret. Its verification instructions require calculating the signature over the raw request body; parsing or casting the body first can invalidate the check. The reviewed documentation does not establish that a Make-only custom-webhook scenario exposes the raw body in a form that supports this verification. Before production use, verify the exact configuration you intend to deploy. If it cannot verify the signature as required, put a small verification endpoint in front of Make: it should validate the raw body, reject invalid requests and forward only trusted event data.
Free tools Windows power users keep installed
One-click scans. No signup required.
#1 Best Overall
- Read Before You Buy — No Video Output: These adapters support charging and USB 2.0 data transfer, but cannot transmit video signals. Except for standard USB webcams (which use USB data only), they are not compatible with HDMI/DisplayPort cables, video-capable USB-C hubs, or docking stations with video output.
- Convert USB-A Ports to USB-C: Designed to connect USB-C earphones, cables, flash drives, card readers, and other USB-C accessories to standard USB-A ports. Plug-and-play with no drivers or software required.
- Aluminum Alloy Housing: Built with a sturdy aluminum alloy shell that aids in heat dissipation and protects against daily wear and scratches. Designed to maintain a stable and secure connection.
- Compact & Travel-Friendly: The ultra-compact design allows the adapter to stay plugged into your device without blocking adjacent ports or adding bulk, reducing wear and tear on your original USB ports.
- 12-Month Warranty: Backed by a 12-month manufacturer warranty for peace of mind. Designed to meet strict quality control standards for reliable everyday performance.
- Deduplicate deliveries: use Razorpay’s
x-razorpay-event-idto identify an event and record processed IDs so a repeat delivery does not create a second screenshot or duplicate downstream action. - Make side effects idempotent: design the scenario so processing the same trusted event again does not create duplicate records or other unwanted outcomes.
- Expect retries and out-of-order delivery: Razorpay documents exponential-backoff retries for failed deliveries for 24 hours after event creation and warns that events may arrive out of order. Make custom webhooks can queue calls that are not processed immediately. Avoid assuming that arrival order alone proves payment state; account for failures and duplicates in downstream processing.
Choose synchronous capture or an asynchronous callback
A synchronous request is the simpler design when Make should receive the screenshot response in the same scenario execution. ScreenshotOne also documents asynchronous capture: request it with async=true and response_type=json, then provide a webhook_url for the result callback. If the callback needs the stored file location, its documentation specifies storage_return_location=true. The callback example can include a screenshot URL and, when configured, a storage location.
| Design | What Make receives | Choose it when |
|---|---|---|
| Synchronous | The screenshot API response during the request step. | You want a direct request-and-route flow and have confirmed the response is usable by the next module. |
| Asynchronous | A later POST callback to the configured webhook, with result details. | You want rendering and result handling as separate stages. Make the callback processing safe for repeated or delayed delivery. |
For asynchronous results, ScreenshotOne signs callback bodies with X-ScreenshotOne-Signature and recommends validating the HMAC-SHA256 signature with its separate secret key. Its webhook_errors=true option can provide error details. Treat callback verification as a separate security requirement from Razorpay’s incoming-payment verification.
Rank #2
- 5-in-1 USB-C Hub: Experience comprehensive connectivity featuring a Power Delivery input, two USB-A 2.0 ports, a USB-A 3.0 port, and an HDMI port. (Note: The USB-C power delivery input port is only for connecting an external wall charger to power your laptop and cannot power peripheral devices.)
- 90W Pass-Through Charging: Achieve optimal charging with 90W pass-through power to your laptop, supported by a total input of 100W, with the hub reserving 10W for operational efficiency. (Note: Wall charger not included.)
- Quick Data Transfers: Accelerate your productivity with rapid data transfers using a high-speed 5Gbps USB 3.0 port and two 480Mbps USB 2.0 ports.
- 4K HDMI Display: Enhance your visual experience with a hub capable of delivering 4K resolution at 30Hz in both mirror and extend modes. Please note that this hub is compatible with MacBook (macOS 12 and newer), Windows 10 and 11, ChromeOS, and laptops equipped with DP Alt Mode and Power Delivery. Note: This device is not compatible with Linux.
- What You Get: Anker USB-C Hub (5-in-1, 4K HDMI), welcome guide, 18-month warranty, and our friendly customer service.
Protect credentials and payment data
- Keep Razorpay credentials, the screenshot API key and any webhook signing secrets private. ScreenshotOne distinguishes its API key from its secret signing key and advises treating the API key like a password.
- Do not expose screenshot URLs containing an API key in public pages. Avoid sending credentials or sensitive options over plain HTTP; ScreenshotOne says to call its API over HTTPS.
- Capture only the page needed for the workflow. Avoid placing payment details or other sensitive values in the target URL unless that is necessary and appropriate for your system.
- Limit which event data is forwarded into Make and which scenario users can access secrets or captured files.
Troubleshoot common failures
| Symptom | Likely cause | What to check |
|---|---|---|
| No scenario run after payment | The selected event does not match a successfully captured payment, or the trigger/webhook setup is incomplete. | Confirm the payment reached captured status, check the selected Razorpay event, and send a test event through the configured trigger. |
| Webhook verification fails | The body was parsed or altered before HMAC calculation, the wrong secret was used, or the Make route cannot access the raw body needed for validation. | Verify the signature against the untouched raw body with the configured webhook secret. If Make cannot do that in your chosen setup, validate at a trusted endpoint before forwarding data. |
| Two captures or downstream records appear | A delivery was retried or processed more than once without deduplication. | Persist processed x-razorpay-event-id values and make later side effects idempotent. |
| Screenshot request fails or returns an unexpected result | The target URL, API key, request parameters or response handling is wrong. | Check the HTTPS endpoint, mapped url and access_key parameters, and inspect the actual response before mapping it to a storage or record module. |
| Asynchronous result never reaches the next step | The callback URL is not configured as expected, or the callback is not being handled or validated correctly. | Confirm the configured webhook_url, inspect callback handling and signature verification, and enable webhook_errors=true when you need error details. |
| Events appear to arrive in an unexpected order | Razorpay warns that webhook events may not always arrive in order; Make custom webhooks may also queue calls. | Use event IDs for deduplication and design state-changing work around verified event meaning, not arrival order alone. |
Or skip the browser setup
Instead of configuring a browser capture yourself, call ScreenshotNeo’s screenshot API with one GET request. It returns a screenshot or PDF; the following example saves a WebP response for a trusted target URL. See the ScreenshotNeo API documentation for request options.
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpIn a Make scenario, configure the HTTP request to call the same HTTPS endpoint with your API key and mapped target URL, then route the response as appropriate for your destination. ScreenshotNeo accepts cookie or consent banners before capture and removes more than 60 known consent platforms, newsletter popups and chat widgets; each of those steps can be turned off. Bot checks, blank pages, timeouts, failed loads and cache hits are not billed, and the response identifies the page verdict and billing status in headers. Its MCP server provides take_screenshot, get_page_info and capture_pdf tools for AI agents. The free plan includes 1,000 screenshots per month with no card; paid plans start at $5 for 3,000 shots.
Recommended Free Tools
Sign up for ScreenshotNeo’s free plan to try 1,000 screenshots a month with no card.
Quick Recap
Best Value
- 5-in-1 Connectivity: Equipped with a 4K HDMI port, a 5 Gbps USB-C data port, two 5 Gbps USB-A ports, and a USB C 100W PD-IN port. Note: The USB C 100W PD-IN port supports only charging and does not support data transfer devices such as headphones or speakers.
- Powerful Pass-Through Charging: Supports up to 85W pass-through charging so you can power up your laptop while you use the hub. Note: Pass-through charging requires a charger (not included). Note: To achieve full power for iPad, we recommend using a 45W wall charger.
- Transfer Files in Seconds: Move files to and from your laptop at speeds of up to 5 Gbps via the USB-C and USB-A data ports. Note: The USB C 5Gbps Data port does not support video output.
- HD Display: Connect to the HDMI port to stream or mirror content to an external monitor in resolutions of up to 4K@30Hz. Note: The USB-C ports do not support video output.
- What You Get: Anker 332 USB-C Hub (5-in-1), welcome guide, our worry-free 18-month warranty, and friendly customer service.
Rank #4
- Dual Converters, Infinite Potential：Includes 2× USB C male to USB A female adapters and 2× USB A male to USB C female adapters. Perfect for a wide range of uses—tablets with Bluetooth keyboards, expand USB ports on macbook, and more. Two different converters for all your daily needs
- Next-Level 10Gbps & 3A Charging: No more slow 480Mbps, this usb to usb c adapter has a transfer speed of up to 10Gbps, allowing you to do more transferring in less time. This usb adapter fits both USB A and USB C charger, supporting up to 3A fast charging
- Upgraded Exquisite Craftsmanship: With an aluminum alloy housing and metal connector, the usbc to usb adapter is extremely durable and sturdy. Rigorously tested to withstand more than 10,000 times of plugging and unplugging, ensuring long-lasting performance
- Broad Compatible: The usb c to usb adapter widely supports all USB C/ USB A devices like laptops, tablets, cellphones, car chargers, and phone chargers. Such as compatible with MacBook Pro/Air 2023/2022, Thunderbolt 4/3 Devices,Apple MagSafe Watch 9/8/7/SE/Ultra, iPad Pro 2022/2021, Samsung Galaxy S23/S20/S10, and iPhone 17/16/15 Pro. Plug and play
- Please Note: To reach 10Gbps speed, keep the cable under 3.3 ft. For USB A Male to USB C adapters, try flipping the USB C connector. USB C Male to USB A adapters support bidirectional 10Gbps transfer within 3.3 ft
Rank #3
- Sleek 7-in-1 USB-C Hub: Features an HDMI port, two USB-A 3.0 ports, and a USB-C data port, each providing 5Gbps transfer speeds. It also includes a USB-C PD input port for charging up to 100W and dual SD and TF card slots, all in a compact design.
- Flawless 4K@60Hz Video with HDMI: Delivers exceptional clarity and smoothness with its 4K@60Hz HDMI port, making it ideal for high-definition presentations and entertainment. (Note: Only the HDMI port supports video projection; the USB-C port is for data transfer only.)
- Double Up on Efficiency: The two USB-A 3.0 ports and a USB-C port support a fast 5Gbps data rate, significantly boosting your transfer speeds and improving productivity.
- Fast and Reliable 85W Charging: Offers high-capacity, speedy charging for laptops up to 85W, so you spend less time tethered to an outlet and more time being productive.
- What You Get: Anker USB-C Hub (7-in-1), welcome guide, 18-month warranty, and our friendly customer service.
For the service overview, visit ScreenshotNeo.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
