Important Disclaimers

Service Disclaimer

We're building something awesome, but let's be real about what our service can and can't do. Here's the honest truth about limitations and responsibilities.

Last updated: August 2025
Honest & transparent

The Reality Check

Best Effort

We aim for perfection but can't guarantee it

Your Environment

Deployment success depends on your setup

Use at Risk

Always backup before deployment

Community Driven

Built by humans, for humans

1

Service Availability & Performance

We work hard to keep our deployment service running smoothly, but let's be honest about what "best effort" means in the real world.

What We Strive For:

  • • High service uptime and availability
  • • Fast, reliable deployments (usually 5 minutes)
  • • Consistent service quality
  • • Rapid response to issues

Reality Check:

  • • Deployments may fail due to external factors
  • • Service may be unavailable during maintenance
  • • Network issues can cause timeouts
  • • Your infrastructure configuration affects success rates
2

Your Infrastructure, Your Responsibility

We deploy to YOUR NocoDB and n8n instances. That means the health, configuration, and compatibility of your environment directly affects deployment success.

For Best Results:

  • • Use supported NocoDB versions
  • • Ensure n8n has sufficient resources
  • • Test credentials before deployment
  • • Backup existing configurations

Common Issues:

  • • Insufficient database permissions
  • • Network connectivity problems
  • • Resource constraints (CPU/memory)
  • • Version compatibility mismatches

Bottom line: We can't fix problems with your underlying infrastructure, but we'll do our best to guide you through troubleshooting.

3

Deployment Outcomes & Warranties

We test our deployment process extensively, but every environment is unique. Here's what you should expect (and what you shouldn't).

"As-Is" Service Provision

What We Provide:
  • • Tested workflow configurations
  • • Community-validated templates
  • • Automated deployment process
  • • Basic deployment verification
What We Don't Guarantee:
  • • 100% success rate in all environments
  • • Compatibility with custom modifications
  • • Ongoing maintenance or support
  • • Data recovery if something goes wrong
4

Third-Party Dependencies

The ECHO workflow system integrates with various third-party services and platforms. Changes to these external services can affect functionality.

External Dependencies:

  • • NocoDB platform (your instance)
  • • n8n workflow automation (your instance)
  • • AI service providers (OpenAI, Claude, etc.)
  • • Webhook endpoints and integrations
  • • Third-party APIs and services

Important: We can't control or be responsible for changes, outages, or policy updates from these external providers.

5

Security & Data Safety

While we take security seriously and follow best practices, deploying any system involves inherent risks that you should understand.

Critical Security Reminders:

  • Backup first: Always backup your existing data before deployment
  • Test environment: Deploy to test instances when possible
  • Review permissions: Ensure deployment credentials have appropriate access
  • Monitor afterwards: Check that deployed systems work as expected
  • Secure your instances: We deploy workflows, but ongoing security is your responsibility
6

Community & Support Expectations

This is a community-driven service. Our support model reflects that collaborative spirit, with some important limitations.

What We Provide:

  • • Community forum support
  • • Deployment troubleshooting
  • • Template updates and improvements
  • • General guidance and documentation

What We Don't Provide:

  • • 24/7 emergency support
  • • Custom deployment modifications
  • • Infrastructure troubleshooting
  • • Ongoing maintenance services
7

Changes & Updates

The ECHO workflow system evolves based on community feedback and improvements. This means occasional changes that might affect existing deployments.

How We Handle Updates:

  • Community input: Major changes discussed in community channels
  • Backward compatibility: We try to maintain compatibility when possible
  • Migration guides: Documentation provided for breaking changes
  • Version control: Multiple workflow versions available when needed
8

The Bottom Line

We're building this service because we believe automation should be accessible to everyone in the WotAI community. We're committed to making it as reliable and useful as possible.

Our Commitment

We will:

  • • Keep improving the service
  • • Listen to community feedback
  • • Be transparent about limitations
  • • Provide honest, helpful support

We ask that you:

  • • Understand the inherent risks
  • • Test in safe environments first
  • • Share feedback to help us improve
  • • Be patient as we grow together

This disclaimer is effective as of January 2025 and applies to all uses of the WotAI ECHO deployment service.

Built with care, served with honesty

Understood the Fine Print?

Great! You're informed about what to expect. Ready to deploy your ECHO workflow with realistic expectations?