Skip to main content
Build an agent tool as an n8n workflow. Activating the workflow creates the organization tool, tests and publishes it, and attaches it to the agents you select. This guide uses the n8n-nodes-slng community node. See Integrate n8n for installation and credentials.

Prerequisites

  • The SLNG community node on a self-hosted n8n instance.
  • An SLNG API credential in n8n.
  • One or more agents in shared tool mode.
Activation sends one request with sample arguments as part of publishing. Build the workflow so this test does not create an unwanted production side effect.
1

Add the SLNG Trigger

Start the workflow with SLNG Trigger and select your SLNG API credential.
The SLNG API credential dialog in n8n

Add the SLNG API credential

2

Choose the agents

Select every agent that should use the tool. Legacy-mode agents are labeled legacy, unsupported and cannot receive shared tool attachments.
The Agents selector in the SLNG Trigger node

Choose the agents for the workflow tool

3

Describe the tool

Enter a specific Tool Name and Tool Description. For a contextual tool, the model uses this information to decide when to run it.
4

Choose the invocation

Choose LLM Tool (Contextual) for a model-invoked action during the conversation. Choose System Tool for a call event.The system events are call start, first user message, call end, tool succeeded, and tool failed. See Run a tool on call events for event arguments and restrictions.
5

Define the input

For an LLM tool, add each parameter’s name, type, description, and required state. For a system tool, select triggers and map arguments from call data.
The SLNG Trigger node with tool settings and a parameter

Configure the name, invocation, and inputs

6

Build the workflow

Read incoming arguments from toolArguments, for example {{ $json.toolArguments.order_id }}. Use n8n’s Pin Data after one real test to map later nodes against a stable sample.
7

Return a result

Set Respond to Using Last Node when the agent needs the final node’s JSON. Set it to Immediately to acknowledge the request while the workflow continues.Use Edit Fields (Set) to shape the final JSON. Respond to Webhook does not support community trigger nodes.
8

Activate and verify

Activate the workflow. Confirm that the published tool appears under Global Tools and on each selected agent’s Tools page.
An n8n workflow tool published in Global Tools

The published tool in Global Tools

The n8n workflow tool on an agent's Tools page

The tool attached to an agent

Authenticate webhook calls

HMAC is the default. SLNG signs the request body and sends the signature in X-Signature-256; the SLNG Trigger node validates that signature. Leave the secret empty to generate one during activation and register it on both sides. Under Show Advanced Settings, you can switch to bearer authentication, change the webhook path or HTTPS method, set the timeout, and control whether the result is shown to the LLM. Deactivating the workflow removes the organization tool and its attachments. The node repository templates include model-invoked lookup workflows and event-driven post-call workflows.