Get started with a free trial today
Already have an account? Sign in
You can now add multiple destinations to your Stitch account! In this guide, you will learn everything you need to know on how to fully utilize this feature. Before selecting destinations, we recommend reading our guide onhow to choose a destination to ensure you’re making the decision that best suits your data warehousing needs.
Can I send data from one integration to multiple destinations?
What happens to my other destinations if I downgrade my plan?
This feature allows you to load data from your integrations into more than one destination in your Stitch account.
You have multiple environments. You may want to ensure you have clean data. To do this you can house your quality assurance and production environments in the same Stitch account instead of having to maintain two unique warehouses to ingest data from each other.
You want to separate your raw data ingestion from your transformed data ingestion. You can use multiple destinations in your Stitch to load raw data from integrations into a data lake for transformation, then load your transformed data into a separate warehouse.
Clients on a Stitch Advanced or Premium plan can use this feature.
The default limit is 3 destinations per Stitch Advanced account, and five destinations per Stitch Premium account. To increase this limit, you must pay an add-on per additional destination. Stitch can support up to 10 destinations per account.
You can’t connect a single integration to multiple destinations, but you can create multiple integrations for the same data source and connect them to different destinations. The easiest way to do this is to use the connection cloning feature:
Stitch will place a hold on your account if your destination count is higher than your destination limit. When a hold is placed or lifted, you will receive an email from Stitch notifying you of the changes.
When you delete a destination, two things will happen. All post-load webhooks linked to the deleted destination will also be deleted. You will have to re-add them again if you still would like to use them in your other destinations. You will also have to choose if all data sources mapped to the deleted destination will be paused for replication or deleted. To continue replication of data, you must go back into the integration setup and re-map to where the data will be loaded.
In this section, you will learn how to add, delete, or edit a destination when you have more than one.
If you want to add an aditional destination through the API, check out ourCreate a Destination with the Connect API guide.
Important:Some things to take note of when deleting a destination
You will be asked to pause or delete any source integrations you have mapped to the destination, and all post-load webhooks will automatically be removed.
DELETE in the text box.In this section you will learn how to map your data sources in Stitch to your destinations.
To map a source to a destination through the Stitch app is a very simple process. Within your setup page, you will be able to select which destination you would like to map your integration to.
Mapping your data sources to via the Stitch Connect API is also a very simple process and you can do it in the Sources POST. Check out our docs onhow to create a source to learn how to do this.
| Related | Troubleshooting |
Did this article help? If you have questions or feedback, feel free tosubmit a pull request with your suggestions,open an issue on GitHub, orreach out to us.