Twin treats Odoo as part of a larger workflow, not as an isolated connector. An agent can read the relevant records, combine them with context from other tools, decide what needs to happen next, and report the finished work back to the team.
The page below shows the practical automation patterns for Odoo: what the agent can monitor, which actions it can take, and how the workflow stays observable when it runs on a schedule.
Common starting points include crm automation, sales prospecting, lead enrichment. Each example is designed to become a reusable agent, so teams can start from a narrow job and expand it as the process matures.
Twin is most useful when odoo's API covers many workflows, but some data lives only in browser-facing pages. Twin can use the structured API where available and fall back to driving the browser interface when it isn't—so you're not blocked by what the API exposes.