Add a destination to the Ampersand Dashboard
Go to the Destinations page in the Ampersand Dashboard to add a new Destination. You’ll need to provide:- Destination name: this is an alias for the destination that you can then refer to in the
amp.yamlfile. - URL: this is the URL of your webhook destination. It must start with
https. In the case of webhooks, you can easily create a temporary one using tools like Hookdeck Console.
Using destinations for data delivery
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 youramp.yaml file might look like if you had created 2 destinations in the Ampersand Dashboard, one named accountWebhook and one named contactWebhook.
YAML
Using destinations for notifications
Destinations can also be used to receive notifications about important lifecycle events in your project, such as when customers install or update integrations, when backfills complete, or when sync issues occur. Notifications use a topic-based routing system where you connect event types to topics, and topics to destinations. See the Notifications overview for complete setup instructions.Supported destinations
Other Destinations
We have many other destination types on the roadmap, including:- Postgres
- Ampersand-hosted Postgres
- Amazon S3
- Amazon SQS
- Google Cloud Storage
- Google PubSub
- RabbitMQ
- Azure Service Bus

