---
title: "Locate Connector Function usage across Tulip"
slug: "where-used-connector-connector-functions"
updated: 2026-03-30T09:27:42Z
published: 2026-03-30T09:27:42Z
---

> ## Documentation Index
> Fetch the complete documentation index at: https://support.tulip.co/llms.txt
> Use this file to discover all available pages before exploring further.

# Locate Connector Function usage across Tulip

**In this article, you will learn how to:**

- **Locate** where your connectors or connector functions are used in Tulip.
- **Identify** which specific apps and automations utilize a connector function.
- **Find** triggers using connector functions to verify their configuration.

---

## Locate where a connector is being used

If you have recently updated a connector environment, you may want to see where that connector is being used within Tulip.

1. On the **Connectors** page, click anywhere on a connector’s row (except for the name) to open the side panel.
2. Scroll down to view all development apps and automations currently using that connector.

![Image](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/image-A4Y0TGQU.png)

## Locate where a connector function is being used

1. Select a connector from the **Connectors** page.
2. Click anywhere on a connector function’s row (except for the name) to open the side panel.
3. Scroll down to see all development apps and automations that utilize that specific function.

![Image](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/image-78OARNFO.png)

## Locate which trigger is using a connector function

1. On the **Apps page**, click on an app list to navigate to the **Resource Modal** for that app. In this view, you can see which connectors are used in the development version of that app.

You can also access the Resource Modal by clicking **View Resources Used** in the **Versions** tab of the **App Overview** page.

1. When you click on a connector function's name, you will view the list of triggers in that app that use the connector function.
2. Click on a trigger name to navigate to that trigger in a new tab.

![r356 connector function where used](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/r356%20connector%20function%20where%20used.gif)

## Locate which trigger is using a connector function in an older App Version

1. To see the breakdown of connector functions used in a different version of an app, navigate to the **Versions** tab on the **App Overview** page.
2. Click the **three-dot-menu** for an app version and then click **"View resources used."**

![Image](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/image-V9PMMA5T.png)

## Locate Snapshots in an older App Version

1. To see the breakdown of connector functions used in a different version of an app, navigate to the **Versions** tab on the **App Overview** page.
2. Click the **three-dot-menu** for an app version and then click **"View resources used."**
3. Click on the name of the connector function in the modal.

![Image](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/image-JS1OPCE6.png)

## Locate Where your Snapshots are Used

1. To see where your old snapshot configurations are used in iterate over to the connector function.
2. Under "View History" click on a snapshot configuration.
3. Click "Where Used".

![Image](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/image-JC6W6ITS.png) ![Image](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/image-F7M9V57O.png)

## Further reading

- [Run a connector function in a trigger](https://support.tulip.co/docs/run-a-connector-function-in-a-trigger)
- [Connectors](https://support.tulip.co/docs/connectors)

---

Did you find what you were looking for?

You can also head to [community.tulip.co](https://community.tulip.co/?utm_source=intercom&utm_medium=article-link&utm_campaign=all) to post your question or see if others have solved a similar topic!