# 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="triggers/tcp-connectivity" %}
[tcp-connectivity](https://docs.bolt.observer/readme/liquidops/integrations/triggers/tcp-connectivity)
{% endcontent-ref %}

{% content-ref url="triggers/tor-connectivity" %}
[tor-connectivity](https://docs.bolt.observer/readme/liquidops/integrations/triggers/tor-connectivity)
{% endcontent-ref %}

{% content-ref url="triggers/lightning-connectivity" %}
[lightning-connectivity](https://docs.bolt.observer/readme/liquidops/integrations/triggers/lightning-connectivity)
{% endcontent-ref %}

### Node checks

{% content-ref url="triggers/sync-to-graph" %}
[sync-to-graph](https://docs.bolt.observer/readme/liquidops/integrations/triggers/sync-to-graph)
{% endcontent-ref %}

{% content-ref url="triggers/sync-to-chain" %}
[sync-to-chain](https://docs.bolt.observer/readme/liquidops/integrations/triggers/sync-to-chain)
{% endcontent-ref %}

### Liquidity checks

{% content-ref url="triggers/channel-balance" %}
[channel-balance](https://docs.bolt.observer/readme/liquidops/integrations/triggers/channel-balance)
{% endcontent-ref %}

{% content-ref url="triggers/node-balance" %}
[node-balance](https://docs.bolt.observer/readme/liquidops/integrations/triggers/node-balance)
{% endcontent-ref %}

{% content-ref url="triggers/onchain-balance" %}
[onchain-balance](https://docs.bolt.observer/readme/liquidops/integrations/triggers/onchain-balance)
{% endcontent-ref %}

{% content-ref url="triggers/channel-open" %}
[channel-open](https://docs.bolt.observer/readme/liquidops/integrations/triggers/channel-open)
{% endcontent-ref %}

{% content-ref url="triggers/channel-close" %}
[channel-close](https://docs.bolt.observer/readme/liquidops/integrations/triggers/channel-close)
{% endcontent-ref %}

{% content-ref url="triggers/inactivity" %}
[inactivity](https://docs.bolt.observer/readme/liquidops/integrations/triggers/inactivity)
{% endcontent-ref %}


---

# Agent Instructions: 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:

```
GET https://docs.bolt.observer/readme/liquidops/integrations/triggers.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.