What actually happens to your website on Shabbat?
A single form submission can create a CRM record, send emails, trigger webhooks, update analytics, notify sales, and start a billing flow. See what keeps running — and how to govern it.
- The hidden chain behind one click
- Which actions are passive vs business-generating
- Where Shabbat-aware controls fit
- Quick wins you can implement first
One click, many systems
A visitor who submits a form on Friday night can quietly set off a chain across your CRM, email platform, webhooks, analytics, and billing. This guide traces that chain step by step, so you can see exactly what your stack does on your behalf after sundown.
Passive vs business-generating
Serving a page or showing content is one thing; creating an order, charging a card, or pushing a sales notification is another. The guide separates passive actions from those that generate business, so you can decide what to pause, delay, or queue with intent.
Quick wins first
You do not have to redesign everything at once. The guide ends with a short list of high-impact, low-effort controls — the settings you can switch on first to bring Shabbat-aware governance to your most sensitive flows.
The hidden chain behind one form submission
When a visitor fills out a form on your site Friday evening, they see a confirmation screen. Behind that confirmation, your stack quietly runs a chain of automated steps — and most of them continue whether or not you are observing Shabbat. The six systems below are the ones most likely running on your behalf right now.
CDN & Web Server
Passive — continues normallyServing HTML, CSS, images, and static content is passive delivery. Your CDN and web server can continue to respond to requests during Shabbat without raising any concern.
Payment Gateway
Business-generating — review carefullyAuthorizing, capturing, or processing a payment creates a financial transaction. This is typically considered business-generating and should be deferred, paused, or queued for post-Shabbat capture.
CRM & Lead Capture
Business-generating — review carefullyCreating or updating a CRM record from a form submission initiates a sales workflow. The act of prospecting and lead acquisition during Shabbat is worth reviewing with your rabbinic authority.
Email Automation
Depends on content and triggerTransactional confirmation emails may be acceptable. Outbound sales sequences, promotional campaigns, and follow-ups triggered by a Shabbat form submission are business-generating and worth deferring.
Webhooks & Zapier Zaps
Business-generating — review carefullyA webhook is silent but its consequences are not. Zaps that notify sales, create records, or trigger further automations in third-party tools create business activity that extends well beyond your own servers.
Cloud Jobs & Cron
Classify per typeA nightly backup is maintenance. A billing renewal job, a subscription trial-expiry check, or a triggered fulfillment workflow is business-generating. Each scheduled job deserves its own classification.
What you can do
You have four practical options for every flow that could run on Shabbat. The right choice depends on the nature of the action and your rabbinic guidance.
Pause the flow
Temporarily disable the form, checkout, or trigger so no input is accepted during Shabbat. Visitors see a respectful message. The flow resumes automatically after Havdalah.
Delay the action
Accept the submission but defer the downstream action — CRM write, payment capture, webhook — until after Shabbat ends. The data is safely stored and processed in order at the release window.
Route to a non-observant handler
If your business cannot pause, route incoming events to a non-observant team member or an automated system that can act on your behalf. This keeps SLAs intact without requiring you to work on Shabbat.
Queue for post-Shabbat release
Send all events into a durable queue during Shabbat. After Havdalah, the queue drains in order — CRM records, payment captures, fulfillment events, emails — with a full audit trail per item.
FAQ
Does my website go offline on Shabbat if I use ShabbatCloud?
No. Your website stays fully online and continues to serve content. ShabbatCloud governs specific actions — form submissions, payments, webhooks — not the delivery of your pages and content.
Is serving a web page considered 'doing business' on Shabbat?
Serving a static page or displaying content is generally considered passive. The concern arises when the server takes a business action on your behalf — such as processing a payment, creating a CRM record, or firing a sales webhook.
What happens to orders placed during Shabbat?
With ShabbatCloud, orders are received and held in a durable queue. Payment capture, fulfillment, and CRM creation run after Shabbat ends, in the exact order they were received.
Do webhooks and Zapier Zaps actually run during Shabbat?
By default, yes — most platforms fire webhooks immediately on any trigger. ShabbatCloud intercepts these at the edge and holds them until the post-Shabbat release window, so nothing fires while you are offline.
Can I configure different rules for different forms on the same site?
Yes. Each form, endpoint, or automation can have its own policy — pause, delay, route, or queue — based on whether the downstream action is passive or business-generating. A contact form and a payment form on the same site can behave differently on Shabbat.
Ready to map your stack?
ShabbatCloud walks you through every system that can act on your behalf on Shabbat and helps you assign a policy to each one — before Friday arrives.