Use Worship Flow to keep local service state, Holy Resource operator devices, and ProPresenter aligned on the same network.

Worship Flow gives your team one place to follow the live service step, stay in sync across devices, and control ProPresenter when needed.

Worship Flow is built around one simple idea: one Holy Resource device can lead the service flow, and the other Holy Resource devices can follow along on the same local network.

What Worship Flow does

Keeps the active plan, section, item, slide position, and shared note inside Holy Resource on the local device.
Shares that service state with other Holy Resource devices on the same local network when they join the same team session code.
Lets the leader choose the event, plan, section, and item from real Holy Resource service-plan records.
Lets one Holy Resource device connect to ProPresenter to send slide commands, browse playlists, manage the stage message, and mirror the full current and next slide text into Worship Flow.
Keeps the last synced full lyrics available locally on joined devices if the ProPresenter connection drops during the service.
Keeps working in local-only mode even when ProPresenter is not connected.

What mobile includes

On phones and tablets, Worship Flow keeps the parts that matter in the room:

joining or starting the team session code
following or sharing the current event, plan, section, item, and shared note
viewing mirrored lyrics and cached lyrics after the presentation link drops
seeing which other Holy Resource devices are still joined

The ProPresenter bridge setup, playlist browser, and stage-message tools stay on the full operator console.

How device sync works

You do not need ProPresenter on every device.

In the usual setup:

The church has one main ProPresenter computer.
One Holy Resource device connects to that ProPresenter computer.
That same Holy Resource device starts the team session code.
The other Holy Resource devices join that same team session code.
Those other devices receive the same current plan, section, item, slide position, shared note, and any mirrored slide lyrics over the local network.

This means the media or tech team can keep ProPresenter on one machine, while the worship leader and other Holy Resource devices stay in sync through Worship Flow.

What “lyrics sync” means

Worship Flow shares the live service step, the shared note from Holy Resource, and the full current and next slide text that comes from ProPresenter when one device is connected.

It now listens to ProPresenter's live status update stream so lyric changes can show up faster than the earlier timed polling approach.

If your team is asking, “Do we all need ProPresenter installed?” the answer is no. Only the device that needs to control ProPresenter must connect to it. The rest of the devices can still follow the shared service state and the mirrored lyrics inside Worship Flow.

Why ProPresenter

Worship Flow uses ProPresenter as its first presentation bridge for a practical reason: it is widely used in churches and it exposes a public control API that covers the pieces Worship Flow needs most, including slide status, playlists, triggers, and stage messages.

That makes it a strong fit for the local operator model described on this page. One Holy Resource device can connect to the ProPresenter machine, follow the live presentation state, and share that state with the rest of the team over the local network.

Worship Flow is not limited to ProPresenter in principle, but it also does not treat every presentation product as the same. A presentation bridge belongs here only when it can support the same operator loop with dependable remote control, dependable live status, and a setup path that is realistic for churches during a service.

Third-party product notice

A few things to note:

Holy Resource is not affiliated with, endorsed by, or sponsored by ProPresenter or Renewed Vision.
Holy Resource is a separate product built by a different company, and it does not require ProPresenter to work. It only uses ProPresenter as one option for controlling slides and mirroring lyrics when that is helpful for the team.
Holy Resource does not have access to ProPresenter's internal data or user accounts. It only interacts with ProPresenter through the public API when you choose to connect it.
Holy Resource does not share any data with ProPresenter or Renewed Vision. It only shares the current slide text and status updates from ProPresenter with the other Holy Resource devices on the same local network when you connect it.

Before you connect ProPresenter to Worship Flow, review ProPresenter's own product details and policies so your team understands their licensing, privacy, support, and operating terms:

Why this matters

Many worship teams still split their workflow across multiple products:

a planning tool for service order and volunteer scheduling
a presentation tool for lyrics and stage display
a separate tracks or cue tool for rehearsal and live playback

That stack can work, but it also creates handoff friction. Leaders end up managing the plan in one place and the live service in another. Worship Flow helps by making Holy Resource the place where the live service step is shared first and then passed to the rest of the team.

Basic flow

Open Worship Flow on the operator device.
Start a shared team session code for the current service.
If you want slide control and live lyric mirroring, connect that device to ProPresenter by scanning likely hosts or entering the host and port manually.
Choose the current event, service plan, section, and item from Holy Resource.
Share the current step with the team, then use the operator controls to advance slides, browse playlists, or show a stage message.
As slides move in ProPresenter, Worship Flow listens to the live update stream and mirrors the current and next slide text to the other joined devices.

Starting and ending a session

When you press Start session, Worship Flow does not create a timed meeting that ends by itself after a fixed countdown.

Instead, that device starts broadcasting the shared service state on the local network for the session code you chose.

The session stays active on that device until you end it there.
If that device closes, loses the app runtime, or stops broadcasting, other devices stop seeing it after a short timeout.
In Worship Flow, that timeout is about 15 seconds for peer visibility.

If you want to stop the session from one device, use End session on this device in the Team session card.

That ends broadcasting from that device and clears the local peer list there. Other devices stop treating it as live once the last heartbeat ages out.

Connect ProPresenter

This is the usual setup when ProPresenter is on a separate media computer.

What you need first

The ProPresenter computer and the Holy Resource device need to be on the same local network.
ProPresenter needs to be reachable through its public API on the ProPresenter machine.
The default API address uses port 50001.
If the Holy Resource device is not the same machine as ProPresenter, do not use 127.0.0.1. Use the ProPresenter computer's local network address instead.

Connection path

Step-by-step

Open Worship Flow on the Holy Resource device that will control ProPresenter.
Go to the Presentation connection card.
If ProPresenter is running on the same device, you can try 127.0.0.1 with port 50001.
If ProPresenter is running on another computer, enter that computer's local network IP address instead.

Finding the local network address

On Windows, run ipconfig in Command Prompt and look for the IPv4 address under the active network adapter.
On macOS, run ifconfig in Terminal and look for the inet address under the active network interface (like en0 for Wi-Fi).
On Linux, run ip addr in Terminal and look for the inet address under the active network interface.

Keep the port as 50001 unless your ProPresenter setup uses a different API port.
Press Connect.
If you are not sure which address to use, try Scan this address for the likely host or connect from a discovered result.
After the connection succeeds, Worship Flow should show a linked presentation state and begin mirroring current and next slide text when ProPresenter reports it.

Quick checks if it does not connect

Make sure ProPresenter is running on the target computer.
Make sure you are using the ProPresenter computer's LAN address, not localhost, when connecting from another device.
Make sure both devices are on the same Wi-Fi or Ethernet network.
If the connection worked before and then stopped, use Refresh status and check the reconnecting message in the Presentation connection card.

Operator screen sections

Team session

The Team session card is where you set the shared code for the current service. Every Holy Resource device that uses the same code can receive the live service state over the local network.

ProPresenter bridge

The ProPresenter bridge card is used to scan likely hosts, connect manually, and watch connection health. Only the device that needs to control ProPresenter has to connect here. Holy Resource keeps trying to reconnect if the connection drops during the service, while the last synced lyrics remain available across joined devices.

When the link is healthy, Worship Flow listens to ProPresenter's live status updates so lyric changes reach the joined Holy Resource devices with less delay.

For a practical setup path, use the Connect ProPresenter guide above.

Live service controls

The main service controls are where you choose the live event, plan, section, and item from your real service data. You can share that step with the team, send a note or quick update, repeat a section, control slides, browse playlists, and update the ProPresenter stage message.

Shared lyrics

The Shared lyrics area shows the full current and next slide text mirrored from ProPresenter. If the ProPresenter link drops unexpectedly, the last synced lyrics stay visible on the joined Holy Resource devices until a new update comes in.

Current app relationship

Related foundations already exist elsewhere in Holy Resource:

Events -> OOS Components for reusable service-plan building blocks.
Events -> Service Plans for event-level order-of-service work.
Volunteers for scheduling and assignment workflows.

Worship Flow does not replace those areas. It sits on top of them as the live operator layer.

Worship Flow appears when it is available in your Holy Resource setup.

Notes for operators

If you do not connect ProPresenter, Worship Flow still works for Holy Resource device-to-device sync on the same LAN.
Only the device that will control ProPresenter needs the ProPresenter connection.
Use one clear team session code per service so the correct devices join the same session.
When ProPresenter is connected, Worship Flow mirrors the current and next slide text into the shared local session.
If the ProPresenter link cuts during the service, joined devices keep the last synced lyrics locally until new lyric data is received.
If the ProPresenter bridge drops, the screen will show a reconnecting state while Holy Resource keeps the local service state alive.
Hard-wired networking is still the safest choice when you are driving slides live.

Module scope

Worship Flow is the live operator layer inside Holy Resource. Its job is to keep the active service step, joined devices, and presentation bridge aligned during the service.

It does not replace your planning tools, rehearsal tools, or presentation software. It sits between them where teams usually feel the most friction: the handoff from the prepared plan to the live moment in the room.

Introduction