Get the ProofAge app for Zapier
The app is in beta and not yet listed in the Zapier app directory. Open this invite link, accept it, and ProofAge appears in your Zap editor. You need a ProofAge account and a workspace’s API keys to connect it.
What it does
The triggers give the status, the decision reason, your External Reference and metadata, the duplicate and blocklist flags, whether the age threshold passed, and the time of the decision. Every decision runs the trigger: a verification approved and later declined after a face block runs it twice.
Set it up
1
Connect a workspace
Add a ProofAge step to a Zap and sign in with the workspace’s Public API Key (
pk_…) and a Secret Key (sk_…) of the same workspace, from its page in the console. Zapier signs its requests with the secret key and uses it to check that results come from ProofAge. The connection is named after the workspace, with (Test) or (Live).2
Send a verification
Use Create Verification. Set External Reference to your own ID for the person or record: the user ID, the enrolment ID, the form response ID. It comes back with every result and is how later steps find the record, so never use an email address or a name. Redirect URL, Language and Metadata are optional. ProofAge sends no email: send the Verification URL with an email step of your own.
3
Act on the result
Start a second Zap with Verification Completed and pick the status you act on. Find the record in your app with External Reference and update it.
Your data
By default ProofAge sends Zapier the decision and the fields above, and nothing read from the person’s ID: no name, date of birth or document number. Include Extracted Document Data, on a trigger or on Find Verification, adds the fields read from the ID. Zapier then keeps them in your task history, so turn it on only when a later step needs them. Device signals, the identity of the person on your team who moderated, and images never reach the Zap’s output. Behind the triggers, Zapier creates a webhook subscription when you turn a Zap on and deletes it when you turn the Zap off. A workspace can hold 50.Test before going live
Connect a test workspace while you build: nothing is analysed or billed, and you choose each outcome.- Run Create Verification and open the Verification URL, or skip the widget entirely.
- Set the outcome on the verification’s page in the console, or with
POST /v1/verifications/{id}/test-outcome. The trigger runs within seconds. - When the Zap works, reconnect its ProofAge steps with the live workspace’s keys.
review first, so Verification Needs Review runs before the outcome you set.
Example Zaps
- Marketplace sign-ups (Sharetribe): User created → Create Verification (External Reference = user ID) → send the link by email. Then Verification Completed (Approved) → Approve User.
- Course certificates (Thinkific, Teachable): new enrolment → Create Verification. Approved → enrol the student in a gated certificate course.
- Forms to a sheet (Typeform, Webflow, Google Forms): new entry → Create Verification → add a Google Sheets row. Verification Completed (Any decision) → look up the row by External Reference → update its status.
- A list of people in Google Sheets: new row → Find Verification with Find or Create → write the link back to the row.
- Alerts: Verification Completed (Declined) or Verification Needs Review → a Slack or email message to your team with the External Reference and the reason.