Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.younegotiate.com/llms.txt

Use this file to discover all available pages before exploring further.

Real-World Example

Jane connects Google Calendar from My Bill Pay Calendar. After she grants access, the portal should store the Google calendar connection and create payment events for eligible future payments.

Visual Flow

How It Should Work

  • It should connect the authenticated consumer to their Google Calendar account.
  • It should store the needed calendar metadata and enable live updates when the connection succeeds.
  • It should dispatch calendar event creation for eligible future payments.

How It Should Not Work

  • It should not sync events for another consumer.
  • It should not keep showing live sync as active after the connection is revoked or invalid.
  • It should not create duplicate events for the same scheduled transaction.

Developer Notes

  • Google authorization redirects back to the consumer payment calendar.
  • Calendar creation and updates should happen in jobs, not long-running page requests.
  • routes/consumer/index.php
  • app/Http/Controllers/Consumer/GoogleCalendarController.php
  • app/Jobs/CreateCalendarEvents.php
  • app/Jobs/UpdateCalendarEvents.php
Last modified on May 25, 2026