Data layer
App env readySupabase
Dashboard database, reporting facts, sync logs, and app-ready records.
Admin settings
Settings
Configure the account connections that make this Hub portable for IPA now and customer deployments later.
4 of 8 app runtimes ready
Connection center
Account integrations
This shows what the IPA Hub app runtime can see. Existing n8n workflow credentials, Codex app connections, and external account logins may still work even when this page needs app env values.
Secret values belong in environment variables or n8n credentials, not in this read-only screen.
Automation
No app envn8n
Workflow runner for source syncs, normalization, schedules, and run logs.
CRM
Needs envGoHighLevel
Sales CRM source for opportunities, contacts, conversations, calls, and pipeline status.
Work management
App env readyClickUp
Team-facing task and project surface for delivery work, client lists, and team execution.
Knowledge and planning
Needs envNotion
Docs, intelligence, source records, development tracking, and human review.
Research
No app envFirecrawl
Web search, scraping, source monitoring, and market-intel collection.
AI
App env readyOpenRouter
Ask Hub model gateway for executive questions and analysis modes.
Calendar
App env readyGoogle Calendar
Team calendar embed used by the Calendar workspace.
How the Hub works
Business systemsGoHighLevel, ClickUp, Notion, Google reporting, and approved source tools hold the operational work.
Automationn8n schedules imports, normalizes records, and logs each run. It moves data; it does not make business judgments.
Data foundationSupabase keeps the durable, queryable records that power the Hub. It is the app's source for dashboard data.
IPA HubThis workspace turns those records into concise, staff-facing decisions, registers, and performance views.
Working surfaces
SalesGoHighLevel -> n8n -> Supabase -> Sales Pipeline
Projects & tasksClickUp and Notion -> n8n -> Supabase -> Operations
Properties & accountsNotion or ClickUp -> n8n -> Supabase -> Properties and Accounts
Market intelligenceFirecrawl, public sources, and team signals -> n8n -> Supabase -> Intel
MarketingSearch Console and GA4 -> n8n -> Supabase -> Marketing
AI answersSupabase context -> OpenRouter -> Ask Hub
What each tool owns
ClickUpTeam task execution, client folders, specialist lists, and delivery follow-through.
NotionDocumentation, intelligence, customer profiles, operating references, and development tracking.
n8nSchedules, routing, API connections, data transforms, and sync logs.
SupabaseApplication-ready data, relationships, history, and reporting facts.
AgentsJudgment-heavy synthesis, recommendations, drafting, diagnosis, and QA.
Builder tools
Supabase CLIA developer command-line tool for checking schemas, generating migrations, and maintaining the database safely. It is optional for staff and does not change the Hub by itself.
GitHub and local codeVersioned app code, database migrations, and reusable n8n workflow builders live here so the platform can be reviewed and improved safely.
Internal platform notesDetails
Dashboard screens read from Supabase, not directly from GoHighLevel, Notion, ClickUp, or Google. New integrations should follow the same path: source system, n8n collection and normalization, Supabase contract, then a focused Hub surface. The current credential UI is environment-backed and read-only; saving customer-owned OAuth connections needs the auth and encrypted-secret slice before resale.