WordPress Post Publishing
Publish app content to a WordPress site with media, taxonomy, and post status intact.
What it adds
A publishing path that creates and updates WordPress posts from app records, including uploaded media and assigned taxonomy.
What your agent is told to do
5
What your agent is told to do
5-
1
Let an operator register the target site once and store the resolved host, then validate every outbound request against that stored host so a user-supplied address can never point the app at an internal network service.
-
2
Authenticate with a credential scoped to the narrowest role that can publish, hold it encrypted on the server, and never expose it to the browser or include it in a client-rendered configuration blob.
-
3
Upload media first, confirm each upload, and only then create the post that references it, carrying alt text and attribution across so the published article is not a page of broken image frames.
-
4
Keep a persistent link between the app record and the created post so subsequent saves update it, and support the site's draft, scheduled, and published states explicitly rather than always publishing immediately.
-
5
Sanitize the content against the markup the target site actually permits before sending. Do not assume the destination will clean it up — pushing raw user-authored markup into a publishing endpoint is how one app's input becomes another site's stored script.
Edge cases it handles
8
Edge cases it handles
8- Only hosts an administrator configured may be contacted. Accepting an arbitrary site URL turns this feature into a request-forgery tool pointed at whatever the app's network can reach.
- The credential must carry the least capability that works. A full administrative account stored for convenience means a leak of the app's database is a full takeover of the customer's site.
- Media uploads fail independently of the post. A post created with references to uploads that did not complete must be held back or repaired, not published with missing images.
- Slugs collide. Two records with the same title will fight over one slug, so decide whether the app disambiguates, updates the existing post, or refuses, and make the outcome visible.
- Scheduled posts depend on the destination's own time zone, not the app's. A time sent without an explicit zone will publish hours early or late.
- Content that survives the app's own editor may still be stripped or mangled by the destination's allowed markup. Sanitize to the target's rules and show the operator what was removed.
- Sites go down, plugins break the endpoint, and requests time out mid-write. Retry with backoff on transient failures, key the retry so a post created before the timeout is updated rather than duplicated, and tell the user plainly when the site is unreachable.
- Deleting or unpublishing in the app needs a defined effect on the live post, and the app must not assume it still has permission to make that change.
Definition of done
9
Definition of done
9- Outbound requests reach only administrator-configured hosts.
- Credentials are stored server-side, encrypted, and scoped below full administrative capability.
- Media is uploaded and confirmed before the referencing post is created, with alt text preserved.
- Draft, scheduled, and updated posts all work, and scheduling uses an explicit time zone.
- Slug collisions resolve by a stated rule instead of creating silent duplicates.
- Content is sanitized to the destination's allowed markup before transmission.
- An unreachable site produces a clear message and a bounded retry, never a duplicated post.
- 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.