EAD Factory — n8n connector

Connect n8n to EAD Factory to generate certified digital evidence and manage qualified signature request workflows.

Install this connector and use EAD Factory operations as steps inside any n8n workflow. Each operation maps to one capability of the underlying EAD Factory platform.

Install (self-hosted n8n)

npm install @g-digital/n8n-nodes-ead-factory

Then restart n8n. The node will appear in the Nodes panel under "EAD Factory".

Using with n8n AI Agent

For AI-driven automation, configure an n8n AI Agent node with the following system prompt. It covers all lifecycle workflows: evidence creation, certified notifications, signature processes, dossier certification, and certified chats.

→ Full system prompt and workflow guide: @g-digital/n8n-agent-system-prompt — see the docs/n8n-agent-workflows/gocertius-ead-system-prompt.md in MCP_Market_Distribution.

Quick system prompt snippet

Paste this into your AI Agent node's System Message:

You are a Digital Trust assistant using the EAD Factory n8n connector.
UUID generation: generate UUID v4 for all `id` fields you must supply.
IDs from responses: never invent path parameters — always use values returned by previous tool calls.
Async operations: after evidence_seal, dossier_certify, signature activation, and chat certification — poll the corresponding list/status tool until the terminal state is reached before proceeding.
File uploads: when a tool returns uploadFileUrl or url, PUT the file bytes there with a separate HTTP Request node before calling the next step.
See the full lifecycle guide at: https://github.com/g-digital-by-Garrigues/MCP_Market_Distribution/blob/main/docs/n8n-agent-workflows/gocertius-ead-system-prompt.md

Operations

| Operation | Description | |---|---| | generate_evidence | Hash, upload, and timestamp a local file to create a certified digital evidence record with full custody tracking. | | get_evidence | Retrieve complete details of a digital evidence record by its ID, including status and custody information. | | create_signature_request | Create a new signature request, optionally running the full setup flow with document, signatory, and activation. | | add_document_to_signature_request | Attach and upload a document to an existing draft signature request, returning the new document ID. | | add_signatory_to_document | Add a signatory to a document within a draft signature request. | | add_observer_to_document | Add an observer to a document within a draft signature request. | | add_validator_to_signatory | Add a validator to a specific signatory on a document within a signature request. | | activate_signature_request | Activate a draft signature request, triggering notifications to all signatories. | | get_signature_request | Retrieve full details of a signature request by ID, including documents, participants, and status history. |

Credentials

This node requires a "EAD Factory API" credential with the following fields:

| Field | Description | Secret? | |---|---|---| | API Base URL | Base URL of the EAD Factory REST API. Leave blank only if you know your environment uses a different endpoint. | no | | API_BASE_URL | Base URL for the Evidence Manager API endpoint provided by EAD Factory. | no | | FULL_FLOW_EMAIL_BASE | Base email address used to generate participant addresses in full-flow signature requests. | no | | FULL_FLOW_FILE_PATH | Default local file path used when running the full signature-request flow. | no | | HTTP_PORT | Port number the MCP server listens on when running in HTTP transport mode. | no | | OKTA_CLIENT_ID | Client ID for your Okta application, obtained from your EAD Factory onboarding credentials. | no | | OKTA_CLIENT_SECRET | Client secret for your Okta application, obtained from your EAD Factory onboarding credentials. | yes | | OKTA_SCOPE | OAuth scope string required when requesting tokens from the Okta authorization server. | no | | OKTA_TOKEN_URL | Full URL of the Okta token endpoint used for the client credentials OAuth flow. | no | | POLL_INTERVAL_MS | Milliseconds to wait between status-polling attempts when generating evidence. | no | | POLL_MAX_ATTEMPTS | Maximum number of polling attempts before evidence generation returns a timeout error. | no | | SIGNATURE_API_BASE_URL | Base URL for the Signature Manager API endpoint provided by EAD Factory. | no | | TRANSPORT | Set to stdio for local use or http for remote deployments requiring authentication. | no |

Need credentials? Sign up or log in at https://eadtrust.example.com/onboarding.

Use as an AI Agent tool

This node is flagged usableAsTool: true, so any n8n AI Agent (n8n ≥ 1.79.0) can consume it dynamically: drag it into the workflow and wire its main output to an AI Agent's "Tool" input.

For best results pair with an AI Agent node running V2 — V3 has a known empty-tool-response bug in some recent n8n versions (see n8n issue #26202).

License

MIT. See LICENSE.