> For the complete documentation index, see [llms.txt](https://docs.euno.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.euno.ai/sources/transformation-etl/stitch-integration/stitch-integration-discovered-resources.md). # Stitch Integration Discovered Resources The Euno-Stitch integration discovers the following resources: * The Stitch account * Stitch sources * Stitch streams * Warehouse tables referenced by selected Stitch streams Supported destination services for Stitch-to-warehouse table links: **Snowflake**, **BigQuery**, **SQL Server**, and **Databricks**. {% hint style="info" %} Stitch warehouse tables are observed by reference. A selected Stitch stream can define that it writes a table, but the corresponding Snowflake, BigQuery, SQL Server, or Databricks integration remains the source of truth for the physical table lifecycle and rich table metadata. {% endhint %} ## Stitch Account A Stitch account represents the client/account scope available to the configured Stitch API token. Destination configuration is summarized on the account for table resolution and support; individual destinations are not data-model resources. | Property | Value | | --------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `name` | Stitch client/account ID | | `type` | `stitch_account` | | `native_id` | Stitch client/account ID | | `container_type` | `pure_container` | | `stitch_destination_count` | Number of destinations configured in the Stitch account | | `stitch_active_destination_count` | Number of active destinations configured in the Stitch account | | `stitch_destination_types` | Sorted destination types found in the Stitch account | | `stitch_destination_context` | Minimal account details for each destination, including its name, type, active state, sorted list of mapped source IDs, and allow-listed non-secret Stitch-reported pre-mapping identifiers | | `external_links` | Link to the account in Stitch | | `native_raw_object` | Recursively redacted destination payloads retained as account context | The account sidepane shows at most five destination summaries and the number of additional destinations. Resolver details are limited to the Snowflake or SQL Server host/database and the BigQuery project identifier reported by Stitch. These values help support and **Database mapping** configuration; they are not canonical post-mapping warehouse identities. The crawler resolves tables from each run's current typed destination payload, not from stored account context or graph state. Databricks JDBC URLs and their derived hostnames are not included in account context. ## Stitch Source A Stitch source represents a Stitch integration that extracts data from an upstream SaaS, database, or other source system. | Property | Value | | ----------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------ | | `name` | Source display name in Stitch, when available; otherwise the Stitch source name | | `type` | `stitch_source` | | `subtype` | Source type reported by Stitch | | `native_id` | Source ID in the Stitch account | | `parent_container` | URI of the Stitch account that contains this source | | `parent_container_name` | Stitch client/account ID | | `is_active` | `true` when the Stitch source is active; otherwise `false` | | `stitch_source_type` | Stitch source type, such as `platform.salesforce` | | `created_at` | Source creation timestamp, when Stitch provides it | | `updated_at` | Source update timestamp, when Stitch provides it | | `description` | Source description, when available | | `external_links` | Link to the source in Stitch, when available | | `stitch_schedule_interval` | Replication schedule interval, when Stitch provides it | | `stitch_schedule_unit` | Replication schedule unit, when Stitch provides it | | `stitch_replication_schedule_type` | Replication schedule type, when Stitch provides it | | `stitch_last_successful_extraction` | Latest successful extraction timestamp in the configured lookback window, when history observation is enabled and Stitch provides the data | | `stitch_last_successful_load` | Latest successful load timestamp in the configured lookback window, when history observation is enabled and Stitch provides the data | | `native_raw_object` | Redacted Stitch source payload | Sources group their child streams and retain connection-level schedule and status details. A source does not define warehouse tables; each selected stream owns its own table mapping. ## Stitch Stream A Stitch stream represents stream or table metadata inside a Stitch source. Euno observes streams when **Observe streams and warehouse lineage** is enabled, which is the default, and Stitch stream metadata is available. | Property | Value | | --------------------------- | ---------------------------------------------------------------------------------------- | | `name` | Stream name in Stitch | | `type` | `stitch_stream` | | `subtype` | Replication method, when Stitch provides it | | `native_id` | Stream ID in Stitch | | `parent_container` | URI of the Stitch source that contains this stream | | `parent_container_name` | Name of the Stitch source that contains this stream | | `is_active` | `true` when the Stitch stream is active; otherwise `false` | | `stitch_is_selected` | `true` when the stream is selected for replication in Stitch | | `stitch_tap_stream_id` | Tap stream ID reported by Stitch, when available | | `stitch_replication_method` | Replication method reported by Stitch, when available | | `stitch_replication_key` | Replication key reported by Stitch, when available | | `stitch_selected_fields` | Selected field names, when Stitch stream detail is available | | `defines` | Warehouse table URIs written by this selected stream, when table resolution is available | | `native_raw_object` | Redacted Stitch stream payload | ## Destination Tables (by reference) For each selected Stitch stream with a supported destination, Euno may observe a non-authoritative `table` reference so it can resolve stream-to-table **defines** relationships before or alongside the warehouse integration. | Property | Value | | --------------------- | ----------------------------------------------------------------------------------------- | | `name` | Destination table name | | `type` | `table` | | `subtype` | `base_table` | | `database_schema` | Destination schema or dataset name derived from the Stitch source name | | `database_database` | Snowflake or SQL Server database name, BigQuery project identifier, or Databricks catalog | | `database_technology` | `snowflake`, `bigquery`, `mssql`, or `databricks` | | `platform_uri_prefix` | Warehouse platform URI prefix used by Euno | | `utl` | Euno URI for the destination warehouse table | Stitch does not write the shared, single-valued `defined_by` property on destination tables. The exact Stitch provenance is represented by the stream's **defines** relationship and the table's inverse **has definer** relationship, which can represent every current defining stream. ### Destination Table Resolution Euno resolves Stitch destination tables for supported destination types: * **Snowflake**: Euno uses the Stitch destination host and database. If Stitch and Euno use different identifiers for the same Snowflake account, configure **Database mapping** from the Stitch host to the Snowflake identifier Euno observes. * **BigQuery**: Euno uses the Stitch `project_id`. The official Stitch destination type is `bigquery_v2`; the compatibility types `bigquery` and `big_query` use the same identity contract. If Stitch and Euno use different project identifiers, configure **Database mapping** from the Stitch project ID to the BigQuery project ID Euno observes. * **SQL Server**: Euno uses the Stitch destination host and database and applies the same canonical hostname rules as the native SQL Server integration. If Stitch and Euno use different hostnames, configure **Database mapping** from the Stitch host to the SQL Server hostname Euno observes. * **Databricks**: Euno parses only the hostname from the Stitch `jdbc:spark://[:port]...` URL. **Database mapping** is required from that hostname to `databricks..`. Euno does not infer the catalog from the JDBC path or a default catalog. Snowflake and SQL Server host keys and BigQuery project-ID keys must exactly match the identifiers reported by Stitch. Only Databricks mapping-key lookup trims and compares keys without case; multiple keys that normalize to the selected JDBC hostname fail as ambiguous. Stitch always constructs BigQuery references with the default `bigquery` URI prefix, and its **Database mapping** changes only the project identifier. A native BigQuery source configured with a custom `uri_base` emits a different URI prefix and therefore does not automatically join those Stitch references. This is a limitation of the pre-existing configurable BigQuery identity, not a change to the native crawler's output. Other destination types can appear in Stitch account context, but destination warehouse table references are not currently supported for them. A selected stream with no mapped destinations remains visible without a **defines** relationship. If a mapped destination is missing from the API response, or a supported destination has missing, blank, incorrectly typed, or malformed Stitch-reported resolver input, the run fails instead of treating the incomplete result as proof that an existing table mapping was removed. Non-string **Database mapping** keys and values are rejected when configuration is validated. Crawl-time mapping failures are limited to a blank used mapping, a missing or ambiguous required Databricks mapping, or a semantically invalid mapped string. Failure details contain safe source, stream, destination, type, reason, and remediation information; credential-bearing resolver or mapping values are not included. ## Relationships | Source type(s) | Relationship | Target type(s) | Notes | | ---------------- | -------------------- | ------------------- | ---------------------------------------------------------------------------------------------------------------------------- | | `stitch_account` | has child | `stitch_source` | Sources belong to the Stitch account available to the configured API token | | `stitch_source` | has child | `stitch_stream` | Streams belong to their Stitch source when stream observation is enabled | | `stitch_stream` | defines | `table` | Destination warehouse tables written by selected streams | | `table` | has definer | `stitch_stream` | Inverse of **defines**; the stream is the mapping owner, while the warehouse integration owns the physical table lifecycle | | `table` | has upstream | `salesforce_object` | Only for Stitch Salesforce sources when Salesforce metadata and authoritative warehouse table metadata are present | | `column` | has upstream\_fields | `salesforce_field` | Only when Stitch selected-field evidence, Salesforce field metadata, and authoritative warehouse column metadata are present | {% hint style="info" %} Definition relationships answer which selected Stitch stream writes a warehouse table. They use **defines** and **has definer**. Dependency lineage answers which upstream data object a downstream table or column depends on. Stitch dependency lineage is currently documented only for Salesforce sources, where replicated warehouse tables can have upstream Salesforce objects and replicated warehouse columns can have upstream Salesforce fields. {% endhint %} ## Salesforce Lineage For Stitch Salesforce sources, Euno can connect replicated warehouse tables back to Salesforce objects and fields. This lineage requires: * A Stitch source whose source type is Salesforce. * **Observe streams and warehouse lineage** enabled for the Stitch source, which is the default. * Selected Stitch streams with destination table links. * A Salesforce source in Euno that has crawled the Salesforce org metadata. * A Snowflake, BigQuery, SQL Server, or Databricks source in Euno that has crawled the destination tables and columns. * A destination table name that matches the Salesforce object represented by the Stitch stream. * Selected-field evidence from Stitch for column-level lineage. When all required evidence is present, Euno can show: * `table` **has upstream** `salesforce_object` * `column` **has upstream\_fields** `salesforce_field` 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. ## Known Limitations * Destination warehouse table resolution is supported for Snowflake, BigQuery, SQL Server, and Databricks. Other Stitch destination types do not create table links. * Stitch destinations are account context, not separate data-model resources. * Stitch does not create or own `database`, `schema`, or `column` placeholders for the destination warehouse. * Stitch does not own destination warehouse table lifecycle in Euno. * Databricks destination resolution requires an explicit JDBC-hostname-to-warehouse-and-catalog mapping. * Stitch BigQuery references always use the `bigquery` URI prefix and do not automatically join a native BigQuery source configured with a custom `uri_base`. * 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. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.euno.ai/sources/transformation-etl/stitch-integration/stitch-integration-discovered-resources.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.