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

Integration with external systems #49

Closed
tttp opened this issue Mar 10, 2020 · 1 comment
Closed

Integration with external systems #49

tttp opened this issue Mar 10, 2020 · 1 comment
Assignees
Labels
help wanted Extra attention is needed question Further information is requested

Comments

@tttp
Copy link
Member

tttp commented Mar 10, 2020

Trying to bundle together various needs expressed in multiple issues :

  • Send signatories/action taken to a crm
  • sending emails to the targets of an action (mail 2 target)
  • sending progress updates (we reached 50k signatures today) to the organisers, supporters or targets
  • double optin emails?

Some, campaigns will need to be able to personalise (eg send both the total of signatures and the one from their constituencies to an mp) or have different thresholds or...)

Rather than trying to have everything done in the core and dealing with a gazillion options in the ui, let's instead have Web hooks and have external services dealing with that

I am not keen on calling the hook for every signature, because it forces every external services to implement some kind of queuing or we risk dos them

What I see is to have a web hook and call it max every X seconds to notify "we got one or more new actions, and let the external system call our API to get the details based on their needs:

  • one count API (with filter on timestamp?)" how many actions" (that is the API that can be reused by the frontend for the progress counter)

  • one aggregate per action page (option to aggregate per day too?) can be used for the dashboard too

  • one fetch actions (with limit and start id/timestamp) used for sync with crm or email 2 target or whatever funky action they want to set up

  • one aggregate per target?

@tttp tttp added question Further information is requested help wanted Extra attention is needed labels Mar 10, 2020
@tttp
Copy link
Member Author

tttp commented Mar 30, 2020

fixthestatusquo/archive-proca-backend#10 moved that discussion to the backend repo

@tttp tttp closed this as completed Mar 30, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Extra attention is needed question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants