Cloud Function
If you want the fastest way to use a published OOMOL function, start with the CLI guide. If you need to call Cloud Function programmatically, use the docs in API & SDK. The current execution endpoints and SDK packages still use the name Cloud Task v3, which is the current integration layer behind Cloud Function.
OOMOL Cloud Function is a serverless computing platform that allows you to deploy your OOMOL workflows as production-ready APIs without managing infrastructure. Focus on writing code, and let OOMOL handle the rest.
Overview
OOMOL Cloud Function turns your workflow blocks into scalable cloud services with one click. You build the function logic, and OOMOL handles deployment, scaling, and operations.
Key Benefits
- Fast deployment: Deploy your workflows without complex setup
- Pay-as-you-go: Only pay for actual usage, no upfront server costs
- Zero Maintenance: No need to manage servers, environments, or scaling
- Auto-scaling: Automatically handles traffic spikes and scaling
Four Ways to Deliver And Consume the Same Capability
Once your logic is packaged and deployed, the same capability can be distributed and consumed in several ways.
Package publishing is the distribution layer. CLI, API, and MCP are the main consumption layers.
1. Publish as a Package
Share your blocks with the community, or reuse them inside more complex workflows.
Use Cases:
- Share reusable components with other developers
- Build modular functionality that others can extend
- Create building blocks for community innovation
How it Works:
- Package your blocks with clear inputs and outputs
- Publish to the OOMOL community package library
- Others can discover and use your blocks in their workflows
2. Consume with CLI
Use oo-cli to search packages, inspect package metadata, run cloud functions, and fetch results directly from the terminal.
Use Cases:
- Use OOMOL functions from Codex or Claude Code
- Let individual users run cloud functions without building an app
- Validate packages and workflows before investing in API integration
Why It Matters:
- Usually simpler than integrating APIs directly
- Usually lower setup cost than running an MCP server
- Works well for both AI-assisted development and direct terminal usage
See the CLI guide for the recommended workflow.
3. Integrate through API & SDK
Call the deployed capability from your own application, backend, scripts, or automation code.
Use Cases:
- Create product integrations with your own frontend or backend
- Trigger tasks from scripts, services, or scheduled jobs
- Build custom workflows around polling, uploads, and result handling
Features:
- TypeScript and Python SDKs
- Direct HTTP access for debugging and minimal environments
- Full control over task creation, polling, and uploads
For the current API shape and SDK naming, see Cloud Function API Overview.
4. Expose as MCP for AI
Publish your functions via Model Context Protocol (MCP) for AI agents to use.
Use Cases:
- Let AI assistants call your functions directly
- Create tools that AI agents can discover and use
- Make your code available to AI-driven tools and workflows
How it Works:
- Your function is exposed via MCP protocol
- AI agents can discover and call your function
- Seamless integration with AI assistants that support MCP
Pricing
OOMOL Cloud Function uses a simple pay-per-use pricing model:
- No fixed costs: No monthly server fees or upfront payments
- Usage-based billing: Pay only for actual function invocations
- Transparent pricing: Clear pricing per API call
- Free tier available: Get started with generous free usage limits
Visit OOMOL Console for detailed pricing information.
Getting Started
Prerequisites
- An OOMOL account
- OOMOL Studio installed on your computer
- A workflow ready to deploy
Deployment Steps
-
Create Your Workflow
- Build your workflow in OOMOL Studio
- Test it locally to ensure it works correctly
- Define clear input and output parameters
-
Configure Deployment
- Open the deployment panel in OOMOL Studio
- Select "Cloud Function" as deployment target
- Configure function settings (timeout, memory, etc.)
-
Deploy
- Click "Deploy to Cloud"
- Wait for deployment to complete
- Get your function's invocation details
-
Test Your Function
- Use the provided endpoint or SDK to test your function
- Monitor usage and performance in OOMOL Console
- Share the API with your users
Example Deployment
After deployment, most users should start with the CLI guide. Cloud Function currently uses the Cloud Task v3 integration layer for direct API access. For a working request example, see HTTP API With curl.
Management
OOMOL Console
Access OOMOL Console to:
- View all your deployed functions
- Monitor usage and performance metrics
- Manage API keys and access control
- Check billing and usage statistics
- Update function configurations
- View logs and debugging information
Monitoring
- Real-time metrics: Track invocations, latency, and errors
- Usage analytics: Understand how your functions are being used
- Error tracking: Quickly identify and fix issues
- Performance insights: Optimize function execution time
Best Practices
Function Design
- Keep functions focused: Each function should do one thing well
- Define clear interfaces: Document input and output parameters
- Handle errors gracefully: Return meaningful error messages
- Optimize for cold starts: Minimize initialization time
Security
- Use API keys: Protect your functions with authentication
- Validate inputs: Always validate and sanitize user inputs
- Set rate limits: Prevent abuse with appropriate rate limiting
- Monitor usage: Watch for unusual patterns or potential attacks
Performance
- Optimize dependencies: Only include necessary libraries
- Cache when possible: Reduce redundant computations
- Use appropriate timeouts: Set realistic execution time limits
- Test at scale: Verify performance under expected load
Comparison with Traditional Deployment
| Feature | Traditional Server | OOMOL Cloud Function |
|---|---|---|
| Setup Time | Hours to days | Minutes |
| Server Management | Required | None |
| Scaling | Manual | Automatic |
| Costs | Fixed monthly fees | Pay per use |
| Maintenance | Ongoing | Handled by OOMOL |
| SSL/HTTPS | Manual setup | Built-in |
| Deployment | Complex | One-click |
Use Cases
API Services
Build RESTful APIs for mobile apps, web applications, or third-party integrations.
Data Processing
Process files, transform data, or perform batch operations on-demand.
Integrations
Connect different services and automate workflows between them.
AI Tools
Create specialized tools that AI assistants can call to extend their capabilities.
Webhooks
Respond to events from external services like GitHub, Stripe, or Slack.
Support
If you encounter any issues:
- Check the Documentation Center
- Visit OOMOL Console
- Submit issues on GitHub
- Contact us through the support page