Setup & usage
Installation, Notion connection, user ID detection, single save, and batch export.
Open documentation →Use the troubleshooting guides for common account, Notion, image, and batch-export problems. If the issue remains, send a focused report.
Installation, Notion connection, user ID detection, single save, and batch export.
Open documentation →Report a reproducible bug, affected page URL pattern, extension version, and visible console error.
Open GitHub Issues →Include the purchase email and plan. Never send card details, passwords, or Notion access tokens.
Email support →Sign in to the intended Midjourney account, open midjourney.com/imagine, refresh once, and reopen the extension popup. The current extension stores the canonical detected value as midjourneyUserId in local extension storage.
Refresh the signed-in Midjourney page so the extension can detect the account again. A stale or unrelated ID cannot be used to request another account’s history.
Popup and options should share one selected database setting. Reconnect Notion if needed, then select the database again and confirm the integration has access to it.
A required property already exists with a different type. Rename the conflicting property or change it to the expected type listed in the documentation, then retry.
The source download or Notion file upload may have failed, or the file may exceed the direct-upload limit. The extension attempts an R2 fallback and records the saved URL in the page body.
Confirm the page matches a supported Midjourney Jobs or Discord channel layout, reload the page after updating the extension, and include the page URL pattern and relevant HTML when reporting the issue.