Social Media Automation · Feature guide

Connect Threads and publish supported text or media

Authorise a Threads profile with the required publishing scopes and check the final thread after provider processing.

Audience: authorised staffReviewed 13 November 2026

Use these steps in your selected Pixie CRM company workspace. The module, dependent tools and actions available to you follow its configuration and your permissions.

Where to start

Social accounts → Threads; Configuration where applicable

Permission

Manage connections; administrator for app credentials; Create posts + Publish posts for a live test

Before you begin

An authorised Meta Threads application, its matching client credentials and the intended Threads test profile.

Follow these steps

In Configuration, copy the Threads 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 Threads Connect and complete the official Threads consent for the intended profile.
In Social accounts, choose Verify connection and compare the account or destination identity with the intended test account.
Use supported text, image or video content and keep the complete caption within 500 characters. Media can require asynchronous container processing.
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.

Fields and options

Requested OAuth permissions: threads_basic and threads_content_publish. These are the scopes requested by the current adapter; provider products/review must permit them.
Destination and scope: Threads credentials and scopes are distinct from a Facebook Page connection. Verify the discovered Threads identity before selecting it in the composer.
Publishing format: Use supported text, image or video content and keep the complete caption within 500 characters. Media can require asynchronous container processing.

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.

Check the result

Open the Threads profile and locate the actual thread. A receipt may contain a remote identifier without a public link.
Match the actual provider outcome to the destination receipt, remote reference and intended visibility.

If something does not look right

For media-container errors, inspect the existing receipt and fetchable media before creating another request. For login errors, check the Threads app callback and permissions.
Do not repeat Post Now after an ambiguous result until the original provider outcome has been checked.

Common questions

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.