> For the complete documentation index, see [llms.txt](https://docs.flowbookings.io/knowledgebase/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flowbookings.io/knowledgebase/integrations/zapier-integration-guide/available-triggers.md).

# Available Triggers

Triggers start your Zaps automatically when something happens in your FlowBookings account.

### How Triggers Work

When you use a trigger, Zapier checks your FlowBookings account for new or updated items every few minutes. When it finds something that matches your trigger, it starts the Zap and runs your automation.

**Note:** How often Zapier checks depends on your plan. Free plans check every 15 minutes, while paid plans check every 1-5 minutes.

***

### New Booking

Triggers when a customer creates a new booking in your account.

#### When to Use This

* Send a Slack notification to your team
* Add the booking to a Google Sheet for tracking
* Create a calendar event in Google Calendar
* Send a welcome email to the customer
* Create a task in your project management tool

#### What Information You Get

When this trigger fires, you'll receive all the booking details:

* Customer name and email
* Service name
* Booking date and time
* Booking status (PENDING or APPROVED)
* Price
* Any custom form data the customer submitted

#### Example Use Case

**Scenario:** You want to get notified in Slack every time someone books a consultation.

**Setup:**

1. Trigger: New Booking
2. Filter: Service equals "Strategy Consultation" (optional)
3. Action: Send channel message in Slack

**Result:** Your team gets instant notifications without manually checking FlowBookings.

***

### Booking Cancelled

Triggers when a booking is cancelled by you or the customer.

#### When to Use This

* Send a cancellation confirmation email
* Remove the event from your calendar
* Update your availability tracking
* Trigger a follow-up sequence to reschedule
* Log cancellation reasons in a spreadsheet

#### What Information You Get

You'll receive:

* Customer details
* Original booking information
* Service that was cancelled
* Cancellation timestamp

#### Example Use Case

**Scenario:** You want to track cancellation patterns to improve your business.

**Setup:**

1. Trigger: Booking Cancelled
2. Action: Add row to Google Sheets
3. Include service name, cancellation date, and customer info

**Result:** Build a database of cancellations for analysis.

***

### Tips for Using Triggers

#### Use Filters to Focus

Add filters to your Zaps so they only run for specific conditions. For example:

* Only trigger for high-value bookings (price > $100)
* Only trigger for specific services
* Only trigger during business hours

#### Combine Triggers

Create multiple Zaps with the same trigger but different actions:

* Trigger: New Booking → Action: Send Slack message
* Trigger: New Booking → Action: Add to Google Calendar
* Trigger: New Booking → Action: Create customer in CRM

#### Test with Real Data

Always test your triggers with actual booking data to make sure they capture the information you need.

#### Monitor Your Zaps

Check your Zapier dashboard regularly to ensure your triggers are firing as expected. Zapier will notify you if a Zap fails.

***

**Need help setting up a trigger?** Check out our [Getting Started](/knowledgebase/integrations/zapier-integration-guide.md) guide or visit the Zapier Integration overview.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.flowbookings.io/knowledgebase/integrations/zapier-integration-guide/available-triggers.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.