Is there a native Verdict Capture module in Make?

Most customers use the HTTP module to call the Verdict Capture REST API — this is officially supported and works for all flows. A native module is planned; in the meantime, importable scenario blueprints cover the common patterns.

What file types can I send through Make?

Verdict Capture accepts JPEG, PNG, and HEIC. Most Make file modules pass through binary data unchanged, which works directly with the verification endpoint.

How do I handle errors and retries?

Use Make's break-on-error and retry settings on the HTTP module. For more sophisticated handling, use a separate error-handler scenario that catches failed runs and routes them to ticketing or human review.

Can scenarios call my own backend after verification?

Yes. After the Verdict Capture HTTP module, add any custom HTTP module to POST the result to your backend. Many customers use this pattern to update internal databases or trigger billing logic.

Does this work for high-volume real-time pipelines?

Make is excellent for medium-volume orchestration. For pipelines processing tens of thousands of verifications per hour, consider calling the Verdict Capture REST API directly from your backend or using n8n in queue mode.

Verdict Capture Make Integration

Drop Verdict Capture into any Make scenario to add photo verification to your visual automations. Trigger on photos from any app, verify with AI, and branch by is_compliant.

Try Live Demo Contact Sales

Quick Start

1. Install

text

Add an HTTP module to your scenario. Point it at the Verdict Capture REST API and authenticate with your API key.

2. Use

text

Module: HTTP — Make a request

URL: https://verdictcapture.com/api/v1/verify
Method: POST
Headers:
  X-API-Key: vai_your_api_key
Body type: multipart/form-data
Fields:
  image (File): {{1.photo_data}}
  policy (Text): scooter_parking
  metadata (Text): {"trip_id": "{{1.trip_id}}"}

Parse response: Yes (JSON)
Use {{2.is_compliant}} in downstream router to branch.

Features

Visual Scenario Builder

Drop the Verdict Capture HTTP module into any scenario and connect it visually. No code required for typical pipelines.

1,500+ App Connectors

Trigger from Webflow, Jotform, Notion, Airtable, ShipStation, Klaviyo, or any other Make-supported source.

Router-Based Branching

Route compliant and non-compliant verifications down different paths. Trigger notifications, tickets, or DB updates per branch.

Error Handling Built In

Per-module retry, error-handler scenarios, and break-on-error options keep scenarios resilient under load.

Async Mode

For high-volume pipelines, use Verdict Capture's async option. Make's webhook trigger fires when each verification completes.

Importable Scenarios

Pre-built scenario blueprints for common patterns — form-to-verify, return-photo-check, delivery-proof flows.

Code Examples

Requirements

A Make account on any paid tier (free tier supports limited ops)
Verdict Capture API key (free sandbox available)
Source app (Webflow, Jotform, Drive, Airtable, etc.) connected in Make
Destination app (CRM, sheet, ticketing) connected in Make

Frequently Asked Questions

Add Photo Verification to Your Make Scenarios

Wire Verdict Capture into any visual automation. Start your free sandbox today.