Bring your tools into your community
Eight webhook sources, slash commands, and a cross-repo agent fabric so the conversation stays where the work happens.
Webhook sources
Subscribe any channel to any source. Every secret is AES-256-GCM encrypted at rest. Per-source admin UI lets you pick which events land where.
GitHub
PRs, issues, deployments, and CI status post into a channel as bot messages. HMAC-verified per subscription.
Vercel
Deployment lifecycle events (succeeded / failed / canceled) routed to the channel that owns the project.
Stripe
Receipts, payment failures, subscription changes — into a workspace channel for the finance team.
Zapier
Bidirectional. Inbound Zaps post to a channel; outbound triggers fire when a channel event matches.
Forge Error
Production errors from the BlueForge error-tracking pipeline land in your incident-response channel.
Forge Hosting
Hosting events (build, deploy, scale, alarm) routed to the channel that owns the workload.
Office Platform
Document and meeting events from BlueForge Office. Meeting transcripts post as agent cards with playback.
TaskMaster
Task creation, assignment, and completion events. Pairs with the /task slash command for the round trip.
Slash commands
Type a command in any channel. The server-side parser routes it to the right service and posts the bot reply back into the conversation. Your message stays in context.
/task <title>creates a TaskMaster task; reply links back so anyone can track it./task project=<id> <title>pins the task to a specific project.
More commands ship as the BlueForge stack grows.
Round-trip — not just inbound
Subscribe a channel to listen, then configure outbound dispatch so channel events fire back to Slack, Discord, or a GitHub repo. Bidirectional Zapier means a single channel can be both source and destination.
Inbound
External services post events to /api/webhooks/<source>. Verified, rate-limited, routed to subscribed channels.
Outbound
Each subscription has an optional outbound config (Slack webhook URL, Discord webhook, or GitHub repo + token). Channel events forward there with the same payload shape.
Encrypted at rest
Every secret in inbound or outbound config is AES-256-GCM encrypted with a master key on disk. A rotation script re-encrypts the entire table without downtime.
Service-account auth for cross-repo work
Mint long-lived API keys at /settings/service-keys. SHA-256-hashed at rest, plaintext shown once. The same key authenticates calls from Office Platform, TaskMaster, and your own integrations into SocialSphere routes.
Backed by a unified users table that mirrors identity across the BlueForge stack — sign in once, your account is the same account everywhere it appears.
Wire it up in minutes
Pick a channel, pick a source, paste a webhook URL. The admin UI walks you through it.