Skip to content

Social media posts from articles and news in Kotia

Set up the Social media post card to turn articles, news and offers into posts. Choose platform, audience, length and the reader's action.

Updated

Automate preparing social media posts from articles, news and descriptions of your offers. The "Social media post" card can take material from the previous step and prepare a post that meets your channel's requirements: one main idea, a suitable presentation and the right ending.

Set the platform, audience, length and style, then connect a save step or a separate sending step. These requirements will be saved in the workflow and will apply to the next materials. This way you can create posts announcing new articles or prepare posts based on news you've found.

Example: invite people to a pottery workshop

A pottery studio has a detailed description of a class. For Telegram, you need a short post that makes clear what the participant will make, when to come and how to sign up. Task:

Write a Telegram post based on the workshop description. Start with what the participant will make with their own hands. Keep the date, time, address, price and booking link. End with an invitation to sign up. Write warmly and specifically, without artificial urgency or promises that are not in the description. Length: about 1,000 characters.

The post should work without the full description: the main terms and booking details stay in the text. The detailed program can be moved to a link.

How to set up post preparation for your platform

  1. On your computer, open "Add a step" → "Basic tasks" → "Social media post".
  2. Connect material from a document, from "Data", or from the previous step. For an external article, first get its text with "Page parsing". Without an incoming connection with material, the card still runs and does the task alone, at a cost, without seeing your text — the result will have nothing to do with your material.
  3. Choose a model and complete "Task": name the platform, audience and one main idea of the post.
  4. Specify the length, links and the reader's action. Add requirements for emoji, hashtags and tone if they matter for your channel.
  5. If needed, connect a style. You can also choose a skill if you need a specific way of working on the text.
  6. Connect "Document", run it, and check the finished post before using it.

You set the platform and length in the task text. The card doesn't choose an account to publish to. It only prepares the text.

Which requirements affect the result

What to set Why
Main idea Don't try to fit the whole article into one post
Audience Choose explanations and emphasis the reader will understand
Platform and length Get a suitable presentation and check the length before publishing
Action at the end Booking, going to the article, a question to readers or a conclusion
Required facts Don't lose the date, price, terms or link

Check the exact character limit after generation. If you need several platforms, create separate branches with different tasks based on the same source. This way each text is prepared for its own audience and format.

Using it in publishing workflows

You can create a post after searching for and selecting news, parsing a chosen article, or preparing your own material. Pass the model the full text and the links you need. From a headline alone, it won't know the details of the event.

For Telegram, connect a separate sending to a channel step. If you want to read or edit the post before it's sent, place "Ask me" between generation and publishing.

The card produces text only. Image preparation, choosing where to publish, and scheduling belong to other steps and workflow settings.

Checking the post and cost

Check the facts, links and terms. Make sure the first line clearly names the topic, the text sticks to one idea, and the ending offers an action the reader can actually take. In the workshop example, the link should lead to booking, and the date and price should match the source.

Generation is charged based on the model's actual work. Each version for another platform and each repeated run uses tokens separately. If the post is too general, specify what the reader gets from it, and provide the missing details instead of a general request to "make it more interesting".