Investigation Workflow Templates (n8n)
Investigative Tools

Investigation Workflow Templates (n8n)

Skip to main content
Table of Contents
< All Topics
Print

Investigation Workflow Templates (n8n)

Last updated: October 21, 2026

Reusable n8n workflow patterns for automated investigation pipelines. Each template describes the node chain, webhook configuration, credential requirements, and expected outputs.

Available templates

Template Pattern Endpoints used
Corporate investigation Follow the money: entity → registry → contracts → graph /investigate/workflow, /investigate/entity-lookup
Document triage Batch intake: file drop → extract → cross-reference /investigate/entity-lookup, /investigate/tool-recommend
Media verification Viral content: trigger → reverse search → geo → assessment /investigate/workflow, /investigate/entity-lookup

Prerequisites

  • n8n instance with HTTP Request node access
  • Patriot API base URL and JWT token configured as n8n credentials
  • For Tier 2 integrations: respective API keys configured in the Patriot API .env

Credential setup in n8n

  1. Create an HTTP Header Auth credential in n8n:
  • Name: Patriot API
  • Header Name: Authorization
  • Header Value: Bearer
  1. For each workflow, configure the Patriot API base URL as an n8n variable:
  • Variable name: PATRIOT_API_URL
  • Value: https://your-api-host/api/v1

Notes from the n8n documentation

  • The HTTP Request node sends a request to any service with a REST API. You can fill in its parameters by hand or import a curl command, and it can also be attached to an n8n AI agent as a tool. Each template’s request nodes use the credential from step 1.
  • Header Auth versus Bearer Auth. n8n’s documentation notes that bearer authentication is just header authentication with the name set to Authorization and the value set to Bearer . That is the setup in step 1. n8n also offers a separate Bearer Auth credential type that does the same thing.
  • Variables are not available on every plan. n8n custom variables are available on n8n Cloud Pro and Enterprise and on self-hosted Business and Enterprise. Only instance owners and admins can create them. Keys may contain only letters, numbers and underscores, so PATRIOT_API_URL is valid. A workflow reads it as $vars.PATRIOT_API_URL. On a plan without variables, type the base URL directly into each HTTP Request node, and update every node if the host changes.
  • Keep the token in the credential from step 1. Never type it into a node’s URL or body.

Zero-PII discipline

All workflow data stays within the n8n execution context and the Patriot API. Workflows must not:

  • Log personally identifiable information
  • Send data to third-party analytics
  • Store intermediate results outside the Patriot infrastructure

Sources

Expanded with AI research and drafting assistance from the primary sources cited; editorial review pending.

Was this article helpful?
0 out of 5 stars
5 Stars 0%
4 Stars 0%
3 Stars 0%
2 Stars 0%
1 Stars 0%
5
Please Share Your Feedback
How Can We Improve This Article?