Twin treats Perplexity 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 Perplexity: 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 sales prospecting with perplexity, lead enrichment via perplexity, competitive research with perplexity. 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 the most common friction with Perplexity is that search results stay in the browser. Users copy summaries into sheets or docs by hand, which means stale data and missed follow-ups. Twin moves results directly into Google Sheets, Docs, or Notion as part of the same agent run.