Home/Integrations/Make

Make IntegrationAlpha Testing

TamperCheck scenarios on Make's visual canvas

Use Make (make.com, formerly Integromat) to connect TamperCheck with Gmail, Google Drive, Airtable, HubSpot, and thousands of other apps. Watch folders, inboxes, or forms for new files, send them to TamperCheck for forensic analysis, then update rows, tickets, or Slack threads based on authentic / tampered / suspicious verdicts - all without writing glue code for each integration.

Join the waitlist View API docs →

Why Make

Document fraud detection where your team already works

Huge app catalog - Make's modules cover CRMs, storage, email, and databases. TamperCheck handles the hard part; Make handles routing and notifications.

Readable scenarios - your fraud-check step sits on the canvas next to triggers and actions, so ops and engineering share the same picture of the flow.

Filters and routers - only run TamperCheck when file type or source matches your rules; split paths by risk band to cut noise and cost.

Schedules and instant triggers - poll cloud folders on a cadence or react the moment a new file appears.

How it works

File in, verdict out - in four steps

1

Pick a trigger module

Choose what starts the scenario - new file in Drive, attachment in Gmail, row in a sheet, webhook from your product, or any Make trigger that gives you a document.

2

HTTP module → TamperCheck

Use Make's HTTP app to POST the file or URL to the TamperCheck API using your API key. Map trigger outputs into the request body or multipart upload.

3

Parse the verdict

Use Make's built-in JSON tools to read verdict, risk score, and findings. Optional: add a Router to send different paths for tampered vs authentic results.

4

Sync downstream apps

Update Airtable or Sheets, post to Slack or Teams, create Jira issues, or tag CRM records - whatever your team uses to act on document risk.

Setup guide

Set up TamperCheck in Make

~10 min

Use Make's HTTP 'Make a request' module against the REST API. Upload is async, so you poll or take a webhook.

  • API key from Dashboard - Developers (dt_...).
  • A trigger that provides the file (Drive Watch + Download, Gmail attachment, Custom webhook).
  1. 1

    Add an HTTP "Make a request" module

    POST the document.

    URL
    https://api.tampercheck.ai/api/v1/documents/
    Method
    POST
    Headers
    Authorization: Bearer dt_YOUR_API_KEY
    Body type
    Multipart/form-data
  2. 2

    Add body fields

    One File field for the document, Text fields for options.

    document
    File; map from trigger
    strategy
    Text = tampering_detection
    document_identifier
    Text (optional)
  3. 3

    Grab the job id

    Make parses the JSON: 202 + id (status: processing).

    job id
    {{ 1.id }}
  4. 4

    Get the verdict

    Webhook (recommended) or poll until done.

    Webhook
    Custom webhook id as webhook_id
    Poll
    GET /api/v1/documents/{id}/status/
    Loop
    Repeater + Tools/Sleep 5s
    Stop when
    status = completed
  5. 5

    Route on the verdict

    Branch on verdict or risk_score.

    Branch
    Router + filters
    Report link
    POST /api/v1/documents/{id}/report-link/
    Then
    Airtable/Sheets, Slack/Teams, Jira

Request reference

curl -X POST "https://api.tampercheck.ai/api/v1/documents/" \
  -H "Authorization: Bearer dt_YOUR_API_KEY" \
  -F "document=@/path/to/statement.pdf" \
  -F "strategy=tampering_detection" \
  -F "document_identifier=loan-app-12345"

What you see

A verdict card your whole team can read

TamperCheck

APP · just now

Verdict

⚠ Tampered · Risk 72/100

●

Font inconsistency in totals row (confidence: 0.89)

●

Running balance mismatch on rows 4-7 (confidence: 0.71)

statement_march.pdf · bank_statement · ~1m

View full report →
  • Structured JSON - map fields directly into Make's subsequent modules
  • Risk score - use in filters before notifying humans
  • Findings - aggregate into ticket descriptions or digest emails
  • Report link - append to CRM notes or support tickets
  • Error handling - retry and fallback paths in the same scenario

Workflows

How teams use TamperCheck in Make

Mortgage & lending: New uploads from a borrower portal trigger Make; TamperCheck runs before files sync to the LOS.

Procurement: Vendor invoices hit a watched inbox; only passes advance to payment workflows.

Property: Tenant application bundles are verified before lease generation.

Sales ops: Contracts from DocuSign or Drive are screened before executive approval steps.

FAQ

Common questions

Be the first to use TamperCheck in Make

Join the waitlist and we'll notify you the moment the integration is live. In the meantime, start with the API - we'll match your first top-up in free credits.

Join the waitlist Try the API now →