Process incoming documents
Ingest a file, extract required information, validate it, and request anything that is missing.
Move files and documents through extraction, validation, transformation, and review workflows. Explore example AgentRuntime patterns for Google Slides, then confirm connector availability and supported actions before production use.
Use content systems as sources and destinations while AgentRuntime coordinates the decisions and people around each asset.
Example architecture only. Exact triggers, actions, scopes, and deployment requirements depend on the connector configuration.
These are representative patterns for the Content & Filescategory. They are not claims about currently enabled Google Slides actions.
Ingest a file, extract required information, validate it, and request anything that is missing.
Draft or transform content, apply policy checks, and route it through the required review path.
Move approved assets and metadata to the correct destination with a traceable execution history.
Catalog coverage changes. Validate the actual connector build, authentication method, supported operations, and environment requirements with the AgentRuntime team.
Bring the trigger, actions, access constraints, and human decision points. We will map the governed execution path.