Ampersand currently supports webhook destinations. Destinations allow you to define where the data synced from SaaS instances via Read Actions or Subscribe Actions is routed to.
Go to the Destinations page in the Ampersand Dashboard to add a new Destination. You’ll need to provide:
amp.yaml
file.https
. In the case of webhooks, you can easily create a temporary one using tools like Hookdeck Console.For read and subscribe actions, you can specify destinations for each object. You can either have one destination for each object or route multiple objects to the same destination. Here’s what your amp.yaml
file might look like if you had created 2 destinations in the Ampersand Dashboard, one named accountWebhook
and one named contactWebhook
.
We have many other destination types on the roadmap, including:
Ampersand currently supports webhook destinations. Destinations allow you to define where the data synced from SaaS instances via Read Actions or Subscribe Actions is routed to.
Go to the Destinations page in the Ampersand Dashboard to add a new Destination. You’ll need to provide:
amp.yaml
file.https
. In the case of webhooks, you can easily create a temporary one using tools like Hookdeck Console.For read and subscribe actions, you can specify destinations for each object. You can either have one destination for each object or route multiple objects to the same destination. Here’s what your amp.yaml
file might look like if you had created 2 destinations in the Ampersand Dashboard, one named accountWebhook
and one named contactWebhook
.
We have many other destination types on the roadmap, including: