The SpiffWorkflow execution engine is open source. The community shapes what it becomes — through code, conversations, bug reports, and real-world use cases shared with each other.
Real-time chat with the community. Channels for help, showcasing projects, and following development progress.
Browse the source, open issues, submit pull requests, and follow the roadmap. Everything is in the open.
Product updates, open source news, and company announcements from the SpiffWorks team.
You don't need to write code to make SpiffWorkflow better. Here's how the community builds together.
Found something that doesn't work? Open an issue on GitHub with a reproducible example and we'll investigate.
Built something useful? Post it in Discord. Real-world patterns are some of the most valuable contributions.
Spotted a gap or wrote a better explanation? Documentation PRs are always welcome and always needed.
Check the GitHub issues tagged "good first issue" for approachable starting points. The core team actively reviews PRs.
If you know the answer to a Discord question, share it. The best communities teach each other.
The best way to learn SpiffWorkflow is to use it on a real process. The community is here to help.