Vibe App Scanner for Zapier

Read an existing website report and use its summary in a workflow you configure. The first version provides Get Website Report and Find Website Report, with reported counts, coverage notes and an authenticated report link.

This integration is in development and is not yet available to install on Zapier. The setup instructions below describe the planned release.

What you need

A VAS account with REST API access and an existing website report.
An expiring VAS key scoped only to scan:read; contact VAS support for a scoped key.
A Zapier account with access to the integration once released. Zapier tasks, plan limits and any destination-app requirements still apply.

First workflow after release

Choose the approved integration, or accept a private test invitation provided by VAS.
Connect VAS by entering the report-only key in the connection's password field.
Choose Get Website Report, then enter an existing website report UUID.
Test the action and inspect the coverage note, reported counts and report access.
Configure the destination step only after reviewing the output and recipient access.

Find Website Report looks up the exact UUID and returns one report. It does not search arbitrary URLs, list all reports or create a missing report. The first version has no polling trigger and does not start or restart scans.

Output

The summary API reference describes the fields. Counts remain unknown while pending. A failed report can retain findings. Zero findings and completion do not establish that an application is secure.

The report link requires VAS authentication and account permission. Your destination users do not gain report access merely because a Zap sends them the link.

Errors

Error	What to check
Authentication rejected	Use an unexpired report-only API key.
Access denied	Check `scan:read` scope and REST API eligibility.
Report not found	Check the existing report UUID and connected account.
Rate limited	Wait, then retry only the read.
Read unconfirmed	Check VAS service availability and retry this read later.

Privacy and execution history

Only the summary endpoint is used. VAS excludes findings, evidence, target URLs and account details before sending a response to Zapier. Zapier can still retain summary fields, report IDs, request metadata and response headers in its history. Use an account and destinations approved for that information.

Connection privacy and execution history are still being tested. Wait for the released integration before connecting customer reports.

Support: Contact VAS.