Node reference

Trigger nodes

A trigger starts the workflow, and decides what kind of thing the workflow is. Flux ships thirteen. A workflow can carry several, which is how one piece of logic answers on every channel at once.

All thirteen

TriggerFires whenPairs with
UISomeone uses the chat interface Flux generates for youChat response
APIYour system calls the workflow's endpointWebhook response
IntervalA schedule elapsesAny response, or none
Session EndA session finishesClean-up, logging, follow-up
SpreadsheetA row is read from an uploaded fileAny response
Cognify SheetA row arrives from a Cognify panelAny response
WhatsAppA WhatsApp message arrivesWhatsApp response
ViberA Viber message arrivesViber response
TelegramA Telegram message arrivesTelegram response
FacebookA Facebook message arrivesFacebook response
InstagramAn Instagram message arrivesInstagram response
Inbound ChatA chat arrives from CognifyOutbound Chat
Inbound Chat (Generic)A chat arrives from any system you chooseOutbound Chat (Generic)
Match the pair. Almost every trigger has a matching response node. A WhatsApp trigger with a Chat response will run, but the customer will never see the answer — it went to the wrong place.

UI trigger

Flux generates a chat interface for the workflow, so you can talk to your agent without connecting any channel. It is the right starting point for a first build, and stays useful afterwards as the fastest way to test a change.

The UI trigger gives you a chat interface with no setup.

API trigger

Turns the workflow into an endpoint your own systems can call. Pair it with a Webhook response node to return a result to the caller. Together they make a workflow behave like any other HTTP service — see Web and API channels.

Interval trigger

Runs on a schedule. The interval is a number plus a unit — second, minute, hour, day, week, month or year.

This is what turns Flux into a job runner: fetch a feed every hour and summarise it, check an API every morning and alert on a change, send a digest every Friday.

Every interval firing is a billable trigger, and anything downstream of it consumes tokens. A one-minute interval is 1,440 runs a day. Start with a longer interval than you think you need and shorten it once you have seen the cost.

Session End trigger

Fires when a session finishes rather than when one starts. Use it for the work that belongs at the end of a conversation — writing a summary back to a record, logging the outcome, scheduling a follow-up.

Spreadsheet trigger

Reads an uploaded file and fires per row, which turns a workflow into a bulk processor. Enrich a list of companies, classify a backlog of tickets, send a personalised message to each row.

Cognify Sheet trigger

The same idea, but the rows come from a Cognify panel rather than a file. See Working with Cognify.

The messaging triggers

WhatsApp, Viber, Telegram, Facebook and Instagram each have a trigger that fires on an incoming message from that channel. They need the channel connected and a credential stored first — see Messaging channels.

Inbound Chat, and its generic twin

Several nodes come in a Cognify flavour and a Generic flavour:

Inbound Chat

The conversation arrives from Cognify, and the record it belongs to is already there.

Inbound Chat (Generic)

The conversation arrives from any system you wire up. Use this when Flux is running behind something other than Cognify.

Several triggers, one workflow

Wire a WhatsApp trigger, a Telegram trigger and a UI trigger into the same AI node and you have one agent serving three channels. Give each its matching response node, and each customer is answered where they asked.

It also means one place to change the prompt when the answer needs to improve.