When an Integration that is calling a custom trigger is turned OFF, shouldn't the unsubscribe URL be called?

hi @JCorrell

You are correct, the unsubscribe is ONLY called when the integration recipe is deleted. Also good to know that an update of the recipe (e.g. changing a column) is implemented with a unsubscribe followed by a subscribe.

I don’t know of a method to know when an integration is switched off, the user should turn the correct webhook to off, which is kind of cumbersome.

@basdebruin

How would the user turn off the webhook?

hi @JCorrell

I was focused too much on my own apps 🙂. When I use custom triggers they always insert webhooks in the board to trigger the app’s endpoints. These webhooks can be switched off in the UI by the user.

As usual, I’m just going to agree with what @basdebruin just said 🙂

One thing to add: your custom trigger shouldn’t need to know when the recipe is turned off. You can continue to send events to the webhook URL, they just won’t kick off the rest of the workflow (ie, the corresponding action won’t run).

If the unsubscribe URL is not being triggered when the integration is turned off, you may need to explore alternative methods to ensure that the integration no longer processes or sends a call to the system.

Here are a few steps to investigate and address the issue:

1. Verify Unsubscribe Logic: Ensure that the unsubscribe URL is properly configured in the integration settings and correctly mapped to the “off” state.
2. Implement Status Flags: Use a status flag in your integration to explicitly check whether it is active or inactive before processing any calls or actions.
3. Monitor Logs: Check logs to see if there are any errors or warnings when attempting to process the unsubscribe action. This may help pinpoint why the URL is not triggered.
4. Use Fallback Options: If the unsubscribe URL cannot be triggered automatically, consider adding a manual step to deactivate or remove the integration’s configuration from the source system.

These measures can help ensure that your integration no longer processes unnecessary actions once it has been turned off.

Yes, when an integration that is calling a custom trigger is turned OFF, it is a good practice for the unsubscribe URL to be triggered as part of the deactivation process. This ensures that users or systems are properly unsubscribed from receiving further communications, such as SMS notifications or messages.

The unsubscribe URL is typically designed to remove a user from an automated messaging list, which helps to prevent sending unwanted or irrelevant SMS messages. By calling the unsubscribe URL when the integration is turned off, it ensures that users are no longer subscribed to the trigger, thus halting any SMS alerts or notifications associated with that particular integration.

To me it would be a very bad idea to call the unsubscribe event (the app is not unsubscribed from the board, just (temporarily) switched off. In the unsubscribe endpoint I do all the cleanup, including freeing up the license in case the app is licensed per board.