Browse documentation

Automate Blog Publishing with n8n

Use n8n to automate blog publishing in Grigora. This guide shows how to connect an RSS feed and send API requests to create and publish posts. You can also schedule posts.

Why Blog Publishing Automation Matters

An n8n workflow can fetch content and publish it through the Grigora API, reducing the manual steps needed for recurring posts.

Setting Up Your n8n Workflow

Initial Workflow Creation

Example n8n workflow linking an RSS Feed Trigger to two HTTP Request nodes.

Open n8n and create a new workflow to begin your automation setup. For this automation, we'll use three nodes:

  • RSS Feed Trigger for monitoring new content

  • Two HTTP Request nodes for creating and publishing posts to Grigora

This three-node structure provides complete automation from content detection to final publication.

Step 1: Configure RSS Feed Trigger

RSS Feed Setup

RSS Feed Trigger node selected in the n8n workflow.

Feed URL field indicated in the n8n RSS trigger settings.

Configure the RSS feed trigger first by accessing the RSS node settings. Paste your RSS feed URL into the RSS URL field - this can be from any blog, news site, or content source you want to automatically republish.

Polling interval controls indicated in the n8n RSS trigger settings.

Choose the polling time depending on how often you want to check for new posts - options typically range from every few minutes to daily, depending on your content needs and source update frequency.

Testing RSS Connection

Successful RSS trigger test with feed items displayed in the output table.

Click "Fetch Test Event" to verify it can successfully read a post from the feed. This test ensures your RSS connection is working properly and that n8n can access and parse the content before proceeding to the next steps.

Once the RSS trigger is working, we'll pass this data to Grigora via the n8n workflow for automated post creation and publishing.

Step 2: Configure HTTP Request to Create Post

First HTTP Request node selected to create a Grigora blog post.

API Endpoint Setup

HTTP request method and Grigora API endpoint configured in n8n.

Set the method to POST for creating new content. In the URL field, use Grigora's API endpoint for creating a post - this endpoint handles the initial post creation with all your content data.

Refer to Grigora's API reference guide to map the required parameters correctly and ensure your workflow communicates properly with Grigora's system. The API reference documentation provides detailed parameter specifications and examples.

Headers and Authentication

Request headers and authentication fields in the n8n HTTP node.

Configure the headers including authorization and content type for proper API authentication. This typically includes your API key and content-type specification for JSON data transmission.

Configure body parameters such as:

  • Title from the RSS feed content

  • Content body from the RSS source

  • Excerpt for post summaries

  • Slug for URL generation

  • Categories and tags based on your content organization needs

Step 3: Configure HTTP Request to Publish Post

Second HTTP Request node selected to publish the created post.

Publishing Endpoint Configuration

Grigora publishing API endpoint configured in the second n8n HTTP request.

Set the method to POST for the publishing action. Use Grigora's API endpoint for publishing a post - this endpoint takes created posts from draft status to live publication.

Map the necessary parameters including the post ID returned from the create step. This ID links the creation and publishing actions, ensuring the correct post gets published.

Ensure headers and body fields match the API requirements for successful post publication and proper content delivery to your live website.

Testing and Verification

Workflow Execution

Execute the workflow to test your complete automation setup. When execution is successful, you'll see confirmation messages indicating that each step completed properly.

Go back to Grigora's posts section and reload the page to verify the automation results. You'll see that a new post has been added with the fetched content, confirming that the automation is working as expected.

 


Help guide image