Facehunch + n8n
Bring your existing photo search reports and their source context into n8n workflows. Sign in with your Facehunch account, read reports and sources, and send what matters to Slack, Google Sheets, Notion or email.
The node is read-only. It reads reports you already own and runs no new searches, so it never spends credits.
Reports in, context out.
Every operation reads data that already exists in your account.
Keep a running case log
List the reports in your account on a schedule and append each new one to the tracker your team already uses.
Archive source context
Read the stored source links, source names and similarity scores from an unlocked report and keep them in a sheet or database.
Notify people who need to know
Post a short summary with the report link to Slack, email or chat when a report finishes.
Check the account you automate
Read your own profile first, so a scheduled workflow always runs against the Facehunch account you expect.
Add the node to n8n.
Two routes, depending on where your n8n runs.
n8n Cloud
- 01Open a workflow and press the plus button to open the node panel.
- 02Search for “Facehunch” and choose the verified community node from the results.
- 03Add the node to the canvas. No package installation is needed on n8n Cloud.
Self-hosted n8n
- 01Open Settings, then Community Nodes, then Install.
- 02Enter the package name n8n-nodes-facehunch, confirm the community-node notice and install.
- 03Open a workflow, search for “Facehunch” in the node panel and add the node to the canvas.
Sign in once.
Reuse the credential.
The credential authorises against https://facehunch.com/oauth/n8n for the REST resource https://facehunch.com/v1, using dynamic client registration, the authorisation code flow with PKCE, expiring access tokens and refresh tokens. n8n keeps them refreshed.
Review or revoke the connection from Manage connected apps in your Facehunch account. Revoking stops future reads but does not delete reports.
What connected apps can seeVersion 3 talks to the product REST resource at https://facehunch.com/v1 with its own OAuth audience, instead of the earlier MCP endpoint. Tokens issued for the old resource cannot be reused, so create a new Facehunch OAuth2 API credential, connect it and select it in your Facehunch nodes before running workflows again. Operation names and inputs are unchanged.
- 01
Add the node and create a credential
Place a Facehunch node, open the credential field and choose Create new. The only credential type is Facehunch OAuth2 API.
- 02
Connect your account
Click Connect my account. n8n discovers the Facehunch authorisation server at facehunch.com/oauth/n8n for the REST resource https://facehunch.com/v1, registers its own callback address and uses the authorisation code flow with PKCE. There is no API key or client secret to paste.
- 03
Sign in and approve on facehunch.com
A Facehunch consent page opens. Sign in with the email code (or Google, where available), check the account shown under Signed in as, review the permissions and press Connect Facehunch.
- 04
Pick an operation
Save the credential and choose Get Profile, List Reports or Get Report. Manage or revoke the connection at any time from Manage connected apps at facehunch.com/oauth/n8n/connections.
Everything the node can do.
Grouped by resource. All three are plain REST reads that return JSON.
Account
Information about the signed-in Facehunch account only.
GET /v1/accountReadReturns your own account ID and email. Does not search for or identify other people.
No inputs.Report
Photo search reports that already exist in your account.
GET /v1/reportsReadBrowses existing owned reports, newest first. Each item carries the report ID, creation time, status, unlocked flag, result count and the report URL. With Return All the node follows paging internally and combines the pages for you.
Return All, or Limit (default 50).GET /v1/reports/:reportIdReadReturns metadata for one owned report and, when the report is unlocked, its stored sources: position, source name, URL and similarity score. Locked reports return metadata only.
Report Id (required).- Reads existing reports that your account owns. It cannot read anyone else’s.
- Respects locked reports: source links stay hidden until you finish access in the Facehunch app.
- Runs no new searches, uploads no photos and spends no credits.
- Performs no identity inference. A similarity score is not proof of who someone is.
- Version 3 ships only these three read operations. There are no trigger nodes. Use n8n’s Schedule trigger with List Reports to poll for change.
Six workflows to start from.
Each one pairs a Facehunch read with nodes n8n already ships.
New report summary to Slack
Poll your reports, keep only IDs that were not seen on earlier runs, read each new report and post its status, result count and link to a channel.
List ReportsSplit OutRemove DuplicatesGet ReportSlackArchive report sources to Google Sheets
Read one unlocked report, split the sources array into one item per source and append position, source, URL and score as rows for later review.
Get ReportSplit OutGoogle SheetsEmail a report digest
Collect the week’s reports, count completed and unlocked ones and send a short digest with links to each report in Facehunch.
List ReportsSummarizeGmail or SMTPNotion case log
Create one Notion database page per report with its ID, creation date, status and link, so every case has a place for notes and conclusions.
List ReportsRemove DuplicatesNotionWeekly report inventory
Fetch every report with Return All, total them by status and unlocked state and write one inventory row per week.
List Reports (Return All)AggregateGoogle SheetsLocked report reminder
Find reports whose sources are still locked and remind the owner to finish access in the app. The node never unlocks a report itself.
List ReportsFilter unlocked = falseSlack or emailA careful fit for careful work.
OAuth, not pasted keys
The credential uses dynamic client registration, the authorisation code flow with PKCE, expiring access tokens and refresh tokens. n8n stores and refreshes them, and you can revoke the grant from your Facehunch account.
Read-only by design
Every operation is annotated read-only. A scheduled workflow can run as often as you like without creating reports or spending credits.
Plain REST, plain JSON
Version 3 sends ordinary HTTP requests to the product REST API and returns JSON. No MCP server, no JSON-RPC, and each input item produces one linked output item.
Works with the tools you already use
Combine the node with Slack, Google Sheets, Notion, email and hundreds of other n8n nodes.
Where to look next.
Version 3.2.0, MIT licensed. Not an n8n core node.
Automate the follow-up.
Not the search.
Searches start in the Facehunch workspace, with a photo you have permission to use and a credit you have chosen to spend. The n8n node picks up afterwards: it reads the report you already have and helps you file, share and revisit it. Similarity results are leads, not verified identities.
How search and reports workRun a search, then let n8n handle the paperwork.
Upload a photo, get every matching page with its link and a similarity score. The n8n node reads the finished report. $9 per search, no subscription.