Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Epic: finish courtbot #1

Open
6 tasks done
groovecoder opened this issue Jul 4, 2019 · 0 comments
Open
6 tasks done

Epic: finish courtbot #1

groovecoder opened this issue Jul 4, 2019 · 0 comments

Comments

@groovecoder
Copy link
Member

groovecoder commented Jul 4, 2019

Based on hack night's session, we came up with these major "phases" of building the new courtbot system:

  • Set up Amazon Lex with Twilio and Lambda functions to get Year, County, and Case from the end user.
  • courtbot-python Add an API: GET /case?year=&county=&case= #2 : Add an API call: GET https://courtbot.com/case?year=&county=&case= endpoint finds the case, and responds with the full case object, including the arraignment date.
  • lambda function Add case call and return proper message to user via lambda_function #15: Call the GET /case? endpoint from the lambda function, and then ask the user to confirm reminders.
  • courtbot-python Add an API call: POST /reminders #3: Add an API call: POST https://courtbot.com/reminders with the case, phone #, and date. courtbot.com creates all reminders for the case.
  • lambda function: When the user confirms the reminders, the lambda function invokes the POST /reminders endpoint
  • courtbot-python: Add cron job to courtbot.com that checks for un-sent reminders and sends them.

IMG_0185

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant