Webflow CMS Publishing
Push app content into Webflow CMS collections and publish it to the right site.
What it adds
A one-way sync that creates and updates Webflow CMS items from app records and triggers site publishing.
What your agent is told to do
5
What your agent is told to do
5-
1
Let an administrator connect a site and choose the target collection, then store the resolved collection and field identifiers rather than their display names, because designers rename things and the sync must survive it.
-
2
Build an explicit mapping between app fields and collection fields, held in configuration the operator can see and change, and refuse to sync a record whose mapping references a field that no longer exists in the fetched schema.
-
3
Keep a persistent link between each app record and the item it created, so a second sync updates the existing item instead of creating a duplicate every time the record is saved.
-
4
Treat publishing as a separate step from writing. Write the item, confirm it, then request the site publish, and surface the publish outcome to the operator because a written item that was never published is invisible to visitors.
-
5
Do not send a field the app has no value for. Writing an empty string over a description a designer wrote in Webflow destroys work the app did not create and cannot restore.
Edge cases it handles
8
Edge cases it handles
8- Collection and field identifiers are the only stable reference. Matching by display name means the first rename in the designer silently redirects content into the wrong field or fails outright.
- Items exist in draft, archived, and published states, and the app must decide which state it writes and whether it is permitted to move an item out of a state a human deliberately set.
- Blank or missing app values must be skipped rather than written. A partial record in the app must not blank out designer-managed copy, images, or SEO fields on the live site.
- Collections have item ceilings and the API has request ceilings. Batch writes, back off on rate limit responses, and stop cleanly with a clear message when the plan's item limit is reached rather than retrying forever.
- A renamed collection, a changed schema, or a failed site publish must leave the app's link records intact and the sync paused with a readable error, not half-applied across a hundred records.
- Reference and multi-reference fields point at items in other collections. Those targets must be resolved and confirmed to exist before the referring item is written, or the write fails on the last field after everything else succeeded.
- The stored access credential expires or is revoked when someone disconnects the site. Detect the authentication failure specifically, mark the connection as needing reconnection, and stop retrying instead of hammering the endpoint.
- If a record is deleted in the app, decide and document whether the item is archived, unpublished, or left alone. Silently leaving orphans on a live site is a defensible choice only if it is a stated one.
Definition of done
9
Definition of done
9- Field mappings are stored against stable identifiers and survive renames in the designer.
- Each app record maps to exactly one CMS item, and repeat syncs update rather than duplicate.
- Empty app values never overwrite existing content in the destination.
- Draft, archived, and published states are handled explicitly rather than assumed.
- Rate limits and item ceilings produce backed-off retries and a clear operator-facing message.
- A revoked or expired connection surfaces as a reconnect prompt, not as repeated silent failures.
- Publishing is a distinct, reported step whose success or failure is visible in the app.
- The feature matches the existing design system.
- No existing functionality is broken.
Related features
Contentful Entry Sync
Contentful Entry Sync
Create and update Contentful entries against the connected space, environment, and locale.
What it does
A sync that writes app records into Contentful entries using the connected space's content model and locale configuration.
How it works
- 1 Have the operator select the space, the environment, and the default locale during connection, and store all three, because writing production content into a sandbox environment is an easy and expensive mistake.
- 2 Fetch the content model at connection time and again before each sync run, map app fields to entry fields by their stable identifiers, and validate the value type against the model before attempting the write.
- 3 Write every localized field under an explicit locale rather than relying on whatever the space treats as default, and state clearly which locales the app owns and which it leaves to editors.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/contentful-entry-sync
Typesense Index Sync
Typesense Index Sync
Keep a search index in step with your records so results stay current and correctly scoped.
What it does
A one-way sync from the app's records into a Typesense collection, with server-enforced tenant filtering and a rebuild path.
How it works
- 1 Identify every model users search today and declare the indexed shape explicitly: the fields people type into, the fields they filter and sort on, and nothing more. Treat a missing or newly added field as absent rather than letting the document fail validation.
- 2 Reuse the app's existing background-job system to push creates, updates, and deletes. Do not index inside the request cycle; a slow or unreachable search service must never make a save fail or hang.
- 3 Build the tenant, workspace, and permission filter on the server at query time and attach it to every search. Do not accept a filter, collection name, or scope value from a client-supplied parameter, because anything the browser can set the browser can change.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/typesense-index-sync
Algolia Index Sync
Algolia Index Sync
Keep the search index matching the database, including who is allowed to see what.
What it does
A sync pipeline that mirrors records into a search index with tenant-scoped filters and scheduled reconciliation.
How it works
- 1 Identify every record type that should be searchable and define one index document per record, keyed by an identifier that never changes for the life of that record.
- 2 Push changes through the app's existing background-job system on create, update, and delete, and make every write idempotent so a replayed job produces the same document rather than a duplicate.
- 3 Put tenant, workspace, and visibility values on each document as filter attributes, and have the server issue short-lived scoped search credentials that pin those filters. The browser must never choose its own filter.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/algolia-index-sync
How it works
-
1
Copy the link
Grab the Markdown instruction URL for this feature.
-
2
Give it to your AI
Paste it into Claude Code, Cursor, v0, Lovable — whatever you build with.
-
3
It inspects, then implements
Your agent reads your existing app first, then adds the feature to fit it.
Works with your stack
These instructions are written to adapt. They tell the agent to detect your framework, match your existing design system, and reuse what you already have — rather than assuming a particular stack.
Need it tighter than that? Customize the feature and tell it exactly what you're running.