An OAuth connection that says "success" has only proved one thing: someone clicked Allow. It hasn't proved that the right account came in, that the person who clicked had enough access to publish, or that the connection will still be alive next month. Run seven checks in the ten minutes after a connect, before anything touches the calendar.
TLDR: Treat every new connection as pending until you've checked the account name, the platform type, the authorizer's role, a test draft, the expiry date, the naming and the workspace assignment. In Mydrop's data, the most common hard failure when publishing was an expired platform connection, so the last check is a date in your calendar.
Seven post-connect OAuth checks, in order
| # | Check | How to run it | What a fail looks like |
|---|---|---|---|
| 1 | Right account | Compare the imported name and handle with the client's live profile | A personal profile or old page came in |
| 2 | Publishing profile | Confirm it's a page or business account, not a service link | Google Drive or Photos shows up as a "profile" |
| 3 | Authorizer's role | Ask who clicked Allow and what role they hold on the page | Connects fine, fails when you publish |
| 4 | Test draft | Create a draft and open the platform preview | Missing options or a permission error |
| 5 | Expiry | Note when the connection needs to be refreshed | A post fails on a Monday morning |
| 6 | Naming | Rename to client, brand and platform | Three profiles all called "Main" |
| 7 | Workspace | Assign it to one client workspace only | A profile visible to the wrong team |
Check the import list before you confirm anything
The authorization screen shows everything the signed-in person can reach. When a client has a dozen sub-brand pages, it's easy to click and import all of them.
Keep a simple rule: import official brand profiles and regional pages, skip test sandboxes and personal profiles. Cleaning up a "connect all" import takes longer than choosing carefully. In Mydrop, new connections arrive as pending, so you can name each one and archive the rest before it reaches a production calendar. The step-by-step version is in how to safely import multi-brand profiles via OAuth.
Ask who clicked Allow, then check their role
This is the check people skip, and it's behind most "it connected but won't post" tickets. The connection carries the access of the person who authorized it.
- If the client's intern authorized with a low role, publishing can fail even though the import looked perfect.
- If the person who authorized later leaves or loses admin rights, the connection can break with them.
Write down the authorizer's name and role next to the profile. If it's a single person, ask a second admin to be a named backup. Our guide on role-based permissions shows how to split who can connect, who can approve and who can only comment.
Run a test draft before the first real post
A draft with the platform preview open tells you in a minute what a status label can't. Use post preview to confirm the account, the image ratio options and the caption limits look right for that platform. If the draft can't be created or previewed, fix the access now, while the client is still on the call.
Don't publish a test post to a live client audience unless the client agreed to it. A draft and a preview are enough for most platforms.
Put the expiry date on a calendar you actually read
Connections don't last forever. Platforms expire them, and password or role changes can break them. In Mydrop's data on posts published in the 30 days to 16 September 2026, 98.5% went live at the first attempt, and the most common hard failure was an expired platform connection.
So the seventh check isn't about today. Add a recurring weekly slot to look at your connection list, and re-authorize anything that shows a warning. When a connection has already gone stale, when to force re-authentication explains how to decide quickly.
Send the client a two-line confirmation
Close the loop in writing. Tell the client what you connected, which role authorized it and how they remove your access if they ever want to. It costs two lines and removes the doubt that makes clients ask for passwords in the first place.
Next step: pick the last connection you made and run checks 3 and 5 on it today. Those two catch the most expensive failures. To run this on several client accounts, start free with Mydrop and connect your first profile.
Google review
Trustpilot review
Product Hunt comment
