Waiting for the first webhook to verify a customer’s subscription creates the question: has setup failed, or has no new customer data changed yet?
Ampersand now helps verify that an subscribe setup is working with observability into lifecycle events. The Ampersand dashboard now show subscribe lifecycle events and supports configuring notifications for successful or failed subscription changes.
Subscription lifecycle events
Creating, updating, or deleting an installation’s subscription now produces an operation for each subscribed object labeled: Subscription Created, Subscription Updated, Subscription Deleted.
Each subscribe operation includes logs with additional details.
Subscription notifications
Six notifications now add observability into the subscribe action lifecycle: subscribe.create, subscribe.update, and subscribe.delete, each with a .success and an .error event.
subscribe.create.successNEWThe subscription is active and events can flow.
subscribe.create.errorEXISTINGAmpersand could not set up the subscription.
subscribe.update.successNEWA change to the subscription was applied.
subscribe.update.errorNEWA change to the subscription failed.
subscribe.delete.successNEWThe subscription was removed, including on the provider's side.
subscribe.delete.errorNEWThe action was removed, but provider-side cleanup failed. The remaining subscription may require manual removal in the provider.
The timing of subscribe.create.success depends on the provider. For providers Ampersand subscribes to programmatically, it fires when setup succeeds. For providers whose webhooks are configured manually in their own UI, it fires when the first event is delivered.