Fill in a web form on a schedule
Replays a saved web task in a headless browser: opens the demo newspaper's members' sign-up form, fills in a name and an email, types the members' access code from the connection's secrets, picks a topic, ticks the consent box, submits, checks the thank-you message appeared and reads it back as the node's output. The form regenerates every id and class on each load, so the task finds its fields by label and role, never by id. The site is ours, served by the demo stack.
Connects to
- HTTP API
How you know it worked
Run the pipeline (not a trace: a trace never replays a web task, because a replay acts on the site). The node's output is { "task": "demo-newsletter-signup", "version": 1, "extracted": { "confirmation": "Thanks, Sam! sam@example.com is subscribed to Ferries." }, "healed": [] }. The run log lists each step and how it found its element, and names the access code as (secret access_code), never its value.
Try this templateUsed in: Logistics & distribution
Related templates
HTTP API → database table
Calls a public JSON API and loads the response into a table, column by column. The classic 'fetch it nightly and keep a copy' shape.
File in, cleansed, joined to a price list, exceptions emailedSupplier invoice against the contract price
A supplier's invoice arrives as a file, the way it actually does. It is written to SFTP, read back, cleansed — quantities and prices arrive from a…
Stop moving data by hand.
Start free with three projects, or talk to us about running it across your organisation.