Connection troubleshooting

Authorization did not finish#

Return to Settings → Integrations and inspect the connection state. A closed consent window or an expired callback may leave setup incomplete. Start a fresh authorization from the correct account rather than manually editing the callback URL.

No eligible resources#

Check that the provider account can access the intended property, page, repository or collection. Some providers require a resource to exist before authorization can discover it. Follow the provider-specific guide’s “No resources” advice.

Grant only the permissions needed for that resource. Broader personal-account access is not a safe substitute for correctly configured business permissions.

Connected but not synchronized#

Inspect sync history and any source error. A token may be valid while a selected property is missing, a quota is exceeded or the provider is unavailable. Check the resource selection and last successful sync before reconnecting.

Platform configuration needed#

Some connectors require an approved Obelo provider application or licensed service. If the interface identifies a platform issue, contact the team. Customer credentials cannot repair missing platform provisioning.