Amelia Transpired Webhook self-updates

WordPress plugin for Amelia Booking. It sends an HTTP POST with a JSON body to your chosen URL after an appointment’s scheduled end time (bookingEnd in Amelia’s database), not when the customer completes the booking form.

Use cases include Zapier, Make, custom APIs, CRM updates, and internal automations that should run only once the time slot has finished.

Requirements

• WordPress 5.4+
• PHP 7.4+
• Amelia Booking (paid recommended; plugin reads wp_amelia_* tables and uses Amelia action hooks)

Installation

1. Copy the amelia-transpired-webhook folder into wp-content/plugins/.
2. Activate Amelia Transpired Webhook in Plugins.
3. Ensure Amelia is active so the admin menu and database tables exist.

Configuration

Admin UI

1. In wp-admin, open Amelia → Transpired webhook.
2. Enter your webhook URL (https://…). Leave empty to disable all scheduling and outbound requests.
3. Click Save Changes.

This screen sits next to Amelia’s built-in Settings entry. Amelia’s settings use a single-page app (#/general, etc.), so this plugin adds a separate submenu rather than injecting a tab into their JavaScript bundle.

Test webhook

Under Test webhook, use Send test webhook to POST a sample payload. It uses the same structure as production and the most recent appointment-linked booking in the database. The JSON includes "test": true (and related fields) so automations can ignore test traffic.

• If the Webhook URL field has text, that value is used for the test (even before saving).
• If the field is empty, the saved URL is used—save first if you only typed a new URL.

Reliability

WordPress cron depends on site traffic unless you trigger wp-cron.php from a system scheduler. For time-sensitive webhooks, configure a real cron job on the server.

How it works

1. On relevant Amelia events (booking saved, rescheduled, appointment updated, etc.), the plugin schedules one wp_schedule_single_event at the appointment end time (read from the DB in UTC).
2. When the event runs, it rebuilds the payload from the database, checks booking/appointment status against your rules, then POSTs JSON.
3. Cancellations, rejections, no-shows, and deletions remove pending events for affected bookings.
4. Successful sends store a short-lived transient so the same booking is not posted twice.
5. Failed HTTP requests retry with increasing delay, up to a configurable maximum.

JSON payload (production)

Top-level keys include:

Test requests add test, test_note, and may be altered via atw_test_webhook_payload.

Filters

All filters are optional. The webhook URL is: saved option → then atw_webhook_url (return a string to override or force empty).

Example:

add_filter( 'atw_webhook_url', function ( $url ) {
    return $url ?: 'https://hooks.zapier.com/hooks/catch/xxx/yyy/';
});

add_filter( 'atw_debug', '__return_true' );

Uninstall / deactivation

• Deactivate clears pending cron events registered under atw_booking_transpired_v1.
• The plugin does not register an uninstall routine; the atw_webhook_url option and transients remain unless you remove them manually.

Development

• Text domain: amelia-transpired-webhook
• Prefix: ATW_ classes, atw_ functions and hooks
• Bootstrap: atw() returns the singleton ATW_Plugin

Changelog

See CHANGELOG.md.

License

GPL-2.0-or-later. See license.

Amelia Booking is a trademark of its respective owners; this plugin is not affiliated with or endorsed by Amelia.