Skip to main content

​
Overview

This article covers how to hide connectors from end users and when this feature is relevant.

​
When to Use It

Most workflows have two sides: one that requires user authentication and another that sends data to your application or data warehouse. While users need to connect their accounts for the former, the latter sends data to your system and doesn’t require any user configuration. Let’s look at an example: In the Integration Structure article, we discussed streaming data from events to destinations. A common destination is a data warehouse like Snowflake. Suppose you need to stream data from your users’ Shopify stores directly to your Snowflake warehouse.
In this workflow, users must authenticate their Shopify account but don’t need to take any action for the Snowflake destination. Since the Shopify data should land in your Snowflake instance, there’s no reason to show the Snowflake connector to your users. To implement this, select the Hide this connector from users checkbox. This routes data to the Snowflake warehouse using the credentials you configured in the Authenticate (Step 2) section of the Workflow Builder. It also removes any mention of Snowflake from the user-facing flow. When users set up this integration, they’ll only be prompted to connect their Shopify credentials:

​
Summary

Use this feature when you need to route data to your own systems or warehouses without requiring user configuration or authentication.
⌘I