Automating Google Docs to WordPress Posting with n8n - Encountering Login Page Issue

[josephavetti]

Hello, n8n community!

I’ve successfully set up a workflow to automatically post content from Google Docs to our WordPress site, but I’m encountering a problem. When I execute the workflow, instead of the document being published, I’m redirected to the WordPress login page.

Here’s a brief overview of my workflow:

1. Google Drive Node: This node checks for new files in a specific folder on my Google Drive. It filters for Google Docs files using the “application/vnd.google-apps.document” file type.
2. Google Docs Node: After identifying a new document, this node retrieves the content of the Google Doc, including its title and body.
3. Edit Fields Node: This node is used to structure the data that will be sent to WordPress by assigning the document ID, title, and body.
4. Markdown Node: The content is converted from Markdown to HTML to ensure it is properly formatted for WordPress.
5. WordPress Node: Finally, this node attempts to publish the post on WordPress using the structured data from the previous nodes.

Despite this setup, executing the WordPress node results in being redirected to the login page, rather than successfully publishing the post.

Potential Areas to Investigate:

• Authentication: Could there be an issue with how the WordPress API credentials are set up? Are the permissions granted properly?
• API Endpoints: Am I using the correct endpoint for publishing posts?
• Post Status: Is there a specific post status I need to set for the content to publish directly?

Any guidance or suggestions to troubleshoot this issue would be greatly appreciated. Thank you for your help!

[n8n]

It looks like your topic is missing some important information. Could you provide the following if applicable.

• n8n version:
• Database (default: SQLite):
• n8n EXECUTIONS_PROCESS setting (default: own, main):
• Running n8n via (Docker, npm, n8n cloud, desktop app):
• Operating system:

[ihortom]

Hey @josephavetti , have you tried login in with the same credentials in the same browser as you access n8n Cloud to your Wordpress account? I wonder if it has anything to do with the session expiration.