Getting started with Canary

About five minutes, most of it waiting for the first scan.

Install

Install Canary on the client accounts you want watched. The consent screen asks for three read-only permissions. If you add a client later, Canary shows it as not yet covered and links you straight to the install - nothing slips through silently.

Install Canary

Consent screen - what you will be asked to approve
[x]oauth.readonly  list your client accounts
[x]oauth.write     read each account in turn
[x]account.readonly  see connected social accounts
Allow & install

Read permissions only. Canary cannot post, send, or change anything.

Wait for the first scan

Canary reads the expiry date on every connected account. The first pass usually finishes in a few minutes. It is common to find one or two connections already inside the warning window.

$ canary scan --first-run
scanning accounts ............... ok 12 client accounts found 47 connections read 2 already within the warning window northside-dental facebook 6d harbor-fitness instagram 13d
done in 2m 14s

Add your domains

Email authentication and SSL checks run against public DNS and the public certificate log, so they need to know which domains to look at. Paste the domains you send email from and the domains your funnels and sites are published on.

Settings → domains
mail.northsidedental.com✕
go.harborfitness.co✕
add a domain…+

The one manual step - these cannot be discovered automatically. Checked daily afterwards.

Where alerts go

To the email of the first admin who opens Canary - one message at 14, 7 and 2 days before anything runs out, with a link to the fix. To use a different address, write to contact@jimapps.dev from the current one.

Reconnect when warned

Canary tells you which client account, which connection, and the exact date it runs out. Reconnecting is done in the client's own account - here is how. The warning clears as soon as you open Canary again.

$ canary status northside-dental
facebook reconnected expires 2026-12-01 66d
One thing to know up front. Canary tracks scheduled expiry. If a client revokes access early - removes the app, changes a password, drops a page permission - the platform API still reports the connection as valid, so that case is invisible to Canary and to any other tool reading the same data.

Next

Full documentation covers the checks, schedules and permissions in detail. Anything not answered there - support.