Build & integrate

For teams building on top of Synap or connecting Synap to external systems.

How this space is organized

• Build — change or extend Synap backend capabilities safely
• Integrate — connect agents, websites, and automation systems to an existing pod
• Reference — exact contracts and catalogs when you already know what to call

Use this order: Build first, then Integrate.

Build

Start here if you are adding capabilities to Synap itself.

• Build on the backend — architecture-first backend extension path
• Development — setup, type packages, testing, SDK, and extension patterns

Core architecture before coding:

• Data pod
• Event flow
• Validation policy
• Hub Protocol flow

Integrate

Start here if Synap is already running and you want to connect systems to it.

• Integrate core — Hub Protocol model and event-driven integration basics
• Agents — Synap AI, OpenClaw, channels, MCP, and skills
• Websites — frontend/app integration patterns
• External sources — webhooks, automation systems, and sync/import pipelines

Integration playbooks are split into the relevant section pages (Agents, Websites, External sources) instead of a separate redundant integrations bucket.

Reference

When you need exact interfaces and payload contracts:

• API reference
• Events API
• Event catalog