Twin treats Globo 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 Globo: 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 competitive research, lead enrichment, content repurposing. 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 globo does not expose a structured API for its editorial content. Twin operates the browser directly, reading pages the same way a person would—so agents can extract search results, article links, dates, and summaries without requiring any API key.