Integrations
Connect Make
Create a workspace API key, then use Make when a verification is created, completed, or stopped.
Updated 6 October 2026
You connect Make with an API key from Settings. The key belongs to one workspace. It cannot read another workspace. Make uses the same key as Zapier and n8n.
Create your API key
- 1
- 2
Open Settings.
- 3
Under API keys, enter a name you will recognise, such as Make.
- 4
Select Create API key. FreeAML shows the key once. Copy it into Make. We store only a hash.
- 5
In Make, add the FreeAML connection and paste the key. Reports from modules you run go to the email on the account that created the key.
Triggers
Make can start a scenario when something happens in your workspace. FreeAML sends the event to the hook Make gives you.
- Verification completed. The status is complete and the report is ready. You receive the verification id, reference, client email when we have one, person or entity, paid or unpaid, the completed time, a report link when there is one, and the workspace id.
- Verification failed, expired, or declined. FreeAML stores those as rejected, expired, and declined.
- Verification created. A new verification exists.
invite_sentis true when the client email has gone out.
The payload does not include identity document images.
Modules
- Create a verification (your client pays). Enter the client email, an optional reference, and an optional role. Your client chooses person (KYC) or entity (KYB) on the link. An individual check is $20. A company, trust, or SMSF check is $40. You can add a service charge of $0, $25, $50, or $100 on that verification only.
- Create a verification (your workspace pays). You choose person or entity before the invite is emailed, and there is no service charge. Pay from the link in the module output before the invite goes out. The report email is the account that created the API key.
- Get a verification. Looks up one verification in this workspace by id or reference.
- Resend invite. Emails the same link again. Enter the verification id. Wait a minute between sends. When your workspace pays, pay for the verification before you resend.
If a key stops working
- Revoke removes access immediately. Hooks that used that key stop as well.
- Paste a new key into Make. The old connection does not pick up the new key on its own.
- The FreeAML app in Make is published after Make reviews it. Until then, a Make account that has been invited to the app can still connect with your key.
Where do reports go?
To the email of the person who created the API key. That address has to be the signed-in account.
Can one key see every workspace I belong to?
No. Create the key while that workspace is open. It only reads and sends verifications for that workspace.