n8n/dist/modules/agents/builder/skills/integrations.skill.js

n8n Workflow Automation Tool

"use strict";
Object.defineProperty(exports, "__esModule", { value: true });
exports.integrationsSkill = integrationsSkill;
function integrationsSkill() {
    return {
        id: 'agent-builder-integrations',
        name: 'Agent Builder Integrations',
        description: 'Use when deciding whether Slack, Linear, Telegram, or another external platform should be a target-agent chat integration/trigger versus a node tool, and when adding or changing chat integrations; not for built-in Build chat or Preview chat behavior.',
        instructions: `\
## Purpose

Use this to decide whether the target agent needs an entry in \`integrations\`
or a normal node/workflow tool for an external product, then configure
\`integrations\` only when the integration is the right surface.

## Use when

- The user asks to add, update, or remove entries in the target agent's
  \`integrations\` array.
- The user asks to connect the target agent to an external chat platform with
  credentials.

## Integration vs Node Tool Decision

Use an integration when the product is the agent's conversation or trigger
surface: humans will mention, message, comment to, or resume the agent there,
or the agent needs to respond in that same platform conversation context.

Use a node/workflow tool when the product is only something the agent operates
on: searching records, creating tickets, updating objects, or sending a
business-process notification while the conversation happens elsewhere.

Examples:

- Slack integration: the agent should be chatted with in Slack, respond in
  Slack threads, DM users, message channels, add reactions, or render rich UI
  to Slack users.
- Linear integration: the agent should be triggered from Linear issues/comments,
  understand the current Linear subject, or reply in the same Linear
  conversation.
- Linear node tools: the agent is triggered from Slack, Preview, a task, or a
  workflow and only needs to search/create/update Linear tickets.

## Workflow

The \`integrations\` array controls how the target agent is triggered.

### Chat Integrations

- These are connected external chat platforms, not built-in Preview chat.
- Call \`list_integration_types\` first.
- Read the returned \`capabilities\`, \`useIntegrationWhen\`, and
  \`useNodeToolWhen\` fields before deciding to add an integration.
- Pick one returned \`credentialTypes\` entry and pass it to \`ask_credential\`.
- Persist only \`type\` and \`credentialId\`; never invent credential IDs or names.
- Preserve existing chat integrations unless the user asked to remove them.

## Gotchas

- Chat integration credential types must come from \`list_integration_types\`.
- Do not add a Linear integration just because the agent needs Linear issue
  CRUD. Use Linear node tools unless Linear itself is the chat/trigger context.
- For recurring or scheduled runs, create a task (\`create_task\`), not an
  integration.

## Verify

- Connected chat integrations use a credential id returned by \`ask_credential\`.
- The chosen integration matches \`useIntegrationWhen\`; otherwise use node or
  workflow tools.
- The final \`integrations\` array keeps unrelated integrations intact.`,
    };
}
//# sourceMappingURL=integrations.skill.js.map