> 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/site-installation/external-systems/configuring-ftcapi-trigger-strings-and-reflected-outputs.md).

# Configuring FTCAPI Trigger Strings and Reflected Outputs

### Introduction

The dispatch of trigger strings through the Gallagher Controller API (FTCAPI) can be configured for External System Items and DVR Cameras, and can be based on:

* Output state changes, and/or
* event and alarm occurrences

This procedure provides instructions on how to configure trigger strings and/or reflected outputs for an External System Item or DVR Camera. The example used here is for a DVR Camera.

### Procedure

1. Click **Configure** from the menu bar, then **External Systems**.

   The **External Systems** List Window opens (in [tree view](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/list-windows/tree-view.md)).
2. **Right click** on the appropriate External System Item or DVR Camera.
3. Do you want to configure FTCAPI strings that will be triggered by Output switching?

   If **yes**, go to Step 4.

   If **no**, go to Step 12.
4. Click the **Trigger -- Outputs** tab.

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

   This screen allows Outputs to be associated with the External System Item or DVR Camera, used to group and identify the outbound strings.
5. Open the **Hardware** List Window, and drag and drop the Output(s) required onto this screen, and click **Apply**.
6. Open the property pages for the Output(s) from the previous step.
7. Click the **Messages** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-6eb596f0d77122ce4bdb382e1b0ce044ffbf9cd0%2Foutputs_messagestab.png?alt=media)
8. In the **Controller API strings** section of this screen, enter the definition of one API Output string for each state, (i.e. **On** and **Off** ) of the Output.

   **Note:** The On and Off strings can include control characters to support ASCII text plug-ins.
9. Click **Apply**.
10. Repeat Steps 7 - 9 for each Output associated with the External System Item or DVR Camera.
11. Do you want to configure FTCAPI Strings that will be triggered by Events also?

    If **yes**, go to Step 12.

    If **no**, go to Step 19.
12. Click the **Trigger -- Events** tab.

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

    This screen allows you to define a trigger string for the External System Item or DVR Camera, that is dispatched out of the API on the activation of an Action Plan.
13. Enter a string into the grid.

    This is achieved by typing in text and selecting the appropriate 'Insertable Fields', (i.e. **Event details** and **Control characters** ), from the drop-down lists where necessary, and clicking the applicable **Insert** button.

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

    **Notes:**

    * The string is limited to 100 characters.
    * The Insertable fields represent entities that can be named within Command Centre, (e.g. ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-d6268b0d1046590c172a16e799219e927e88e150%2F%5Bch%5Dstring.png?alt=media) represents a cardholders name, and ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-7adb0557f3bbcc244eb580a2f71079c09e1f8863%2F%5Bes%5Dstring.png?alt=media) represents a Door), and control characters, (e.g. carriage return, line feed, etc.).
14. Click **Apply**.
15. Open the Action Plan you want assign the External System Item or DVR Camera to as a trigger.
16. Click the appropriate State tab, (i.e. **Armed**, **Disarmed**, **User 1** or **User 2** ).

    ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-aa90d5c7fb0c9c6cbe613519df10b76ebb9c8210%2Fdvr_actionplan_trigger.png?alt=media)
17. Drag and drop the External System Item or DVR Camera into the **Cameras, Macros, and External System Items** grid.

    When this Action Plan is activated, the trigger string will be dispatched.
18. Click **OK**.

    The Action Plan screen closes.
19. The FTCAPI is able to reflect the state of Outputs (with the support of inversion), based on the External System Item’s or DVR Camera’s status values submitted through the API to Command Centre.

    Do you want to configure reflected outputs for this External System Item or DVR Camera?

    If **yes**, go to Step 20.

    If **no**, go to Step 22.

    Click the **Reflected Outputs** tab of the External System Item or DVR Camera.

    ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-66a702f673499f3750a4291335dd4f0bbc65063f%2Fdvrcamera_reflectedoutputstab.png?alt=media)
20. Drag and drop the Outputs required into the appropriate grids on this screen.
21. Click **OK** to exit and save your changes.

    Click **Cancel** to exit without saving your changes.

    Click **Apply** to save your changes and stay in this window.

### Result

Trigger strings have been configured for the External System Item or DVR Camera.


---

# 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/site-installation/external-systems/configuring-ftcapi-trigger-strings-and-reflected-outputs.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.
