Introducing Reconn2: procurement intelligence in one workspace

If you sell into construction or public procurement in Canada, you already juggle member portals: ConstructConnect (LeadManager), ARHCA, and more. Each has its own login, export format, and change cadence — and none of them is your CRM.

Reconn2 closes that gap.

What Reconn2 does

Reconn2 is a multi-tenant operator workspace. Trigger.dev runs schedules (and manual test runs) that POST to protected FastAPI automation routes. Python connectors hold credentials, perform extraction or health checks, upload one JSON blob per run to the private raw-artifacts bucket in Supabase Storage, and record public.source_runs rows with status and storage keys.

Structured rows project into public.graph_entities (companies, contacts, projects, opportunities) with entity_claims so you always know which source asserted what. The web app gives you:

• Automations — run or inspect ConstructConnect and ARHCA jobs; download raw artifacts when present.
• Entity browser & graph — filter, inspect, promote rows into active CRM lists.
• Enrichment — Apollo → Tavily → Bright Data chain, per row or in bulk.
• Pipeline — Kanban deal flow on top of the same Postgres data.
• API tokens & MCP — attach Cursor or Claude Desktop to list CRM entities and project intelligence without copying exports.

Why this shape

Secrets never leave the Python runtime on Render. Trigger.dev only stores the API base URL and an automation shared secret — not ConstructConnect passwords or OpenAI keys.

Raw artifacts plus source_runs give you an audit trail when extraction drifts or a portal changes. The graph layer keeps “what we believe” separate from “what the portal said” via claims.

What is next

More connectors reuse the same automation contract: fetch_raw → Storage → graph projection. If a portal matters to your team and is not on the list yet, we want to hear it.

Start your free trial and run a dry automation from the workspace.