Documentation

An event trigger starts work when something happens, instead of on a clock: a deal is won in your CRM, a webhook arrives, or a message is posted in a channel. Viktor sets it up for you in chat.

Event triggers are best when a reaction has to be quick. If checking every so often is good enough, a scheduled task is usually cheaper, and Viktor may suggest one: each event can start its own AI run.

How it works

An automation has two parts:

• A source that receives events. It can be a trigger from a connected app, a raw webhook from another service, or, when that chat platform is connected, a Slack or Microsoft Teams event.
• One or more handlers that run for each event. An agent handler runs Viktor with your instructions. A script handler runs a Python script, which suits high-volume events.

Viktor test-fires a new automation before telling you it is live. By default the test captures chat messages instead of sending them and blocks writes to your integrations.

Set up an event trigger

1. Ask Viktor in Slack, Microsoft Teams or the web app chat. For example: "When a HubSpot deal is won, post a summary in #sales."
2. If the tool isn't connected yet, connect it first.
3. Viktor checks existing triggers so he doesn't create a duplicate, then creates the source and the handler.
4. Viktor test-fires it and shows you the result. Confirm before he runs a test with real side effects.

Connect a raw webhook

For a service that sends webhooks you configure yourself:

1. Viktor gives you an inbound URL and a one-time setup link.
2. Open the setup link in your browser and select Reveal credential. The page shows the signing secret. Viktor never sees it.
3. Copy the URL and secret into the other service's webhook settings.

The setup link works once and expires after 30 minutes. If it has expired, or you lose the secret, ask Viktor for a new one.

If the other service can't sign its requests, Viktor can set up the webhook with a shared token instead. The setup page then shows a ready-to-paste URL that contains the token. Requests to the plain URL without the token are rejected.

Slack and Teams events

• A Slack or Teams listener belongs to the person who created it. Only they can see it, manage it or add handlers to it. A teammate who wants the same automation creates their own.
• You can't create a listener on a channel you can't read. A listener on all channels skips events from channels its owner can't read.
• In Microsoft Teams, supported events are new, edited and deleted messages, and meeting start and end for meetings where Viktor is installed. Reactions and membership changes are not supported. A new or changed Teams listener can take up to two minutes to start receiving events.

App triggers

Gmail triggers are checked by the provider on a schedule and can take up to 15 minutes to fire.

Manage event handlers

1. Open Tasks and choose Event handlers from the scope list. It is shown in the list view, not the calendar.
2. Pause or resume a handler. You see "Event handler paused" or "Event handler resumed".
3. To remove one, expand it, select Delete, and confirm with Delete. You see "Event handler deleted". The trigger source and any other handlers on it stay active.
4. A handler that failed shows its last error under Handler error.

You can also ask Viktor in chat to pause, resume, change or delete an automation.

Workspace admins can see event handler credit use in Usage → Tasks, where handlers show "On event" as their frequency.

Limits

• A script handler run is stopped after 10 minutes. After three timed-out runs in a row, the handler is paused automatically.
• If you lose access to the integration a trigger uses, your handlers on it stop. They start again by themselves once you are added back to that integration's access list.
• A workspace can hold up to 240 handler runs waiting to start. Past that, new events are refused until the backlog drains, and a single source accepts up to 240 events a minute.
• Each agent handler run uses credits. Script handlers suit high event volume.

Common problems

• The setup link says "Setup link not found" or "Setup link expired". It was already used or is older than 30 minutes. Ask Viktor for a fresh setup link.
• A handler was paused and you didn't pause it. It timed out three runs in a row. Ask Viktor to fix the script before resuming it.
• Handlers stopped after an integration change. You were removed from the integration's access list. Ask whoever connected the integration to add you back; don't delete and recreate the handlers.
• A Gmail automation reacts late. Gmail triggers can take up to 15 minutes.
• An app trigger stopped firing. Ask Viktor to check the trigger. He can see its last event and errors, and tell you whether the app needs reconnecting. See also integration problems.

Related

• Scheduled tasks
• Connect your tools
• Manage integrations
• Integration permissions