Short answer
Set ChatGPT to generate complete drafts, push each draft into a Notion database (with explicit metadata fields and a “Status” select), then use Zapier to watch Notion for records with Status = “Approved” and post those to WordPress. Key pieces: a Notion content schema, an editor approval gate in Notion, a Zapier filter that only fires on approved records, and careful field mapping so metadata (slug, tags, publish date, featured image, SEO fields) are preserved.

Recommendation (one-line)
Use ChatGPT to create drafts, store them in a Notion database with structured properties, and use Zapier to run a filtered Zap that publishes approved items to WordPress and maps all metadata fields.

Why this works
Notion is a readable, editor-friendly place for review and comments. Zapier handles integrations and simple transforms (slugify, date conversion, file upload) without custom code. This is low-friction for small to medium teams and editors.

Decision criteria
- Budget: Zapier multi-step Zaps and premium app connections require paid plans; ChatGPT API costs depend on volume. If budget is tight or you need bulk/complex branching, consider Make or a small custom webhook service.
- Skill level: Zapier + Notion needs minimal dev skill. If you want finer control (file streaming, retries), a dev should build a webhook + server.
- Team size & workflow stage: For single editors or small teams, Notion review + status is ideal. For larger orgs, add approval roles and audit logging (Notion comments + created_by fields).
- Output quality: If you want human-in-the-loop editing, require editor approval in Notion before Zapier publishes.

Practical checklist (step-by-step)
1) Create a Notion database with properties: Title, Content (page body / rich text), Status (Draft / In review / Approved / Needs edits), Author, Tags (multi-select), Slug, Publish Date (date), Featured Image (file / URL), SEO Title, Meta Description, Publish Error (text).
2) Use ChatGPT (manual or API) to generate drafts. Push drafts to Notion via Zapier (or the ChatGPT/Notion API): set all properties including a generated slug (or leave blank for Zapier to slugify).
3) Editor reviews in Notion. Use comments and change Status to Approved and set Publish Date when ready.
4) Build a Zap in Zapier: Trigger: New or Updated Database Item in Notion. Filter: Status exactly equals Approved AND (Publish Date is empty or comma list. If Featured Image is a Notion file, use “Get file URL” step or store images externally first.
6) Action: WordPress — Create Post. Map: Title, Content (HTML), Excerpt (if used), Slug, Categories/Tags, Publish Date, Featured Media (upload by URL), and custom fields (SEO plugin or ACF fields).
7) Add a final step: Update Notion record with Publish Status = Published and link to WordPress post URL. On failure, write error into Publish Error and notify Slack/email.

Best-for / Avoid-if
- Best-for: small/medium teams that want a no-code editor review step and simple publishing automation.
- Avoid-if: you need heavy transformations, large-scale bulk publish, or real-time media streaming — then use Make or a custom webhook + server.

Extras & tips
- Preserve metadata by mapping Notion properties to WP fields (use ACF or Yoast fields if needed).
- For images, prefer hosting them in a cloud bucket or external URL so Zapier/WordPress can fetch them reliably.
- Add a retry and error-handling path that writes errors back into Notion so editors can fix and re-approve.

Quick sanity checklist to launch
- [ ] Notion DB created with required properties
- [ ] ChatGPT draft -> Notion flow working
- [ ] Zapier trigger for Notion item updates configured
- [ ] Zapier filter: Status == Approved
- [ ] Field mappings for slug, tags, dates, images tested
- [ ] Post-publish Notion update + error notifications set

If you want, I can outline the exact Zapier steps (trigger/action names and Formatter rules) or a sample Notion schema you can copy.

Compare Zapier and Make