Instructions for Social Networks Autopost

The add-on helps you prepare content in advance and automatically publish store content to social networks. It is useful when you need to post products, promotions, and pages regularly without manual work for every post.

What the add-on does

The add-on builds publications from templates, adds base text and hashtags, and sends them to selected social networks on schedule or manually. It can work with products, promotions, and pages, and it supports several queues with different settings.

Where to find it

• Add-on settings in the add-on card, where you set cron_pass, base_text, and base_hashtags.
• Products → Social templates (social_templates.manage) for post templates, text, and hashtags.
• Website → Social Autopost Queue (social_queue.queue) for autoposting queues and their statuses.
• Website → Social Autopost Snap for connecting social network accounts for the current company.

How to set it up

1. Open the add-on settings and set cron_pass, the base text, and the base hashtags if you want them to be added to all publications.
2. Create templates in social_templates.manage. In each template, set the title, post text, and hashtags that will be inserted into publications.
3. Connect social network accounts on the Website → Social Autopost Snap page.
4. Create a queue in social_queue.queue and choose how it should work, as a regular posting queue or as an automatic export.
5. Set the social network and account, language, number of items per run, and queue status.
6. For a regular queue, add products and, if needed, define the publishing schedule.
7. For automatic mode, choose the content source, template, additional text, and hashtags, then save the queue.
8. Copy the cron URL from the queue card and add it to your server scheduler so posts run automatically.

How to check it works

1. Create a test template and a test queue with one product.
2. Run the publication through the cron URL or manually from the queue card.
3. Check that the post gets a successful status and that the execution history is saved in the queue.
4. If the product image is in WebP format, make sure the publication still goes through and the image is attached correctly.
5. Check that the queue shows clear processing statuses and the result is visible for each record.