Skip to main content

​
Getting Help

We’re here to support your success with Tydli. Here’s how to get help when you need it.

​
👋 About Tydli

Tydli is currently a side project run in my free time. I’m committed to helping users succeed, but please understand that response times may vary. I appreciate your patience and feedback as we grow! For the fastest help, join our Discord community where users help each other, and check the comprehensive guides below.

​
Self-Service Resources

Before reaching out for support, try these resources (usually the fastest way to solve issues):

​
Documentation

​
Learning Resources

​
Community Support

Join our Discord community for real-time help from other users and the Tydli team.

​
Why Discord is Great

  • Fast responses: Community members online 24/7
  • Learn from others: See how others solved similar problems
  • Share your work: Get feedback on your implementations
  • Network: Connect with other developers building with MCP
Join Discord Community →

​
Discord Etiquette

To get the best help:
  • ✅ Search previous messages for similar issues
  • ✅ Provide deployment ID and error logs
  • ✅ Describe what you’ve already tried
  • ✅ Share relevant parts of your OpenAPI spec
  • ✅ Be patient and respectful
  • ❌ Don’t DM admins directly (ask in public channels)
  • ❌ Don’t post the same question in multiple channels
  • ❌ Don’t share sensitive credentials or data

​
Direct Support

For account issues, bugs, or detailed technical questions, contact us directly.

​
When to Use Direct Support

  • Account problems: Billing, authentication, access issues
  • Bug reports: Something broken that affects functionality
  • Security concerns: Potential vulnerabilities or data issues
  • Feature requests: Suggestions for improvements
  • Complex technical issues: Problems that require deep investigation

​
Before Contacting Support

Please have ready:
  • Deployment ID: Found in your dashboard
  • Error logs: Copy from deployment details
  • What you tried: Steps you’ve already taken
  • Expected vs. actual: What should happen vs. what’s happening
  • OpenAPI spec: Relevant portions (remove sensitive data)
Contact Support Team

​
Expected Response Times

As a side project, response times vary:
  • Discord community: Usually minutes to hours
  • Direct support: 24-48 hours typically
  • Complex issues: May take up to a week
  • Weekends/holidays: Slower response
Critical bugs affecting multiple users are prioritized.

​
Reporting Bugs

If you’ve found a bug, here’s how to report it effectively:

​
Good Bug Report Includes

  1. Clear title: Describe the problem concisely
  2. Steps to reproduce: 
    1. Deploy API with this spec...
2. Configure authentication with...
3. Try to call endpoint X
4. See error Y
  3. Expected behavior: What should happen
  4. Actual behavior: What actually happened
  5. Environment details:
    • Tydli deployment URL
    • Claude Desktop version (if relevant)
    • Browser/OS (if UI bug)
  6. Error messages: Full text of errors
  7. Screenshots: If applicable

​
Where to Report

  • Security vulnerabilities: Email directly (not public Discord)
  • General bugs: Discord #bug-reports channel
  • Feature requests: Discord #feature-requests channel

​
Feature Requests

Have an idea to improve Tydli?

​
How to Submit

  1. Check existing requests: Someone may have already suggested it
  2. Describe the use case: Why would this be useful?
  3. Explain the benefit: How would this help users?
  4. Provide examples: Show how it would work

​
What Happens Next

Feature requests are reviewed based on:
  • Number of users who would benefit
  • Complexity of implementation
  • Alignment with Tydli’s goals
  • Available development time
Popular requests may be prioritized or opened for community contribution.

​
Contributing

Want to help make Tydli better?

​
Ways to Contribute

  • Documentation: Improve guides, add examples
  • Community support: Help others in Discord
  • Bug reports: Detailed reports help us fix issues faster
  • Feature ideas: Suggest improvements
  • Spread the word: Share Tydli with others

​
Documentation Contributions

Found a typo or want to improve docs?
  1. Docs are on GitHub (link in footer)
  2. Submit a pull request with improvements
  3. Get recognition in contributor list

​
Emergency Support

​
Critical Issues

If you have a production-down emergency:
  1. Try the Troubleshooting Guide first
  2. Check Common Issues for quick fixes
  3. Post in Discord #urgent-help with details
  4. Email support if absolutely critical
Note: As a side project, 24/7 emergency support isn’t guaranteed, but the community often helps quickly.

​
What Qualifies as an Emergency

  • ✅ Production deployment completely down
  • ✅ Security vulnerability discovered
  • ✅ Data loss or corruption
  • ✅ Account compromised
NOT emergencies:
  • ❌ Question about how to use a feature
  • ❌ Request for new functionality
  • ❌ Non-urgent configuration help

​
Support Best Practices

To get the best help:

​
Do

✅ Search first: Check docs and Discord history ✅ Be specific: Provide details, logs, and context ✅ Be patient: Remember this is a side project ✅ Be kind: Treat helpers with respect ✅ Give back: Help others once you’ve learned ✅ Share solutions: Post what worked for you

​
Don’t

❌ Don’t expect 24/7 support: Response times vary ❌ Don’t post credentials: Never share API keys or secrets ❌ Don’t cross-post: Ask in one place, wait for response ❌ Don’t demand: Polite requests get better responses ❌ Don’t assume: Provide context, don’t assume knowledge

​
Feedback

We love feedback! Tell us:
  • What’s working well
  • What’s confusing or frustrating
  • What features you need
  • How we can improve docs
  • Your success stories
Share feedback in:
  • Discord #feedback channel
  • Direct support email
  • Feature request form
Your feedback helps shape Tydli’s future!
Thank you for using Tydli! Together we’re building the future of AI-API integration. 🚀