Data Sources — Publishing & Generation (Drive, WordPress, Napkin, Manus)

Connect Google Drive for exports, WordPress for direct publish, and Napkin/Manus for AI generation.

What is it?

Four connections that power output and AI:

• Google Drive — OAuth. Per-user (each team member connects their own Drive). Used for exporting article drafts to Docs.
• WordPress — API via a connector plugin installed on the target site. Enables direct publish from NexusSEO.
• Napkin — API key. Powers the infographic generator.
• Manus — API key. Powers citation-heavy article generation.

When should I use it?

• Drive: any user who wants to export drafts as Word docs for client review.
• WordPress: clients that use WordPress and want one-click publish from NexusSEO.
• Napkin: whenever visual infographics matter to the content workflow.
• Manus: when citations or web-browsing AI generation is required.

How to use it

Google Drive

1. Click Connect Account on the Drive card.
2. Google OAuth window opens. Grant Drive scopes.
3. Pick a Root Folder — the parent for all NexusSEO-exported docs.
4. Alternatively, switch to Shared Drive mode and the owner assigns Drive folders per client (see My Settings for the full workflow).

WordPress

1. Install the NexusSEO Connector plugin on the WordPress site (download link on the WP card).
2. Activate the plugin. The settings page (Settings → NexusSEO) shows the API key. Copy it now — from v1.4.0 the key is only shown once. After the first display, only its hash is stored and the plaintext cannot be retrieved.
3. In NexusSEO, click Connect Account on the WordPress card and paste the API key + site URL.
4. Save. The card shows the connected site URL.

Napkin / Manus

1. Click Connect Account.
2. Paste the API key. Both keys are account-specific — get them from the respective service dashboards.
3. Save. Keys are stored server-side as secrets.

Tips and best practices

• Drive is per-user; coordinate with teammates if you're using Shared Drive mode to avoid duplicate folders.
• WordPress plugin version matters — download the latest version from the app's link to keep it compatible. v1.4.0+ recommended for hashed key storage and rate-limit defense.
• Napkin and Manus both charge per use. Track credits in the Asset Library Manus badges and the Napkin dashboard.

Gotchas and limits

• Drive refresh tokens can silently expire after long periods of inactivity. Reconnect if exports suddenly fail.
• WordPress connector requires plugin v1.0.0+ and PHP 7.4+. Older WP installations may not work.
• Lost the WordPress API key? From v1.4.0 the key is stored as a one-way hash and cannot be recovered. Click Regenerate Key in Settings → NexusSEO on the WP site, copy the new key (one-time view), and paste it back into NexusSEO Data Sources.
• "WordPress site is rate-limiting us" error? v1.4.0 locks out an IP after 10 failed authentication attempts within 10 minutes. Wait 10 minutes and verify the API key is correct before retrying.
• WordPress publishing fails with CORS or "internal" error: Go to Settings → Permalinks in WP Admin and click Save Changes (no need to change anything). This flushes rewrite rules and re-registers the plugin's REST API routes. Most common cause of "plugin installed but publishing fails."
• Custom admin URLs (e.g. /wadmin25/ via LoginPress or WPS Hide Login) do not affect the WordPress connector — it uses /wp-json/ REST routes, not the admin path.
• Manus API keys start with sk- — if yours doesn't, you're looking at the wrong key in the dashboard.
• Napkin URLs expire in 30 minutes — the app downloads and persists them automatically on generation completion.

Related

• Overview
• Generation modes
• Save & schedule