Social Media Automation
Connect Facebook Pages and publish a Page post
Authorise the Facebook Page you manage, select the correct destination and verify a controlled Page publication.
Where to start
Social accounts → Facebook; Configuration where applicable
Fields and options
- Access needed
- Manage connections; administrator for app credentials; Create posts + Publish posts for a live test
- Requested OAuth permissions
- pages_show_list, pages_read_engagement and pages_manage_posts. These are the scopes requested by the current adapter; provider products/review must permit them.
- Destination and scope
- The current adapter publishes to authorised Facebook Pages, not personal profile timelines. Check the Page identity rather than relying only on a similar display name.
- Publishing format
- Prepare a text post or supported image/video. The composer’s main-caption field remains limited to 5,000 characters even though Facebook permits a larger provider caption.
Before you begin
An organisation-owned Meta developer app with Facebook Login and the relevant Page permissions; a test Facebook identity with authorised Page access.
Follow these steps
- In Configuration, copy the Facebook application callback into the matching provider app. Save its matching ID and secret with Save encrypted credentials. Leave direct publishing locked during connection setup.
- Choose Facebook Connect, approve the official Meta consent and select the intended Page when discovery offers more than one destination.
- In Social accounts, choose Verify connection and compare the account or destination identity with the intended test account.
- Prepare a text post or supported image/video. The composer’s main-caption field remains limited to 5,000 characters even though Facebook permits a larger provider caption.
- When a controlled test is authorised and the direct gate is enabled, select only this destination, choose Post Now once and inspect its existing receipt.
Check the result
Open the actual Page and check the post, media and intended audience. A successful login to a personal account does not prove Page publishing access. Match the actual provider outcome to the destination receipt, remote reference and intended visibility.
If something does not look right
If no Page is discovered, check Page administrative access, the granted Page permissions and whether the app/test identity can use the configured app. Do not repeat Post Now after an ambiguous result until the original provider outcome has been checked.
Fields, rules and limits
- Saving credentials or passing connection verification does not prove that a live publication succeeded.
- Use a dedicated test destination and the most restrictive appropriate visibility. Provider consent, app review and organisational approvals remain separate requirements.
Questions and answers
Does a connected account mean publishing is approved?
No. Connection identity, app publishing entitlement, content eligibility and the separate direct-publishing gate are independent checks.
What is a complete first test?
Official consent, correct destination discovery, successful verification, one deliberate test publication, a destination receipt and direct verification in the actual provider account.
Related technical reference: Britixo's detailed product guide (opens in a new tab). The screens available to you depend on your configured modules, company and permissions.
Useful next steps
- Social Media Automation: account setup to verified publication
- Configure social provider apps and exact OAuth callback URLs
- Publish with Post Now and verify every destination receipt
Contact the Proplix team if you need help with your setup. Include the page or record reference and a description of the issue; leave passwords and private access tokens out of the message.