> For the complete documentation index, see [llms.txt](https://help.security.gallagher.com/knowledge-hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/enterprise-data-interface/configuring-an-interface/adding-an-interface-to-a-sequence.md).

# Adding an interface to a sequence

### Introduction

**Note:** Functionality specific to adding an interface to a sequence is only available if your site is licensed to schedule interfaces.

When an interface has been added to an execution sequence and enabled, it will run according to the sequence without operator intervention.

**Notes:**

* An interface added to a sequence will run immediately after the completion of the previous interface in the sequence. If the previous interface failed to run, the next interface in the sequence will not be run, and so on.
* If an interface located midway in a sequence is run, the next interface in the sequence will run immediately after the completion of the previous interface in the sequence, and so on.
* When importing data from a source file, you will need to configure your third party application to provide the source file, in order for the sequenced interface to "pick-up" and import the source file. If an interface is sequenced to run and there is no source file, the interface will not run.
* When importing data from a database, if the interface is sequenced to run and the interface is unable to connect to the database server, the interface will not run.
* If an interface is sequenced to run from a database, the interface will process the records as present in the database, at that time.

### Procedure

1. Click the **Schedule** tab.

   This tab displays the schedule configured for this interface.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-36c4cb216686f5a80e2421170911049b83d18871%2Fscheduletab.png?alt=media)

   **Note:** If your site is not licensed to schedule interfaces this tab will be grayed out.
2. Check the **This integration runs in a sequence** checkbox.

   The Sequence tab displays below the Schedule tab.

   **Note**: This checkbox is disabled if the interface is the first interface in a sequence and all other interfaces belong to this sequence, (i.e. you cannot configure a sequence that is a continuous loop).
3. Select the interface that this interface will run after from the **Execute interface after** drop-down list.
4. To view the interfaces added to this sequence, click the **Sequence** tab. This diagram displays the flow structure of the sequence.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-bd15601a542adc45e106a1d96eb47906136d83e8%2Fsequencetab.png?alt=media)

   This table provides an explanation for each interface colour.

   <table><thead><tr><th width="132">Interface colour</th><th>Explanation</th></tr></thead><tbody><tr><td>Blue fill</td><td>The first interface in the sequence. This interface "kicks-off" the sequence.</td></tr><tr><td>Black outline</td><td>The current interface. The interface that is open.</td></tr><tr><td>Red outline</td><td>Represents an interface whose status is Incomplete, Disabled, Schedule-Expired or Not licensed.</td></tr><tr><td>Blue outline</td><td>Represents an interface whose status is Sequenced.</td></tr></tbody></table>


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/enterprise-data-interface/configuring-an-interface/adding-an-interface-to-a-sequence.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
