How Customer Onboarding Intelligence Agent Builds Briefs

Your support team closed 340 tickets last week. Average resolution time: 4.2 hours. But 23 of those tickets were escalations that sat for 6+ hours before anyone noticed the SLA clock. A team lead spends 1–2 hours daily pulling reports from Hubspot, Notion, cross-referencing with CRM data, and writing up findings. By the time the analysis is done, the queue has moved on.

The result is reactive support instead of proactive operations. SLA risks surface after the breach. Routing problems persist because nobody has time to audit the rules. Agent coaching happens based on gut feel, not pattern data. Customer Onboarding Intelligence Agent automates the customer onboarding and contact management workflow, delivering structured analysis from Hubspot, Notion data without manual report-building.

Three Agents. Closed Won to Onboarding Brief. Before the First Call.

The Customer Onboarding Intelligence Agent pipeline runs 3 agents in sequence. The Researcher pulls data from Hubspot and Notion, and The Formatter delivers the output. Here is what happens at each stage and why it matters.

• The Researcher (Web Intelligence): When a deal closes in HubSpot, the Researcher activates.
• The Analyst (Reasoning (Tier 1)): the primary reasoning model synthesizes the full customer profile — HubSpot CRM data, 4 enrichment API calls, and web research — into onboarding intelligence.
• The Formatter (Delivery): Assembles the analysis into an 8-section Notion page: Customer Overview, Key Stakeholders, Success Criteria, Friction Points, Onboarding Questions, Quick Wins, Risk Flags, and Deal Context.

When the pipeline completes, you get structured output that is ready to act on. The blueprint bundle includes everything needed to deploy, configure, and customize the workflow:

• 22-node n8n workflow (.json) — you own it
• 2 tested agent system prompts (ITP-validated, Researcher + Analyst)
• HubSpot Closed Won trigger — fires automatically on every deal close
• Full customer enrichment — company, contacts, owner, web signals
• Stakeholder mapping with title-to-role inference
• Onboarding complexity scoring (LOW / MEDIUM / HIGH)
• 8-section Notion brief delivered before your first CS call
• $0.068/activation average — under $4/month at 50 closes
• Error handling matrix (17 failure modes documented)

SLA thresholds, escalation rules, and routing logic are configurable in the system prompts — customize for your ticket volume and priority structure. This means Customer Onboarding Intelligence Agent adapts to your specific process, terminology, and integration requirements without forking the entire workflow.

Understanding how the pipeline works helps you customize it for your environment and troubleshoot issues when they arise. Here is a step-by-step walkthrough of the Customer Onboarding Intelligence Agent execution flow.

Step 1: The Researcher

Tier: Web Intelligence

The pipeline starts here. When a deal closes in HubSpot, the Researcher activates. the analysis model with web_search crawls the customer — recent news, leadership changes, product launches, competitive landscape, and known challenges. Not a LinkedIn skim. Deep context for the onboarding team.

This stage ensures all downstream agents receive clean, validated input. If this step returns incomplete data, every downstream agent works with a degraded picture.

Step 2: The Analyst

Tier: Reasoning (Tier 1)

the primary reasoning model synthesizes the full customer profile — HubSpot CRM data, 4 enrichment API calls, and web research — into onboarding intelligence. Scores complexity (LOW / MEDIUM / HIGH), maps stakeholders by role (decision maker, champion, end user), identifies success criteria and friction points, and generates a recommended first-call agenda.

Why this step matters: This is where the pipeline applies judgment — not just data retrieval, but analysis.

Step 3: The Formatter

Tier: Delivery

This is the final deliverable — what lands in your inbox or dashboard. Assembles the analysis into an 8-section Notion page: Customer Overview, Key Stakeholders, Success Criteria, Friction Points, Onboarding Questions, Quick Wins, Risk Flags, and Deal Context. Structured for a CS Manager to scan in under 2 minutes before their first call.

The entire pipeline executes without manual intervention. From trigger to output, every decision point follows a documented path. Every execution produces a traceable audit trail.

All nodes have been validated during Independent Test Protocol (ITP) testing on n8n v2.7.5. The error handling matrix in the bundle documents the recovery path for each failure mode.

n8n's webhook v2 nests data under a body key. The webhook receives { body: { email: "..." } } instead of { email: "..." }. Two lines of defensive code prevent the most common deployment failure: const data = raw.body || raw. Every blueprint ships with this guard.

— ForgeWorkflows Engineering

Every metric is ITP-measured. The Customer Onboarding Intelligence Agent processes a Closed Won deal in under 60 seconds at $0.068/activation.

The primary operating cost for Customer Onboarding Intelligence Agent is the per-execution LLM inference cost. Based on Independent Test Protocol (ITP) testing, the measured cost is: Cost per Activation: $0.068/activation avg | ~$0.04 Researcher + ~$0.03 Analyst. This figure includes all API calls across all agents in the pipeline — not just the primary reasoning step, but every classification, scoring, and output generation call.

To put this in context, consider the manual alternative. A skilled team member performing the same work manually costs $40–60/hour for a support team lead’s analysis time at a fully loaded rate (salary, benefits, tools, overhead). If the manual version of this workflow takes 1–2 hours daily, the per-execution cost in human labor is significant. The blueprint executes the same pipeline for a fraction of that cost, with consistent quality and zero fatigue degradation.

Infrastructure costs are separate from per-execution LLM costs. You will need an n8n instance (self-hosted or cloud) and active accounts for the integrated services. The estimated monthly infrastructure cost is $2–5/month, depending on your usage volume and plan tiers.

Quality assurance: Blueprint Quality Standard (BQS) audit result is 12/12 PASS. ITP result is 20/20 accuracy | 14/14 milestones PASS. These are not marketing claims — they are test results from structured inspection protocols that you can review in the product documentation.

All cost and performance figures are ITP-measured — tested against real data fixtures on n8n v2.7.5 in March 2026. See the product page for full test methodology.

9 files — workflow, system prompts, schemas, and complete documentation.

When you purchase Customer Onboarding Intelligence Agent, you receive a complete deployment bundle. This is not a SaaS subscription or a hosted service — it is a set of files that you own and run on your own infrastructure. Here is what is included:

• README.md — Setup and configuration guide
• analysis_output.json — Analysis output schema
• analyst.md — Analyst system prompt
• customer_onboarding_intelligence_agent_v1_0_0.json — n8n workflow (main pipeline)
• customer_profile.json — Customer profile schema
• error-handling-matrix.md — Error handling reference
• researcher.md — Researcher system prompt
• tdd-v1.md — Technical Design Document
• webhook_input.json — Webhook input schema

Start with the README.md. It walks through the deployment process step by step, from importing the workflow JSON into n8n to configuring credentials and running your first test execution. The dependency matrix lists every required service, API key, and estimated cost so you know exactly what you need before you start.

Every file in the bundle is designed to be read, understood, and modified. There is no obfuscated code, no compiled binaries, and no phone-home telemetry. You get the source, you own the source, and you control the execution environment.

Customer Onboarding Intelligence Agent is built for Customer Success teams that need to automate a specific workflow without building from scratch. If your team matches the following profile, this blueprint is designed for you:

• You operate in a customer success function and handle the workflow this blueprint automates on a recurring basis
• You have (or are willing to set up) an n8n instance — self-hosted or cloud
• You have active accounts for the required integrations: HubSpot CRM, Notion workspace
• You have API credentials available: Anthropic API, HubSpot API, Notion API
• You are comfortable importing a workflow JSON and configuring API keys (the README guides you, but basic technical comfort is expected)

This is NOT for you if:

• Does not replace your CS platform — it delivers intelligence briefs, not task management or ticket routing
• Does not integrate with Salesforce or Pipedrive — HubSpot CRM only in v1.0
• Does not provide ongoing account health monitoring — it fires once at Closed Won, not on a recurring schedule
• Does not auto-create follow-up tasks or calendar events — the brief is informational, action is yours

Review the dependency matrix and prerequisites before purchasing. If you are unsure whether your environment meets the requirements, contact support@forgeworkflows.com before buying.

Every pipeline has boundaries. These are intentional design decisions, not oversights — understanding them helps you deploy with the right expectations and plan for edge cases in your environment.

Does not replace your CS platform — it delivers intelligence briefs, not task management or ticket routing

This is intentional. We default to human-in-the-loop for actions that carry reputational or financial risk. Once your team has validated output accuracy over 20+ cycles, you can adjust the pipeline to auto-execute — the workflow JSON supports it, but the default is conservative.

Does not integrate with Salesforce or Pipedrive — HubSpot CRM only in v1.0

We scoped this boundary after ITP testing revealed inconsistent results when the pipeline attempted this. The agents handle what they handle well — extending beyond this scope requires custom prompt engineering specific to your data shape.

Does not provide ongoing account health monitoring — it fires once at Closed Won, not on a recurring schedule

This keeps the pipeline focused on a single workflow. Adding this capability would introduce branching logic that varies by organization, and the tradeoff between complexity and reliability was not worth it for a reusable blueprint. Fork the workflow JSON if your use case demands it.

Deployment follows a structured sequence. The Customer Onboarding Intelligence Agent bundle is designed for the following tools: n8n, Anthropic API, HubSpot, Notion. Here is the recommended deployment path:

1. Step 1: Import workflow and configure credentials. Import customer_onboarding_intelligence_agent_v1_0_0.json into n8n. Configure your Anthropic API key (for Researcher + Analyst), HubSpot private app token (CRM read scopes), and Notion integration token.
2. Step 2: Set up HubSpot webhook and Notion database. Create a HubSpot webhook subscription for Deal property change on dealstage. Point it at your n8n webhook URL. Create a Notion database and share it with your integration. Set the Closed Won stage ID and Notion database ID in the workflow.
3. Step 3: Activate and test. Enable the workflow in n8n. Send a test payload with _is_itp: true to verify end-to-end. Check that a Notion page appears with 8 sections. Then let the Closed Won trigger take over.

Before running the pipeline on live data, execute a manual test run with sample input. This validates that all credentials are configured correctly, all API endpoints are reachable, and the output format matches your expectations. The README includes test data examples for this purpose.

Once the test run passes, you can configure the trigger for production use (scheduled, webhook, or event-driven — depending on the blueprint design). Monitor the first few production runs to confirm the pipeline handles real-world data as expected, then let it run.

For technical background on how ForgeWorkflows blueprints are built and tested, see the Blueprint Quality Standard (BQS) methodology and the Inspection and Test Plan (ITP) framework. These documents describe the quality gates every blueprint passes before listing.

Ready to deploy? View the Customer Onboarding Intelligence Agent product page for full specifications, pricing, and purchase.