If your connection is tested and ready for customers, prepare your materials for Meta’s official application and review. If you are still proving the idea, start with a small custom test. This independent guide does not accept applications, approve connectors, or determine listings.
APPLICATION SUPPORT PREPARE TO APPLY
Get help with your connector application
Prepare a finished connection for Meta’s official review and application process.
Best when real customers already want the task
You have a stable connection, safe sign-in, and test proof
Your next move: prepare the plan below, then apply
CUSTOM CONNECTOR TEST FIRST
Try the idea with early users
A small trial for learning whether people actually want the task before you pursue a public listing.
Best when the idea is new or unfinished
Test one task with a few trusted users
Collect five real requests and note what breaks
02 / READINESS CHECK
Is your product ready to connect with Muse?
Answer what you know. Choose “Not sure” when you need to ask your web or product team—we’ll translate the gap into a clear next step.
01
Can you name one useful thing Muse should help a customer do?Example: “Check an order and change the delivery date.” One job is stronger than a long feature list.
02
Can your product already share information with another app?Ask your developer whether you have a working API that returns clear answers and errors.
03
Can each customer safely connect and disconnect their own account?They sign in, choose what Muse may access, and can remove that access later.
04
Can Muse look something up without being allowed to change it?Viewing an order, balance, or booking should not automatically allow edits.
05
Will customers review the final details before anything important happens?Show what will happen before a message, order, payment, cancellation, or account change.
06
If Muse repeats a request, can your product avoid doing it twice?A retry should never create a second order, payment, message, or change.
07
Do you have the basics ready for someone else to test?A test login, privacy policy, short demo, and examples of what happens when something fails.
03 / MAKE A PLAN
Put the idea into a simple plan.
Give your product, engineering, and security teams the basics they need. Nothing is uploaded; copy or download the plan when you’re done.
Connector plan
LIVE DRAFT
MUSE CONNECTOR PLAN
===================
PRODUCT
[Product name]
ONE MAIN JOB
[Describe what Muse should help someone do]
THREE THINGS PEOPLE MIGHT ASK
[Add three real requests]
WHAT MUSE CAN DO
View only
HOW PEOPLE CONNECT THEIR ACCOUNT
[Describe how people sign in, choose access, and remove access]
MOST SENSITIVE ACTION
[Name the action that needs the most care]
WHAT PEOPLE SEE BEFORE THEY APPROVE
[Describe the plain-language summary shown before the action]
PROOF TO PREPARE
- A test account and simple sign-in steps
- A list of what Muse can view or change
- Examples of success, errors, and slow responses
- Proof that repeated requests do not create duplicates
- Privacy policy and terms
- A short start-to-finish demo
Use this as your team’s prep document. Meta’s application may ask for different details.
FREE CONNECTOR MESSAGE REVIEW
Make your connector easy to understand.
Send your plan for one focused note on what the connector does, why it matters, or how to explain it in the application.
Open review requestReview the draft in your email app, then choose Send when ready.
04 / GET READY TO APPLY
Turn the score into a working connector.
Each step ends with something concrete your team can review. Do not move to the next step until the current one works.
1
Prove the task
Collect five real customer requests for the same job.
2
Map the access
List what Muse may view, change, and what needs approval.
3
Try to break it
Test expired sign-ins, repeated requests, and slow responses.
4
Build the review packet
Prepare a test login, privacy policy, terms, short demo, and test steps.
Ready to apply?
Take your plan, check Meta’s latest requirements, and apply through the official Connector Platform.