Facebook Friend Request Automation: Filters, Queue, and Review
Facebook friend-request automation organizes profile selection and scheduled requests. In Friender, review a source, apply scanner filters, inspect Friend Requests, and configure the queue before enabling it. Advanced includes targeted requests; Pro adds broader CRM and follow-up tools.
On this page
Build a repeatable connection workflow by separating audience selection, queue review, and follow-up. Friender's web app manages the queue; its Chrome extension connects the workflow to your Facebook account. Targeted friend requests start with Advanced. Pro adds broader CRM, campaign, and automation capabilities.
Set up your first reviewable queue
- Open Friender with your connected Facebook account and Chrome extension. Use Sync Now to refresh the information available to the app.
- Choose a source with a clear connection reason. On a supported Facebook post, open its menu and choose Run Friender to open the scanner.
- Review the scanner's available filters and the people you intend to add. Choose criteria that match the context of the conversation or community.
- Open Friend Requests in the web app. Review the queued profiles before enabling requests.
- Review the queue's Profile Filter, schedule, hourly and daily controls. Keep the queue paused while changing the audience or resolving an account notice.
- Enable the reviewed workflow when requests are available on your account. Check the recorded outcomes before expanding the audience.
For other entry points, the seven-source overview covers groups, posts, suggested friends, public friends lists, uploaded profiles, Non Friends, and the Frienders directory.
Scanner filters and the queue's Profile Filter
| Stage | Purpose | Review point |
|---|---|---|
| Run Friender scanner | Select candidates to add to the queue | Check source and available profile information |
| Friends Queue Profile Filter | Apply a separate check before a queued request is sent | Review the criteria currently enabled in your account |
| Outcome review | Check what happened after processing | Separate accepted, pending, and restricted outcomes |
The two filter stages serve different jobs. A profile entering the queue does not establish that it will pass the later check. Negative keywords take precedence when a profile matches both positive and negative terms.
Public profile information can be incomplete. Treat keyword matches as information to review, not proof that a person needs your offer.
Which settings should you review?
| Setting | What it controls | How to choose it |
|---|---|---|
| Source | Where candidates came from | Use a source with relevant relationship context |
| Keywords and other available filters | Which profiles meet your selection criteria | Inspect the underlying profile information |
| Hourly and daily controls | Configured activity volume | Follow your account's current notices and available actions |
| Schedule | When the workflow is enabled to run | Choose a window when you can review outcomes |
| Request messages | The content associated with a request workflow | Use a relevant introduction for the selected audience |
| Queue run control | Whether the queue is active | Pause while reviewing an error or changing the audience |
Read the values currently shown in your account before changing them. This guide does not prescribe numerical defaults or a universal safe sending rate. Facebook controls action availability independently of your queue settings.
A worked review example
Suppose five workshop attendees asked to stay connected. Confirm each profile against your attendee notes, add the relevant profiles to the queue, and retain the workshop context. If three have accepted at your review date, record three accepted and two pending.
That is an illustrative example, not a customer result or recommended sending volume. Use the acceptance-rate guide to compare cohorts at the same age. A request acceptance and a qualified sales conversation are separate outcomes.
Resolve an interrupted workflow
First read the exact Facebook notice. Pause the affected queue while checking an explicit restriction. If the issue is the browser connection, confirm you are signed into the intended account and that the extension is connected. Follow the request troubleshooting checklist for the appropriate next step.
Friender's profile-level suppression setting helps avoid repeating the relevant failed request. It is separate from an account-wide safety guarantee. Meta describes its own controls for preventing unwanted repeat contact.
Frequently asked questions
Is automatic sending the same as automatic acceptance?
Sending places a request for the recipient to consider. The recipient decides whether to accept. Review incoming requests separately from outgoing queue results.
Which plan should I choose?
Choose Advanced for targeted requests and automated request messages. Choose Pro when you also need labels, tags, Messenger campaigns, and automations. Review current plan scope and billing terms before selecting a plan.
What should I send after somebody accepts?
Use the relationship context and any request they made. The Messenger follow-up templates provide examples for requested resources, open questions, and agreed next steps.