Overview
Node IQ is Mothernode’s AI integration layer. It allows you to connect external AI providers (like OpenAI, Claude, Gemini, etc.) and use them directly within your workflows—job analysis, exports, reporting, and more.
This is not plug-and-play. It’s a controlled integration that requires proper setup, permissions, and an active AI subscription on the provider side.
Access Requirements (Non-Negotiable)
Before you start:
- Admin access is required
- Navigate to:
Administration → API Settings → AI Assistant Settings - You must have:
- A paid AI provider account
- A valid API key from that provider
If those aren’t in place, nothing else matters—this won’t work.
Step 1: Configure Provider Profiles
This is where you define which AI services Mothernode can use.
What you’ll configure:
- Display Name (internal reference)
- Provider
- Examples:
- OpenAI
- Anthropic (Claude)
- Google (Gemini)
- Custom (OpenAI-compatible endpoints)
- Examples:
- Model Selection
- Example:
gpt-5-mini,claude-sonnet-4-5, etc.
- Example:
- API Key
- Pulled directly from your AI provider account
Key Insight
You can configure multiple providers and models. This gives you flexibility:
- Different models for different use cases
- Redundancy if one provider throttles or fails
- Cost optimization across providers
Step 2: Set Default Provider (Optional but Strategic)
You can assign a default provider.
This becomes your baseline AI engine unless overridden elsewhere.
Recommendation:
Set your most reliable + cost-efficient model as default. Use premium models selectively.
Step 3: Configure Pre-Built Page Prompts
This is where the real value is created.
You’re defining how AI behaves inside Mothernode.
Each prompt includes:
- Page Key
- Example:
export_historyorder_detail
- Example:
- System Instructions
- Controls tone, rules, and constraints
- User Message Template
- Injects real Mothernode data into AI prompts
What’s happening behind the scenes:
- Mothernode sends structured data (JSON)
- Your prompt tells AI how to interpret it
- AI returns structured analysis
- Mothernode displays the result
Important Rule
The AI only knows what you send it. If data is missing, results will be incomplete or wrong. Sending incomplete results or missing data will skew responses.
Step 4: Save Configuration
- Accept the Node IQ Usage Policy
- Click Save AI Settings
Step 5: Assign User Permissions (Critical Step)
This is where most setups fail.
After configuration:
- Access each User Account in your organization who shoul have permission to Node IQ services.
- Go to User Permissions
- Explicitly grant access to:
- AI Assistant
- Node IQ features
If you skip this:
Users will not see or be able to use AI—period.
Financial & Subscription Reality
Let’s be direct:
- Mothernode does NOT include AI usage
- Your AI provider subscription is separate
What to expect:
- Most providers use credit-based billing
- Every AI query:
- Consumes tokens/credits
- Has a real cost
Action Items:
- Understand your provider’s pricing model
- Monitor usage
- Set internal expectations with your team
Data Handling & Responsibility
This matters.
- Mothernode:
- Sends your data to the AI provider
- Receives results
- Displays them in the system
- Mothernode does NOT:
- Validate accuracy
- Guarantee correctness
- Take responsibility for output
Best Practice:
Treat AI output as a draft, not a decision.
Always verify:
- Financial data
- Job costing
- Operational recommendations
Common Pitfalls
Avoid these:
- ❌ No API key entered
- ❌ Using a free AI account (won’t work reliably)
- ❌ Forgetting to assign user permissions
- ❌ Poor prompt design (garbage in → garbage out)
- ❌ Assuming AI “knows” missing data
Strategic Takeaway
Node IQ isn’t just a feature—it’s a force multiplier.
- Done right → faster decisions, deeper insights
- Done poorly → noise, cost, and confusion
The differentiator is not the AI.
It’s how you configure and control it.
Node IQ Usage Policy
Review the full policy here:
👉 https://support.mothernode.com/node-iq-policy
