Run your first task
Follow Conversation analytics from an approved function and conversation batch to verified counts and a separately authorized report update.
This walkthrough follows Conversation analytics: the Analytics agent requests conversation-categories for batch-042, and the Analytics integration receives permitted category counts. The input owner, agent and receiving integration can belong to one organization while holding distinct responsibilities.
The figures and operation sequence are illustrative. The downloadable classifier is JavaScript reference logic, not a deployed Wasm function or a complete install-and-run project. The steps below describe the setup to agree before using your own accepted workload; they do not imply that conversation-categories is already installed in your account.
Agree the function and setup
Request access and complete the assisted setup checklist. Agree the supported execution route, input format, limits, recipient and verification references. An installed owner host, a hosted requesting agent and an authorized recipient have different responsibilities.
Current hosted limit: connecting and approving a hosted request does not establish that it can execute. When admission is approved but Control has reported no progress, the hosted status route returns hosted_continuation_unavailable; the continuation transport is not available on that path. Repeated polling does not start it. Confirm the supported execution path during setup. See Connection and execution availability.
1. Create the Space
The sponsoring organization creates the reusable Space and pays for the execution it sponsors. Define the input owner, Analytics agent and Analytics integration. Sponsoring or signing in grants no execution or release permission. See Accounts, Spaces and billing.
2. Deploy the function and its profile
Use the conversation classifier reference to define category rules, the input format and duplicate-ID rejection. Adapt that logic to the supported Wasm interface and prepare a complete project, operation profile and fixture suite. Test the exact artifact before publication. Any model used by the classifier must run inside the protected runtime.
The permitted output contract includes category counts and redacted failure reports. A duplicate conversation ID produces a failure report with no counts. The profile also names the input slots, recipient and execution limits; it does not authorize use of the input.
Write a protected function explains the interface and real build/test/deploy commands using a separate sales-calculation example. Those example files and binary formats are not the conversation classifier. During setup, supply the corresponding classifier project, profile and fixtures before using the commands for .