Skip to content

Developer section: these pages cover the S6S workflow engine for self-hosted installs and developers. On s6s.ai, API keys and MCP access are issued by S6S on request (contact us); on a self-hosted install, an admin creates them on the API Keys page. For the AI Visibility product, start at the AI Visibility docs.

Self-hosted engine changelog

Early release notes for the self-hosted workflow engine, from February 2026, for developers who run it themselves. They don't describe AI Visibility. For what S6S does for agencies today, see AI Visibility and the private beta.

v0.6.0February 24, 2026
NewGitHub OAuth sign-in alongside Google OAuth
v0.5.0February 23, 2026
NewOne-click credential connection page for OAuth and API key providers
NewWebhook trigger URL exposed in deploy response (webhookTrigger.invokeUrl)
NewExpression engine supports trigger.output.* and step_ref.output.* natively
NewRecipe compiler rewrites step ref expressions to UUID-based format
NewExact timestamps (hours:minutes:seconds) on run details and graph views
Fixaction.code executor now handles multi-statement JavaScript (const, let, return)
FixWebhook-triggered runs now associated with workflow owner's userId
FixWebhook handler stores body (not payload), plus headers and query params
FixWebhook workflows no longer auto-run on deploy
ImprovedGoogle OAuth token auto-refresh before workflow execution
ImprovedCredential resolution fallback by provider name when ref isn't a UUID
v0.4.0February 18, 2026
NewLearn and save integrations on demand — dynamic provider.action syntax
NewDisconnect button for credentials (replaces hover-only delete)
NewMCP server for AI agent integration (@s6s/mcp-server)
NewREST API v1 for workflow deployment and management
InfraDeployed workflows keep running on their schedule without anyone starting them
InfraAES-256-GCM credential encryption at rest