Syntic Community
Where Syntic builders, developers, and operators gather.
Ask questions. Share what you're building. Debug alongside people who've already hit the same wall. The Syntic community is open to everyone — solo developers experimenting with the API, operators running AI Employees in production, engineers using the CLI, and enterprise teams scaling across whole departments. Whatever you're building on Syntic, there are people here who are building alongside you.
Where to plug in
Four places the community lives
Pick the one that fits what you need right now.
Discord
The fastest way to get an answer and the best place to show what you're shipping. Live channels for technical help, product feedback, Skills sharing, and casual conversation with the Syntic team and other builders. Syntic engineers and researchers are active — not just community managers. When something ships, we announce it here first.
Channels include: #help, #showcase, #skills-library, #api-developers, #cli-users, #workforce-operators, #feedback, and #off-topic.
Join the Discord →GitHub
The Syntic open source home. SDKs in TypeScript, Python, and Go. Sample Skills you can fork and adapt. Reference implementations for common API patterns. Integration examples for the tools people actually use. We welcome PRs, issues, and contributions from the community — and we review and respond, not just accept and ignore.
Browse on GitHub →Documentation
The full Syntic reference at docs.syntic.ai. API reference, CLI documentation, Skills authoring guide, Workforce platform docs, getting-started guides, and best practices. Updated continuously — when the product changes, the docs change with it, not six weeks later. If something in the docs is wrong or missing, open an issue on GitHub and we'll fix it.
Read the docs →GitHub Discussions
For the questions that need more than a Discord thread. Long-form technical questions, architecture discussions, RFCs, and feature requests. The place to propose something substantive and have a real conversation about it with the team and other community members. We track feature requests here and reference them when we're scoping what to build next.
Browse Discussions →Community guidelines
How we run this community
The Syntic community is useful because it's substantive and respectful. A few things that keep it that way:
Share what you're actually building. The most valuable posts are specific — here's the workflow I built, here's where I got stuck, here's what I learned. Generic questions get generic answers.
When you ask for help, include context. What you're trying to do, what you've already tried, and what happened. The people who answer are volunteers giving their time.
Syntic team members are here to help, not to be held to SLAs. For production support, use the support channels in your account dashboard. Discord and GitHub Discussions are community spaces, not a support queue.
Be direct and be kind. Critique ideas, not people. If you disagree, explain why. If something is broken, say what's broken. Vague complaints don't help anyone.
Showcase
What the community builds
A few things community members have shared recently — Skills, integrations, and workflows built on top of Syntic.
This section updates as the community ships. The best place to see what's new is #showcase on Discord.
- A Skill for turning a sales call transcript into a structured CRM update — shared by a community member running a 12-person sales team.
- A CLI script that runs a security audit on every PR and posts findings as GitHub comments — submitted as a reference implementation on GitHub.
- A Forge-built AI Employee for managing grant submission deadlines across 40+ funders — built by an NGO using Syntic Workforce.
- A Python wrapper around the Syntic API for batch document processing — open sourced and accepting contributions.
Recognition
Community recognition
The people who contribute the most — answering questions, sharing Skills, submitting PRs, writing guides — get recognized. Top contributors get early access to new features, invitations to Syntic team calls, credit in our changelog when their contributions ship, and occasional swag.
There's no formal program. We just notice who shows up and say thank you in ways that matter.
The fastest way to get good at Syntic is to build alongside people who already are.
Ask the question you've been sitting on. Share the workflow that's saving your team hours. Show the thing you built. The community is most useful when people actually participate — not just read.