Bookly
Overview
AFI captures appointment events from Bookly and forwards them to any receiver — sync bookings to your CRM, drop them into a calendar via Google Calendar, get Slack alerts on new appointments, or write them to a sheet for accounting.
Available triggers
AFI listens for the following events from Bookly. Each event runs as its own integration — you can have several integrations on the same plugin firing on different events.
- Appointment Created
- Appointment Updated
- Appointment Rescheduled
- Appointment Deleted
- Appointment Status Changed
- Appointment Approved
Mappable fields
Each event exposes the customer fields (name, email, phone, address, plus any Bookly custom fields), the service, the staff member, location, and the appointment date/time. The Bookly appointment ID and status are available so you can correlate back to the plugin’s own dashboard.
Requirements
- Bookly (free or Pro) installed and activated.
- At least one service and staff member configured.
Quick start
- In WordPress admin, go to AFI > New Integration.
- Trigger > Sender: pick Bookly.
- Event / Form: pick the specific event you want this integration to listen on (e.g. Appointment Created).
- Pick a Receiver (e.g. Mailchimp, HubSpot, Google Sheets, Slack) and the desired task.
- Map Bookly fields onto the receiver’s fields. Use special tags (
{{_date}},{{_user_ip}}, etc.) for values not present in the form. - Optional: add Conditional Logic to control when the receiver is called.
- Save and run a test event to confirm the integration. Check AFI > Log if anything looks off.
Notes & caveats
- Custom fields appear in the mapping panel once the field has been added to a Bookly service.
- Multi-service bookings are sent as one event per service — your integration runs multiple times per multi-service booking.
- Pending vs Approved — if you only want confirmed appointments, use the Appointment Approved trigger instead of Appointment Created.