Stitch

Euno's Stitch integration observes replication metadata from Stitch and connects it to the warehouse tables Stitch writes.

The integration discovers:

• Stitch destinations

• Stitch sources

• Stitch streams

• Destination warehouse table references for supported warehouses

Stitch table resolution is supported for Snowflake and BigQuery destinations. Other Stitch destination types are still observed as Stitch metadata, but Euno does not promise destination table links for them.

Setting up Euno's Stitch Integration

Step 1: Create a Stitch API access token

1. Log in to your Stitch account.

2. Open Account Settings.

3. Go to API Access Keys.

4. Create or copy an API access token for the Stitch account you want Euno to observe.

5. Keep the token available for the Euno source setup.

Step 2: Configure Euno's Stitch source

Step 1: Access the Sources Page

1. Go to the Sources page.

2. Click Add New Source or open the source gallery.

3. Select Stitch.

Step 2: General Configuration

Asterisk (*) means a mandatory field.

Configuration	Description
Name*	Enter a name for your Stitch source, for example "Stitch - Production".
API token*	Enter the Stitch API access token generated in Stitch.

Step 3: Advanced Configuration

Under Advanced, you can configure:

Configuration	Description
Base URL	Optional Stitch API base URL. Leave blank to use https://api.stitchdata.com/v4.
Observe extraction and load history	When enabled, Euno collects bounded latest successful extraction and load timestamps for Stitch sources.
History lookback days	Number of days of Stitch extraction/load history to inspect. The supported range is 1-60 days. Default: 30.
Observe streams	Enabled by default. Euno creates stitch_stream resources and records selected stream details when available. Keep this enabled for stream-level visibility and Salesforce lineage support.
Source filter	Optional allow/deny regular expressions matched against Stitch source names. The default includes all Stitch sources.
Database mapping	Optional key/value mapping from Stitch destination hosts or project identifiers to the warehouse identifiers Euno uses for the same Snowflake or BigQuery destination.

Use Database mapping when Stitch and Euno use different identifiers for the same warehouse. For Snowflake, map the Stitch destination host to the Snowflake account identifier Euno observes. For BigQuery, map the Stitch project identifier to the BigQuery project identifier Euno observes.

Step 4: Scheduling Updates

1. Enable the Schedule toggle.

2. Choose from the following:

   1. Weekly: Specify the days and times for updates.

   2. Hourly: Enter an interval in hours, for example every 6 hours.

Step 5: Resource Cleanup

To keep your data relevant and free of outdated resources, Euno provides automatic resource cleanup options. These settings determine when a resource should be removed if it is no longer detected by a source integration. For a detailed explanation on Euno's cleanup strategies, see: Resource Sponsorship in Euno.

• Immediate Cleanup: Remove resources not detected in the most recent successful source integration run.

• No Cleanup: Keep all resources indefinitely, even if they are no longer detected.

Step 6: Save Configuration

Click the Save button to complete the setup.

What Euno Discovers

The Stitch integration discovers Stitch destinations, sources, streams, and supported destination warehouse table references.

For the full resource and relationship reference, see Stitch Integration Discovered Resources.

Destination Warehouse Table Links

Euno can link Stitch streams and sources to destination warehouse tables when the Stitch destination is Snowflake or BigQuery and the destination metadata contains the required warehouse identifiers.

For the best table matching results, connect the corresponding Snowflake or BigQuery source in Euno as well. Stitch contributes replication context, but Snowflake or BigQuery remains the source of truth for the physical warehouse table lifecycle and rich table metadata.

Salesforce Lineage

For Stitch Salesforce sources, Euno can connect replicated warehouse tables back to Salesforce objects and fields.

This requires:

• A Stitch source whose source type is Salesforce.

• A Salesforce source in Euno that has crawled the Salesforce org metadata.

• A warehouse source in Euno, such as Snowflake or BigQuery, that has crawled the destination tables and columns.

• Stream observation enabled for the Stitch source, which is the default.

Euno avoids guessing when Salesforce objects or fields are missing or ambiguous. Non-Salesforce Stitch sources are visible as Stitch metadata, but they do not produce source-system lineage in this version.

Validation After Setup

After the first Stitch run completes:

1. Confirm the Stitch source run is successful.

2. Open the data model and search for Stitch destinations, sources, and streams.

3. Check that selected Stitch streams or sources define expected Snowflake or BigQuery destination tables.

4. For Salesforce lineage, confirm the related Salesforce and warehouse sources have also run successfully.

5. If table links are missing, review the destination type and database mapping configuration.

Troubleshooting

Symptom	Possible cause	What to check
Stitch setup fails during validation	Invalid or expired Stitch API token	Create a fresh Stitch API access token and update the Euno source.
Stitch sources appear but destination table links are missing	Unsupported destination type or incomplete destination metadata	Confirm the Stitch destination is Snowflake or BigQuery and includes the required host/database or project identifier.
Destination tables do not match existing warehouse resources	Stitch and Euno use different warehouse identifiers	Add or adjust Database mapping for the destination host or project identifier.
Salesforce lineage is missing	Required Salesforce or warehouse metadata is missing	Run the Salesforce source and the destination warehouse source, then rerun Stitch.
Stream resources or selected-field details are missing	Stream observation is disabled or Stitch stream details were unavailable	Enable Observe streams and rerun the source.
Latest extraction/load timestamps are missing	History observation is disabled or Stitch history data is unavailable in the lookback window	Enable Observe extraction and load history and adjust History lookback days if needed.

Known Limitations

• Destination warehouse table resolution is supported for Snowflake and BigQuery only.

• Stitch does not own destination warehouse tables in Euno; the warehouse integration owns the physical table lifecycle.

• Source-system lineage is currently supported only for Stitch Salesforce sources.

• Row-count metrics, rolling success-rate metrics, and rolling error-count metrics are not currently supported.