Add internal links to Japanese WordPress posts with Gemini and Slack approval

## Add internal links to Japanese WordPress posts with Gemini and Slack approval For editors of Japanese WordPress sites who want to add relevant links to related articles and priority pages, while choosing each link before it is written. ### How it works 1. Enter a post ID in the form, or send it to the optional authenticated webhook. 2. Gemini suggests Japanese search phrases. WordPress search results are combined with matching pages from your priority table. 3. Existing and logged links are excluded. Priority pages rank first; other candidates use search matches and the link history recorded by this workflow. 4. Gemini proposes anchors copied from the article. Code checks word boundaries and filters unsuitable anchors. These checks are conservative heuristics, not a full Japanese grammar analysis; the editor makes the final choice. 5. Slack shows each proposed link in context. Select the links to add using the checkboxes; the form stays open for one day. 6. Before writing, the workflow reads the post again. If the content changed during approval, it stops and asks you to run it again. Otherwise, only the selected links are inserted and logged. ### Setup 1. Create Data Tables internal_links (source_url, target_url, anchor, added_at) and link_priority_pages (url, title, keywords), using string columns. Priority-page keywords can be separated by commas or Japanese commas. Use URLs from the same site. 2. Add WordPress application-password Basic Auth credentials to Get Post, Reload Post and Update Post. 3. Add Gemini credentials to both model nodes. 4. Add Slack credentials to all three Slack nodes. Invite the bot to the channel and set its channel ID; the app needs chat:write. 5. Set site_url and post_type in Config. post_type is the REST collection name, such as posts. 6. Start with Run for One Post and a test article. Approve one suggestion and check that only its anchor was linked. Submit with no boxes checked to verify that the article stays unchanged. ### Optional: run when a WordPress post is published Importing this workflow does not install a WordPress publish hook. Configure a WordPress webhook plugin or a site-side integration separately. 1. In Post Published, create a Header Auth credential, for example with header name X-N8N-Token. Store the secret in the credential and configure the sender with the same name and value. 2. Configure the sender for