Triggers

A trigger is the first step of a workflow. It decides what starts a run and what the workflow receives as its input. You add a trigger like any other step, from Components in the Triggers category. Each trigger has its own reference page, linked below.

Start from a chat#

• Chat Input receives what a user types in the chat. It is the trigger behind the playground, a chatbot and the API.
• Chat Opened fires when a chat window opens, before the user sends anything. Use it for a greeting.
• Chat Hook fires when the web page that hosts your chatbot calls sendHook() through the FlowHunt JavaScript API.
• Session Closed fires when a chat session expires after a period of inactivity. In the Run tab you can fire it by hand with Close Session Now.
• Search On Type receives the phrase a visitor types in a commerce search bar.

Start from a form, a webhook or a schedule#

• Webhook runs when another system sends a POST or GET request to the workflow’s webhook URL. The step shows the URL with a copy button.
• Form Submission runs when someone submits a form and passes the form data on.
• Scheduled Task runs on a timetable. See Schedules.

Start from an app#

These triggers react to something that happens in a connected account.

The GitHub, Jira, Zendesk, Slack and Google Calendar triggers need the matching integration. If it is missing, FlowHunt asks you to connect it when you add the step. See Connecting accounts.

Plans#

Chat Input, Chat Opened, Chat Hook, Search On Type, Webhook and Scheduled Task are available on every plan. The form, session and app triggers need a Trial, Pro, Agency or Enterprise plan. On other plans, adding one is refused with a message that the component can only be used with certain plans.

When triggers go live#

Chat in the Run tab tests your draft. Triggers that run without you, such as a webhook, a schedule or an email, run the published version. Publish the workflow before you rely on them, and publish again after you change a trigger. See Publishing and versions.