Jumplinks Flow – Client Feedback & Editorial Workflow

Send your client one link. They open the page exactly as visitors will see it, highlight the sentence or image they mean, type the comment right there, and click Approve when it’s ready. No WordPress account, no screenshots in email, nothing stored outside your own site.

Try it without installing: open the Live Preview above and you’re already logged in as a reviewer. The demo page itself walks you through what Flow does, with screenshots and a short video, and you can comment on all of it.

Turn on Mandatory review and WordPress will not publish until a reviewer approves. Works in Gutenberg, Classic, Elementor, Bricks, Breakdance, Beaver Builder, Divi, Avada and Oxygen 6 — and the review link keeps working behind your cache plugin or maintenance mode.

Flow takes the GitHub pull request review process with inline comments and approve or request changes workflow and builds it into WordPress. It runs entirely on your site, and your clients never need to create a WordPress account.

If your current process depends on long comment threads, scattered docs and email, or third-party review tools, Flow gives you a cleaner path without complex setup or heavyweight workflow tools. If AI or automation is writing the first draft, Flow is the human checkpoint between that draft and Publish.

⚙️ How it works

1. Assign a reviewer to a page or post: a WordPress user, or just your client’s email address.
2. Your client gets a private magic link straight to the review page. No account, no signup, no login.
3. They pin comments to the exact text or image on the rendered page.
4. They approve or request changes. You fix, resubmit, and repeat until it’s approved.
5. You publish once it’s approved, knowing exactly who signed off.

🎯 Why agencies and freelancers use Flow

• One link, no login. Your client clicks and is in. No “how do I log in” call, no password reset at 11pm. Email invite links stop working the moment you remove the reviewer or cancel the review, and a cancelled review stays readable for your team.
• They review the real page. Mobile, menus, fonts — what they see is what visitors get, so “the blue box on the phone” never needs a screenshot. They never touch the editor.
• Comments sit where the problem is. Every comment is pinned to the exact words or image, with threaded replies, so nothing has to be described twice.
• A yes you can point to. With Mandatory review on, WordPress will not publish until a reviewer clicks Approve, and the review records who did.
• Nothing leaves your site. Comments, approvals and links live in your own database. No third party sees the draft, no per-seat bill.
• Works where you build. Gutenberg, Classic Editor, Elementor, Bricks, Beaver Builder, Divi, Avada, Breakdance and Oxygen 6 — and the review link keeps working behind your cache plugin or your builder’s maintenance mode.
• Three decisions at setup, then one screen. Optional or mandatory review, which content types, who can review — under Flow → Settings. A Review column on your post lists shows where every piece of content stands, a dedicated Reviewer role is created for you, and the interface ships in 86 languages.

📝 Also works for editorial teams

Writers send drafts to an editor, the editor comments in context and approves, and the post goes live. No custom statuses to design, no workflow builder to configure. Flow works on posts, pages, WooCommerce products, and custom post types. It can assign a default reviewer automatically and show a “Reviewed by” credit on published content.

✨ Human approval for AI and automated drafts

Flow doesn’t generate text or detect AI content. It’s the checkpoint between a draft and Publish, whoever or whatever wrote the draft.

• Drafts created by ChatGPT, Claude, n8n, Make, Zapier, or the REST API can get a reviewer assigned automatically the moment the post is created.
• With mandatory review on, the first Publish or Schedule stays blocked until a person approves, including attempts through the REST API.
• AI agents connected through WordPress Agent Connector or MCP can send content for review, read comments, resolve threads, and resubmit. Only a human can approve or request changes.
• Optionally let an agent reply to a comment to ask what you meant, and make it say what it changed when it resolves one. Off by default; you choose which user those comments are posted as.

🤖 What makes Flow different

Most feedback tools are paid-only SaaS subscriptions that charge per reviewer and require clients to sign up for separate accounts. Flow runs entirely inside your WordPress site, and lets you invite reviewers with a single link — no signup, no monthly fee, no third-party service collecting your content.

Editorial workflow plugins optimize for maximum configuration. Flow optimizes for feedback momentum. You get a clear approval process and contextual collaboration without overwhelming your team or clients with complexity.

If you want an editorial workflow that is modern, focused, and easy to use from day one, Flow is built for you.

🚀 Flow Pro

Everything above is free. Flow Pro adds:

• Public review: share one review link that anyone can open and comment on, with no WordPress account and no email invite needed.
• Site-wide review: send the whole site. Reviewers browse in review mode and comment on any page.
• Unlimited reviewers: Free allows one reviewer per post, a WordPress user or an email invite. Pro removes the limit.
• Multiple reviewers: set a minimum number of approvals, with each reviewer’s vote tracked separately.
• Device switcher: reviewers check desktop, tablet, and mobile widths without leaving the page.
• Rich comments and @mentions: formatting, links, and code blocks, plus mentions for reviewers, authors, and external invitees.
• Slack notifications: DMs for assignments, mentions, approvals, change requests, and site review invites.
• Webhooks for n8n, Zapier, and Make: signed JSON payloads for 17 events across the review lifecycle — sent, approved, changes requested, resubmitted, comments and site reviews. Deliveries are queued and retried with a full log. Payloads include the exact passage each inline comment points at, formatted for a prompt, so a writing agent can apply the fixes and resubmit.
• Activity log: every status change on the review page, with the user who triggered it.

🛠️ Development

Where is the JavaScript and CSS source?

Human-editable source for the compiled assets in build/ lives in the src/ directory. Files under build/ are generated by webpack; edit src/ instead of hand-editing build/.

How do I rebuild the compiled assets?

From the plugin directory, with a supported Node.js release:

1. Run npm install or npm ci to install dependencies.
2. Run npm run build to regenerate webpack output.

Third-party JavaScript

Packages such as @wordpress/scripts and @wordpress/icons are declared in package.json. After npm install, see each package under node_modules/ for license text, or refer to the upstream WordPress repositories.

🔌 External services

This plugin loads avatar images from Gravatar (operated by Automattic), which is a third-party service.

• What is sent: an MD5 hash of the user’s email address, generated by WordPress core via get_avatar_url(). No raw email address leaves the site.
• When: whenever the plugin renders a comment author avatar (review page comment cards, inline comment threads) or a reviewer/requester avatar (REST responses for the review sidebar and the Elementor, Bricks, Beaver Builder, Divi, Avada, Breakdance, and Oxygen Builder drawers).
• Why: to display each commenter’s avatar next to their comment, matching the rest of the WordPress avatar experience.
• Service URL: https://gravatar.com/
• Terms: https://automattic.com/terms/
• Privacy: https://automattic.com/privacy/

This is the same Gravatar integration that ships with WordPress core. The free plugin contacts no other external service.

Flow Pro adds optional integrations that only send data once you configure them:

• Slack (https://slack.com/) — when you save a Slack bot token, Flow calls chat.postMessage and users.lookupByEmail on api.slack.com to deliver direct messages. Sent: the reviewer’s WordPress email address (to find their Slack account), reviewer and author display names, content titles, review links, and the text of comments they are mentioned in. Terms: https://slack.com/terms-of-service · Privacy: https://slack.com/privacy-policy
• Webhooks — Flow posts signed JSON to the endpoint URLs you enter under Flow → Webhooks. Payloads contain review status, post title and links, reviewer and requester names and email addresses, and comment text including the exact passage a comment points at. Deliveries and their payloads are kept in your database for the retention period you set and pruned by cron.
• Akismet — if the Akismet plugin is active and configured, anonymous comments on open-to-public reviews are checked with Akismet’s comment-check endpoint (comment text, name, email, IP address, user agent and referrer), governed by Akismet’s terms and privacy policy: https://akismet.com/privacy/
• Freemius (https://freemius.com/) — Pro licences are activated and updates are fetched through Freemius; no usage data is sent unless you explicitly opt in. Privacy: https://freemius.com/privacy/