04 · Integrations

External systems

The live integrations behind the sales pipeline and the bots. Each has a direction (in / out / both), an auth model and a single owner. Since the Maestro cutover the pipeline runs on AWS (Lambda · DynamoDB · SQS · ECS Fargate · Bedrock); Airtable stays the config/brain SSOT. If anything in this list goes down, the corresponding flow in Current Flow stops cold.

System	Role	Direction	Auth	Owner
Airtable	Config / brain SSOT · 4 bases	↕ both	PAT · 2 tokens	Farid
HubSpot	CRM source · deals / contacts / owners	↓ in	OAuth + API key	Jess
AWS	Maestro pipeline · Lambda · DynamoDB · SQS · ECS Fargate · Bedrock	↕ both	IAM · us-east-2	Daniel
n8n Cloud	Generation crons (→ /generate) + legacy send-worker	↑ out	API key · happenventures workspace	Farid
Gmail	Outbound send (as the rep · gmail.send)	↑ out	Service acct · domain-wide delegation	Ops
Slack	Hermes chat + #hv-alerts observability	↕ both	Bot token	Daniel
QuickBooks	Finance bots data	↓ in	OAuth	Finance
Make.com	Legacy automations	↕ both	API key	Farid

HV Hub v2 — AWS architecture (us-east-2) — Animated · interactive — the AWS topology behind these integrations: a VPC fronting three ECS Fargate services, with the Maestro Lambdas, SQS, DynamoDB, S3 and Bedrock as the serverless plane, all in us-east-2. Open full ↗

Airtable Bases

4 bases · the config/brain SSOT

These four are the config/brain bases the bots and Hub actually read and write. The Airtable PAT's scope is broader — it can reach many more HV workspaces (including archived and non-system bases) — but only these four are part of the live pipeline; the older PAT still used by some workflows sees only the original three.

SSOTappUDQ65M1lSnSM5pTask Table + Ai Hub · Workflows · Bots · Guardrails · Connected Resources · Queues

R3app6GEKoBtHW1iyu1Amazon R3 Program · Robin orchestration · robin_tasks

HubappBQNv9S5SlJ2nuWHappen Ventures Hub · CRM + ops: deals · orders · AR/AP · clients

GMCappGDkdfPiiZ2lwO2General Mission Control · orchestration

SSOT key tables

What lives in appUDQ65M1lSnSM5p

tbl38RfIpWTRJKyiQ

Workflows & Automations

16 playbooks. Fields: Task Name, Owner, Status, Enabled, Approval, Schedule, Bot Settings (link), Inputs (link). Editing here is the only legitimate way to enable/disable a playbook.

tblRiSakPTB4cVJSr

Agent Settings (22)

Per-bot config (a.k.a. Bot Settings). Fields: system_prompt, voice, guardrails, never_do, escalation_logic, model. The sales draft bot is Gabrielle Sales (rec K11x… — formerly Sales_Assistant / ClawBot); the Maestro consumer reads this record to draft.

tblmjEywNRz7Hv2w5

Guardrails (71)

applies_to="All bots" — global, not per-playbook. Categories: Inbox Rules, Content, Human Required, Communication Limits, Data Hygiene. Priorities 1 (Critical) → 5 (Catch-all).

tblOenbL6Iq2WZo4C

Connected Resources

Two heavy-link records: recXbj3ykSg5Tqw9v Suppression_List (DNC · 9 outreach playbooks · ~17 SSOT links) and recPk47mTFYk78BWG Company Employee Database (rep inbox/Slack · 16 SSOT links).

DynamoDB · hv-hub-v2-development-tasks

Approval queue (post-cutover)

Since the cutover the sales queue lives in this AWS single-table (us-east-2), not Airtable's task_queue_sales. n8n crons POST /generate → SQS → task_consumer Lambda → DynamoDB. Reviewers act in Hub v2 (Approve&Send, Edit, Reject, Snooze, Comment, Escalate); approved rows are delivered by the Unified Sender (SQS outbound-messages → message-dispatcher Lambda → per-channel adapter: Gmail / Slack / WhatsApp).

robin_tasks → DynamoDB

Operational tasks

Internal work driven by Robin (R3 ops bot) from inbound emails, forms, Slack. Migrated to the same DynamoDB single-table (source='robin', cut over 2026-06-12); the Hub reads/acts on DynamoDB. Frank is the separate finance bot.