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.

​
Supported events

ServiceTrigger operationsDelivery
SlackOn Channel Message, On App Mention, On Reaction Added, On Member Joined Channel, On Channel Created, On File SharedInstant push
HubSpotOn Contact Created, On Contact Updated, On Contact Deleted, On Company Created, On Deal Created, On Deal Updated, On Ticket CreatedInstant push
GitHubOn Push, On Issue Comment, and granular issue, pull request, release, and star events (On Issue Opened, On Issue Closed, On Pull Request Opened, On Pull Request Merged, On Release Published, On Star Created, and more)Instant push
JiraOn Issue Created, On Issue Updated, On Issue Deleted, On Comment AddedInstant push
LinearOn Issue Created, On Issue Updated, On Issue Deleted, On Comment Created, On Comment Updated, On Comment Deleted, On Project Created, On Project Updated, On Project DeletedInstant push
DiscordOn Application Authorized, On Application Deauthorized, On Entitlement Create/Update/Delete, On Lobby Message Create/Update/Delete, On Game Direct Message Create/Update/DeleteInstant push
ShopifyOn Order Created, On Order Paid, On Order Fulfilled, On Order Cancelled, On Product Created, On Product Updated, On Customer CreatedInstant push
Google DriveOn Drive Change, On File Changed, On File Removed, On Folder Changed, On Folder RemovedInstant push
Google CalendarOn Calendar Event, On Event Created, On Event Updated, On Event Cancelled, On Event TentativeInstant push
Google SheetsOn New RowScheduled poll
Google FormsOn Form ResponseScheduled poll
GmailPoll for New EmailsScheduled poll
NotionOn Database ItemScheduled poll
TypeformOn New Form ResponseInstant push
TwilioOn Incoming SMSInstant push
TelegramReceive Webhook MessagesInstant push
WhatsAppReceive Message, Receive Status UpdateInstant push
InstantlyReceive Webhook EventsInstant push
ResendReceive Webhook EventsInstant push
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.
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.