Skip to main content
Many integration nodes can act as triggers. Instead of performing an action, the node listens for an event in the connected service (a new Slack message, a HubSpot contact, a GitHub push) and starts a run each time one arrives.

​
Select a trigger operation

1

Add the integration node

Add the service’s node (for example Slack) and connect your credential.
2

Pick a trigger operation

Open the node’s operation picker. Trigger operations are grouped under Triggers at the top of the list. Select one, such as On Channel Message.
3

Configure and connect

Fill in any event filters (for example, which channel or repository to watch) and connect the node to your downstream steps. NoClick registers the event subscription with the provider automatically, and the workflow runs on each matching event.
Registration happens as soon as the trigger is part of your workflow, whether you added the node yourself or the AI builder did. You do not have to open the node for it to start listening. Slack, HubSpot, and Discord triggers show a readonly Status field naming what they are listening to, and a registration that failed, or never happened, is repaired on its own within a day. A trigger that still has required fields to fill in is not registered yet, whoever is filling them: registration waits until the configuration can run, and happens on the edit that completes it. Changing the node to a different operation, or to one that is not a trigger, removes the registration again.

​
Supported events

Instant push events arrive via webhook subscriptions that NoClick creates for you. Google Drive, Google Calendar, and Jira subscriptions expire periodically and are renewed automatically. Scheduled poll triggers cover services without a usable push API: you pick a schedule on the node (default: every 5 minutes) and each poll fires the workflow only for items it has not seen before. A poll that finds no new items runs nothing downstream, so connected nodes and AI agents stay idle until there is something new. That applies to a run you start yourself as well, so use a node’s mocked output to test the steps after a trigger when there is no new data.

​
What counts as new

A poll trigger takes its starting point the moment it is registered, so anything that arrives after you finish setting it up fires a run, including a test entry you submit right away. Everything already in the form, sheet, or mailbox at that point counts as history and is left alone. Pointing the trigger at something else later, a different form or spreadsheet, takes a fresh starting point for the new resource rather than firing for its entire backlog. Edits that do not change what the trigger watches leave its history untouched. Running the workflow yourself polls the same way a scheduled run does, and anything it finds is delivered to the nodes downstream, including an AI agent wired to the trigger.
Most subscriptions register automatically. Two exceptions show a webhook URL on the node to paste into the provider yourself: Resend (add it as an endpoint at resend.com/webhooks) and WhatsApp Cloud API credentials (configure it in the Meta Developer Console; QR-paired WhatsApp registers automatically).

​
App events and AI agents

Wire the trigger node directly into an AI agent and each event is delivered as part of the agent’s turn. One node cannot both fire runs and provide agent tools: to build an agent that listens and replies in the same service, use two nodes, one with the trigger operation and one wired in as a tool provider. See Channel agents.