Invision Community 4: SEO, prepare for v5 and dormant account notifications Matt November 11, 2024Nov 11
Posted January 6Jan 6 Hello, I've implemented webhook for RSVP status change. It works well for RSVP going and not going. But when a user is leaving an already joined event, there is no trigger. Is it a bug ? Because regarding the documentation, it should triggger for a change "Fired when somebody changes his RSVP status". Regards
January 6Jan 6 I can't reproduce this, it's working fine for me. In fact the same webhook is fired for all 3 RSVP states, you have to look for the "action" parameter in the payload, which can be "yes", "no" and "maybe"
January 7Jan 7 Author I can't reproduce this, it's working fine for me. In fact the same webhook is fired for all 3 RSVP states, you have to look for the "action" parameter in the payload, which can be "yes", "no" and "maybe" @Daniel F Action "no" is for : no I'm not coming. But there is no statut and no call when someone cancel their subscription.
January 7Jan 7 Can you please explain what exactly you mean? It is also fired when one changes his status
January 7Jan 7 Author @Daniel F When I click on "Leave event", the webhook is not fired. So i'm not aware when someone leave the event. So if it should be fired, there is an issue, because it does not work on my side on this case.
January 7Jan 7 @Daniel F When I click on "Leave event", the webhook is not fired. So i'm not aware when someone leave the event. So if it should be fired, there is an issue, because it does not work on my side on this case. Thanks a lot! I can confirm that it's missing here. I have filled a bug report for this and a missing language string which I noticed while testing this.
January 7Jan 7 Author Thanks a lot! I can confirm that it's missing here. I have filled a bug report for this and a missing language string which I noticed while testing this. Thanks. Can you inform me when the issue will be fix ?
January 7Jan 7 Thanks. Can you inform me when the issue will be fix ? I have just pushed the fix to our repo. Once it was reviewed and approved, it will be shipped in a future release:)