Planning Center

KERYX can connect to Planning Center Services (PCO) on both the web and the desktop app, to bring in your church's plans and song library instead of rebuilding them by hand.

#Signing in with Planning Center

#On the web

Sign in with Planning Center on the login page sends you to Planning Center's own sign-in screen, then back to KERYX. Only people who belong to your church's Planning Center organization are let in — it checks your PCO organization on the way back and rejects anyone else, so this button can't be used to create an account at a different church.

#On the desktop

Nothing to sign in to. The Mac reaches Planning Center through KERYX Cloud, using the connection set up on the web. Once the Mac is signed in to KERYX Cloud, Settings → Accounts → Planning Center shows Connected through KERYX Cloud.

#Importing plans

#On the web

Import from Planning Center on the Services dashboard (only shown once Planning Center sync is configured) opens a list of upcoming plans across every service type — title, service type, and date. Click Import on one and KERYX builds a new draft service from it and opens it.

#On the desktop

The download-arrow button in the top toolbar of the service editor — Import next plan from Planning Center — pulls in the nearest upcoming plan in one click, using whichever service type is set in Settings → Accounts → Planning Center → Service type to import from. If several service types exist in Planning Center and none is chosen, it instead switches you to the Services screen so you can pick the plan yourself.

#What comes across

Whichever side does the import, a plan turns into a service the same way:

• Songs on the plan become song items, in order, with the plan's own item length carried over as a planned duration.
• Scripture readings are detected from the item's title (or its description, when the title itself says "Scripture," "Reading," or "Passage") and the passage text is filled in automatically.
• Everything else — sermon, welcome, offering, and so on — comes in as a placeholder item, so the running order and its timings stay complete even though there's no slide content yet.
• Section headers in the plan (dividers like "Pre-Service" or "Message") are skipped — they aren't slides.

#How songs come across

Song sync (Sync songs from Planning Center on desktop, Import from Planning Center on the Songs page on web) pulls your whole Planning Center song library into KERYX:

• Matching order is Planning Center ID → CCLI number → song title, so songs you already have (including a library imported from elsewhere) get linked to their Planning Center counterpart instead of duplicated.
• Lyrics are only pulled in for songs that don't already have any. If a song already has lyrics in KERYX, sync leaves them alone and only refreshes title, author, copyright, and CCLI number — your local lyrics are treated as the trusted copy.
• Lyrics themselves come from the song's arrangement in Planning Center (the songs list itself doesn't carry lyrics) — specifically the first arrangement that has lyrics or a chord chart. A song's arrangement sequence also becomes its default section order (e.g. V1 C V2 C B C) in KERYX.

#Song matching during a plan import

When a plan import meets a song, it looks it up by its Planning Center link:

• On the desktop, an unmatched song is created locally on the spot, using that song's title, author, copyright, and CCLI number from Planning Center (and its lyrics, if it has any) — so importing a plan can add new songs to your library as a side effect.
• On the web, a plan import does not create new songs — a song with no existing match comes in as a plain item titled from the plan, without a linked song or lyrics. Run Import from Planning Center on the Songs page first (or import the plan from the desktop) if you want it linked.

#Known limits

• A plan import only follows up to 200 items per page (with a hard cap on how many pages it will follow), so an extremely long plan could in principle be truncated — not something you're likely to hit in a normal Sunday plan.
• Scripture detection is a heading-based guess, not a Planning Center field — an unusually worded item title may need its reference added by hand after import.
• The web sign-in and the desktop's OAuth sign-in are expected to use the same Planning Center OAuth application — that's set up once by whoever configures KERYX, not something you choose per sign-in.