Put the HumanAuth node in front of the step that moves money, emails a client or changes a system. The workflow pauses, an approver says yes with a biometric on their phone or Mac, and the run continues carrying a signed receipt — or stops on a no.
receipt_jws is the
proof: signed by the approver's device and the platform, bound to
plan_hash. Verify it
downstream with
@humanauth/verifier
— offline, against public keys — or attach it to the client report.
Install the community node n8n-nodes-humanauth (Settings → Community Nodes → Install), add your HumanAuth API key as a credential, and put the HumanAuth node in front of the step that should not run without a human. The workflow pauses until someone approves on their phone or Mac.
Yes. Approvers get a push notification in the HumanAuth app on iPhone, iPad or Android — or in the Mac menu bar — and approve with a biometric or deny with a reason.
Message-and-wait steps record that someone clicked a button. The HumanAuth node also returns a receipt signed by the approver's device and bound to the exact action, which you can verify offline later or in a downstream step — useful when you need to show a client or an auditor who approved what.
Yes. Point the node at a group and set a quorum, such as two of three approvers. Other approvers' votes stay hidden until the request resolves.
Yes. The node's Base URL can point at a self-hosted HumanAuth platform instead of api.humanauth.ai.
Onboarding is hands-on for now. Tell us about the workflow and we will set you up. 1,000 approval requests are free every month.