WordPress

Connecting a site

Only self-hosted WordPress sites reachable over a public HTTPS URL can be connected — no localhost, private/link-local ranges, or cloud metadata addresses, matching the same SSRF protections used for webhooks.

Authentication uses a dedicated WordPress Application Password (Users → Profile → Application Passwords in wp-admin), never the account's main login password.

New connections start pending and must pass a verification check (valid credentials, media upload capability, and a reachable media REST endpoint) before they can publish.

What publishing does

Publishing uploads the image's active derivative (or the original, if no derivative is selected) to the site's Media Library and sets its title, alt text, caption and description from your approved metadata.

Every publish is verified by re-reading the media item back from WordPress after upload; partial failures (e.g. metadata update failed but the upload succeeded) are reported separately from full failures.

Uploads are never repeated once a remote media ID exists — retries resume from the metadata/verification step, they do not re-upload the file.

What publishing does not do

Img Pilot never creates, edits, or deletes WordPress posts or pages — only media library items it uploaded itself are touched.

Nothing is ever deleted remotely on your WordPress site by this integration; disconnecting a connection only stops future publishing and destroys the locally stored credentials.

Credentials (username and Application Password) are encrypted at rest and are never returned by any API response or shown again in the dashboard after they are saved.

Limits and retries

Connection counts, monthly publish volume, and bulk publish batch size are limited by plan.

Failures such as authentication or permission errors are not retried automatically; transient network or availability errors are retried with a bounded attempt count before a job is marked failed.