Welcome to day 4 of Convoy Launch week! We are thrilled to unveil On-The-Fly events and Meta events, these features will enrich your webhook experience with Convoy.
In this article, we will delve into how we’ve simplified the integration process with Convoy providing just a single API endpoint to help you get started with sending events. We also added Meta events, a feature that provides you with Webhook notifications for specific events happening within your Convoy project.
Meta events are operational events generated by Convoy for specific activities happening within your Convoy project. This allows you to subscribe and listen for events and perform any action based on these events within your own internal systems, providing a seamless headless experience. Convoy uses webhooks to notify you of these events.
Types of event
At the moment, these are the events we currently support with plans to add some more later in the future.
|An endpoint was created
|An endpoint was updated
|An endpoint was deleted
|An event delivery was successful
|An event delivery failed
Here’s an example of the sample payload sent with an
description: "testing endpoint",
Meta events are completely optional and can be turned on under the Project settings page. All you need to do is provide a webhook URL to receive these events, a secret for signing the payload (optional) and the events you would like to subscribe to.
You can also view a list of all your Meta events.
We received several requests in our community slack, asking if Convoy allowed endpoint information to be specified in the same API call as the event payload. The flow initially looked like this:
With the addition of the On-The-Fly Event API, you can now do all that in one call:
Convoy will implicitly create the endpoint, create the subscription and then dispatch the event. If an endpoint with the same target url already exists, then Convoy will update all other parameters and endpoint configuration with your provided data. This brings flexibility for use cases where endpoint data is expected to change frequently, allowing their workflow to be more efficient. For the subscription, if the subscription config is absent from the request body, default configuration will be applied when the subscription is created newly. If the subscription already exists, the supplied config in the request body will be used as if in an
This feature enables developers to dynamically define and update endpoint information on the fly, providing greater adaptability in their applications. In a dynamic environment or rapidly evolving system, this feature becomes invaluable. Developers can easily modify endpoint information as needed through a single call, ensuring that the endpoint data in Convoy remains up to date.
We plan on taking your feedback and improving on all of these features. For example, a future iteration on Meta events is to enable delivery via other channels asides from HTTP such as Pub/Sub platforms like Google Pub/Sub and Amazon SQS.
Stay tuned for more updates. Interested in giving Convoy a go? Join our community slack here and give us feedback!