Service Source edition 1.0.4
Booking & Calendar
Turn available time into confirmed work.
Offer timezone-aware appointment availability, durable holds, confirmation, rescheduling, and cancellation, with optional Google Calendar, Stripe deposits, and reminders.
Example scenario
Reserve a consultation and keep its history
A customer chooses an available consultation time in their timezone. Hold the slot while confirmation or a configured deposit is completed, then retain the booking through a later reschedule or cancellation.
From setup to the result
- Configure resources, working hours, and an IANA timezone.
- Offer a slot and save a time-limited hold.
- Confirm the appointment and any required verified deposit.
- Update changes, calendar jobs, and permitted reminders through the worker.
What the package handles
What you can build with it
- Resource hours, fixed durations, buffers, lead time, and booking horizon.
- Transactional local holds and saved appointment changes.
- Google Calendar jobs, reconciled Stripe deposits, and opted-in Resend reminders.
Supported behavior
- Node 22/PostgreSQL 17
- IANA timezones
- Google Calendar free/busy and event jobs
- Stripe Checkout payment deposits
- Resend reminders
Before you choose
Will it fit your project?
Who it is for
- Consultants and appointment-based businesses.
- Teams booking shared staff or resources.
- Businesses that need deposits and calendar events to stay in sync.
Runtime and connections
Current packages run on Node.js 22.13+ and PostgreSQL 17. You provide hosting and connect the package to your existing app. The included guide describes the supported integration; this is not a hosted service.
Depending on the features you enable, setup can require your own Stripe, Resend, Google Calendar accounts and credentials. Their usage, plans and transaction charges are separate from the source purchase. Check the supported behavior below before choosing a connection.
A useful handoff to your coding agent
How setup works
The source package includes local setup instructions, an integration guide, examples, help articles and verification resources. Your agent can use those files without signing in to a hosted reference page.
- Check the requirements. Your agent inspects the application, runtime, database and supported connections before making changes.
- Configure your installation. Answer the product-specific questions below, connect your own accounts where needed and retain the configuration privately.
- Connect and verify. Use the included checks and a representative workflow, then verify any chosen external service separately before relying on it.
Questions to prepare
- What can customers book, for how long, and when is each resource available?
- Is a deposit required, and what are its amount, currency, and return pages?
- Which Google calendar belongs to each resource?
- Should opted-in customers receive a reminder, and from which verified sender?
What your agent checks
- Prevent simultaneous local holds from claiming the same capacity.
- Check timezone, buffer, rescheduling, and cancellation rules.
- Keep late deposits out of a released slot and inspect calendar/reminder outcomes.
Scope of this edition
Important limits
One resource per reservation and one fixed appointment duration per installation. Local holds cannot atomically lock independent changes in Google Calendar. Cancellation refunds, multi-resource bundles, and tax accounting require separate work.
- One resource per reservation; fixed duration per installation
- Local reservation locking cannot atomically lock independent changes in Google Calendar
- Deposits do not implement cancellation refunds or tax accounting
- Customer identity must come from an authenticated integrating application
Before you decide
Will this work with my existing app?
The package runs on Node.js 22.13+ and PostgreSQL 17. Your coding agent connects it to your application using the included integration guide and supported interfaces. Check the requirements, supported behavior and limits on this page; compatibility with every framework or hosting provider is not promised.
What will my agent need from me?
Your goals, the relevant app details and permission to configure your own accounts. The setup questions on this page help prepare that handoff. Keep credentials in your own private environment; do not paste secrets into a public support request.
What happens if setup fails?
The package includes verification and troubleshooting resources so your agent can inspect the failure and resume the documented setup. Initial setup and reproducible-defect support lasts 30 days from purchase. The refund policy covers material defects we cannot fix, alongside applicable statutory rights.
Is this a subscription?
Helpful Mods sells the source package once. There is no monthly maintenance subscription or automatic renewal. Hosting and connected services have their own costs. Optional major upgrades require a separate purchase.
Can I buy this now?
Purchases are not open yet. You can inspect the product information and use the library planner while checkout is being prepared. A plan is not an order and does not grant source access.