The Situation
Responder.live is a solid CRM for Hebrew-language newsletters. It has one meaningful weakness: no automation API worth building on. Every newsletter required manual UI work - log in, create a draft, select the list, set the send time, confirm. Repeating that for every issue, at scale, was friction that compounded.
The constraint was real: the platform wouldn't give us the API. So we stopped asking for one.
The Solution Structure
We built a Playwright-based browser automation layer that treats the Responder.live UI as the interface. A persistent browser profile means authentication happens once - after that, any script can open a session and operate the platform as if it were a logged-in user.
The pipeline works like this: the content system generates an HTML newsletter file. One script call drafts it into Responder, assigns the correct list, and either sends immediately or schedules for a target date and time. No manual steps. No re-login. No clicking through screens.
The scripts are modular - separate files for launch, individual steps, full send, and scheduling. Each can run independently or chain together. The browser profile persists across sessions so the automation stays live without maintenance.
The lesson: when a platform withholds API access, Playwright is the API.