This section outlines the process flow—from development and publication (by the Developer) to customization, deployment, and usage (by the User)—for a Worker that helps with Email Summarization Use Case.
Coding:
The developer creates the core logic of the Email Worker using any agentic framework. Autoppia’s standardized interfaces (e.g., Email Integration, LLM Integration) ensure the worker template is compliant and ready for publication.
Worker Configuration: Configuration expected by the worker is specified on the worker.yml file.
Publishing on Marketplace thorugh Autoppia Developers Studio.
2
User: Configuration & Deployment
Users browse the marketplace and select the Email Worker. They configure it by providing secure credentials (e.g., Gmail OAuth) and any other necessary parameters. To configure a worker user must have prepared all his integrations, llms etc on Autoppia Studio. Then, select the specific configuration that must be inyected into the worker. This conf must follow the desgin specified by developer on Worker Config yml file.
Deployment:
The system merges the worker template with the user’s configuration to create a customized instance that is deployed on Autoppia’s infrastructure in a privacy-preserving manner.
Designer Note:
Include a flow diagram or step-by-step widget that illustrates the user configuration and deployment process.
3
Anyone: Use Worker and deploy apps based on it
After deployment, the worker can be accessed through multiple channels:
The Autoppia SDK
Direct API calls
The chat interface on Autoppia Chat
Check this sections for more information on how to publish a Worker Template or how to deploy a Worker.