Twin treats Superproxy 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 Superproxy: 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 ecommerce monitoring, competitive research, spreadsheet operations. 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 a recurring pain with Superproxy workflows is that scraped data sits in one place while the team works in another. Twin writes results directly to Sheets, CRMs, or other destinations as part of the same agent run, removing the manual transfer step.