Group Posting Pro Features, Plans and Setup Requirements

Group Posting Pro helps you organise Facebook groups, prepare reusable content and run posting workflows from your own browser. The product includes Direct API and Classic DOM posting on every plan; Pro adds ongoing AI tools, campaigns, Lead Radar and other advanced workflows. It does the repeatable publishing work while you remain responsible for relevance, permissions and follow-up.

This is a current capability and setup guide, checked against the feature documentation, pricing page and privacy policy on October 3, 2026. It explains what each feature does and what it needs, without treating a tool installation as proof of more reach, leads or sales.

What the product does—and what you still need to do

Capability overview with the corresponding human task

Capability	Product role	Your role
Group library and collections	Import or extract joined groups and organise reusable destination sets	Read rules, check participation, remove irrelevant destinations and keep identities correct
Templates and variants	Save copy, use spintax and work with reviewed variations	Keep the offer accurate and adapt the substance to each audience
Posting runs	Attempt destinations in sequence using the selected browser engine	Keep the environment available and review the actual results
Simple schedules	Plus and Pro support planned one-time, daily and weekly runs	Maintain browser availability and verify the saved destination, time and recurrence
Campaigns and advanced scheduling	Pro supports multi-step workflows and additional cadences	Review triggers, steps, repeat behaviour, expiry and follow-up capacity
Lead Radar	Pro checks selected groups/feed periodically for keyword matches	Review relevance, respect discussion rules and decide how to respond

Activity records describe posting outcomes. They are not a complete analytics system for likes, comments, customers or revenue. For engagement and commercial results, inspect the actual posts and use your own lead and website measurement.

Two posting engines in your existing browser session

Direct API is the default/recommended mode and sends authenticated requests to Facebook’s internal web GraphQL endpoints. Classic DOM is selectable and automates the visible composer. Both run through the existing logged-in browser session, and both are included on Lite, Plus and Pro. This is separate from the public Facebook Groups API retired in 2024; neither engine restores that public service.

Text, links, images and video are supported according to the selected mode and the Facebook composer, group and account permissions. A profile and a managed Page are different identities. A Page can participate only where the group permits it. The posting engine documentation explains the supported methods and the multiple-group posting walkthrough covers a first run.

Retry is outcome-dependent. Eligible definite failures in a personal-profile Direct run can fall back to Classic; Page Direct runs do not automatically resend through Classic. Blocking, authentication problems and uncertain outcomes require review rather than a blind resend. An engine switch should not be used to repeat a post whose first outcome is unknown.

Group collections: organise permission and relevance together

Bring in the groups you have joined, then tag or collect them by audience, location, language and permitted use. A library is useful only when it helps choose the right destination for a particular post. “Local homeowners” and “trade professionals” may both concern the same service but need different explanations.

Keep a simple destination note: rules checked, commercial posting allowed or not, links permitted or not, eligible identity, formats and any participation/approval requirements. Meta’s public-group guidance explains that participation approval and post approval can be distinct. Do not treat library membership as permanent authorisation to promote.

The group management documentation covers extraction, collections and discovery. Paid-plan discovery and join requests are separate from permission to post; an accepted request does not override the group’s rules. Pro’s AI Group Finder helps with search ideas and group fit, and its suggestions still need your review.

Templates, spintax and AI content

A reusable template removes repeated typing. Spintax chooses among alternatives you supply, such as {Hello|Hi}. That small change can vary wording, but it cannot make an irrelevant promotion useful. Use separate templates when the audience, service area, evidence or allowed next step differs.

Pro’s AI content engine uses your AI Studio details and either a quick tone or saved writing voice to draft content and variations. The current quick tones are Helpful, Professional and Promotional; saved voice styles are Warm, Clear, Playful, Calm and Bold. Templates can carry up to four A/B/C/D variations. Review every draft for facts, price, availability and fit before using it.

For example, a hypothetical cleaning-business workflow might use one educational checklist for a homeowners group and a separate commercial-availability template for a group that allows offers. The AI can help draft each, but it should not invent customer reviews, before-and-after outcomes or a service area. Keep any factual evidence supplied by the business separate from generated wording.

Schedules and campaigns need an available computer

Plus includes simple one-time, daily and weekly schedules. Pro adds advanced scheduling and the visual campaign builder for multi-step flows. A campaign can organise recurring content, but every scheduled browser run still requires the computer awake and online, Chrome running, the extension enabled and Facebook signed in.

The feature called “Post at my best times automatically” uses your posting history to choose an hour associated with successful publication. It does not measure audience engagement or prove that hour produces more leads. Review the destination, time zone and recurrence before enabling a schedule, especially for an offer that expires.

A calendar start time is not the publication time of every destination. Sequential work, pauses, interruptions and admin approval can move later results. The campaign setup guide is the next step when you need a sequence rather than a single scheduled post.

Lead Radar finds matches periodically

Lead Radar checks at configured 15-, 30- or 60-minute intervals while the required browser environment is available. Its checks alternate between selected groups and the Groups feed. You can select up to 25 groups and define phrase, word and exclusion rules. Some posts may be missed; a match is not proof of a sale-ready buyer.

When you open a match and ask for a reply, the AI can draft a response and explain how relevant the post appears. These are relevance labels to help you review the conversation. Optional automatic replies have their own controls, so check that configuration explicitly rather than assuming every reply requires a manual click.

Use a few precise need phrases and review exclusions. A designer might distinguish “looking for a garden designer” from a job vacancy or a request for free work. Start by reading the real conversation and replying helpfully; do not turn every keyword match into a promotional message.

Posting controls and outcome review

Group Posting offers randomised pacing, a pre-flight risk check, optional account warm-up, a night pause and an automation stop after a Facebook block. Warm-up is optional and off by default. These controls manage the run; no tool can promise zero risk or certify a posting volume. Facebook rules and each community’s permissions and admin approval continue to apply.

How to interpret a per-group result

Result	Meaning for your workflow	Next action
Confirmed published	A published result was recorded	Open the receipt/destination where available; review media and replies
Awaiting approval	Submitted for admin review	Keep it pending; check the group’s approval process
Definite failure	The attempt has a known failure result	Read the reason and fix eligibility or content before a suitable retry
Uncertain	Publication could not be established	Inspect the group and activity before another send

Exports and history help you maintain a record of work. They should not inflate “published” by including pending items, or inflate “leads” by counting submissions. See the posting control documentation and help centre for current behaviour.

Lite, Plus and Pro: choose the feature you need

Consumer plans checked October 3, 2026; prices in EUR

Plan	Current price	Main boundary
Lite	Free	5 composer group-posts per day; five lifetime AI uses; both engines, import and auto first comment; no scheduling or campaigns
Plus	€69/year, equivalent to €5.75/month; annual only	Removes the product composer cap and adds simple schedules; no ongoing AI, campaigns, Lead Radar or cloud backup
Pro	€24/month, €39/quarter or €119/year	Includes Plus, ongoing AI, campaigns, advanced scheduling, Lead Radar, AI Group Finder, cloud backup and priority support
Pro trial	€1 for 6 days	Continues at €24/month from day 6 unless cancelled before then

“Unlimited posting” means no product daily composer cap, not unlimited permission from Facebook or group administrators. In-feed sharing of an existing Facebook post has a separate product rule: Lite shares have no product daily cap and include a credit line. The five lifetime AI uses are a shared allowance, not a fresh grant each time you buy Plus. Check the pricing page for current terms and VAT at checkout.

Data and agency boundaries

Your Facebook password, cookies and session are not sent to Group Posting’s servers; authentication to Facebook happens through your browser. That does not mean the entire product is offline. Licensing, anonymous diagnostics and AI requests have service connections. AI features send the text needed for their task, and consumer Pro includes an automatic daily cloud backup of supported settings, content and redacted history/lead data. Read the privacy policy for the payload and retention details before adding sensitive client information.

If clients each have their own Facebook login, agency plans provide a dashboard while each client’s own extension does the posting. Their computer and browser still need to be available. Managed client browsers do not include consumer Pro cloud backup; a client with a separate personal licence retains the backup provided by that licence. Agency plans retain Group Posting branding. A freelancer publishing as managed Pages through their own authorised account may need a different setup from an agency with many client logins.

Your first-run checklist

1. Install from the Chrome Web Store and sign into Facebook in that browser.
2. Choose the profile or managed Page allowed in the destination.
3. Import groups and build a small, relevant collection with rules recorded.
4. Prepare one accurate post and inspect its format and intended next step.
5. Review pacing, optional warm-up, night settings and browser availability.
6. Run the post, then open results and distinguish publication from approval or uncertainty.
7. Record useful replies and business outcomes in your own measurement system.

This is a setup process, not a timed hands-on test or a customer case study. The tutorial provides the walkthrough. The earlier release update provides historical context; use this guide and current feature pages for today’s capability and plan boundaries. For a broader vendor reference, see the FewFeed catalogue guide.

Add Group Posting to Chrome and start with an appropriate Lite post. Upgrade when a specific schedule, AI or campaign workflow fits your needs, using the current plan comparison.

Questions about Group Posting Pro

What does Group Posting Pro do?

Group Posting is a browser extension for organising groups, preparing posts and running posting workflows. Pro adds ongoing AI content tools, campaigns, advanced scheduling, Lead Radar, the AI Group Finder and cloud backup. You still choose appropriate communities, review content and follow Facebook and group rules.

What is the difference between Direct API and Classic DOM?

Direct API sends authenticated requests to Facebook’s internal web GraphQL endpoints from your logged-in browser. Classic DOM uses the visible Facebook composer. Both are included on every plan and depend on mode, format and permissions; neither uses the retired public Facebook Groups API.

What has to stay running for schedules and Lead Radar?

Keep the computer awake and online, Chrome open, the extension enabled and Facebook signed in. Schedules, campaigns and Lead Radar execute through that browser environment. Lead Radar checks at configured intervals rather than continuously.

Does an Activity entry prove a post is public?

Check the specific result and the destination. A post awaiting admin approval is submitted but not public. A definite failure differs from an uncertain outcome; inspect uncertain destinations before retrying so you do not create a duplicate.

Do the posting controls remove account risk?

No tool can promise zero risk. Pacing, optional warm-up and pause controls help manage activity, but Facebook rules, group permissions, post formats and admin approval still apply. These controls do not certify a posting volume or predict account outcomes.