Integrations & connections

OAuth connection flow and redirect URIs

Learn what happens when you connect a platform, why permission screens and redirect URLs matter, and how to troubleshoot common connection issues.

6 min readLast updated: May 2026

FliklyPlatform permission screenSecure redirectConnected account

Choose platform in Flikly

Approve permissions

Return to Flikly

Connection ready

When you connect a social or content platform, Flikly uses a secure authorization flow. You approve access on the platform’s own screen, then return to Flikly to finish setup—without sharing your platform password.

What OAuth means in Flikly

OAuth is the secure handoff many platforms use when you connect an external tool. Instead of giving Flikly your platform password, you sign in on the platform (if needed) and approve access on that platform’s permission screen.

Flikly only receives the access the platform allows after you approve the request. You stay in control of what you grant, and you can disconnect later from Flikly or from the platform’s own account settings.

The connection flow

1You choose a platform from Flikly.
2Flikly sends you to the platform’s secure authorization screen.
3You sign in to the platform if needed.
4The platform shows the permissions Flikly is requesting.
5You approve or cancel the request.
6The platform sends you back to Flikly using a redirect URL.
7Flikly confirms whether the connection was successful.

Finish the full flow in the same browser session when possible. Closing the permission window early can stop the connection before Flikly can confirm it.

Why redirect URIs matter

A redirect URI is the safe return address the platform uses after you approve or cancel access. It tells the platform where to send you back—usually to Flikly—so the connection can be completed.

Platforms typically require that return address to match the one configured for the app. If the return address is wrong, missing, or blocked, the platform may stop the connection and show an error.

Do not manually edit redirect URLs in the browser address bar.
Always start connections from the Connect button in Flikly.
If you see a redirect error, retry from Integrations or contact support with the exact message shown.

Permissions explained

Profile or account access

Lets Flikly identify which account you connected so the right profile, page, or channel appears in your workspace.

Publishing access

Allows Flikly to prepare, schedule, or publish content on your behalf when you use publishing features.

Page, channel, or workspace access

Some platforms require access to a specific page, channel, board, community, or workspace you manage.

Analytics or performance access

Depending on the platform and your plan, Flikly may request read access to help you review performance.

Actual permissions vary by platform and by the feature you are using.

What can cause a connection to fail

You are signed in to the wrong platform account.
The platform account does not have the right page, channel, or admin access.
The permission screen was closed before you finished approving access.
Browser popup, cookie, or session settings interrupted the flow.
The platform rejected the redirect back to Flikly.
The platform requires app review, a specific account type, or provider-side approval.
The connection attempt expired before you completed approval.

Safe troubleshooting checklist

1Start again from Flikly’s Integrations page.
2Use the same browser tab until the flow completes.
3Make sure popups and third-party sign-in screens are allowed.
4Confirm you are signed in to the correct platform account.
5Select the correct page, channel, board, community, or workspace when prompted.
6Approve the requested permissions.
7Return to Flikly and confirm the account appears as connected.
8If it still fails, contact support with the platform name, time of attempt, and the error message shown.

For workspace owners and admins

Make sure the person connecting the account has the right role on both Flikly and the external platform.
For brand pages, channels, boards, or communities, platform-side admin or manager access may be required.
If a teammate cannot connect an account, ask them to confirm their platform role and try again from Integrations.
Plan limits may affect how many platforms or accounts can be connected, depending on your subscription.

Common issues

Why did the platform ask me to sign in again?

The platform may need to confirm your identity before it can grant access. Sign in with the account you plan to connect, then continue the approval screen.

Why did I return to Flikly without a connected account?

The flow may have been canceled, expired, or blocked before approval finished. Start again from Integrations and complete every step on the platform screen.

Why does the platform say the redirect URL is invalid?

Retry from the Connect button in Flikly. Do not edit redirect URLs yourself. If the error continues, contact support with the exact message shown.

Why are some permissions required?

Permissions let Flikly prepare, schedule, publish, or measure content depending on the platform and the features you use. You approve them on the platform’s own screen.

Why can I connect but not publish?

Publishing may require additional platform permissions, account type, page or channel access, app review, or content that meets platform format rules.

Can I change permissions later?

You can usually disconnect and reconnect from Flikly, or revoke access from the platform’s own account or security settings.

Next steps

Continue with these Integrations & connections guides.

Still need help?

Visit the Help Center or contact support if you need help completing a platform connection.