New:Microsoft Teams Notifications Are Now Available in Socket.Learn more →
Get Started

n8n-nodes-facehunch

Package Overview
Dependencies
Maintainers
1
Versions
3
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

n8n-nodes-facehunch

Native Facehunch REST API integration for n8n workflows.

latest
Source
npmnpm
Version
2.0.0
Version published
Maintainers
1
Created
Source

Facehunch for n8n

Build workflows with the Facehunch REST API. This community node sends ordinary HTTP resource requests and returns JSON responses. It does not connect to an MCP server or use JSON-RPC.

Installation

Install n8n-nodes-facehunch from Settings → Community nodes in your n8n instance. You can also install the npm package in a self-hosted n8n installation.

Authentication

Create the Facehunch OAuth2 API credential, select Connect my account, sign in to Facehunch, and approve the listed permissions. Credentials use dynamic registration, OAuth authorization code flow, PKCE, expiring access tokens, and refresh tokens. The API resource is https://mcp.facehunch.com/v1; REST tokens are separate from MCP tokens.

Upgrading from 1.x: reconnect the credential before running workflows. Version 2 replaces the old MCP transport with the native REST API. Inputs retain their names, while outputs are the API's resource JSON. Review existing workflows before enabling writes.

Operations

OperationHTTP request
Read your Facehunch profileGET /v1/account
Read an existing reportGET /v1/reports/:reportId
List your reportsGET /v1/reports

Workflow behavior

Each input item makes one API request and produces one linked output item. Optional pagination fields can be passed through the node's options; list responses retain their next-page cursor or offset. Write operations require the node's explicit confirmation switch. Failed requests stop the workflow unless Continue On Fail is enabled. HTTP errors are summarized without including credentials or raw request headers.

Requests use the fixed product API origin, encode resource identifiers, and do not follow redirects. Use a dedicated account for automation when you want separate access and data. Account ownership, workspace permissions, billing limits, and entitlement checks are enforced by the product API.

Development and support

Run npm ci, npm run lint, and npm test to build and validate the package with the n8n node CLI. Source and release automation: facehunch/n8n-nodes-facehunch. Report node issues in GitHub Issues.

Product: Facehunch · Privacy · Agent skill · MCP integration

MIT license.

Keywords

n8n-community-node-package

FAQs

Package last updated on 01 Oct 2026

Related posts