task ▸ template opened 0
Login-gated automation

Update a payment card on file

Sign in to a billing portal on your own account and replace the saved payment method, confirming the change.

Install this template See the steps
5 steps 20-50s ✓ Safety rails on
Writ runs on your own accounts, with your own credentials and data, on sites you are authorized to use.
guard ▸ rails set 01
01
safety

This template can take an action with consequences.

Safety rails on Action templates lead with guardrails. Before anything happens, every guard below is in force: a dry-run preview, a confirm-gate, a rate limit, an audit log, and idempotency so a retry never double-acts.

  • ✓Confirm-gate before saving
  • ✓Card details supplied as an encrypted secret, never logged
  • ✓Dry-run
does ▸ outcome shaped 02
02
what it does

The outcome

Sign in to a billing portal on your own account and replace the saved payment method, confirming the change.

Backed by a real, installable recipe, not a generated stub. Install it, attach your own inputs, and run it on your own accounts.

Expected output

A successful run returns a structured result:

output.json
json 
{ "updated": true, "last4": "....", "is_default": true }
steps ▸ recipe mapped 03
03
the steps

5 steps

Real step types from the 30+ in the workflow vocabulary. Edit any of them after you install.

  1. 1
    navigate

    Open the billing or payment-methods page.

  2. 2
    twofa

    Sign in with a Persona, including any 2FA.

  3. 3
    fill

    Enter the new card details from a secret you provide.

  4. 4
    click

    Save the new payment method and remove the old one if requested.

  5. 5
    extract

    Read the payment method back to confirm the new card is now the default.

inputs ▸ shape defined 04
04
what you provide

Inputs

  • billing_urlurl must match ^https?://
Resources you attach
Persona (your account)Secret (new card details, stored encrypted)

Input shape

Inputs are validated against per-slot regex rules before a run starts.

inputs.json
json 
{
  "billing_url": "<url>"  // matches ^https?://
}

Estimated runtime: 20-50s.

run ▸ template installed 05

Install in one click

Open the template in the app, attach your own inputs and resources, and run it on your machine or the cloud.

Install this template Browse all templates

Local runs have no compute charge and do not use Writ cloud compute. Paid plans are for cloud execution, faster monitors, teams, managed AI, and fleet features.

sites ▸ works here 06
06
works on

Point it at a site

This recipe adapts to any of these, all on your own authorized accounts.

Automate Salesforce open a record, update a field, run a report, turned into a callable workflow. · Also: extract · monitor Salesforce Automate Notion open a page, read a database view, create a row, turned into a callable workflow. · Also: extract · monitor Notion
faq ▸ questions answered 08
08
faq

Update a payment card on file questions

What does the Update a payment card on file template do?
Sign in to a billing portal on your own account and replace the saved payment method, confirming the change.
Where does it run?
On your own machine free of compute charges with the local agent, or on metered cloud running time. Either way it runs on your own authorized accounts and data.
Does it spend money automatically?
No spend happens without the safety rails: Confirm-gate before saving, Card details supplied as an encrypted secret, never logged, Dry-run. You stay in control with a confirm-gate and a rate limit.
more ▸ templates nearby 09
09
more templates

Related templates

Login-gated automation Cancel a subscription ▸ Sign in to a service on your own account and complete its cancellation flow, capturing the confirmation. · 5 steps Login-gated automation Log in and export a report ▸ Sign in to a SaaS tool on your own account, run a report, and export the rows. · 5 steps

Browse all templates ▸

rec ▸ ready ●

Start with the Update a payment card on file template

Install it, attach your own inputs, and run it on your own account in minutes.

Get started