The first phase of every Stitch replication job is called Extraction. During Extraction, Stitch completes the following:

  1. Check for changes to the structure of your data, including the addition of new tables and columns.
  2. Query for data according to the integration’s replication settings. This includes the tables and fields you set to replicate and the Replication Methods used by those tables.
  3. Extract the appropriate data, if any.

The Extractions tab — accessed by clicking into the integration from the Stitch Dashboard — provides detail about the extraction portion of the replication process for a given integration.

Extraction tab availability

The features in the Extractions tab may not be available for some integrations.

Generally, these features are available for integrations powered by Singer taps. As integrations are converted to the Singer system, the features listed below will be made available.

Note: Integrations that send data directly and continuously to Stitch will not have these features. This applies to Import API and webhook-based integrations.

Extraction tab features

The Extractions tab contains the following features:

  • Start/stop an extraction - All integrations run on a schedule but you can also start and stop extractions on demand. This is useful for testing configuration changes or recovering from an error. Refer to the Start and stop extraction jobs documentation for more info.

  • Extraction logs - Extraction logs provide detail about the extraction portion of the replication process for an integration. Refer to the Extraction logs documentation for more info.

Questions? Feedback?

Did this article help? If you have questions or feedback, feel free to submit a pull request with your suggestions, open an issue on GitHub, or reach out to us.