Workflow recipes

Each recipe below is a complete workflow: a trigger, optional filters, and an action. Build it under Settings → Workflows with Create workflow.

Confirming new bookings automatically

Create a workflow with trigger Status reached → Confirmed, action Send email, and pick your confirmation template. From now on, every booking that reaches Confirmed sends the client a confirmation message.

Reminding clients before their appointment

Use trigger Relative time reached, relative to Booking start time, direction Before, offset 1 day. Pair it with a friendly reminder template. Requiply will send the reminder for every future booking without further work.

Messaging a client a reminder over SMS, Viber, or Telegram

First connect a provider on the Communications page and write a message template with the client name and booking time. Then use trigger Relative time reached, relative to Booking start time, direction Before, offset 1 day, with action Send message to client, the channel your provider supports, and that template. Clients are reminded on their phones automatically. (Use Booking created instead for an instant confirmation, or Payment status reached for a payment follow-up with a payment link.)

Sending Telegram only to clients who can receive it

Add a filter on Client · Telegram connected — Yes to a Telegram workflow so it skips clients who never opened your bot. Pair it with a second workflow filtered on No that reaches the same clients over SMS, and everyone gets the notification on whatever channel they actually have.

Notifying the assigned manager, not the client

Use action Send email to organization accounts (or Send push notification to organization accounts) and pick the team members who should be alerted. Because these go to real Requiply accounts, they're better than a typed list when you want the message to reach specific people on your team, for example to ping the manager when a booking is confirmed. To alert a whole team instead of named people, use the group action below.

Alerting the warehouse before a pickup

Use trigger Relative time reached, relative to Booking start time, direction Before, offset 2 hours, and action Send push notification to account groups with the Warehouse group. Write a title such as Pickup #{{bookingId}} in 2 hours and set the tap action to Open booking #ID. Everyone in the group at that moment gets the push and lands on the booking with one tap, including people who joined the group after you built the workflow.

Confirming a booking once it is paid

Use trigger Payment status reached → Completed, add a filter Booking status is New, and action Change booking status to Confirmed. Paid bookings move to Confirmed on their own, and any Status reached → Confirmed workflow, such as your confirmation email, runs right after.

Only confirming high-value bookings

Use trigger Status reached → Confirmed, then add a filter Total cost — greater than — 500. The confirmation only fires for bookings above that amount.

Targeting VIP clients or a single location

Add a filter on a client's Pricing discount — is any of — … to reach only your VIP tier, or filter on a Booking custom field (such as a location) to limit a workflow to one site.

Combining AND and OR conditions

For "weekend bookings or anything over $300", put two conditions in the same group (OR). For "weekend bookings and over $300", put each condition in its own group (AND). Always read the "Only when" preview before saving to confirm the logic.

Chasing failed payments

Use trigger Payment status reached → Failed (or your equivalent), action Send email to the client, and a template that explains how to retry payment.

Pausing a workflow without losing it

Turn off the switch in the workflow's card on the Workflows page (or the Enabled switch inside the workflow). The card fades and shows Disabled, and the workflow keeps its full configuration but stops firing until you turn it back on. Better than deleting if you only want a temporary pause, for example a review request during a holiday closure.