Integrations
Connect Power Automate
Create a workspace API key, then use Power Automate when a verification is completed or stopped.
Updated 12 October 2026
You connect Power Automate with an API key from Settings. The key belongs to one workspace. It cannot read another workspace. Power Automate uses the same key as Zapier, Make, and n8n.
Microsoft’s cloud flow steps are in Create a cloud flow in Power Automate. FreeAML appears in the trigger search after Microsoft publishes the connector.
Create your API key
- 1
- 2
Open Settings.
- 3
Under API keys, enter a name you will recognise, such as Power Automate.
- 4
Select Create API key. FreeAML shows the key once. Copy it. We store only a hash.
Create a cloud flow
- 1
Sign in to Power Automate.
- 2
From the navigation bar on the left, select My flows.
- 3
Select Create from blank.
- 4
Select the Add a trigger node. The Add a trigger pane opens.
- 5
In the search field, enter FreeAML, then select the trigger you want.
- 6
When the connection opens, paste the API key into the field labelled API key. That label is the one on the FreeAML connector.
- 7
To add an action in the new designer, select the plus sign after the trigger and search for FreeAML. In the classic designer, select + New step, then search in Choose an operation.
The same key works in Zapier, Make, and n8n while you are waiting for FreeAML to show in the Power Automate search.
Triggers
Power Automate can start a flow when something happens in your workspace. FreeAML posts the event to the address Power Automate gives it. The payload does not include identity document images.
- When a verification is 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.
- When a verification is stopped. The status changed to rejected, expired, or declined.
Actions
- 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. Leave the service charge blank for no charge. There is no saved default, and the charge is not stored on the workspace. 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, including its status.
- Resend an invite. Emails the same link again. Enter the verification id. Wait a minute between sends.
- Get this workspace. Confirms the key and returns the workspace name.
Credits, if you use them on FreeAML, belong to the workspace. This connector does not buy credits and it does not pay out to a bank.
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.
Does this connector charge my client by itself?
No. Your client pays on FreeAML. The service charge, if you set one, applies only to the verification you are sending.