n8n-nodes-toldguard

Community nodes for integrating n8n workflows with ToldGuard.

Nodes

• ToldGuard Message sends one normalized upstream chat message into a ToldGuard aggregator_only instance.
• ToldGuard Aggregation Trigger receives the aggregation.ready batch emitted by ToldGuard.

Aggregator-Only Workflow

Use this mode when n8n owns the upstream chat integration, AI/CRM workflow, and final channel delivery.

Inbound messages:

Chat / CRM / Webhook -> ToldGuard Message

Aggregated batch:

ToldGuard Aggregation Trigger -> AI / CRM / analytics / channel delivery

Configure the ToldGuard API credential with:

• Base URL: for example https://toldguard.com
• Tenant ID: the aggregator-only instance ID
• Aggregator Input Token: the instance input token generated in ToldGuard

Set the production webhook URL from ToldGuard Aggregation Trigger as the instance output webhook in ToldGuard. If a signing secret is configured in ToldGuard, put the same secret in the trigger.

ToldGuard Message Input

The message node posts to:

POST /aggregator/messages/:tenantId

It sends this contract:

{
  "conversation_id": "external-conversation-id",
  "message_id": "external-message-id",
  "sender": "user",
  "content": "message text",
  "content_type": "text",
  "created_at": "2026-06-14T12:00:00.000Z",
  "contact_id": "optional-contact",
  "inbox_id": "optional-inbox",
  "phone_number": "optional-phone",
  "source_channel": "whatsapp",
  "attachments": [],
  "raw_event_ref": "optional-event-id",
  "raw_payload": {}
}

ToldGuard returns accepted, duplicate, or ignored in toldguard.status.

Aggregation Trigger Output

The aggregation trigger exposes:

• event
• tenant_id
• batch_id
• conversation_id
• message_count
• consolidated_text
• messages
• toldguard
• request
• raw