One workflow. Start to finish.

See Brain → Plan → Execute → Render with guardrails (Hub) and meaning-preserving normalization (Spine).
Target: 4–5 minutes. Enterprise buyers, architects, senior operators.

Start Free Book Demo

Video Outline (4–5 minutes)

Modern work isn't hard because teams lack capability—it's hard because tools don't cooperate. IntegrateWise fixes that.

Full Demo Video (Coming Soon)

Connect once. Everything flows.

Video Chapters

  • 0:15 – Hook: scattered tools, lost AI ideas, brittle integrations
  • 0:30 – Stack Connection: Notion, Slack, Google, HubSpot, Stripe
  • 0:45 – Brainstream Ingest: AI chats become memory
  • 0:45 – Spine Normalization: canonical entities, preserved meaning
  • 0:45 – Hub Guardrails: policy-evaluated, audited routes
  • 0:45 – Agents in Action: plan → tasks → calendar sync
  • 0:30 – Render Outputs: docs, decks, emails with correlation IDs
  • 0:20 – Compliance Mode: Render Only, zero-write, TTL cache
  • 0:20 – BYOM: model picker, cost guards, fallbacks
  • 0:10 – Close + CTA

Tight Narration Script

  • Connect once. Everything flows. No migrations.
  • AI conversations are your thinking—streamed into searchable memory.
  • Meaning matters. Canonical entities preserve relationships and context.
  • Safety is a control plane. Hub authorizes, applies policies, writes audit trails.
  • Agents act with context: compose plans, create tasks, sync timelines, draft updates.
  • Outputs everyone can use: deterministic inputs, versioned outputs, correlation IDs.

Workflow 1: Brain → Plan → Execute (Universal)

From AI chat to structured execution across tools

The Flow

1

Webhook Ingest

AI chat streams via webhook to Brain

slack_webhook / ai_chat_webhook
2

Brain Agent Plans

Creates structured plan with milestones, tasks, owners

brain.agent.plan
3

Spine Normalize

Tasks converted to canonical Task schema

spine.normalize
4

Hub Authorize

Policy checks: write or render-only?

hub.authorize
5

Dispatch Tasks

Tasks created in Notion

dispatch.create_tasks → notion
6

Update Calendar

Timeline synced to Google Calendar

dispatch.update_calendar → google_calendar
7

Render Doc

Weekly status document generated

render.generate
8

Audit Log

Correlation ID recorded

audit.log

Proof Elements

  • event_id: evt_abc123def456
  • X-IW-Idempotency-Key: idem_xyz789...
  • correlation_id: corr_w1_20250115

Artifacts Generated

  • Weekly Status Doc (rendered)
  • Tasks in Notion workspace
  • Calendar events in Google Calendar
  • Audit log entry with correlation ID

Download Template

Get the JSON workflow template to import into your IntegrateWise workspace

Workflow 2: CS Intelligence (Specialized Lens)

From multi-source signals to governed intervention with manager approval

The Flow

1

Ingest Signals

Slack message, HubSpot deal, Stripe subscription

webhook.ingest + connector.sync
2

Spine Normalize

Account, Opportunity, Interaction schemas

spine.normalize
3

Recompute Health

Health score, ARR risk, technical health, churn risk

cs.health.recompute
4

Generate Playbook

Intervention steps, owners, timing, comms

agent.generate_playbook
5

Render Email Draft

Customer email template populated

render.generate
6

Hub Authorize

Policy requires manager approval

hub.authorize + policy_manager_approval
7

Approval Request

Manager reviews and approves

approval.request
8

Send Email

Dispatched via Google Workspace

dispatch.send_email (full mode)
9

Audit Log

Correlation ID + policy ID + approver ID

audit.log

Measurable Outcomes

  • 67%

    faster time to intervention

  • 40%

    reduction in handoffs between teams

  • 3x

    faster executive updates

  • 100%

    audit trail from signal → action

CS Intelligence Views

Health Scores
ARR & Revenue
Churn Risk
Technical Health

Download Template

Get the JSON workflow template for CS Intelligence

Architecture Diagrams

Spine + Hub + Agents + Render with guardrails-first design

End-to-End Flow

Source ToolsNotion · Slack · Google · CRM · StripeIngestWebhooks · ConnectorsSpine (Canonical)Task · Document · InteractionPreserve relationships & formulasHub (Control Plane)AuthN/Z · Policies · AuditRoutes: full | render-onlyRate caps · Spend guardsAgentsPlan · Orchestrate · DraftRetrieve contextRenderDocs · Decks · EmailsCorrelation IDsMode: Render Only / Full

Hub Tables + Policy Evaluation

Routeid, source_app, target_app, resource_typetransform_id, policy_id, mode, statusPolicyid, scope, rbac_role, boundaryretention_ttl, redaction_rulesaudit_requiredAuditLogactor_id, action, resourcebefore, after, correlation_idtimestampEvaluation Flow1. Authorize (RBAC + scopes)2. Evaluate policy (boundary, retention, redaction)3. Transform (mapping + PII handling)4. Dispatch (target app route)5. Audit (immutable log)GuaranteesRender Only: read-only connectors, zero mutationsFull Integration: two-way sync under policyPer-route overrides; per-role permissionsRate caps · spend guards · anomaly alerts

Spine Canonical Entities

AccountCanonicalID · ExternalIDLabels · PIIClassContactCanonicalID · ExternalIDLabels · PIIClassOpportunity / DealSourceApp · SchemaVersionCreatedAt · UpdatedAtTaskAssignee · DueDateStatus · LabelsDocumentType · VersionCorrelationIDInteractionChannel · TimestampLinkedEntity

Modes: Full Integration vs Render Only

Full Integration

Two-way sync + automation

  • Agents can create and update workflows
  • Execute actions across tools
  • Best for teams that want execution
  • Governed by Hub policies and boundaries

Render Only

Read-only analytics + outputs (zero write)

  • Read-only connectors with no write scopes
  • Zero mutation of source systems
  • Best for compliance-first orgs
  • Perfect for executive reporting and dashboards

"If you're enterprise/compliance-first, start Render Only."

Connect your stack. Keep meaning. Add guardrails.

Start with one workflow and scale to an operating system.

Start Free Book DemoView Docs