> For the complete documentation index, see [llms.txt](https://docs.bolt.observer/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bolt.observer/readme/liquidops/integrations/triggers.md).

# Triggers

**TCP**Basic tcp check to see if your node is reachable on port 9735 over internet. Supports ipv4 and ipv6.Triggers are events or conditions that initiate a workflow. They can be based on various parameters, such as network events (e.g., connectivity, channel openings or closings, synchronization with the chain) or liquidity events (e.g., node balance, channel balance, and on-chain funds). The user sets up triggers and defines the conditions under which a workflow should be executed.

### Reachability checks

You can use any combination of checks for your node,limited only by connectivity options you have - ipv4, ipv6, tor.

{% content-ref url="/pages/TTuGCKGOCfIzMb53fte4" %}
[TCP connectivity](/readme/liquidops/integrations/triggers/tcp-connectivity.md)
{% endcontent-ref %}

{% content-ref url="/pages/UKnhKJvMtqq1vMb3WeBz" %}
[Tor connectivity](/readme/liquidops/integrations/triggers/tor-connectivity.md)
{% endcontent-ref %}

{% content-ref url="/pages/De5jJf8IskwsOKB3GdIR" %}
[Lightning Connectivity](/readme/liquidops/integrations/triggers/lightning-connectivity.md)
{% endcontent-ref %}

### Node checks

{% content-ref url="/pages/ZIc4D1t8utZkB8D41kGq" %}
[Sync to graph](/readme/liquidops/integrations/triggers/sync-to-graph.md)
{% endcontent-ref %}

{% content-ref url="/pages/GRMHVetR61nb5dH96K4H" %}
[Sync to chain](/readme/liquidops/integrations/triggers/sync-to-chain.md)
{% endcontent-ref %}

### Liquidity checks

{% content-ref url="/pages/KbtcIcbeW72qBRsyzSPt" %}
[Channel balance](/readme/liquidops/integrations/triggers/channel-balance.md)
{% endcontent-ref %}

{% content-ref url="/pages/vHoRPfgbB3RctU3dqF4H" %}
[Node balance](/readme/liquidops/integrations/triggers/node-balance.md)
{% endcontent-ref %}

{% content-ref url="/pages/oCUivtrpRYx8706VScwx" %}
[Onchain balance](/readme/liquidops/integrations/triggers/onchain-balance.md)
{% endcontent-ref %}

{% content-ref url="/pages/Fhl5WH41bNYukDbevH7e" %}
[Channel open](/readme/liquidops/integrations/triggers/channel-open.md)
{% endcontent-ref %}

{% content-ref url="/pages/5J8r9EOiNJDNKQsgPENl" %}
[Channel close](/readme/liquidops/integrations/triggers/channel-close.md)
{% endcontent-ref %}

{% content-ref url="/pages/xvrSezH7a0rzpkhoGPvO" %}
[Inactivity](/readme/liquidops/integrations/triggers/inactivity.md)
{% endcontent-ref %}


---

# 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.bolt.observer/readme/liquidops/integrations/triggers.md?ask=<question>&goal=<endgoal>
```

`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.