Happy Business Starts Here

Set a global / default URL destination for events

Hi

 

We would like to be able to set a global / default URL destination for all event notifications, rather than having to set them all by hand.

 

thanks

peter

2 Comments
Zuora Product Team
Status changed to: Under Consideration

Thanks for the suggestion @petergradwell. We're thinking of providing a way to create "Connections" which would contain the URL and associated authentication and retry settings, as well as an ability to make one a default, so that it would be automatically configured on any new Notification created. Does that sound like it would address your needs?

Guru

 @lukasz I think this would be very beneficial. Our QA team often has to shift the callouts between environments to test and changing a large number of them along with credentials is time consuming and error prone.

 

I like the idea of "connections" that contain the URL+Auth+Retry rules and you can select a connection from each notification (or use a default value). In this way you still have the flexibility of multiple connections but can make changes in one place if necessary.

 

I would imagine most tenants have at most one or two unique systems that they talk to for all notifications.

 

One point to consider is that while there may only be one or two systems, the exact paths might differ per event.

 

Example:

api.myservice.com/v1/integration/subscription/create

api.myservice.com/v1/integration/subscription/amend

api.myservice.com/v1/integration/subscription/cancel

 

At least with our system, this is broken into two distinct parts... The host: api.myservice.com and the path /v1/integration/subscription/amend.

 

What is likely to change more frequently is the host (for QA testing on different environments) and credentials (since best practices dictate every system uses different credentials and that they are rotated out periodically)

 

If an application used this model, then the "connections" concept discussed above might not be as helpful as you would still need to maintain 3 connections. While this would not impact us (we use a generic URL to handle all incoming callouts and route it based on the event type), it might impact other customers that have events tied to the path in the URL. It may be worth considering splitting the host from the path and potentially allowing the event to override the path so you could still leverage centralized configuration of the connection but provide the flexibility on the event config.