List postsRead a feed of posts: one community's, or everything your server can see. Each post comes back with its title, its text, the link it points at, its score, its comment count and its author's handle, plus its own address so a later step can link to it. Sort by what is busy, what is new or what is top this week. Set 'Only what is newer than' to the newest post from your last run and a scheduled workflow will only ever see what it has not seen before.
Get a postRead one post in full, along with the community it was posted in - its rules, its size and who moderates it - and anywhere the same link was cross-posted. Takes the post's address or its number. Use it after a search or a feed to get the whole text before summarising it, or to check the room's rules before a person replies.
List comments on a postRead a post's discussion, in the order a person would read it: every reply follows the comment it answers, and each one says how deep it sits. 'How many' counts whole conversations rather than rows, so ten means the top ten threads with their replies attached, not ten comments cut out of the middle. Feed the result to a summarising step to get the gist of a hundred-comment thread in one line.
Get a commentRead one comment: what it says, who wrote it, what it answers, how it scored and which post and community it belongs to. Takes the comment's address or its number, both of which come out of any listing or search here. Use it to pull the full text of a comment a search only showed the start of.
Search LemmySearch your server and everything it federates with, for posts, comments, communities or people. This is the brand- and topic-monitoring step: search your product's name, narrow to a community or an author, set 'Only what is newer than' to the last run, and a scheduled workflow reports only what is new. Leaving the text empty is allowed and useful - an empty search of one community, newest first, is 'what has just been said in here'.
Get a communityLook up one community: what it is for, its rules, how many people follow it, how busy it has been this month and who moderates it. This is the step to run before a workflow posts anywhere near a community, and the quickest way to tell a 50-subscriber namesake on your own server from the 80,000- subscriber one everybody means.
List communitiesBrowse the communities your server carries, busiest or biggest first. Use it to find where a subject is discussed before you start watching it, or to keep a directory of the rooms your team cares about. Each one comes back with its handle, ready to paste into any other action here.
Get a personLook up somebody: their profile, when they joined, how much they have written, which communities they moderate, and their latest posts and comments. Use it to weigh a comment before acting on it - a three-day-old account with four comments reads differently from a moderator of the community it was posted in - or to follow one person's activity.
List moderation actionsRead the public moderation log as one list of events in time order: posts removed, comments removed, people banned, moderators added, communities purged. Every entry says what happened, who did it, what it was about and the reason they gave, and carries a ready-made line to paste into a message. Use it to keep a record of what happens in a community you run, or to be told when something is removed.
Get server detailsDescribe the Lemmy server this connection reads: its name, what it is for, its rules, how many people and communities it holds, how many are active this month, whether sign-ups are open and who its admins are. It needs nothing filled in, so it is also the one-step check that the connection works and points at the server you meant.
