stephaniesimms
commented
5 years ago investigating Calendly integration and Webhooks subscription: https://developer.calendly.com/docs/getting-started https://help.calendly.com/hc/en-us/articles/360020052833-Advanced-embed-options#3 https://stackoverflow.com/questions/53891698/embed-calendly-into-react
Stripe webhooks documentation (more informative): https://stripe.com/docs/webhooks/setup
- [x] add webhook endpoint to elevate server
- [x] create a webhook subscription POST to calendly, use ngrok to test locally
- [x] test receiving webhook events, respond with 200 received
- [x] design data model for appointments/events: users, appointments (entire event object), join table for active appts
- [x] parse JSON event object
- [x] create schema to validate data TODO: add email
- [x] add validation to route
- [x] write business logic to handle invitee.created and invitee.canceled events
- [x] appointments model with find, create/reschedule, cancel
- [x] finish tests
Testing notes:
- restart local server AND ngrok every time we make a change to code
- establish new webhook with calendly
- continue testing
- as long as 200 status can continue testing without restarting
Misc questions:
- single webhook subscription for team/admin. each professional needs own calendly account. add calendly user ids to elevate users_calendly_users table to associate it with user id.
- Stripe docs on best practices/handling duplicate events: logging the events you’ve processed, and then not processing already-logged events
- exception for CSRF - other security issues?
PRs to submit:
- data.sql update (make appt dates for distant future)
- webhook endpoint and tests; appointments model and tests
Data model for the appointments table For now appointments can be one to one between two users
Some general ideas on the data model model :
start time/date end time/date
did the appointment actually take place / no-show (boolean value)
description / needs (provided by customer) description / notes (provide by admin)