Short answer
Use Zapier to either (A) call ChatGPT/OpenAI to generate drafts on schedule or (B) watch a staging place (Notion/Airtable/Google Docs) where your team saves ChatGPT drafts, then have Zapier create WordPress posts with a future publish date, SEO meta, and author ID. For a 3-person team I recommend a human approval step before publish.

Recommendation (one-line)
Create drafts into an approval table (Airtable or Notion) and use a Zap that triggers on "Status = Approved" to POST to WordPress (via Zapier’s WordPress action or Webhooks) with post_date, meta fields, author, and featured image.

Decision criteria (how to pick a flow)
- Budget & skill: Use Zapier’s built-in WordPress actions if you want low-dev setup; use Webhooks + WP REST API (requires Application Passwords) if you need custom SEO fields or more control.
- Trust & brand risk: If brand/SEO sensitivity is high, require human approval. If you trust your prompts and quality, you can auto-publish scheduled posts.
- Volume & recurrence: For regular recurring series, use Schedule by Zapier to generate drafts or to move approved drafts into publishing flow.
- Team size/workflow: With 3 people, a simple author-approval-review mapping in Airtable/Notion keeps ownership clear.

Practical Zap template (high-level steps)
Option A — Human-reviewed publishing (recommended):
1) Trigger: New/updated row in Airtable or new page in Notion where Status = "Approved".
2) Action: Optional Formatter — convert publish date to WP timestamp.
3) Action: Upload media (featured image) to WordPress or use Webhooks to upload and get media ID.
4) Action: Create Post (WordPress) or Webhook POST to /wp-json/wp/v2/posts with fields: title, content, status=future, date (post_date), categories, tags, author (post_author = WP user ID), featured_media.
5) Action: Set SEO fields — if using Yoast/RankMath, include meta keys like _yoast_wpseo_title, _yoast_wpseo_metadesc, _yoast_wpseo_focuskw (or use plugin-specific API). If Zapier action doesn’t support, call WP REST API via Webhooks to set meta.
6) Action: Log result in Airtable/Slack and set row = Published.

Option B — Auto-generate drafts: Use Schedule by Zapier -> OpenAI (ChatGPT prompt) -> place draft into Airtable for review or straight to WP with status=future.

Reliability & recurring-post tips
- Use WP Application Passwords for secure REST auth.
- Include retry logic in Zapier and set Zap to notify you on failure (Slack/email). Enable Zap history alerts.
- Rate limits: chunk large media uploads; cache credentials.
- Testing: use a staging WP site and run end-to-end tests before going live.
- Logging: always write a record (Airtable/Google Sheet) for traceability and rollback.

Checklist before go-live
- [ ] Decide approval vs auto-publish
- [ ] Map author names to WP user IDs
- [ ] Configure WP Application Password or OAuth
- [ ] Build Zap: trigger -> generate/import draft -> set post_date/status -> set meta (SEO) -> upload media -> create post
- [ ] Add filter/approval step and failure notifications
- [ ] Test on staging and monitor Zap history for 72 hours

Best-for / Avoid-if
- Best-for: teams that want predictable recurring posts with review and clear ownership. Good when you need mapped SEO fields.
- Avoid-if: you must guarantee 100% editorial human review for every post (then keep manual publish).

Tools mentioned: Zapier and ChatGPT (via OpenAI in Zapier). CTA: zapier

Compare Zapier and Make