Meta Muse Connector Guidelines, Explained

Meta's connector guidelines explain what a service must provide to get approved on Muse. They cover the work a connector must complete, the permissions it asks for, how it handles user data, and what Meta checks before listing it.

Read the official guidelines for the source requirements and submission details.

Core requirements

An approved connector should finish the user's task from start to finish. That can include finding an item, completing checkout, confirming a status change, cancelling a service, or requesting a refund. It should not send the user back to a website to complete the important step.

The connector also needs to offer something beyond what Muse's browser can already do. A connector should provide a useful, reliable integration rather than recreate a basic browser visit.

Tool permissions

Muse groups tools by the kind of access they need:

• Read. Looks up information without changing an account or transaction.
• Write. Changes account or service data, such as updating a setting or creating an order.
• Sensitive write. Performs an action with higher impact, such as a financial or account-critical change.

OAuth can be set up as read-only when the connector only needs to look things up. When an action needs approval, Muse gives the person choices such as Allow once, Always allow, or Deny. Sensitive writes ask every time. Approval also has a defined scope. If the details of an action change, the connector must ask for fresh approval instead of reusing the old one.

Trust and integrity

Connectors should collect the least data needed for the job and should not reuse it for unrelated purposes. Their descriptions and results need to be accurate and clear, including what an action will do and whether it succeeded.

Meta expects reasonable security controls, honest tool behavior, and no practices that mislead people, hide important effects, bypass consent, or use access for an unrelated purpose. Finance connectors may offer read access, but tools that move money are not currently approved.

Transactions need clear disclosure before the user commits, including the relevant business and action. Connector operators must report a security or integrity incident within 48 hours. Meta can limit, suspend, or remove a connector when it fails these expectations.

Submission and review

A submission includes five pieces:

1. A connector overview.
2. Business verification details.
3. A data processing questionnaire.
4. Integration credentials and tool documentation.
5. A test account and demo.

Meta reviews the submission in three stages: a risk assessment, a tool review, and end-to-end quality assurance. The process checks both the written details and the connector running through a real user journey.

Discovery after approval

Approved connectors appear in Settings → Connectors. Being listed is separate from being featured. Featuring is an editorial decision based on usefulness, task completion, reliability, and ongoing maintenance.