What is your goal?
hi,
I developed a make.com scenario to combine AI generated post with Wordpress. In particular there’s a flow that generate content to pass to Wordpress for update an empy exixisting post. The issue is that, once the content is ‘pasted’ in Wordpress post, that block is a blue bordered block that is not editable. Everything is working fine except for the last module. Looking for a solution all around. It seems is a typical issue between make.com and Wordpress. But is so typical that I can’t find any solution yet. The text that appears in the post in the content block comes with the right format. but if i try to click inside there’s no way to edit. The block seems to be a self standing block without 3 pint to edit or similar. The content and its block can be edit with wordpress Code editor and not with visul editor. Also disabling Gutemberg by plugin, it let ro edit the post. This probably means that the issue is about how the Wordpress update post send the content to the site related to Gutemberg editor
What is the problem & what have you tried?
I tried with code in Wordpress function.php to better import teh conent, I tried by addin a text parser befor the last modulo to send the content to Wordpress. I try by adding to the Wordpress Post Update module field ‘conetent’
Screenshots (scenario flow, module settings, errors)
Does it happens the same if you use create a new post (as a draft for example)
The WordPress update is probably succeeding. Gutenberg is likely loading the result as one Classic or HTML block because the incoming post_content is plain HTML rather than serialized block markup.
Check the WordPress Code editor. If the generated content has tags such as <h2> and <p> but no <!-- wp:heading --> or <!-- wp:paragraph --> delimiters, that is the cause. WordPress uses those comment delimiters to reconstruct editable blocks: Markup representation of a block – Block Editor Handbook | Developer.WordPress.org.
In Make, have the AI return structured fields such as heading, paragraphs, and list items. Then build the Gutenberg markup deterministically before the Update a Post module. For example: <!-- wp:heading {"level":2} --><h2 class="wp-block-heading">Heading</h2><!-- /wp:heading --> followed by <!-- wp:paragraph --><p>Text</p><!-- /wp:paragraph -->. Test it on a draft first; if WordPress reports an invalid block, compare the saved class names and wrapper markup with a block created manually in that site.
The AI-generated content is likely being sent as raw HTML or serialized block markup that Gutenberg treats as a non-editable/custom block instead of standard editable blocks.
this sounds more like a Gutenberg block shape problem than a Make problem
I’d compare the raw content from one manual Gutenberg post with what the WordPress module sends. start with 2 paragraphs, then add a heading, list and link one at a time. when it turns into one blue bordered block, you’ve found the markup Gutenberg is treating as HTML instead of native blocks
once the draft is editable and approved, blotato can use the WordPress article URL as context and turn it into separate social drafts. I’d keep that as a second scenario though. fix the source post first, then repurpose it
