When a request for update is made need to
1) get all users who belong to chatfuel
2) get last update time and see if it's time to send new content to the user(based on the actionplan table, which we may need to rework)
3) create a chatfuel object with information from the query table(we need to either add more fields to the DB, for which we would need to add more detail into the form when we create the content or define some values as defaults in the object(img size, top element style, etc.))
4) create the url to make the post request at incase of questions
5) update db with the sent updates
Alternatively we could make it single user based - each user sends a request with it's user ID and we query only for that user. I think we would create alot more DB requests in this way though so in the long term, it doesn't seem like a good idea.
When a request for update is made need to 1) get all users who belong to chatfuel 2) get last update time and see if it's time to send new content to the user(based on the actionplan table, which we may need to rework) 3) create a chatfuel object with information from the query table(we need to either add more fields to the DB, for which we would need to add more detail into the form when we create the content or define some values as defaults in the object(img size, top element style, etc.)) 4) create the url to make the post request at incase of questions 5) update db with the sent updates
Alternatively we could make it single user based - each user sends a request with it's user ID and we query only for that user. I think we would create alot more DB requests in this way though so in the long term, it doesn't seem like a good idea.