Iara Native AI Social Media Auto Poster – Cross-Platform Sharing, Captions and Image Generation

Yes, after the corresponding accounts are connected and the networks are enabled. Facebook requires an authorized Page, Instagram requires a linked professional account, and X requires suitable developer API access. Iara also supports Threads, LinkedIn organization Pages, Pinterest boards, Bluesky and Tumblr.

The plugin itself does not require an AI subscription to use deterministic templates. Optional AI generation uses your configured WordPress AI provider, which may charge for requests. Social network APIs may have independent approval, pricing or usage requirements, notably X. Check the service's current requirements before connecting.

Yes. Select global networks and post types in settings, then disable auto-publishing or override the destinations for a particular post in its editor. The queue shows outcomes and errors so you can decide when to retry.

Yes. Publishing is triggered when a scheduled WordPress post becomes public. WP-Cron or a correctly configured external cron must be operational; queue delivery is asynchronous and may not be immediate.

With AI copy enabled, a source-grounded explanatory description is reused on networks with enough room. Short-form networks use concise WordPress excerpts to fit the available budget. Links or domain-reading prompts and taxonomy hashtags are composed according to each network. Templates remain the fallback when AI is disabled or unavailable.

No. Instagram publishing requires a public image URL from an existing featured image, an enabled AI-generated image or a configured fallback image. A professional Instagram account linked to an authorized Facebook Page is also required.

Check the queue error and destination authorization. Common causes are missing scopes, changed provider permissions, API limits, expired tokens, image-processing delays or inaccessible images. Transient errors can be retried; reconnecting an account may be necessary if its permissions changed. A retry is a new attempt, not a guarantee the provider will accept the publication.

Create an X developer app with OAuth 2.0 Authorization Code support, set the precise callback URL shown by Iara, and authorize the requested tweet.read, tweet.write, users.read, media.write and offline.access scopes. Iara uses PKCE S256, validates the connected X account and stores encrypted tokens when local cryptography is supported. Posts use the X API's weighted 280-character budget. JPEG, PNG and WebP images up to 5 MB may be attached. Your X API account must have suitable posting permissions and usage allowance.

Reconnect Pinterest to request boards:read, boards:write, pins:read and pins:write. Refreshing an old token cannot add permissions that were not granted. Confirm the app's permission tier and choose an authorized board before retrying.

Styles affect the aesthetic instructions for newly generated images. The optional brand guide specifies a font family and role-based colors; the provider may approximate them. Changing these settings does not modify older images, featured images, CSS, credentials or social publishing APIs. Artwork generation is optional.

Iara uses the same Iara identifiers and slug as this package. A one-time non-destructive import is provided for settings, connections, queue entries and per-post choices from the earlier Yara Native AI Social Media Auto Poster build. Deactivate Yara first to avoid duplicate publication, then update your OAuth app callback URLs to the Iara address. Other experimental plugins are not automatically migrated. Old Yara data is retained for rollback.

Iara stores configuration, connection information and its queue locally in WordPress. It sends the post content and required credentials to a network only for actions you enable, or to an AI provider through WordPress when AI is enabled. There is no built-in tracking or selling of visitor data. See External services and Privacy for the data involved and provider policies.