How to Connect n8n to Your Intrascope AI Workspace: Automate GPT, Claude, and Gemini in Company Workflows

Most teams discover AI automation in two places: a chat window for daily work, and a workflow tool like n8n for repetitive tasks. The problem is that those two worlds rarely connect. Workflows end up with separate API keys, separate billing, and no visibility for admins.

Intrascope closes that gap. With the n8n integration, your automations run through the same governed AI workspace your team already uses, with one place for models, manifests, projects, usage analytics, and cost control.

Why connect n8n to Intrascope?

n8n is excellent at triggering actions: new CRM leads, support tickets, form submissions, scheduled reports. Intrascope is built for running AI inside a company with structure.

Together, they give you:

• One API key in n8n instead of managing credentials for OpenAI, Anthropic, Google, and others separately
• Multi-model access from a single node, including GPT, Claude, Gemini, DeepSeek, and more, depending on what your admin enabled
• Company governance with model limits, usage tracking, and project context applied to automated runs, not just manual chat
• Reusable context so you can attach Intrascope Manifests and Projects to workflow steps and keep output on-brand
• Cost visibility because every n8n call shows up in your workspace analytics alongside human usage

If your team already centralizes AI in Intrascope, n8n becomes the automation layer on top without creating a second, invisible AI stack.

What you need

Requirement	Details
Intrascope plan	Business or higher (n8n integration is included from Business upward)
Role	Admin (to create integration keys)
n8n instance	Cloud or self-hosted
Community node	n8n-nodes-intrascope

No separate OpenAI or Claude keys are required in n8n if your Intrascope workspace already has models configured (BYOK or managed usage).

Step 1: Create an Integration API key in Intrascope

1. Log in to platform.intrascope.app
2. Open Integrations from the sidebar
3. Click Create Key
4. Name it clearly, for example n8n production or n8n support automation
5. Copy the key immediately because it starts with isk_ and is shown only once

Store the key in your password manager or n8n credentials vault. You can revoke or deactivate keys anytime from the Integrations page without affecting user logins.

Step 2: Install the Intrascope node in n8n

1. In n8n, go to Settings → Community Nodes
2. Click Install
3. Enter: n8n-nodes-intrascope
4. Confirm installation

After a few seconds, search for Intrascope in the node picker. It appears under Transform.

Step 3: Add your Intrascope credential

1. Add an Intrascope node to a workflow
2. Click Create New Credential
3. Paste your isk_... API key
4. Click Test; a successful connection confirms n8n can reach your workspace
5. Save the credential (e.g. Intrascope - production)

You can reuse the same credential across every Intrascope node in n8n.

Step 4: Build your first workflow

The Intrascope node supports two operations.

Prompt (recommended for most workflows)

Best when data comes from a previous step, such as a webhook, database row, or email body.

• Instructions explain what the AI should do (system message). Example: "Summarize this support ticket in two sentences and suggest a priority level."
• Input Data defaults to {{ $json }} from the previous node
• Vendor & Model are loaded from your Intrascope account, and only enabled models appear
• Response Only is on by default and returns just the AI text. Turn it off to get tokens, cost, and model metadata.

Send Message (advanced)

For full control over the message array:

[
  { "role": "system", "content": "You reply in English only." },
  { "role": "user", "content": "Classify this lead as hot, warm, or cold." }
]

Additional options

• Max tokens and temperature
• Project ID lets you tie the run to a specific Intrascope project
• Manifest ID applies shared company context such as tone, rules, and brand voice

Example workflows teams actually build

1. Support ticket triage
Zendesk trigger → Intrascope (summarize + classify) → Slack notification

2. Lead enrichment
HubSpot new contact → Intrascope (extract company info from notes) → update CRM field

3. Weekly report draft
Schedule (Monday 9am) → Google Sheets (metrics) → Intrascope (write executive summary) → Gmail draft

4. Content pipeline
Typeform submission → Intrascope with Manifest (brand voice) → Notion page

In every case, the AI call runs through Intrascope, not a personal ChatGPT account buried in someone's n8n credentials. For a real-world example, see our consulting firm enterprise pilot, where we shipped a custom RAG module over more than 1GB of internal regulations via n8n.

How it works under the hood

When n8n executes an Intrascope node:

1. n8n sends a request to the Intrascope API with your isk_ key in the Authorization: Bearer header
2. Intrascope validates the key, resolves the acting company user, and applies workspace rules
3. The request hits POST /api/v1/user/llm/chat with your messages, model preference, and optional project/manifest
4. Intrascope routes to the right provider (OpenAI, Anthropic, Google, etc.) using your workspace configuration
5. The response, including text, tokens, and cost, flows back into n8n for the next step

Admins see last_used_at on each integration key in the Intrascope dashboard, so automated usage is never invisible.

n8n vs. calling provider APIs directly

	Direct API in n8n	Intrascope + n8n
API keys to manage	One per provider	One isk_ key
Model access	Configure each vendor	All enabled models in one node
Company context (manifests)	Manual in every prompt	Reusable Manifest ID
Usage visibility	Per-provider dashboards	Unified Intrascope analytics
Admin control	None	Model limits, projects, governance
Team alignment	Siloed automation	Same workspace as daily AI chat

For teams already on Intrascope, the integration is the difference between automating AI and automating AI with governance.

Security notes

• Integration keys use the isk_ prefix and are stored hashed, so Intrascope never shows the full key after creation
• Keys can be scoped, deactivated, or deleted without changing user passwords
• Keys authenticate as a company user (admin by default, or a specific user you pin to the key)
• Provider API keys stay encrypted inside Intrascope, so n8n never sees your OpenAI or Anthropic credentials. Read more in how Intrascope keeps API keys secure.

Also works with Zapier and custom HTTP clients

The Integration API is not limited to n8n. Any tool that can send HTTP requests with a Bearer token can call the same endpoints, including Zapier, Make, internal scripts, or your own backend. The n8n community node is simply the fastest path for workflow builders.

Get started

n8n integration is included on the Business plan and above. If you are on Starter, upgrade from Pricing to unlock Integration API keys.

Ready to automate AI with governance?

• Start free trial
• Book a demo