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 uses Outlook Calendar for bills. She connects Microsoft Calendar, grants access, and the portal creates future bill-pay events in her calendar while keeping them tied to the correct scheduled transactions.

Visual Flow

How It Should Work

  • It should connect the consumer to Microsoft Calendar only after authorization succeeds.
  • It should create events for eligible future payment dates.
  • It should update or delete events when schedule changes require it.

How It Should Not Work

  • It should not create Microsoft calendar events without valid authorization.
  • It should not confuse Google and Microsoft calendar metadata.
  • It should not create duplicate events for one scheduled transaction.

Developer Notes

  • Microsoft and Google sync share the same job concepts but use different authorization controllers.
  • External calendar failures should not break the core portal schedule.
  • routes/consumer/index.php
  • app/Http/Controllers/Consumer/MicrosoftCalendarController.php
  • app/Jobs/CreateCalendarEvents.php
  • app/Jobs/DeleteCalendarEvents.php
Last modified on May 25, 2026