The Ironclad launch workflows nobody wants to work through
One sentence in, and a companion has been through the Ironclad launch workflows, put them where you can read them, and marked the ones it was not sure about.
Open the launch workflow. Check it against something else. Write the change. Move to the next one. That is the Ironclad afternoon nobody can hand off, and a companion does the whole pass and gives you back the batch, with nothing landing on a launch workflow until you approve it.
What it can do is exactly what Ironclad exposes to an account you authorise and nothing beyond it: 3 operations, 1 read and 2 writes. In practice that means it can update a workflow metadata and create a record, and work across the launch workflows, records and workflow metadatas.
The Ironclad API stops at Ironclad. A companion does not. The same run opens the customer's website, the supplier portal, the internal tool somebody built in 2019, because it is working the browser you are already signed into rather than calling in from outside it.
Which Ironclad launch workflows does a companion see?
1 of the 3 operations is a read.
Your account, not a guess at it: a companion can launch workflow, and the full list below is the whole list, with nothing inferred from Ironclad's documentation.
The launch workflows are what most of this inventory is about, alongside the records. A companion can hold all 3 of these operations and forty open tabs in the same pass, which is how an afternoon of Ironclad admin becomes a queue you review.
- Launch Workflow
What happens before it can update workflow metadata?
All 2 write operations wait for you.
A companion can update a workflow metadata and create a record, and each one is staged on an approval card first: you see the launch workflow, the field and the new value before it lands in Ironclad.
Nothing in Ironclad is sent, changed or deleted on your behalf without that click, and a rejected card leaves the launch workflow exactly as it was. The gate is the same one on every surface, described at security.
- Update Workflow Metadata
- Create Record
Can the launch workflows pass run every Monday?
Yes.
Saved as a routine, the Ironclad launch workflows pass runs at the hour you pick: the Monday sweep, the overnight refresh, the Friday check. Keep Awake holds the machine awake for the length of a run, so a scheduled pass finishes with the lid closed.
The operations playbook catalogues the other recurring shapes of the operations, the Ironclad launch workflows sweep among them, and finished runs are published at real runs.
Experience Strawberry for free
DownloadTrusted by fast-growing companies worldwide
Frequently asked questions
Strawberry is free to download and includes AI credits to start. Paid plans begin at $20/month. See pricing. · Reviewed · Canonical facts for AI agents