3 min read
Trigger Viktor from real-time events
Have Viktor react the moment something happens, like a message in a channel, a webhook from another tool, or activity in a connected app.
Scheduled tasks run on a timetable you set. Event triggers are the other half: they start work the moment something happens, so Viktor can react in real time instead of waiting for the next scheduled run. Event triggers work in both Slack and Microsoft Teams workspaces, and in app chat.
What can trigger Viktor
- Channel activity: new messages in a Slack or Teams channel you can read. Example: triage every message posted in your support channel.
- Incoming webhooks: Viktor gives you a webhook URL and a one-time setup link. Any tool that can send a webhook (forms, CRMs, payment tools, CI systems) can start work the instant it fires.
- Connected apps: events from apps you've connected, such as a deal being won in your CRM. Some app triggers are checked on a schedule; Gmail triggers can take up to 15 minutes to fire.
- Email: only in workspaces that still have a legacy Viktor email inbox. New workspaces don't have one; connect Gmail or Outlook as an app instead.
Set up a trigger: just ask
There's nothing to configure by hand. Describe what you want in a message to Viktor. He checks for existing triggers so he doesn't create a duplicate, sets it up, test-fires it, and shows you the result:
- "Whenever someone posts in #support, summarize the issue and suggest a reply."
- "Give me a webhook URL. When our signup form fires it, enrich the lead and post it to #sales."
- "When a HubSpot deal is won, post a summary in #sales."
If the tool isn't connected yet, connect it first.
For a webhook, open the setup link, select Reveal credential, and copy the URL and signing secret into the other tool. The link works once and expires after 30 minutes; ask Viktor for a new one if you need it.
See and manage your triggers
Open Tasks and choose Event handlers. You can pause, resume, or delete each one there, and see the last error if one failed. You can also ask Viktor in chat to list, pause, change, or delete them.
Event trigger or scheduled task?
| Use a scheduled task when… | Use an event trigger when… |
|---|---|
| Work happens on a rhythm, like daily digests or weekly reports | Every event needs a response the moment it happens |
| You want to batch many items into one run (cheaper than reacting one by one) | Another tool pushes webhooks and you want zero delay |
| Checking periodically is good enough | Waiting for the next scheduled run is too slow |
They combine well: a trigger for instant reactions, a scheduled task to sweep up the rest. To set up the scheduled kind, see Schedule a recurring task.
Good to know
- Each run started by a trigger uses credits like any other task. See How credits work.
- A Slack or Teams listener belongs to the person who created it, and only covers channels that person can read.
- If an app trigger stops firing, see Integration problems or Reconnect an integration.
Questions, or a trigger that isn't firing? Contact us at support@viktor.com.