Automating FlowNexa’s Blog Workflow with n8n, AI, and Strapi 5

The webhook is the single entry point for external systems.

Data is cleaned before it reaches the prompt, which reduces formatting issues.

The workflow can start from a short brief or from a source URL.

One run produces the Vietnamese and English versions together.

The output is parsed and checked before the next step.

Technical and editorial quality gates run one after the other.

maxQualityRetries prevents endless regeneration.

dryRun lets the team test the output before touching the CMS.

contentOnly is useful when the team wants to inspect text first.

The image prompt is separated from the content prompt for better control.

coverQualityRequired forces the workflow to confirm the image before use.

maxCoverRetries limits how many times the image can be regenerated.

This reduces the risk of unwanted words or symbols in the image.

It helps avoid misleading brand elements or noisy details.

The image is uploaded only when QA returns an acceptable result.

cmsTargets lets the workflow sync to staging or production as needed.

cmsTargetModes ensures the post is not published directly.

Each environment uses its own credentials to reduce operational risk.

The system checks before creating a new record.

cmsAction helps pick the safer path.

The post lands in Strapi 5 as a draft for manual review.

Need to publish VI/EN blog content on a regular basis.

Need SEO consistency and review without adding too much manual work.

Want AI to speed up content while keeping quality under control.

From brief to prompt to CMS sync in one operational flow.

Connect staging, production, and draft states safely.

Add content and cover checks before editorial review.