Purpose
1.2. Prevent over/underbooking by increasing prices during peak demand and lowering them when seats are available.
1.3. Maximize revenue and seat utilization for ground transportation providers, enhancing profitability while providing transparent pricing to customers.
1.4. Free up staff from manual price monitoring and frequent updates while ensuring regulatory and compliance adherence if location-based rules apply.
Trigger Conditions
2.2. Approaching booking date/time increases urgency within configurable ranges (e.g., 24–72 hours before departure).
2.3. Integration detects local event schedules, weather alerts, or traffic spikes.
2.4. Competitor price monitoring identifies undercutting or rapid price changes.
2.5. Custom business rules triggered by API callbacks or system events.
Platform Variants
• Feature/Setting: Webhooks + Formatter + Scheduled Trigger — Webhook captures event, formatter recalculates price, schedule pushes update.
3.2. Make (Integromat)
• Feature/Setting: HTTP Module + Aggregator — Fetch occupancy, evaluate triggers, PATCH booking prices via shuttle platform API.
3.3. Salesforce
• Feature/Setting: Process Builder + Apex Trigger — Define occupancy/demand logic, automatic record updates on Shuttle Service objects.
3.4. Microsoft Power Automate
• Feature/Setting: Scheduled flow + HTTP request — Poll demand info, adjust pricing fields in Dataverse or Dynamics 365.
3.5. Google Cloud Functions
• Feature/Setting: Scheduled Cloud Scheduler + Cloud Function — Cron triggers Python/Node.js logic to update Firestore or external systems.
3.6. AWS Lambda
• Feature/Setting: API Gateway + Lambda — Endpoint receives occupancy or time data, executes DynamoDB updates for pricing.
3.7. Azure Logic Apps
• Feature/Setting: Event Grid + Logic App workflow — Respond to booking spikes, update Cosmos DB or shuttle database prices.
3.8. Amadeus APIs
• Feature/Setting: Travel Innovation Sandbox — Pull flight traffic for airport, update shuttle prices for arriving passengers.
3.9. Sabre APIs
• Feature/Setting: Schedule Change Alerts + Pricing API — Detect event, recalculate shuttle fare matrix.
3.10. Stripe
• Feature/Setting: Product Update API — Update product pricing dynamically as received from automation logic.
3.11. WooCommerce
• Feature/Setting: REST API — PUT price changes for shuttle as WooCommerce Product on events.
3.12. Shopify
• Feature/Setting: GraphQL Admin API — Mutation to update productVariant price for shuttle listing.
3.13. Booking.com Partner API
• Feature/Setting: Price Update endpoint — POST price update when occupancy/time triggers fire.
3.14. Google Sheets
• Feature/Setting: Sheets API + Script — Automatically recalculate pricing column when triggers met.
3.15. QuickBooks Online
• Feature/Setting: Webhooks + Invoice Item Update — Adjust pricing on shuttle items for new reservations.
3.16. HubSpot
• Feature/Setting: Workflow + Custom Code Action — Change price property for shuttle deal record.
3.17. Airtable
• Feature/Setting: Automations + Script — Monitor event fields, PATCH price in shuttle services table.
3.18. MongoDB Atlas
• Feature/Setting: Triggers + Functions — Listen for new bookings, update pricing field in shuttle collection.
3.19. Notion
• Feature/Setting: API + Database Update — PATCH price property based on occupancy formula.
3.20. Postmark
• Feature/Setting: Transactional Email API — Notify admin of price change, send customer dynamic fare notification.
3.21. Facebook Messenger
• Feature/Setting: Messenger API — Respond to booking inquiry with real-time price as generated by logic.
3.22. Twilio SMS
• Feature/Setting: SMS Trigger — Send updated shuttle fare to users after trigger event (SMS API).
3.23. Google Calendar
• Feature/Setting: API Watcher + Script — Event detected, update shuttle price entry in booking calendar.
3.24. Calendly
• Feature/Setting: Webhook + API — Change price within description field of shuttle slots.
Benefits
4.2. Eliminate stale price listings, preventing lost bookings from outdated prices.
4.3. Respond instantly to external factors, improving competitive stance.
4.4. Enhance customer experience by offering fair, transparent fares based on real-world conditions.
4.5. Reduce errors and administrative overhead in price management.