Post job completions, failures, and budget alerts to a Slack channel via incoming webhook.
Integrations
What we plan to connect the factory to. None of these fire on a real job today— some have implementation code (notify-Slack, notify-Teams, notify-Email, webhooks); the orchestrator just doesn’t call them yet. The rest are pure roadmap. Tell us which to wire next at [email protected].
Notifications
Same as Slack — webhook-based incident + completion notifications.
Webhook notifications for build events. Embed-rich format with cost + duration.
Transactional email for job completions, weekly digests, onboarding drip.
Source control
Push generated code as a PR to a target repo. Auto-commit per job with descriptive messages.
Merge request creation against any GitLab project. Same flow as GitHub.
Issue tracking
Triggered by Linear issue assignment to a magic user. Builds the described feature, attaches PR + screenshots to the issue.
Same as Linear — issue → factory job → attachment.
Automation
No-code automation. Trigger factory builds from any Zapier app. Output to any Zapier app.
Self-hostable workflow automation. Same trigger/action surface as Zapier.
Visual automation. Pre-built modules for orchestrate + job status.
Subscribe any HTTPS endpoint to job lifecycle events. HMAC-signed, retried on 5xx.
Storage
Auth
SAML 2.0 SSO. JIT user provisioning. Default attribute mappings shipped.
SAML SSO with Entra-specific role-claim mappings.
OIDC SSO for Workspace org. One-click sign-in.
Cross-tenant user + group provisioning per RFC 7644.
Don’t see your tool?
Every factory action is reachable via our public REST API + SSE. Build your own integration in any language.