Twin treats Folk 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 Folk: 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, lead enrichment, sales prospecting. 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 folk's available connection methods don't always expose every workflow through structured API endpoints. Twin operates the browser interface directly, so actions like updating pipeline stages or writing notes work even when no API route exists for them.