Automate Blog Generation with Power Automate and AI Builder
Introduction
In today’s fast-paced digital landscape, producing consistent, high-quality content is a constant challenge. Power Automate and AI Builder team up to create a low-code, scalable pipeline that generates, formats and publishes blog posts automatically.
This approach frees your editorial team from repetitive tasks and ensures every post aligns with the brand and SEO strategy.
In this article, I will demonstrate the detailed steps to automate creating blog generation.
By the end, you’ll have a production-ready recipe for end-to-end blog automation that you can customize and scale.
Prerequisites
- You should have enough AI credits consumption capacity in the develop environment
- You should have power automate premium license to use office word connector
Solution
We will divide the solution into 2 parts. In part 1, we will create a prompt for generating the blogs content. We will use custom AI builder prompt with text parameters for the instructions part. In part 2, we will design a power automate flow to automate generating blog content.
PART 1 – Creating a custom prompt in AI Builder
We will use input parameters in the custom prompt to make more generic so that we can reuse it for generating blogs on multiple topics.
Enter the prompt name as “Generate Blog Prompt”. Enter the below prompt in the instruction section. The prompt not only return blog content but also returns SEO title and meta description for the blog:

You are an expert blogger and thought-leader in the field of technology.
1. Topic: [Topic]
2. Target Audience: [Audience]
3. Tone & Style: conversational, professional, energetic
4. Word Count: 250
5. Primary Keyword(s): [Primary Keywords]
6. Secondary Keywords: [Related Keywords]
Task:
- Craft an attention-grabbing title that includes the primary keyword.
- Write an engaging introduction that hooks the reader and previews the post.
- Organize content with clear H2/H3 headings.
- Under each heading, provide actionable insights, real-world examples, or data.
- Include at least one bullet or numbered list for readability.
- Conclude with key takeaways and a strong call-to-action.
- Suggest a meta description (≤155 characters) and an SEO title (≤60 characters).
Output in json format with blogcontent ,seotitle ,metadescription as properties:
- A complete blog post in Markdown.
- A suggested SEO title and meta description.
There are 4 text parameters that we will pass via power automate later:
- Topic
- Audience
- Keywords
- Related Keywords
Note: All 4 input parameters are enclosed in [] to differentiate those with the instructions text. Don’t use [] instead those are the placeholders where parameters need to be added in the instruction.
Next, change the output to “JSON”:

Provide sample text value to all 4 input parameters and click test. After testing, click “Save” to save the prompt.

With this we end up with creating a custom prompt for generating blogs based on the input parameters.
PART 2 – Design power automate workflow to automate generate blog content
For simplicity, I used “Manual trigger” flow and named is as “Generate blog flow”. But you are free to use any trigger based on the use case or scenario:

Next, add “Run a prompt” action to call the custom prompt in the power automate flow.

You may be prompted to add connection for this action if you are using ‘Run a prompt’ action first time in the environment. Choose the custom prompt “Generate Blog Prompt” and enter the text value for each input parameters:

Post that, add “Create a Microsoft Word document with the given content” action to generate a word document from a content:

Pass the blog content dynamically from the output of “Run a prompt” action:

In the file name, pass the value of SEO Title from the output JSON of “Run a prompt” action. You don’t need to pass the word file extension in this parameter.

This action will save the word file (.docx) in the one drive of a user whose account is being used in connecting to word online connector.
To get the file content from one drive, add “Get file content using path” action.

Pass SEO title output value dynamically to get the word file name in one drive. As file stores in the root folder so we use ‘/’ in the file path parameter and append .docx word file extension at the end:

Finally, add “Send an email” action to share the blog in word format to the concerned user(s). Set the appropriate email subject as per the need.

In the email body dynamically, pass the text values of SEO title and Meta description:

Select ‘Attachments’ from the advanced parameters. Click ‘Add new item’ to enter attachment details

In the name parameter, pass the output value of SEO title dynamically and append .docx extension to it:

Pass the value of file content dynamically from the output of ‘Get file content using path’ action in the ‘Content – 1’ parameter:

save and Publish the flow.
This was the last action and we are now ready for some tests.
Output
Run the flow to validate the result of the flow run:

Check for the blog word file in one drive:

Check for email received:

Open the word document to verify the formatting and content of the generated blog:

It looks super cool.
Conclusion
Why Choose AI Builder over Azure AI Services?
While Azure AI services often come at a lower cost, AI Builder shines in its seamless integration with Power Automate. With AI Builder you can build end-to-end blog–generation workflow with few low-code actions. And if you’re on a Power Automate premium plan, you already have a pool of AI Builder credits that your team can tap into to generate blogs, whitepapers, or any content without extra procurement steps.
Key Takeaways
- Custom prompts let you tailor AI-generated text for blogs, articles, or newsletters in your brand’s voice.
- Store prompts as reusable templates with input parameters like topic, keywords, word length etc. to drive consistency at scale.
- Premium licensing automatically bundles AI credits, enabling you to build powerful content workflows.
- Ideal for SMBs looking to automate content creation, free up marketing teams and maintain editorial quality.
Nidhi Sharma
nice article…keep it up.
Manish Solanki
Thanks a lot! I am glad you found it useful 🙂