How is WURDX different from using Google Docs with a spreadsheet tracker?

The difference is status is built into the document. In Google Docs, you maintain a separate tracker that's always out of sync. In WURDX, the document IS the tracker. Change a status, everyone sees it. Filter by status, see all content in that stage. No more 'hey, is this draft still active?' Slack messages.

Can we push content directly to our CMS?

Not directly — WURDX isn't a CMS. But when content hits 'Approved', a webhook fires to any URL you specify. Point it at your WordPress REST API, Webflow, Ghost, or Zapier to handle the handoff.

How many content pieces can we have in the pipeline?

Unlimited on Pro and Company plans. Free tier allows 10 documents total. Most content teams we work with have 30-50 active pieces at any time across various stages.

Can different team members have different permissions?

Yes. Admins can change statuses and edit all content. Members can edit content they have access to. Viewers can only read. You can also restrict who can change status to prevent premature 'Published' tagging.

For Content & Marketing Teams

Stop tracking contentin a spreadsheet

If you're publishing 20+ pieces per month, you need more than docs and folders. You need a content production pipeline.

Start free trial See Kanban feature

Sound familiar?

"Where is that draft?"

Your editor asks about a blog post. You check Slack, email, then dig through Drive folders. The post is somewhere, but nobody knows where.

WURDX: Kanban view shows every piece of content and its current status at a glance.

"What's the status on this?"

Is it in draft? Under review? Approved? You label files with prefixes like 'DRAFT_' or 'FINAL_v3' — which means nothing.

WURDX: Custom statuses (Draft, Review, Approved, Scheduled, Published) that everyone can see and filter.

"Can you push this to WordPress?"

Content is approved but getting it from your doc to your CMS is a manual copy-paste dance that introduces formatting errors.

WURDX: Webhooks fire when status changes to 'Approved' — trigger your CMS, Zapier, or any API endpoint.

"We need to see everything pending review"

You maintain a spreadsheet to track what's in review. It's always out of date because updating it is someone's extra job.

WURDX: Filter by status. One click to see all content in 'Review'. No spreadsheet needed.

What content teams actually need

Not another notes app. A production system for content.

Kanban Content Pipeline

Visualize your entire content calendar. Drag articles between Draft → Review → Approved → Published. See bottlenecks instantly.

Custom Statuses That Match Your Workflow

Not everyone uses the same workflow. Create statuses that match yours: 'With Designer', 'Pending Legal', 'Scheduled for Tuesday'.

Webhook Integration When Status Changes

When an article hits 'Approved', automatically ping WordPress, notify #content-team in Slack, or trigger any API endpoint.

Visual Workflow Builder

Build visual automations on a drag-and-drop canvas. Trigger actions when status changes, add approval gates, and remove manual coordination overhead.

Common questions

Key features

Kanban View Custom Statuses Webhooks Workflows

Ready to stop playing content traffic cop?

Start with our free tier. 10 documents, all features.

Get started free See pricing