Overview
UserEvidence Advocacy supports a Snowflake integration that allows your advocates to benefit from enriched customer data originating directly from your Snowflake environment. By syncing Snowflake attributes into UserEvidence Advocacy, your marketing team can build more intentional and personalized advocacy and reference management workflows, segment users more effectively, and optimize the outputs and insights generated from the platform.
This document provides a complete, step-by-step overview of what is required to set up the Snowflake integration and how to complete the configuration.
How the Integration Works
Once connected, UserEvidence Advocacy reads customer data stored in a Snowflake table and syncs it into the platform on a scheduled basis. This enables accurate user segmentation, personalized engagement workflows, and stronger insights across advocacy and reference management.
At a high level:
Your designated technical contact receives an invitation to create a connection using Workato.
They authenticate Snowflake within Workato using their preferred authentication method.
They select the Snowflake table that the integration should read from.
UserEvidence Advocacy ingests customer attributes from that table on a recurring basis.
Important Notes:
Only one table may be selected for ingestion.
That table must contain an email column to uniquely identify each user.
The selected table should include all attributes you want reflected in UserEvidence Advocacy.
What to Prepare Before Setup
1. Identify Your Technical Contact
You will need to confirm the Snowflake administrator or engineer who will:
Prepare the Snowflake table
Authenticate Snowflake in Workato
Select the correct table during setup
Please provide their name and email so an invitation can be issued.
2. Create a Consolidated Table in Snowflake
The integration relies on a single Snowflake table that contains all customer attributes you want to appear in UserEvidence Advocacy.
Required Column
email — must be present and serve as the unique identifier.
Recommended Columns
You can include any fields that will help your team segment users or tailor engagement workflows. Examples include:
first_name
last_name
company_name
region
nps_score
last_active_at
usage_tier
product_adoption
plan_type
most_visited_page
Example Table Structure
Column Name | Type | Description |
string | Required UID for matching users | |
first_name | string | Optional |
last_name | string | Optional |
nps_score | integer | Optional |
last_active_at | timestamp | Optional |
product_adoption | string/json | Optional |
region | string | Optional |
Your internal team may generate this table via SQL, dbt, stored procedures, or any internal ETL pipeline.
The integration reads the final table directly.
Step-by-Step Integration Setup
From here forward, actions are completed by your designated technical contact.
Step 1 — Accept the Connection Invitation
Your technical contact will receive an email invitation to connect Snowflake through Workato.They must accept the invite and sign in.
Step 2 — Authenticate Snowflake
Inside Workato:
Navigate to the Connections tab.
Select Create Connection.
Search for Snowflake.
Choose the authentication method your organization prefers:
OAuth
Private Key
Username + Password
Workato Snowflake Connector – Required Fields
Based on Workato’s documentation, the user will be prompted for:
Snowflake Account Identifier
Username
Warehouse
Database
Schema
Role (optional depending on configuration)
Authentication method details (password, private key, or OAuth)
Once authentication is successful, the connection will appear as Connected.
Step 3 — Select the Table
After authentication:
Choose the Snowflake table that contains the consolidated customer data.
Confirm that the table:
Contains an email column
Includes all desired fields
Is located in the database and schema specified during authentication
Only a single table may be selected. If you need additional attributes later, simply update the table in Snowflake; the integration will read the expanded schema automatically.
Step 4 — Data Sync Begins
Once the connection is established and the table is selected:
The integration begins pulling data on a scheduled basis.
Attributes appear within UserEvidence Advocacy in Member Profiles, Segments, and other areas where customer data is used.
No additional setup is required unless you wish to modify the table or expand attributes.
Data Sync Frequency
Data sync generally occurs daily.
If your team requires a different cadence, your CSM can determine feasibility with engineering.
Snowflake Permission Requirements
Your Snowflake admin must ensure:
The Workato-connected user has read access to the selected table.
The specified warehouse has available compute during sync windows.
Any Snowflake network policies allow connections from Workato.
When IP allowlisting is required
Your security team may request Workato IPs to be allowlisted.
Your CSM can provide the current list upon request.
Frequently Asked Questions (FAQ)
Can we sync multiple tables?
No. A single table must be used. Your team can consolidate attributes into that table as needed.
Can the table be modified later?
Yes. Workato automatically reads updated schemas.
Does the integration support JSON fields?
Yes. JSON is supported, but certain fields may need to be flattened depending on how you plan to use them inside UserEvidence Advocacy.
Is the sync one-way or two-way?
The sync is one-way from Snowflake → UserEvidence Advocacy.
How long does setup take?
After the table is created, configuration typically takes 1–2 minutes.