Connect to EPP
Customer Meeting Request hands off scheduling work to EPP. This app stores the form, submission, mapping payload, and connector packet.
Approval
Not required
Queue PDF policy
Calendar
Queue notice
Backend
pull
Mapped fields
These keys are what EPP receives. Operators see friendly labels; EPP receives stable mapping names.
RequesterFirstName
requester_first_name -> Requester
RequesterLastName
requester_last_name -> Requester
RequesterEmail
requester_email -> Requester
RequesterPhone
requester_phone -> Requester
AttendeeFirstName
attendee_first_name -> ExternalAttendee
AttendeeLastName
attendee_last_name -> ExternalAttendee
AttendeeEmail
attendee_email -> ExternalAttendee
AttendeePhone
attendee_phone -> ExternalAttendee
CompanyName
company_name -> MeetingRequest
AttendeeTitle
attendee_title -> ExternalAttendee
Country
attendee_country -> MeetingRequest
Topic
meeting_topic -> MeetingRequest
InternalAttendeeAll
internal_attendees -> InternalAttendee
Date
operational_date -> Operational
StartTime
operational_start_time -> Operational
EndTime
operational_end_time -> Operational
Location
operational_location -> Operational
Handoff boundary
PDF generation, calendar delivery, and backend request updates are handed off to EPP. The form builder should queue a clear connector packet, expose pull/ack or webhook delivery, and show operator status without pretending to be the scheduling system.