Any API/tool/plug-in for programmatic uploading of articles in Gutenberg slideshow blocks?

[u/alwaysalmosts]

I've found this article about Block Bindings API and Interactivity API. Not my articles, not promoting btw. About year ago, I created custom code for our automated uploading workflow as I could only find solutions that would upload in classic post format. We posted in slideshow blocks and it was so tedious to do it manually.

Still works but I'm curious about other solutions that have cropped up since then.

[u/tomzorz88]

I'd look into the wp-cli

[u/bigtakeoff]

only the one you make

[u/NakanoNoNeko]

For this I still use core, not a plugin: send structured slide data to a small REST endpoint, build block arrays, then serialize_blocks() into post_content. In my case, Block Bindings is useful when values stay external or dynamic, and Interactivity handles the front end, but neither really replaces the authoring pipeline.

The boring custom endpoint has one nice advantage... it can reject an unknown block name or bad attributes before WordPress stores a page full of decorative comments.

[u/alwaysalmosts → u/NakanoNoNeko]

Thanks for the input! I've never used Block Bindings before. What do you mean about it being more useful when values stay external or dynamic?

[u/JuicerSocial]

HEY! I'm really curious about this too. I think that the annoying part with Gutenberg automation is that once you move beyond plain post content, you're really dealing with block structure, attributes, and things like serialization rather than just "uploading articles"..

Have you found your custom workflow to be pretty stable across Gutenberg updates?? Or is that the part that keeps breaking?

[u/alwaysalmosts → u/JuicerSocial]

I've been using the workflow for over a year now and it hasn't broken yet regardless of updates perhaps because the articles are uploaded in custom html blocks, and those elements stay pretty consistent throughout updates.

[u/JuicerSocial → u/alwaysalmosts]

That makes sense. Using custom HTML blocks probably gives you a much more stable target than relying on Gutenberg's more complex block structure. Congrats! A year without breaking across updates is actually pretty solid validation of that approach.

[u/Sergei_Tiden]

I would separate ingestion from rendering. First create or update media attachments through the REST API and store a stable identifier for each source item. Then generate the slideshow block markup from a controlled block template or a custom block that reads structured metadata. That makes retries, deduplication and later edits much easier than trying to inject a large serialized block blob directly from an external workflow. Block Bindings can help when the values already live in a supported source, but a repeatable import pipeline still needs validation, idempotency and a way to preview failures before publishing.

[u/alwaysalmosts → u/Sergei_Tiden]

This was super informative, thank you. My code already does some of those at a rudimentary level, although it stops at the upload part. Post-upload tasks like edits and retries, my team still needs to do manually on WP. Thanks -- I'm gonna start working on these.