I can't seem to get the "appointment booking cancelled" webhook to work.
All the other webhooks work just fine and the data is sent correctly.
Can it be because I am changing the appointment status to "cancelled" from the backend and it only works when either the user who made the appointment or the employee cancels it in their panel? BTW. when I change the status to "cancelled" from the backend the "status change" webhooks are triggered correctly.
I tried Pabbly, Zapier, and Encharge for this. All of which catch al the other available web hooks.
Correctly, you have two options here, to cancel from the cancel URL link that you receive in the notification, or to log in as a customer user and cancel the appointment.
Is there a reason why cancelling the appointment from the backend doesn't trigger the action?
Some clients prefer to call and cancel the appointment, but with the trigger not working in this case and the whole automation organized around it simply doesn't work.
it should be cancelled none the less; would you mind if I take a look?
Please provide me a temporary WP-admin (administrator) user for your site where this happens, so we could log in and take a look ‘from the inside’ as that’s the most efficient way to see and resolve the issue.
We do not interfere with any data or anything else except for the plugin (in case that’s a production version of the site), and of course, we do not provide login data to third parties.
You can write credentials here just check PRIVATE Reply so nobody can see them except us.
I see now; in that case we would need to take a look as trigger should work for action not related to where the action is from.
Please provide me a temporary WP-admin (administrator) user for your site where this happens, so we could log in and take a look ‘from the inside’ as that’s the most efficient way to see and resolve the issue.
We do not interfere with any data or anything else except for the plugin (in case that’s a production version of the site), and of course, we do not provide login data to third parties.
You can write credentials here just check PRIVATE Reply so nobody can see them except us.
Hello,
I can't seem to get the "appointment booking cancelled" webhook to work.
All the other webhooks work just fine and the data is sent correctly.
Can it be because I am changing the appointment status to "cancelled" from the backend and it only works when either the user who made the appointment or the employee cancels it in their panel? BTW. when I change the status to "cancelled" from the backend the "status change" webhooks are triggered correctly.
I tried Pabbly, Zapier, and Encharge for this. All of which catch al the other available web hooks.
I hope you can help
Best regards,
Rafal
Hi Rafal,
thank you for reaching out to us
Correctly, you have two options here, to cancel from the cancel URL link that you receive in the notification, or to log in as a customer user and cancel the appointment.
Is there a reason why cancelling the appointment from the backend doesn't trigger the action?
Some clients prefer to call and cancel the appointment, but with the trigger not working in this case and the whole automation organized around it simply doesn't work.
Best regards
Hi Rafal,
it should be cancelled none the less; would you mind if I take a look?
Please provide me a temporary WP-admin (administrator) user for your site where this happens, so we could log in and take a look ‘from the inside’ as that’s the most efficient way to see and resolve the issue.
We do not interfere with any data or anything else except for the plugin (in case that’s a production version of the site), and of course, we do not provide login data to third parties.
You can write credentials here just check PRIVATE Reply so nobody can see them except us.
Hi Ivana,
Let me clarify a bit.
I can cancel the appointment from the backened, but it doesn't seem to trigger "appointment cancelled" webhook this way.
Is there any reason why the webhook is only triggered when the appointment is cancelled through the link/customer panel?
Best regards
Hi Rafal,
I see now; in that case we would need to take a look as trigger should work for action not related to where the action is from.
Please provide me a temporary WP-admin (administrator) user for your site where this happens, so we could log in and take a look ‘from the inside’ as that’s the most efficient way to see and resolve the issue.
We do not interfere with any data or anything else except for the plugin (in case that’s a production version of the site), and of course, we do not provide login data to third parties.
You can write credentials here just check PRIVATE Reply so nobody can see them except us.