Content & Files connector

    Plan governed AI workflows around PDF.

    Move files and documents through extraction, validation, transformation, and review workflows. Explore example AgentRuntime patterns for PDF, then confirm connector availability and supported actions before production use.

    Discuss this integration →Back to integrations
    Catalogued connectorPDF
    Where it fits

    Move files and documents through extraction, validation, transformation, and review workflows.

    Use content systems as sources and destinations while AgentRuntime coordinates the decisions and people around each asset.

    Example execution path● Planned
    01
    PDFProvide a trigger, context, or destination.
    02
    AgentRuntimeCarry durable state through the complete run.
    03
    Agents + rulesReason, validate, branch, and select actions.
    04
    People + systemsApprove, intervene, and complete the process.

    Example architecture only. Exact triggers, actions, scopes, and deployment requirements depend on the connector configuration.

    Example patterns

    Start with a workflow outcome, not an isolated tool call.

    These are representative patterns for the Content & Filescategory. They are not claims about currently enabled PDF actions.

    01

    Process incoming documents

    Ingest a file, extract required information, validate it, and request anything that is missing.

    02

    Prepare governed content

    Draft or transform content, apply policy checks, and route it through the required review path.

    03

    Keep systems synchronized

    Move approved assets and metadata to the correct destination with a traceable execution history.

    Production readiness

    Confirm the boundary before the workflow acts.

    Catalog coverage changes. Validate the actual connector build, authentication method, supported operations, and environment requirements with the AgentRuntime team.

    1. 01Confirm supported file types and size limits
    2. 02Apply retention and sensitive-data policies
    3. 03Validate destination paths, permissions, and version behavior
    Related Content & Files connectors

    Define the PDF workflow boundary.

    Bring the trigger, actions, access constraints, and human decision points. We will map the governed execution path.

    Discuss the workflow →Browse integrations