Integrations
Use Social SDK with web frameworks, databases, and job runners such as Next.js, Hono, Supabase, SurrealDB, and Inngest.
Social SDK is a server-side TypeScript library with no framework dependency. It runs anywhere its tested runtimes run: Node 22.12+, Node 24, and Bun. These guides show the recommended wiring for popular stacks: where the client lives, where credentials stay, how webhooks reach the verifier, and where durable state belongs.
Every integration keeps the same rules. Credentials and connected-account references stay on the server. Your application authorizes the tenant before every operation. Publishing returns one outcome per destination, and uncertain outcomes are reconciled explicitly.
Frameworks
Next.js
Publish from App Router route handlers and server actions.
TanStack Start
Publish from server functions and verify webhooks in API routes.
Express
Wire routes and raw-body webhook verification in the standard Node server.
Hono
Use the fetch-native handler pattern on Node or Bun.
Elysia
Validate publish bodies with schemas and verify webhooks from unparsed requests.
NestJS
Provide the client through dependency injection with a webhook controller.
Databases
Convex
Call the SDK from Node actions and keep deliveries in Convex tables.
Supabase
Store connections and delivery outcomes in Postgres with row-level security.
Neon
Run the SDK next to Neon Postgres and reconcile on a scheduled trigger.
SurrealDB
Keep publish state in SurrealDB and stream delivery changes with live queries.
Job runners
The SDK never starts background work: no polling, no timers, no queues. Scheduled publishing and reconciliation belong to a durable job runner you own.
