Webflow

Your assistant can list your sites, then every page on the one you name, then the CMS collections and their fields. That gives you the real inventory rather than the one in your head: static pages, collection templates, and what each collection is supposed to hold. It changes nothing while it looks.

What you end up with. A written inventory of pages and CMS collections for the site, with slugs, publication state, and when each was last updated.

Start with it bringing you the information and you deciding.

Never without. An inventory read through the connection is Webflow's own record of pages and collections, not what a visitor is being served. Confirm anything you are about to change against the live URL, because a page can exist in the list and be unpublished.

Built on: List Webflow Sites / Get Webflow Site Information / List Pages / List Webflow Collections / Get Collection Details

Page metadata is readable one page at a time, including the SEO title, the description, and the Open Graph fields. The assistant can walk the page list and report the gaps, which is the audit people pay for and then never repeat. Ask it for the empty ones and it gives you only those.

What you end up with. A list of pages with a missing or duplicated SEO title, description, or Open Graph field, in the order you would want to fix them.

Start with it bringing you the information and you deciding.

Never without. Have it name the locale and branch it read. Webflow page metadata is per locale, so a page can look empty in the report while the field is filled in on the locale your visitors actually see.

Built on: List Pages / Get Page Metadata

Page metadata is writable as well as readable, so the assistant can draft the titles and descriptions from what the page says and then apply them. Metadata edits are staged the way any other change is, so nothing reaches visitors until the site is published.

What you end up with. Page titles, descriptions, and Open Graph fields filled in across the site, staged and waiting for you to look before publish.

Start with it doing the work and checking with you.

Never without. Keep the slug out of the instruction unless you mean it. The same update action edits the URL slug alongside the title, and changing a slug on a live page breaks the existing links to it.

Built on: List Pages / Get Page Metadata / Update Page Metadata / Update Page

The assistant can list the forms on a site and then read the submissions, filtered to one form when you want just the contact page. Because it reads the field values rather than a notification email, it can group the enquiries by what people asked for and tell you which ones look like real work.

What you end up with. A grouped summary of form submissions for a date range, with the individual entries underneath each group.

Start with it bringing you the information and you deciding.

Never without. Treat the submission list as personal data. It carries whatever your visitors typed, including names and email addresses, so decide where the summary is allowed to be stored before you ask for one.

Built on: List Forms / List Form Submissions

Orders are readable in a list filtered by status, and each one opens up into the customer, the items, the payment state, and the shipping details. Once you know which are outstanding, the assistant can set the fulfillment fields and add the internal note on each order it worked through. It can also check the SKU inventory behind the line items so you find out about a short before the customer does.

What you end up with. A list of unfulfilled orders with what each one contains, and the fulfillment fields set on the ones you named.

Start with it doing the work and checking with you.

Never without. Keep refunds out of this. Refund Order reverses the Stripe charge and moves the order to refunded, which is a payment action and not a fulfillment one, so it belongs in a separate instruction you give deliberately.

Built on: List Webflow Orders / Get Order Details / Get Item Inventory / Update Order

Collection items can be created one at a time or up to a hundred in a single request, and both routes accept a draft flag. The safe pattern is to have the assistant read the collection schema first so the field names line up, then create everything as drafts, then look at it in the Designer before anything goes live.

What you end up with. The batch of items sitting in the right collection as drafts, with the fields mapped to the collection's real schema.

Start with it doing the work and checking with you.

Never without. Create as drafts rather than live items. Webflow exposes a separate action that writes straight to the live database and bypasses staging, and Webflow's own note is that field validation is not available through the API, so a bad value lands unchecked.

Built on: List Webflow Collections / Get Collection Details / Create Webflow Collection Item / Bulk Create Collection Items / List Collection Items

Two different things can be published, and the difference matters. The assistant can publish named collection items, which makes just those items live, or publish the site, which pushes every staged change including design work someone else left waiting. Ask for the first unless you mean the second.

What you end up with. The specific items live on the site, or a full site publish you asked for by name, with the domains it published to stated back to you.

Start with it doing the work and checking with you.

Never without. Say which of the two you mean, and which domains. A site publish pushes all staged changes from everyone working in the project, not only the ones your assistant made, and it reaches the live domain immediately.

Built on: Publish Collection Items / Publish Webflow Site / List Live Collection Items / List Custom Domains

There are two different endings here. Unpublishing a live item pulls it off the site and returns it to draft, so the content survives. Deleting removes the item, and deleting a collection removes the collection and its schema with it. Webflow marks the delete routes as permanent, and there is no undo in the API.

What you end up with. The item off the live site and back in draft, or removed outright, with the collection and item IDs recorded before it happened.

Start with it doing the work and checking with you.

Never without. Choose unpublish first and approve the exact item IDs before any delete runs. Webflow's delete actions remove collection items permanently and cannot be undone, and deleting a collection field takes the data in that field with it.

Built on: Get Live Collection Item / List Collection Items / Unpublish Live Collection Item / Unpublish Live Collection Items / Delete Webflow Collection Item / Delete Multiple Collection Items