Heartbeats is still being built. This page maps the accounts and access the planned setup is expected to need; it is not an install guide, and the project source does not yet confirm every detail.
Requirements are subject to change
01 / ACCOUNTS & ACCESS
What to expect
AExpected
Spotify Developer app
For a personal setup, expect to sign in to the Spotify Developer Dashboard with your Spotify account and create an app for Heartbeats. The app supplies credentials for Spotify access; the account that owns a Development Mode app currently needs an active Premium subscription.
Spotify currently limits Development Mode to one client ID per developer and five authenticated users per app.
You will authorize the Spotify account whose playlist Heartbeats updates. The callback address and exact permissions depend on the finished code.
The planned architecture uses Trigger.dev to run the daily check on a schedule. Expect to create a Trigger.dev account and project, then deploy the Heartbeats task and keep its credentials in that project's environment settings.
The Free plan currently lists $5 in monthly usage credits and up to 10 schedules.
That schedule count may fit one daily job; actual compute usage could still exceed the included credits.
Plan limits and prices can change. Check them before deployment.
If Discord notifications ship, you can provide a webhook URL for a channel in your server. Or create one in Discord's Server Settings → Integrations. Creating or editing a channel webhook requires the Manage Webhooks permission; a server admin can create it for you.
A webhook URL lets the service post into its selected channel.
Treat the URL like a password and save it only in the service's secret settings.
Whether Discord is required or optional is not confirmed by the current project source.
Have the source playlist link ready. The project has not confirmed whether it will read a public playlist page or use Apple Music API access, so playlist visibility and any Apple developer enrollment requirement are not settled.
If it uses Apple Music API, Apple requires a signed developer token from an Apple Developer Program member.
Do not enroll in an Apple developer program just for Heartbeats until its import method is decided.
Spotify's current Developer Policy says applications must not integrate with content from another service. It also describes a limited exception for transferring metadata from a user's playlists to another service. Heartbeats starts with an Apple Music playlist and writes a Spotify copy, so the fit is not obvious; resolve it before inviting users to deploy. This page does not determine whether Spotify would approve the design.
The source code has not yet confirmed the required OAuth scopes, callback URL, secret names, Node.js version, deployment path, first playlist copy process, playlist visibility, or whether Discord is optional. These should be written down once the implementation exists.
03
Project access
The GitHub repository is private today, so this public page cannot be used to install Heartbeats yet. A usable release needs accessible source code and a checked setup walkthrough.
